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

validate-usercontext-instructions

Skill12 starsChanged 4 months agoMITView on GitHub

Validate user-context instruction files against schema, section completeness, quality checks, and scoring criteria.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Use this skill to validate *_usercontext.instructions.md files.

    line 17
  2. Distinctive:

    Use this skill before publishing or reusing a user-context file.

    line 18
  3. Distinctive:

    Do not use this skill for project AGENTS.md (project context) files.

    line 19
  4. Very specific:

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

    line 27
  5. Very specific:

    Check for spec_version field in YAML frontmatter: flag as WARNING if absent (pre-existing files may predate this requirement).

    line 28
  6. Distinctive:

    Keep recommendations implementation-ready and non-ambiguous.

    line 51
  7. Distinctive:

    Do not modify validated source files automatically.

    line 53

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

Validate User Context Instructions

Purpose

Validate user-context instruction files and produce structured reports with issues, recommendations, and a compliance score based on a deterministic scoring rubric.

When To Use

  • Use this skill to validate *_usercontext.instructions.md files.
  • Use this skill before publishing or reusing a user-context file.
  • Do not use this skill for project AGENTS.md (project context) files.

Required Inputs

  • Target file path.
  • Expected spec version and required sections.
  • Validation strictness expectations (if any).

Workflow

  1. Run validation phases from references/phase-checks.md.
  2. Check for spec_version field in YAML frontmatter: flag as WARNING if absent (pre-existing files may predate this requirement); flag as WARNING if present but older than 1.5.0.
  3. Generate report using references/report-contract.md.
  4. Apply deterministic scoring from references/scoring.md.
  5. Classify findings into critical/warning/enhancement buckets.
  6. Produce implementation-ready recommendations.

Output Expectations

  • A markdown validation report with phase-by-phase findings.
  • Overall PASS/WARN/FAIL state and numeric score.
  • Actionable fixes for critical and warning issues.
  • Migration guidance when relevant.
  • Report schema follows references/report-contract.md.
  • Scoring and grade bands follow references/scoring.md.

Resources

  • Phase checks: references/phase-checks.md
  • Report contract: references/report-contract.md
  • Scoring model: references/scoring.md
  • Example target: ../../usercontexts/sample_usercontext.instructions.md
  • Example report: ../../usercontexts/sample_usercontext.validation.md

Constraints And Safety

  • Preserve privacy boundaries in findings and examples.
  • Keep recommendations implementation-ready and non-ambiguous.
  • Use provider-neutral language.
  • 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