agentleFS
anwatheranwather/epac-skills/skills/epac-test-fixtures/SKILL.md

epac-test-fixtures

Skill4 starsChanged 8 months agoNo licenceView on GitHub

Scaffold a ready-to-deploy set of EPAC policy artifacts (custom initiative, built-in assignments, and a varied set of exemptions) into an existing EPAC repo so you can reproduce, exercise, or smoke-test EPAC behavior. Use this skill when asked to populate, seed, scaffold, or generate test fixtures, sample artifacts, smoke-test content, or a "demo" set of policies/assignments/exemptions in an EPAC repo — especially when validating an EPAC code change, a new switch, or a workflow end-to-end.

We split this skill into the rules it gives an agent

26 rules. About 0 are common, 13 are distinctive, and 13 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 13

    Very specific

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

No licence file, so all rights are reserved — 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 308,232 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.

Reviews can't be read right now.

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.