audit-skills
$
npx mdskill add yonatangross/orchestkit/audit-skillsAudits OrchestKit skills for quality, completeness, and compliance with authoring standards, ideal for health checks, releases, or after bulk edits.
- Helps identify SKILL.md files with issues like excessive length, missing frontmatter, or unregistered manifests.
- Integrates with tools like Read, Glob, Grep, Bash, Write, Edit, and TaskCreate for scanning and reporting.
- Decisions rely on rules for audit checks and status classification, loaded from specific files in the skill directory.
- Presents results in a table format with defined columns, as outlined in the output format reference.
SKILL.md
.github/skills/audit-skillsView on GitHub ↗
---
name: audit-skills
description: Audits all OrchestKit skills for quality, completeness, and compliance with authoring standards. Use when checking skill health, before releases, or after bulk skill edits to surface SKILL.md files that are too long, have missing frontmatter, lack rules/references, or are unregistered in manifests.
tags: [audit, quality, skills, orchestkit]
version: 2.0.0
author: OrchestKit
user-invocable: false
disable-model-invocation: true
context: fork
complexity: medium
persuasion-type: discipline
allowed-tools:
- Read
- Glob
- Grep
- Bash
- Write
- Edit
- TaskCreate
- TaskUpdate
- TaskList
---
# audit-skills
Scans all `src/skills/*/SKILL.md` files and reports compliance with OrchestKit authoring standards. Each category has individual files in `rules/` and `references/` loaded on-demand.
## Quick Reference
| Category | File | Impact | When to Use |
|----------|------|--------|-------------|
| Audit Checks | `${CLAUDE_SKILL_DIR}/rules/audit-checks.md` | HIGH | What to validate per skill |
| Status Rules | `${CLAUDE_SKILL_DIR}/rules/audit-status.md` | MEDIUM | PASS/WARN/FAIL classification |
| Output Format | `${CLAUDE_SKILL_DIR}/references/output-format.md` | MEDIUM | Table layout and column definitions |
| Edge Cases | `${CLAUDE_SKILL_DIR}/references/edge-cases.md` | LOW | Manifest "all", orchestration skills |
**Total: 2 rules across 2 categories**
## CRITICAL: Task Management is MANDATORY (CC 2.1.16)
**BEFORE doing ANYTHING else, create tasks to track progress:**
```python
# 1. Create main task IMMEDIATELY
TaskCreate(
subject="Audit Skills: full scan",
description="Auditing all OrchestKit skills for quality and compliance",
activeForm="Auditing skill quality"
)
# 2. Create subtasks for each audit phase
TaskCreate(subject="Discover skills", activeForm="Globbing SKILL.md files")
TaskCreate(subject="Run audit checks", activeForm="Checking each skill")
TaskCreate(subject="Classify & render", activeForm="Classifying results and rendering report")
# 3. Set dependencies for sequential phases
TaskUpdate(taskId="3", addBlockedBy=["2"])
TaskUpdate(taskId="4", addBlockedBy=["3"])
# 4. Before starting each task, verify it's unblocked
task = TaskGet(taskId="2") # Verify blockedBy is empty
# 5. Update status as you progress
TaskUpdate(taskId="2", status="in_progress") # When starting
TaskUpdate(taskId="2", status="completed") # When done
```
## Workflow
1. **Discover** — Glob `src/skills/*/SKILL.md` to get full skill list
2. **Check each skill** — Run all checks from `Read("${CLAUDE_SKILL_DIR}/rules/audit-checks.md")` in parallel
3. **Classify** — Apply status rules from `Read("${CLAUDE_SKILL_DIR}/rules/audit-status.md")`
4. **Render** — Output table using format from `Read("${CLAUDE_SKILL_DIR}/references/output-format.md")`
5. **Totals** — Show `X pass, Y warn, Z fail` at bottom
## Quick Start
```bash
bash src/skills/audit-skills/scripts/run-audit.sh
```
Or invoke manually — Claude scans `src/skills/`, applies checks, and renders the summary table.
## Key Decisions
| Decision | Recommendation |
|----------|----------------|
| Manifest check | `"skills": "all"` in ork.json means ALL skills qualify — mark YES |
| 0 rules + refs | WARN only — some orchestration skills are legitimately rules-free |
| Broken refs | WARN (not FAIL) — file may exist under a different path |
## Related Skills
- `ork:skill-evolution` — Guidance on iterating and improving skills
- `ork:quality-gates` — Broader codebase quality checks
More from yonatangross/orchestkit
- agent-orchestrationAgent orchestration patterns for agentic loops, multi-agent coordination, alternative frameworks, and multi-scenario workflows. Use when building autonomous agent loops, coordinating multiple agents, evaluating CrewAI/AutoGen/Swarm, or orchestrating complex multi-step scenarios.
- ai-ui-generationAI-assisted UI generation patterns for json-render, v0, Bolt, and Cursor workflows. Covers prompt engineering for component generation, review checklists for AI-generated code, design token injection, refactoring for design system conformance, and CI gates for quality assurance. Use when generating UI components with AI tools, rendering multi-surface MCP visual output, reviewing AI-generated code, or integrating AI output into design systems.
- analyticsQuery cross-project usage analytics. Use when reviewing agent, skill, hook, or team performance across OrchestKit projects. Also replay sessions, estimate costs, and view model delegation trends.
- animation-motion-designAnimation and motion design patterns using Motion library (formerly Framer Motion) and View Transitions API. Use when implementing component animations, page transitions, micro-interactions, gesture-driven UIs, or ensuring motion accessibility with prefers-reduced-motion.
- architecture-patternsArchitecture validation and patterns for clean architecture, backend structure enforcement, project structure validation, test standards, and context-aware sizing. Use when designing system boundaries, enforcing layered architecture, validating project structure, defining test standards, or choosing the right architecture tier for project scope.
- ascii-visualizerASCII diagram patterns for architecture, workflows, file trees, and data visualizations. Use when creating terminal-rendered diagrams, box-drawing layouts, progress bars, swimlanes, or blast radius visualizations.
- assessAssesses and rates quality 0-10 with pros/cons analysis. Use when evaluating code, designs, or approaches.
- async-jobsAsync job processing patterns for background tasks, Celery workflows, task scheduling, retry strategies, and distributed task execution. Use when implementing background job processing, task queues, or scheduled task systems.
- audit-fullFull-codebase audit using 1M context window. Security, architecture, and dependency analysis in a single pass. Use when you need whole-project analysis.
- bare-evalRun isolated eval and grading calls using CC 2.1.81 --bare mode. Constructs claude -p --bare invocations for skill evaluation, trigger testing, and LLM grading without plugin/hook interference. Use when running eval pipelines, grading skill outputs, benchmarking prompt quality, or testing trigger accuracy in isolation.