agentleFS
Sign inStart free
afaqulislamafaqulislam/handbook/.agents/skills/format-checker/SKILL.md

format-checker

Skill0 starsChanged 32 days agoMITView on GitHub

The record's format rules as a runnable check — frontmatter, filenames, links, structure. Use before handing off any change to knowledge/, when a check fails and you need to fix it, or when unsure whether a document is well-formed. Run with `npm run check` (or node .agents/skills/format-checker/check.mjs).

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is 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.

  • 1

    Very specific

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

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

    Obey the printed fix literally: Every refusal prints where, the rule's slug (problem: ksor-…), why the rule exists, and the fix.

    line 19

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

Format checker

npm run check runs check.mjs. The rules it holds the record to are the ones in AGENTS.md → "Writing knowledge"; this file says only what that section does not, which is how to relate to the program.

  • It is generated, and it is the same rule set ksor build and ksor ingest run, so the three can never disagree about a well-formed record. Do not edit it: ksor init writes it and ksor migrate rewrites both copies when you upgrade, so an edit is overwritten rather than kept. It reports and never rewrites a file.
  • Obey the printed fix literally. Every refusal prints where, the rule's slug (problem: ksor-…), why the rule exists, and the fix. If the fix does not resolve the problem, that is a bug worth reporting to ksor.
  • If its refusals contradict AGENTS.md, the checker is older than the record: upgrade @panaversity/ksor and re-run ksor migrate. Never "fix" the record by undoing what a migration wrote.
  • When you edit any skill under .agents/skills/, re-copy it to .claude/skills/ — the checker holds the two trees byte-identical in both directions.

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