audit-log
View audit log entries for all component types (skills, commands, agents, hooks, etc.) to monitor audit health and track coverage
What this skill does
# Audit Log
View audit log entries from all discovered sources in the repository. Use this command to monitor audit health, identify components needing re-auditing (>90 days old or never audited), and track audit coverage across your codebase.
## Supported Component Types
- **skills** - Skill audit logs
- **commands** - Command audit logs
- **agents** - Agent audit logs
- **hooks** - Hook audit logs
- **memory** - CLAUDE.md file audit logs
- **mcp** - MCP configuration audit logs
- **settings** - Settings file audit logs
- **plugins** - Plugin manifest audit logs
- **output-styles** - Output style audit logs
- **statuslines** - Status line audit logs
## Arguments
- **No argument** or **all**: Show summary of ALL audit logs across all component types
- **{component-type}**: Filter to specific type (e.g., `skills`, `commands`, `agents`)
## Audit Log Location
All audit logs are stored in `.claude/audit/`:
```text
.claude/audit/
├── skills.md # Skill audits
├── commands.md # Command audits
├── agents.md # Agent audits
├── hooks.md # Hook audits
├── memory.md # CLAUDE.md file audits
├── mcp.md # MCP config audits
├── settings.md # Settings file audits
├── plugins.md # Plugin manifest audits
├── output-styles.md # Output style audits
└── statuslines.md # Status line audits
```
## Discovery
Read audit logs from `.claude/audit/{type}.md` for each component type.
Component types: skills, commands, agents, hooks, memory, mcp, settings, plugins, output-styles, statuslines.
## Display Format
### Summary View (default)
When no component type specified, show a summary across all types:
```markdown
# Audit Log Summary
## By Component Type
| Type | Total | Recent | Stale | Never |
| --- | --- | --- | --- | --- |
| Skills | 15 | 12 | 2 | 1 |
| Commands | 27 | 20 | 5 | 2 |
| Agents | 8 | 6 | 1 | 1 |
## Sources Discovered
**Location**: `.claude/audit/`
- skills.md (15 entries)
- commands.md (27 entries)
- agents.md (8 entries)
## Items Needing Attention
Run `/audit-log {type}` to see details for a specific component type.
Run `/audit-{type}` to audit components (e.g., `/audit-skills`, `/audit-agents`).
```
### Component Type View
When component type specified (e.g., `/audit-log commands`), show detailed view:
```markdown
# Command Audit Log
**Location**: .claude/audit/commands.md
| Command | Last Audit | Days Ago | Status |
| --- | --- | --- | --- |
| audit-log | 2025-12-17 | 8 | Recent |
| audit-skills | 2025-12-17 | 8 | Recent |
| scrape-docs | 2025-10-01 | 85 | Recent |
| scrape-claude-docs | 2025-12-15 | 10 | Recent |
**Stats**: 27 commands, 20 recent, 5 stale, 2 never audited
```
## Staleness Rules
- **Recent**: Audited within last 90 days
- **Stale**: Last audit > 90 days ago
- **Never Audited**: No audit date recorded
## Error Handling
If no audit logs found for requested type:
```markdown
# No Audit Logs Found
No {type} audit logs were found in this repository.
**Checked location**: .claude/audit/{type}.md (not found)
**To create audit logs**, run `/audit-{type}` to audit your {type}.
Audit logs are created automatically when components are audited.
```
## Example Usage
### Example 1: View All Audit Logs (Summary)
```text
User: /audit-log
Claude: Discovering audit logs...
# Audit Log Summary
## By Component Type
| Type | Total | Recent | Stale | Never |
| --- | --- | --- | --- | --- |
| Skills | 15 | 12 | 2 | 1 |
| Commands | 27 | 25 | 2 | 0 |
| Agents | 8 | 6 | 1 | 1 |
## Sources Discovered
**Location**: `.claude/audit/`
- skills.md
- commands.md
- agents.md
## Items Needing Attention
- 3 skills need re-audit
- 2 commands need re-audit
- 2 agents need re-audit
Run `/audit-log skills` to see skill details.
```
### Example 2: View Command Audit Logs
```text
User: /audit-log commands
Claude: Reading command audit logs...
# Command Audit Log
**Location**: .claude/audit/commands.md
| Command | Last Audit | Days Ago | Status |
| --- | --- | --- | --- |
| audit-log | 2025-12-17 | 8 | Recent |
| audit-skills | 2025-12-17 | 8 | Recent |
**Stats**: 27 commands, 25 recent, 2 stale, 0 never audited
```
### Example 3: View Skills Only
```text
User: /audit-log skills
Claude: Reading skill audit logs...
# Skill Audit Log
**Location**: .claude/audit/skills.md
| Skill | Last Audit | Days Ago | Status |
| --- | --- | --- | --- |
| docs-management | 2025-12-17 | 8 | Recent |
| skill-development | 2025-12-17 | 8 | Recent |
**Stats**: 15 skills, 12 recent, 2 stale, 1 never audited
```
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.