agentleFS
klich3klich3/skill-search-in-files-ack/.agents/skills/make-skill-template/SKILL.md

make-skill-template

Skill1 starsChanged 8 months agoMITView on GitHub

Create new Agent Skills for GitHub Copilot from prompts or by duplicating this template. Use when asked to "create a skill", "make a new skill", "scaffold a skill", or when building specialized AI capabilities with bundled resources. Generates SKILL.md files with proper frontmatter, directory structure, and optional scripts/references/assets folders.

3 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions3 projects use a version of this.

    Word for word · 3

    1. PickleBoxer/skills★ 1100% same
    2. jmolz/m0lz.01★ 0100% same
    3. ReaperOAK/ForgeOS★ 0100% same

    Edited · 0

    None found.

    Wrote their own version · 0

    None found.

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository2 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Create a new folder with a lowercase, hyphenated name:

    line 27
  2. Very specific:

    Every skill requires YAML frontmatter with name and description:

    line 36
  3. Distinctive:

    After the frontmatter, add markdown instructions.

    line 78
  4. Very specific:

    Write a keyword-rich description:

    line 121
  5. Distinctive:

    Add bundled resources as needed

    line 123

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Make Skill Template

A meta-skill for creating new Agent Skills. Use this skill when you need to scaffold a new skill folder, generate a SKILL.md file, or help users understand the Agent Skills specification.

When to Use This Skill

  • User asks to "create a skill", "make a new skill", or "scaffold a skill"
  • User wants to add a specialized capability to their GitHub Copilot setup
  • User needs help structuring a skill with bundled resources
  • User wants to duplicate this template as a starting point

Prerequisites

  • Understanding of what the skill should accomplish
  • A clear, keyword-rich description of capabilities and triggers
  • Knowledge of any bundled resources needed (scripts, references, assets, templates)

Creating a New Skill

Step 1: Create the Skill Directory

Create a new folder with a lowercase, hyphenated name:

skills/<skill-name>/
└── SKILL.md          # Required

Step 2: Generate SKILL.md with Frontmatter

Every skill requires YAML frontmatter with name and description:

---
name: <skill-name>
description: '<What it does>. Use when <specific triggers, scenarios, keywords users might say>.'
---

Frontmatter Field Requirements

FieldRequiredConstraints
nameYes1-64 chars, lowercase letters/numbers/hyphens only, must match folder name
descriptionYes1-1024 chars, must describe WHAT it does AND WHEN to use it
licenseNoLicense name or reference to bundled LICENSE.txt
compatibilityNo1-500 chars, environment requirements if needed
metadataNoKey-value pairs for additional properties
allowed-toolsNoSpace-delimited list of pre-approved tools (experimental)

Description Best Practices

CRITICAL: The description is the PRIMARY mechanism for automatic skill discovery. Include:

  1. WHAT the skill does (capabilities)
  2. WHEN to use it (triggers, scenarios, file types)
  3. Keywords users might mention in prompts

Good example:

description: 'Toolkit for testing local web applications using Playwright. Use when asked to verify frontend functionality, debug UI behavior, capture browser screenshots, or view browser console logs. Supports Chrome, Firefox, and WebKit.'

Poor example:

description: 'Web testing helpers'

Step 3: Write the Skill Body

After the frontmatter, add markdown instructions. Recommended sections:

SectionPurpose
# TitleBrief overview
## When to Use This SkillReinforces description triggers
## PrerequisitesRequired tools, dependencies
## Step-by-Step WorkflowsNumbered steps for tasks
## TroubleshootingCommon issues and solutions
## ReferencesLinks to bundled docs

Step 4: Add Optional Directories (If Needed)

FolderPurposeWhen to Use
scripts/Executable code (Python, Bash, JS)Automation that performs operations
references/Documentation agent readsAPI references, schemas, guides
assets/Static files used AS-ISImages, fonts, templates
templates/Starter code agent modifiesScaffolds to extend

Example: Complete Skill Structure

my-awesome-skill/
├── SKILL.md                    # Required instructions
├── LICENSE.txt                 # Optional license file
├── scripts/
│   └── helper.py               # Executable automation
├── references/
│   ├── api-reference.md        # Detailed docs
│   └── examples.md             # Usage examples
├── assets/
│   └── diagram.png             # Static resources
└── templates/
    └── starter.ts              # Code scaffold

Quick Start: Duplicate This Template

  1. Copy the make-skill-template/ folder
  2. Rename to your skill name (lowercase, hyphens)
  3. Update SKILL.md:
    • Change name: to match folder name
    • Write a keyword-rich description:
    • Replace body content with your instructions
  4. Add bundled resources as needed
  5. Validate with npm run skill:validate

Validation Checklist

  • Folder name is lowercase with hyphens
  • name field matches folder name exactly
  • description is 10-1024 characters
  • description explains WHAT and WHEN
  • description is wrapped in single quotes
  • Body content is under 500 lines
  • Bundled assets are under 5MB each

Troubleshooting

IssueSolution
Skill not discoveredImprove description with more keywords and triggers
Validation fails on nameEnsure lowercase, no consecutive hyphens, matches folder
Description too shortAdd capabilities, triggers, and keywords
Assets not foundUse relative paths from skill root

References

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.