Skills Marker
Skill0 starsChanged 8 days agoNo licenceView on GitHub
TRIGGER when a git pull landed in the agents-skills repo, when asking which state of the skills a project consumes (Marker, Stand: welche Skills wurden angewendet?), when a skill changed and a project must be checked against it, when scaffolding a new project, on drift between skills repo and project, on a new or extended skill version, on deciding whether a skill change applies to this repo at all, or when advancing a marker. AGENTS.skills.md is the per-project marker (which commit was checked, which skills applied, the range <marker-sha>..HEAD).
In this repository20 other files it gives its agents.
- AGENTS.mdAGENTS.md
- Agent ConfigSkill
- Build Verify FlowSkill
- CodeGraph Project SetupSkill
- Docker Test ImageSkill
- Generated DocsSkill
- GHCR VisibilitySkill
- GitHub CI FiltersSkill
- LaravelSkill
- Node Dependency PolicySkill
- PermissionsSkill
- Playwright ParallelSkill
- Project GatesSkill
- Ratchet GatesSkill
- React i18nSkill
- Security ReviewSkill
- Tailscale ServeSkill
- UI ReviewSkill
- Update ModelsSkill
- Web AuditSkill
The file
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
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.

