agentleFS
th3r-devth3r-dev/th3-skills/.claude/skills/new-skill/SKILL.md

new-skill

Skill2 starsChanged 2 days agoMITView on GitHub

Scaffold a new skill in this repo (skills/<name>/SKILL.md, README entry, and a CI workflow if it has tests). Use when adding a skill to th3-skills.

  • Installs packages

24 other projects use a version of this.

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

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

  • 0

    Common

    Most of the 21 edited versions we read keep these.

  • 2

    Distinctive

    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
  • could be automatic: a setting could enforce it
  1. Very specific:

    Create skills/<name>/SKILL.md with frontmatter of only name and a trigger-heavy description ("Use WHENEVER ..."), plus a short body.

    line 10
  2. Distinctive:

    Add a one-paragraph entry for it to the Skills list in README.md, in the same style as the others.

    line 11
  3. Very specific:

    If the skill has tests, copy .github/workflows/qa.yml to .github/workflows/<name>.yml: change name, both paths filters, working-directory, …

    line 12
  4. Distinctive:

    Run the skill's tests locally before finishing.

    line 14

“Common” is measured: kept by at least 6 in 10 of the 21 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

Scaffold skill $ARGUMENTS (kebab-case) in this repo.

  1. Confirm you're on a feat/<name> branch cut from dev; create it if not.
  2. Create skills/<name>/SKILL.md with frontmatter of only name and a trigger-heavy description ("Use WHENEVER ..."), plus a short body. Add references/, scripts/, tests/ only if needed. Scripts stdlib-only, with --selftest / --dry-run where useful.
  3. Add a one-paragraph entry for it to the Skills list in README.md, in the same style as the others.
  4. If the skill has tests, copy .github/workflows/qa.yml to .github/workflows/<name>.yml: change name, both paths filters, working-directory, the pinned pip install line (--only-binary :all:, versions with wheels for every matrix Python) and the self-check steps.
  5. Mock data must use thai-mock-naming markers; no client hosts, IPs or names.
  6. Run the skill's tests locally before finishing.

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.