<skill-name>

Generate standardized SKILL.md packages with front-matter and directory structure.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/keith-mvs/ordinis --skill skill-name-keith-mvs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: <skill-name>
Source: https://github.com/keith-mvs/ordinis/tree/main/docs/knowledge-base/domains/skills/_template
Command: npx skills add https://github.com/keith-mvs/ordinis --skill skill-name-keith-mvs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides starter structure and standards for creating new skill packages under docs/knowledge-base/domains/skills, reducing setup time and ensuring consistency.

Core Features & Use Cases

  • Template Foundation: Includes a ready-made SKILL.md front matter and starter structure to guide new Skill creation.
  • Documentation Standards: Embeds guidance for references, assets, and scripts organization to streamline knowledge sharing.
  • Discovery & Reuse: Helps teams rapidly spin up new skills with consistent navigation and cross-linking practices.

Quick Start

Copy the Skill Package Template into a new folder under docs/knowledge-base/domains/skills/<your-skill>/, fill in SKILL.md with a real name/description, and add references/scripts/assets as needed.

Frequently Asked Questions about <skill-name>

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create standardized skill package documentation with consistent structure?

This Skill automates creation of standardized skill packages by generating a SKILL.md template with YAML front-matter, directory structure, and cross-linking patterns. It ensures consistent organization across references, assets, and scripts folders for modular, portable documentation workflows.

What's the best way to set up a knowledge-base skill package with proper naming and file conventions?

Use this Skill's template to establish kebab-case folder naming, snake_case data files, and relative linking standards. It provides ready-made front-matter and guidance for progressive disclosure and navigation across your docs/knowledge-base/domains/skills/ structure.

Can I reduce setup time when adding new skills to a documentation knowledge base?

Yes. Copy the Skill Package Template into a new folder, fill in SKILL.md metadata, and organize references, scripts, and assets following embedded standards. This eliminates repetitive configuration and ensures team-wide consistency.

How do I organize markdown documentation with YAML front-matter for a knowledge base?

This Skill defines front-matter structure, directory layout, and cross-linking patterns for markdown-based skill packages. It guides asset and reference organization to enable consistent navigation and modular versioning across your documentation.

What happens if I don't follow skill package standards when creating new documentation?

Without standards, teams face inconsistent folder structures, broken cross-links, and duplicated setup work. This Skill prevents those issues by embedding validation and conventions that ensure portable, discoverable, and maintainable skill packages.

Does this template work for team-based knowledge sharing across multiple skills?

Yes. The standardized template and relative-linking patterns enable rapid skill creation while maintaining consistent discovery paths and reusable navigation conventions across your entire knowledge-base domain.