<domain>-<object>

Provides a reusable SKILL.md template for authoring new agent skills.

1|1|Updated Jul 6, 2026
One-click install
npx skills add https://github.com/muhammaddadu/ai-skill-collection --skill domain-object-muhammaddadu
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: <domain>-<object>
Source: https://github.com/muhammaddadu/ai-skill-collection/tree/main/TEMPLATE
Command: npx skills add https://github.com/muhammaddadu/ai-skill-collection --skill domain-object-muhammaddadu

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Authoring new agent skills without a shared structure leads to inconsistent frontmatter, missing metadata, and skills that discovery tools cannot index. This template enforces a single convention for every skill in the portfolio. ## Core Features & Use Cases - Standardized Frontmatter: Defines required fields such as name, description, type, domain, and tested_date with inline guidance and length limits. - Structured Body Sections: Prescribes Purpose, Outputs, Prerequisites, Workflow, Pitfalls, and Next steps sections so every skill documents its contract. - Use Case: When adding a new skill to the SDLC portfolio, copy this template, fill in the placeholders, and the result passes the repository conventions enforced across all skill directories. ## Quick Start Copy the TEMPLATE SKILL.md into a new skill directory and replace each placeholder with the skill's name, description, workflow, and pitfalls.

Frequently Asked Questions about <domain>-<object>

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

FAQPage Schema
How do I create a new agent skill with SKILL.md?▼

Create a directory named in kebab-case, add a SKILL.md file with YAML frontmatter containing name and description, then write the workflow instructions in the Markdown body. Copying this template ensures all required sections are present.

What frontmatter fields are required in SKILL.md?▼

The name and description fields are mandatory for discovery. The template also defines type, domain, and tested_date, plus an optional requires field for version constraints on tools or SDKs.

How long should a skill description be?▼

The template targets 350 characters or fewer for the description, with a hard cap of 500 characters. The description should state the action, artifact, trigger phrases, and adjacent cases the skill does not handle.

When should skill details go into references files?▼

Route detail to references/ files when the SKILL.md body would exceed roughly 500 lines. The workflow section should include explicit pointers telling the reader which reference file covers each subtopic.

What are the limitations of using a skill template?▼

A template enforces structure but cannot validate content quality, so authors must still write accurate workflows and pitfalls. It also assumes the portfolio conventions, so teams with different tooling may need to adapt the frontmatter fields.