agentleFS
thenavidmthenavidm/skill-builder/skills/skill-check/SKILL.md

skill-check

Skill0 starsChanged 29 days agoMITView on GitHub

Checks a skill or plugin against every AI tool's rules, in code, and explains each fix. Use when a tool won't load a skill, or before installing one someone sent.

  • Reads credentials

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Run the check, then explain what it found in plain words and fix what they want fixed.

    line 8
  2. Distinctive:

    Every finding names the fact it rests on and when that fact was last checked against the tool's own documentation or a real test.

    line 16

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

Check a skill or plugin

Run the check, then explain what it found in plain words and fix what they want fixed. The check reads files only; it never runs anything in the skill, so it's safe on a skill someone sent them.

npx -y @thenavidm/skill-builder@latest check <skill-folder-or-plugin>

(Where skill-builder is installed globally, skill-builder check <path> is the same.)

Every finding names the fact it rests on and when that fact was last checked against the tool's own documentation or a real test.

Reading the result

LevelMeansDo
errorA tool will refuse or misread the skillFix it
warningIt loads, but part of it does nothing, or works in one tool onlyFix it, or note why it stays
noteWorth knowing, nothing brokenMention it if it matters to them

The findings people meet most

FindingWhat happenedThe fix
field-unreadA field no tool reads, so it silently does nothing (auto-activate, a misspelled user-invokable)Use the field the message names, or move the value under metadata
name-folderThe name and its folder differ; some tools look a skill up by one, some by the otherRename one to match
listing-cutThe description and when_to_use are so long that Claude Code cuts the endPut the most important words first and shorten
yaml-unquotedA value holds ": " without quotes; the tools tested load it, a strict YAML reader doesn'tWrap the value in double quotes
missing-reference, missing-pathThe skill points at a file that isn't thereAdd the file or remove the pointer
plugin-root-reference, outside-skillA file outside the skill's folder; it works when the whole plugin installs, not where skills install one by oneMove the file into the skill's folder
claude-skill-dir, claude-arguments, claude-injection, tool-pathA feature or folder only Claude Code hasUse the plain fallback in the message, so other tools follow it too
mac-onlyA command that exists on macOS onlyOffer the Linux and Windows equivalent
secret, secret-fileA key, or a .env file, in what shipsRemove it, rotate the key now, and have the skill read keys from the user's environment
risky-surfaceA script can reach the network, delete, run programs or read keysTell the user what it does and get their yes, or remove it
long, heavyOver 500 lines or about 5,000 tokens of instructionsMove detail into references/

Fixing

Show each fix before you make it, grouped by file, and make them once they agree. Then run the check again and report the new result. For a skill they didn't write, suggest the fixes and leave the files alone unless they ask.

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.