agentleFS
Sign inStart free
MSiccDevMSiccDev/ai-context-kit/skills/validate-skill/SKILL.md

validate-skill

Skill12 starsChanged 4 months agoMITView on GitHub

Validate SKILL.md artifacts for schema, quality, safety, portability, and scoring compliance.

3 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

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

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 4

    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
  1. Very specific:

    Use this skill when validating any skills/<name>/SKILL.md artifact.

    line 17
  2. Distinctive:

    Use this skill before accepting skill updates.

    line 18
  3. Distinctive:

    Do not use this skill to generate new skills.

    line 19
  4. Very specific:

    Run validation phases from references/phase-checks.md.

    line 27
  5. Distinctive:

    Keep the scoring rubric deterministic.

    line 45
  6. Distinctive:

    Do not modify validated source files automatically.

    line 47

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

Validate Skill

Purpose

Validate SKILL.md files with structured checks and produce consistent validation reports based on a deterministic scoring rubric.

When To Use

  • Use this skill when validating any skills/<name>/SKILL.md artifact.
  • Use this skill before accepting skill updates.
  • Do not use this skill to generate new skills.

Required Inputs

  • Target skill folder path.
  • Target SKILL.md path.
  • Validation strictness expectations (if any).

Workflow

  1. Run validation phases from references/phase-checks.md.
  2. Generate report using references/report-contract.md.
  3. Apply deterministic scoring from references/scoring.md.
  4. Classify findings into critical/warning/enhancement buckets.
  5. Produce implementation-ready remediation guidance.

Output Expectations

  • Structured markdown validation report.
  • PASS/WARN/FAIL status and compliance score.
  • Actionable fixes for blocking and non-blocking issues.

Resources

  • Phase checks: references/phase-checks.md
  • Report contract: references/report-contract.md
  • Scoring model: references/scoring.md
  • Skill template: ../../templates/skill_template/SKILL.md

Constraints And Safety

  • Keep the scoring rubric deterministic; findings should be concise and repeatable.
  • Preserve provider neutrality.
  • Do not modify validated source files automatically.

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