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

new-skill

Skill1 starsChanged 30 days agoMITView on GitHub

Scaffold a new db-skills skill (pg-*, mysql-* decision skill or db-* workflow skill) from the templates, then validate and run its examples. 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, 1 is distinctive, and 5 are very specific to this project.

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 5

    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/ exists, or if the name is not lowercase kebab-case starting with pg-, mysql- or db-.

    line 12
  3. Very specific:

    Read CLAUDE.md and the matching template in templates/.

    line 13
  4. Distinctive:

    Every fact (version, default, limit, behavior) comes from the official docs: postgresql.org, dev.mysql.com, docs.aws.amazon.com, or the …

    line 16
  5. Very specific:

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

    line 17
  6. Very specific:

    Run bash scripts/validate.sh and bash scripts/test-examples.sh.

    line 18

“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/ exists, or if the name is not lowercase kebab-case starting with pg-, mysql- or db-.
  2. Read CLAUDE.md and the matching template in templates/.
  3. Decision skill (pg-*, mysql-*): write SKILL.md and examples/good/test.sql plus examples/bad/test.sql. Each test creates its own schema, loads enough rows for the planner to behave realistically, and asserts with the helpers in scripts/lib/ (assert_true, plan_has, assert_error on Postgres; assert_true, plan_has with EXPLAIN FORMAT=JSON INTO @plan on MySQL). The bad example's assertions describe the bad outcome, and each mistake is marked -- MISTAKE:.
  4. Workflow skill (db-*): write SKILL.md and queries/<engine>/*.sql. Queries are read-only; validate.sh rejects writes, DDL, maintenance commands and EXPLAIN ANALYZE.
  5. Every fact (version, default, limit, behavior) comes from the official docs: postgresql.org, dev.mysql.com, docs.aws.amazon.com, or the tool's own docs. Cite the URL in the Why section.
  6. Add the skill to both README.md and README.pt-BR.md.
  7. Run bash scripts/validate.sh and bash scripts/test-examples.sh; 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.