agentleFS
rafapeixerrafapeixer/go-skills/.claude/skills/new-skill/SKILL.md

new-skill

Skill1 starsChanged 31 days agoMITView on GitHub

Scaffold a new go-skills skill from the template, with good and bad example modules, then validate it. Use when adding a skill to this repository.

25 other projects use a version of this, 2 of them edited.

Adopted by

Most recently taken up by

Used with

Projects with it also use commit and handoff.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 4 projects that use this

  • MicrosoftSkill

    handoff

    Compact the current conversation into a handoff document for another agent to pick up.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Create the skill $ARGUMENTS in this repository.

    line 10
  2. Very specific:

    Stop if skills/$ARGUMENTS/ already exists, or if the name is not lowercase kebab-case.

    line 12
  3. Very specific:

    Read CLAUDE.md and templates/SKILL.template.md.

    line 13
  4. Very specific:

    Create skills/$ARGUMENTS/examples/good/ and skills/$ARGUMENTS/examples/bad/, each with:

    line 15
  5. Very specific:

    Add the skill to the index in both README.md and README.pt-BR.md.

    line 19
  6. Very specific:

    Run bash scripts/validate.sh and bash scripts/test-examples.sh and fix everything they report.

    line 20

“Common” is measured: kept by at least 6 in 10 of the 22 edited versions of this file we could read. “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

New skill

Create the skill $ARGUMENTS in this repository.

  1. Stop if skills/$ARGUMENTS/ already exists, or if the name is not lowercase kebab-case.
  2. Read CLAUDE.md and templates/SKILL.template.md. Check that the skill is in the catalog in CLAUDE.md; if not, say so and stop.
  3. Copy the template to skills/$ARGUMENTS/SKILL.md and set name: $ARGUMENTS.
  4. Create skills/$ARGUMENTS/examples/good/ and skills/$ARGUMENTS/examples/bad/, each with:
    • go.mod with module github.com/rafapeixer/go-skills/skills/$ARGUMENTS/examples/<good|bad> and the go directive used by the other examples;
    • a main.go or _test.go under 100 lines.
  5. Write the skill following every rule in CLAUDE.md: one decision, a position, a reason for every rule, real mistakes in the bad example with // MISTAKE: comments, and exceptions in "When not to apply". When a fact is uncertain or may have changed, check current primary sources (go.dev release notes, pkg.go.dev, the package's own docs) before writing it.
  6. Add the skill to the index in both README.md and README.pt-BR.md.
  7. Run bash scripts/validate.sh and bash scripts/test-examples.sh and fix everything they report.

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.