write-a-skill

Create standardized Skill Units with frontmatter and a three-step workflow.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/amodelandme/skill-tree-dotnet --skill write-a-skill-amodelandme
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: write-a-skill
Source: https://github.com/amodelandme/skill-tree-dotnet/tree/main/.claude/skills/write-a-skill
Command: npx skills add https://github.com/amodelandme/skill-tree-dotnet --skill write-a-skill-amodelandme

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a standardized approach to creating Skill Units by enforcing a consistent frontmatter-driven structure (name and description) and a reusable template, reducing ambiguity and onboarding time.

Core Features & Use Cases

  • Structured Skill Template: A ready-to-use skeleton (name, description, optional resources) for every Skill Unit.
  • Guided Workflow: Steps to gather requirements, draft, and review to ensure completeness and consistency.
  • Reference and Script Support: Guidance on optional REFERENCE.md, SKILL.md templates, and a scripts directory for deterministic tasks.

Quick Start

Draft SKILL.md with frontmatter including name and description, then add optional references and scripts as needed.

Frequently Asked Questions about write-a-skill

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

FAQPage Schema
How do I create a standardized skill template with consistent frontmatter?

This skill provides a reusable skeleton and a guided three-step workflow to standardize skill creation. It enforces consistent frontmatter requirements and offers a ready-to-use template to reduce ambiguity during onboarding.

What is the best way to structure an AI skill for consistent documentation?

Structure AI skills by drafting a SKILL.md file with required name and description frontmatter, then attach optional REFERENCE.md files and a scripts directory to support deterministic tasks and provide comprehensive documentation.

How does the guided workflow help draft and review new skills?

The guided workflow breaks skill creation into three steps: gathering requirements, drafting content, and reviewing for completeness. This enforces frontmatter requirements and ensures consistent structure across all Skill Units.

Do I need to include a scripts directory and REFERENCE.md for every skill?

No, scripts directories and REFERENCE.md files are optional resources. You only need to include them when your skill requires deterministic task execution or supplementary reference documentation beyond the standard SKILL.md template.

Can I use this approach to standardize skill creation for a team environment?

Yes, this approach standardizes skill creation for teams by enforcing a consistent frontmatter-driven structure and providing a reusable template, which reduces ambiguity and significantly decreases onboarding time for team members.