spec-driven-analytics
Orchestrate session data mining operations through a 7-phase workflow with structural anti-skip enforcement. Analyzes Claude Code history.jsonl files and workflow artifacts to deliver formatted, actionable analytics for workflow patterns, errors, decisions, and command sequences. Prevents token optimization bias through per-phase reference loading, checkpoint persistence, Execute-Verify-Record enforcement, and artifact verification. Use when analyzing session data, extracting workflow patterns, investigating error trends, or reviewing development decisions. Always use this skill when the user
npx skills add majiayu000/claude-skill-registry --skill spec-driven-analytics-bankielewicz-devforgeai --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Spec-Driven Analytics Orchestrate session data mining operations through the session-miner subagent to deliver formatted, actionable analytics from Claude Code session history, with 4-layer structural anti-skip enforcement. **Context files are THE LAW:** tech-stack.md, source-tree.md, dependencies.md, coding-standards.md, architecture-constraints.md, anti-patterns.md **If ambiguous or conflicts detected: HALT and use AskUserQuestion** --- ## Execution Model This skill expands inline. After invocation, execute Phase 00 Initialization immediately. Do not wait passively, ask permission, or offer execution options. **Self-Check (if ANY box is true = VIOLATION):** - [ ] Stopping to ask about token budget - [ ] Stopping to offer execution options - [ ] Waiting passively for user to say "go" - [ ] Asking "should I execute this?" - [ ] Skipping a phase because it "seems simple" - [ ] Combining multiple phases into one - [ ] Summarizing instead of loading a reference file - [ ] Skipping verification because "I already wrote the file" **IF any box checked:** EXECUTION MODEL VIOLATION. Go directly to Phase 00 Initialization now. --- ## Anti-Skip Enforcement Contract This skill enforces 4 in
- Execution Model
- Anti-Skip Enforcement Contract
- Purpose
- Core Philosophy
- When to Use This Skill
- Trigger Scenarios
- When NOT to Use
- Parameter Extraction
- State Persistence
- Phase 00: Initialization [INLINE - Bootstraps State]
- Step 0.1: Parse Arguments
- Step 0.2: Resume Detection
- Step 0.3: Generate Analytics ID
- Step 0.4: CLI Initialization
source .venv/bin/activate && devforgeai-validate phase-init ${ANALYTICS_ID} --workflow=analytics --project-root=. 2>&1What does the spec-driven-analytics skill do?
Orchestrate session data mining operations through a 7-phase workflow with structural anti-skip enforcement. Analyzes Claude Code history.jsonl files and workflow artifacts to deliver formatted, actionable analytics for workflow patterns, errors, decisions, and command sequences. Prevents token optimization bias through per-phase reference loading, checkpoint persistence, Execute-Verify-Record enforcement, and artifact verification. Use when analyzing session data, extracting workflow patterns, investigating error trends, or reviewing development decisions. Always use this skill when the user
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill spec-driven-analytics-bankielewicz-devforgeai --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.