agents-checker
Skill2 starsChanged 8 months agoUnlicenseView on GitHub
Verifies structural integrity and compliance of .claude/agents/ and .claude/frontend_agent.md against init-agent standards. Use after modifying agent files or adding new agents. Do not use for code quality audits — use /frontend-code-review instead.
In this repository70 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- .cursor/rules/00-project-context.mdcCursor rule
- .cursor/rules/01b-component-gen-next.mdcCursor rule
- .cursor/rules/01-component-gen.mdcCursor rule
- .cursor/rules/02-component-tests.mdcCursor rule
- .cursor/rules/03b-vue-doctor.mdcCursor rule
- .cursor/rules/03-react-doctor.mdcCursor rule
- .cursor/rules/04-ui-tweak.mdcCursor rule
- .cursor/rules/05-refactor.mdcCursor rule
- .cursor/rules/06-frontend-code-review.mdcCursor rule
- .cursor/rules/07-fe-repo-scout.mdcCursor rule
- .cursor/rules/08-be-repo-scout.mdcCursor rule
- .cursor/rules/09-web-vitals.mdcCursor rule
- .cursor/rules/10-browser-check.mdcCursor rule
- .cursor/rules/11-api-bind.mdcCursor rule
- .cursor/rules/12-e2e-tests.mdcCursor rule
- .cursor/rules/13-api-mocks.mdcCursor rule
- agents-checkerSkill
- api-bindSkill
- api-mocksSkill
- be-repo-scoutSkill
- browser-checkSkill
- component-gen-nextSkill
- component-genSkill
- component-testsSkill
- curate-lessonsSkill
- e2e-testsSkill
- fe-repo-scoutSkill
- fix-markdownSkill
- frontend-code-reviewSkill
- init-agentSkill
- init-projectSkill
- init-skillSkill
- prSkill
- react-doctorSkill
- refactorSkill
- setup-configsSkill
- skill-auditSkill
- spec-auditSkill
- ui-tweakSkill
- update-ai-setupSkill
- vue-doctorSkill
- web-vitalsSkill
- api-bindSkill
- api-mocksSkill
- be-repo-scoutSkill
- browser-checkSkill
- component-gen-nextSkill
- component-genSkill
- component-testsSkill
- curate-lessonsSkill
- e2e-testsSkill
- fe-repo-scoutSkill
- fix-markdownSkill
- frontend-code-reviewSkill
- init-agentSkill
- init-projectSkill
- init-skillSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
13 rules. About 0 are common, 6 are distinctive, and 7 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
7
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 26
After manually editing frontend_agent.md or any file in .claude/agents/
- Distinctive: line 27
After adding a new agent
- Distinctive: line 51
Check each required file is present:
- Very specific: line 63
Verify frontend_agent.md contains all required sections:
- Very specific: line 99
Verify the referenced file exists under .claude/agents/
- Very specific: line 104
Check for content in .claude/agents/*.md that duplicates frontend_agent.md verbatim or near-verbatim.
- Very specific: line 108
Read all files in .claude/agents/ and .claude/frontend_agent.md
- Distinctive: line 158
Before finalizing the audit:
- Very specific: line 166
Gardener Protocol: Call .claude/protocols/gardener.md.
- Very specific: line 180
Write the full report to audit/agents-checker-report_{agent}_{YYYYMMDD_HHMMSS}.md using the Write tool.
- Distinctive: line 224
All-pass shortcut: If all files pass with ✅ PASS and cross-refs are clean → replace the 4-row status table with a single line:
- Distinctive: line 230
Only expand the status table when ≥1 file has ⚠️ WARNINGS or ❌ FAIL.
- Distinctive: line 255
All 3 required files confirmed present (frontend_agent.md, engineer.md, auditor.md)
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.
Files
/agents-checker — AI Agent Setup Validator
SILENT MODE: Execute all validation phases silently. Do not output intermediate findings or progress per file. Only the final audit report and SKILL COMPLETE block go to chat.
Status Reporting: After Phase 2 (frontend_agent.md checks) and Phase 3 (each agent file), emit a single-line JSON progress:
{"phase": N, "files_scanned": N, "issues_found": N}
Type: Audit Utility Category: Frontend Setup / Compliance
Checks that the project's Claude agent files comply with the standards produced by /init-agent. Validates structure, required sections, cross-references, and absence of stale placeholders.
When to Use
- After manually editing
frontend_agent.mdor any file in.claude/agents/ - After adding a new agent
- Before running
/update-ai-setup - As a pre-flight check in the development pipeline
Scope
| Target | Path |
| Frontend Lead profile | .claude/frontend_agent.md |
| Agent files | .claude/agents/*.md |
| Skill cross-refs | .claude/skills/*/SKILL.md frontmatter |
Input Parameters
| Parameter | Required | Default | Description |
auto_fix | No | true | When true, auto-repairs safe deterministic issues after full audit and logs each change with rationale. Unsafe issues (missing files, role-specific content) are always flagged only. |
Workflow
Phase 1: File Existence
Check each required file is present:
.claude/frontend_agent.md.claude/agents/engineer.md.claude/agents/auditor.md
If any file is missing → 🔴 CRITICAL. Stop and report. Do not proceed to Phase 2.
Phase 2: frontend_agent.md Structure
Load .claude/skills/init-agent/references/qa-agent-template.md as the reference standard (orchestrator structure).
Verify frontend_agent.md contains all required sections:
| Check | Rule | Severity |
## Core Mindset present | Must have 3–5 principles listed | 🔴 CRITICAL |
## Anti-Patterns (BANNED) present | Table with ≥ 3 rows | 🔴 CRITICAL |
## Quality Gates present | Must contain Start + Generate + Review gates | 🟠 MAJOR |
## Skills Matrix present | Must reference all 10 skills with owners | 🟠 MAJOR |
| No placeholders | Grep for [xxx] pattern — none allowed | 🟠 MAJOR |
| Anti-patterns match role | frontend_agent.md is an Orchestrator — anti-patterns must cover orchestration failures (e.g. micro-management, blind approval, silent looping). Code-level patterns belong in agent files, NOT here. | 🟡 MINOR |
Phase 3: Agent File Validation
For each .md file in .claude/agents/:
| Check | Rule | Severity |
| Role heading present | ## Identity or # [Name] Agent | 🔴 CRITICAL |
## Core Mindset present | At least 3 principles | 🔴 CRITICAL |
## Anti-Patterns (BANNED) present | Table with ≥ 3 rows | 🟠 MAJOR |
## Verbosity Protocol present | Must define output format | 🟠 MAJOR |
## Quality Gates present | At least Commit + Review gates | 🟠 MAJOR |
| Skills list defined | ## Skills section lists at least 1 skill | 🟠 MAJOR |
## Output Contract present | Defines artifact format | 🟡 MINOR |
| No placeholders | Grep for [xxx] — none allowed | 🟠 MAJOR |
Phase 4: Cross-Reference Integrity
- Skills referenced in agent files exist:
- Extract all
/skill-namementions from each agent file - For each: check
.claude/skills/{skill-name}/SKILL.mdexists - Missing skill → 🟠 MAJOR
- Extract all
- Agent references in SKILL.md frontmatter are valid:
- Glob all
.claude/skills/*/SKILL.md - Extract
agent:field from frontmatter (if present) - Verify the referenced file exists under
.claude/agents/ - Broken reference → 🟠 MAJOR
- Glob all
Phase 5: Agent File Duplication
Check for content in .claude/agents/*.md that duplicates frontend_agent.md verbatim or near-verbatim.
Algorithm:
- Read all files in
.claude/agents/and.claude/frontend_agent.md - LLM step: for each agent file, compare each section against the corresponding section in
frontend_agent.md. Flag content that is duplicated word-for-word or with only minor rephrasing - Severity: WARNING — "Content in
agents/{file}.md § {section}duplicatesfrontend_agent.md § {section}. Canonical location:frontend_agent.md. Consider removing from agent file and adding→ see frontend_agent.md." - Exception:
## Anti-Patterns (BANNED)may intentionally contain agent-specific rules — flag only exact/verbatim copies, not agent-specific content
Not fixable via auto_fix — removing content requires understanding of intent; always flag for manual review.
Phase 6: Self-Healing (auto_fix=true)
Skipped if auto_fix=false. Runs after Phase 4 only if audit found fixable issues.
Fixable issues — safe to auto-repair:
| Finding | Fix Action | Rationale |
Placeholder patterns ([Profile], [Framework], [Actor], [xxx]) in any agent file | Remove the containing line via Edit | Placeholders are unfilled template slots — they add noise and confuse the AI reading the file |
## Anti-Patterns (BANNED) missing in frontend_agent.md | Append section verbatim from init-agent/references/qa-agent-template.md | Section is fully standardized in the template; copying it is deterministic and safe |
## Skills Matrix missing in frontend_agent.md | Flag only — content is project-specific | Cannot fabricate skill ownership without context |
Broken agent: reference in SKILL.md frontmatter (target file missing) | Remove the agent: line from frontmatter | A broken ref causes skill routing errors; removing it degrades to default gracefully |
NOT fixable — always flagged, never auto-repaired:
| Issue | Reason |
Required file missing (frontend_agent.md, engineer.md, auditor.md) | Cannot fabricate role-specific content |
## Core Mindset missing | Content is role-specific — wrong defaults are worse than absence |
## Identity / Role heading missing in agent file | Requires understanding of agent purpose |
| Skill cross-references to non-existent skills | May be intentional (planned future skill) |
After fixes: Re-run Phases 2–3 on modified files to confirm healing was effective. Report delta.
Anti-Patterns
| Anti-Pattern | Why It Breaks | Fix |
Agent file missing ## Identity heading | AI doesn't know which agent this is; routing fails | Add explicit role heading: ## Identity with Role + Authority |
Identical content in agent file and frontend_agent.md (verbatim copy) | Duplication wastes tokens; conflicting updates | Keep canonical content in frontend_agent.md; use reference in agent file if needed |
Placeholder text [Profile], [Framework], [xxx] left unfilled | Template cruft confuses the AI; treated as actual rules | Remove all placeholder lines after initial setup |
Broken agent: reference in SKILL.md | Skill cannot find its agent profile; falls back to defaults | Verify agent file exists at .claude/agents/{name}.md |
## Anti-Patterns table with < 3 rows | Insufficient guidance for that role | Add role-specific patterns from the agent's domain |
Missing ## Verbosity Protocol in agent file | AI outputs verbose intermediate findings; wastes tokens | Add protocol section explaining output format |
Quality Gate (Self-Review)
Before finalizing the audit:
- All 3 required files scanned (frontend_agent.md + all agents/*.md)
- Phases 1–5 completed without early exit
- No critical issues left unflagged or auto-repaired unsafely
- Report artifact generated with timestamp
- JSON progress emitted after Phases 2–3
Gardener Protocol: Call .claude/protocols/gardener.md. If you identified missing rules
or inefficiencies during this run, output a brief proposal table. Otherwise: 🌱 Gardener: No updates needed.
Output Format
Derive the {agent} slug from the skill argument:
- Specific agent file (e.g.,
agents/engineer.md) → basename without extension:engineer - Directory or multiple targets (e.g.,
.claude/agents,all) →all - Sanitize: replace
/, spaces, and dots with-, lowercase
Obtain timestamp via date +%Y%m%d_%H%M%S. Use it as the suffix.
Write the full report to audit/agents-checker-report_{agent}_{YYYYMMDD_HHMMSS}.md using the Write tool. Do NOT output the full report body to chat — only the summary block and completion block go to chat.
File structure (audit/agents-checker-report_{agent}_{YYYYMMDD_HHMMSS}.md):
# Agent Setup Audit Report
Date: {YYYY-MM-DD}
## Summary
| File | Status |
|------|--------|
| frontend_agent.md | ✅ PASS / ⚠️ WARNINGS / ❌ FAIL |
| engineer.md | ✅ PASS / ⚠️ WARNINGS / ❌ FAIL |
| auditor.md | ✅ PASS / ⚠️ WARNINGS / ❌ FAIL |
| Cross-refs | ✅ PASS / ⚠️ N broken refs |
## Findings
| # | Severity | File | Issue | Rule |
|---|----------|------|-------|------|
| 1 | 🔴 CRITICAL | .claude/frontend_agent.md | Missing ## Anti-Patterns table | init-agent template |
| 2 | 🟠 MAJOR | .claude/agents/auditor.md | /health-check skill not found | Phase 4 cross-ref |
| 3 | 🟡 MINOR | .claude/agents/engineer.md | ## Output Contract missing | Phase 3 check |
## Auto-Fix Log
- .claude/frontend_agent.md — Appended ## Anti-Patterns from template
→ Reason: ...
## Recommendations (Manual Fix Required)
### 1. [🟠] .claude/frontend_agent.md — <issue title>
**What:** ...
**How to fix:** ...
### 2. [🟡] .claude/agents/auditor.md — <issue title>
**What:** ...
**How to fix:** ...
## Decision
📝 [APPROVE / PASS WITH WARNINGS / ACTION RECOMMENDED]Chat output (summary only):
All-pass shortcut: If all files pass with ✅ PASS and cross-refs are clean → replace the 4-row status table with a single line:
✅ All files compliant (frontend_agent.md, engineer.md, auditor.md, cross-refs)Only expand the status table when ≥1 file has ⚠️ WARNINGS or ❌ FAIL.
🛡️ AGENT SETUP AUDIT
├─ frontend_agent.md: [✅ PASS / ⚠️ WARNINGS / ❌ FAIL]
├─ engineer.md: [✅ PASS / ⚠️ WARNINGS / ❌ FAIL]
├─ auditor.md: [✅ PASS / ⚠️ WARNINGS / ❌ FAIL]
└─ Cross-refs: [✅ PASS / ⚠️ N broken refs]
📝 Decision: [APPROVE / PASS WITH WARNINGS / ACTION RECOMMENDED]
→ Full report: audit/agents-checker-report_{agent}_{YYYYMMDD_HHMMSS}.mdFinish with the standard completion block:
✅ SKILL COMPLETE: /agents-checker
├─ Artifacts: audit/agents-checker-report_{agent}_{YYYYMMDD_HHMMSS}.md
├─ Compilation: N/A
├─ Upstream: .claude/skills/init-agent/references/qa-agent-template.md
└─ Coverage: [X/Y checks passed]Definition of Done
- All 3 required files confirmed present (frontend_agent.md, engineer.md, auditor.md)
frontend_agent.mdcontains all required sections (Core Mindset, Anti-Patterns, Quality Gates, Skills Matrix)- Each agent file contains Identity + Mindset + Anti-Patterns + Quality Gates + Skills
- Zero broken cross-references to non-existent skills
- No
[placeholder]text in any agent file - Agent file duplication check completed: verbatim duplicates of
frontend_agent.mdcontent flagged auto_fix=true: all safe issues repaired with logged rationale; re-validation passes; non-fixable issues remain in report withmanual fix requiredlabel
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.

