agentleFS
kostiantyn-matseborakostiantyn-matsebora/canopy-examples/.agents/skills/scaffold-skill/SKILL.md

scaffold-skill

Skill0 starsChanged 6 months agoMITView on GitHub

Generate a new Canopy skill skeleton — creates SKILL.md, references/ops.md, and standard agentskills.io subdirectories (scripts/, references/, assets/) under .claude/skills/<name>/. Uses the markdown list tree syntax.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. g-bastianelli/nuthouse★ 1same name

    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 repository10 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    IF << $ARGUMENTS is not valid kebab-case

    line 28
  2. Distinctive:

    IF << <skills-root>/$ARGUMENTS/ exists

    line 30
  3. Distinctive:

    ASK << Proceed? | Yes | No

    line 33
  4. Distinctive:

    Never overwrite an existing skill directory

    line 44

≈ “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

Runtime required. This skill uses Canopy tree notation; canopy-runtime must be active.

Detect canopy-runtime — present if either:

  • canopy-runtime/SKILL.md exists under .claude/skills/, .github/skills/, or .agents/skills/, OR
  • a canopy-runtime marker block exists in CLAUDE.md or .github/copilot-instructions.md.

If neither is present — install canopy-runtime first (see the compatibility field for the source and install options), then re-invoke this skill.

Do not interpret the ## Tree without canopy-runtime active.

New skill name: $ARGUMENTS


Tree

  • scaffold-skill
    • validate $ARGUMENTS is a valid kebab-case identifier
    • IF << $ARGUMENTS is not valid kebab-case
      • END Skill name must be kebab-case (e.g. my-skill)
    • IF << <skills-root>/$ARGUMENTS/ exists
      • END Skill already exists — choose a different name or delete the existing one first
    • SHOW_PLAN >> skill name | files to create | directories to create
    • ASK << Proceed? | Yes | No
    • IF << Yes
      • CREATE_SKILL_FILES << $ARGUMENTS
      • confirm files created
      • print next steps to user
      • VERIFY_EXPECTED << assets/verify/verify-expected.md
    • ELSE
      • Cancelled by user.

Rules

  • Never overwrite an existing skill directory
  • Generated SKILL.md must use the markdown list tree syntax (* nested lists), include the compatibility field, and open with the safety preamble guard block
  • Skill file must be named exactly SKILL.md (uppercase) per agentskills.io spec

Response: Summary / Files created / Next steps

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.