agentleFS
Sign inStart free
AymanShamsAymanShams/codex-coding-os/.agents/skills/artifact-validation-workflow/SKILL.md

artifact-validation-workflow

Skill1 starsChanged 2 months agoMPL-2.0View on GitHub

Use when the user asks to validate, acceptance-check, quality-gate, readiness-review, approve, sign off, submit-check, publish-check, handoff-check, archive-check, or decide whether an artifact is ready to use. Use for SOPs, policies, reports, decks, strategy documents, project plans, dossiers, implementation guides, templates, evidence packs, data specs, academic or professional deliverables, and controlled artifacts where acceptance criteria, evidence requirements, pass/fail verdicts, defect logs, required fixes, decision-needed reports, re-validation steps, or readiness recommendations matter. Use when the user asks "is this ready", "can this be approved", "what blocks submission", "make a validation checklist", "create acceptance criteria", "log defects", "give a pass/fail verdict", or "what evidence is required". Do not use for source code behavior review unless the artifact being reviewed is a document or controlled deliverable. If the primary task is broad skeptical critique of reasoning, use deep-critic. If the primary task is SSOT-style artifact completeness and operational quality without a pass/fail acceptance workflow, use ssot-auditor. If the primary task is source, citation, or claim verification, use evidence-checker. If the primary task is designing the surrounding artifact system, use artifact-system-designer. If failed validation requires delivery sequencing or remediation planning, use wbs-artifact-planner.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

Licensed with conditions — read it at the source. We count its rules but don't quote them. Read them on GitHub.

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

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