agentleFS
Sign inStart free
DailybotHQDailybotHQ/deepworkplan-skill/.agents/skills/fix-frontmatter/SKILL.md

fix-frontmatter

Skill23 starsChanged 5 months agoMITView on GitHub

Run the frontmatter validator and fix any SKILL.md that violates the repo's frontmatter contract. Use after editing or adding a SKILL.md.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    After adding or editing any SKILL.md, or when CI's "SKILL.md frontmatter validation" job fails.

    line 19
  2. Very specific:

    Run python3 scripts/validate-frontmatter.py and read every reported issue.

    line 24
  3. Very specific:

    ensure --- delimiters and the required keys exist

    line 29
  4. Very specific:

    Never edit a version: number to make the check pass — fix only quoting or format.

    line 38

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

Fix Frontmatter

Goal

Bring every SKILL.md under skills/ back into conformance with the frontmatter contract that CI enforces, so scripts/validate-frontmatter.py passes.

When to use

After adding or editing any SKILL.md, or when CI's "SKILL.md frontmatter validation" job fails.

Steps

  1. Run python3 scripts/validate-frontmatter.py and read every reported issue.
  2. For each flagged file, fix the frontmatter:
    • name: → kebab-case, starts with deepworkplan (e.g. deepworkplan-create)
    • version: → quoted SemVer ("2.8.0")
    • replace homepage: with documentation_url:
    • ensure --- delimiters and the required keys exist
  3. Re-run the validator until it prints OK: all N SKILL.md file(s) validated.

Validation

python3 scripts/validate-frontmatter.py exits 0.

Notes

Never edit a version: number to make the check pass — fix only quoting or format. The auto-release.yml bot owns version numbers (AGENTS.md §4). The validator scans skills/ only; .agents/skills/* is not CI-gated but follows the same style.

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.

Check your setup, free