skill-stats
Use when reviewing which QE skills are being used, finding undertriggering skills, or analyzing skill effectiveness. Shows usage patterns and recommendations.
Best use case
skill-stats is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Use when reviewing which QE skills are being used, finding undertriggering skills, or analyzing skill effectiveness. Shows usage patterns and recommendations.
Teams using skill-stats should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/skill-stats/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How skill-stats Compares
| Feature / Agent | skill-stats | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Use when reviewing which QE skills are being used, finding undertriggering skills, or analyzing skill effectiveness. Shows usage patterns and recommendations.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Skill Usage Statistics
View QE skill usage patterns to identify popular skills, undertriggering skills, and optimization opportunities.
## Activation
```
/skill-stats
```
## What It Reports
1. **Most Used Skills** — Top 10 skills by invocation count
2. **Undertriggering Skills** — Skills with good descriptions but low usage
3. **Never Used Skills** — Skills that have never been triggered
4. **Trigger Method** — How skills are activated (explicit /command vs auto-selected)
5. **Recommendations** — Skills to improve, merge, or deprecate
## Usage Log Format
Skill invocations are logged to `${CLAUDE_PLUGIN_DATA}/skill-usage.log`:
```
2026-03-18T10:30:00Z|security-testing|explicit|/security-testing
2026-03-18T10:45:00Z|qe-test-generation|auto|model-selected
2026-03-18T11:00:00Z|mutation-testing|explicit|/mutation-testing
```
## Hook Configuration
```json
{
"hooks": {
"PreToolUse": [
{
"matcher": "Skill",
"hook": ".claude/skills/skill-stats/scripts/log-usage.sh"
}
]
}
}
```
## Analysis Script
```bash
#!/bin/bash
# analyze-usage.sh
LOG="${CLAUDE_PLUGIN_DATA:-$HOME/.claude/plugin-data}/skill-usage.log"
if [ ! -f "$LOG" ]; then
echo "No usage data yet. Skills will be logged as they are used."
exit 0
fi
echo "=== Skill Usage Report ==="
echo ""
echo "Top 10 Most Used:"
cut -d'|' -f2 "$LOG" | sort | uniq -c | sort -rn | head -10
echo ""
echo "Trigger Method Breakdown:"
cut -d'|' -f3 "$LOG" | sort | uniq -c | sort -rn
echo ""
echo "Skills Used in Last 7 Days:"
WEEK_AGO=$(date -d '7 days ago' +%Y-%m-%dT%H:%M:%S 2>/dev/null || date -v-7d +%Y-%m-%dT%H:%M:%S)
awk -F'|' -v since="$WEEK_AGO" '$1 >= since' "$LOG" | cut -d'|' -f2 | sort | uniq -c | sort -rn
```
## Gotchas
- Log file grows unbounded — rotate periodically with `tail -n 1000 $LOG > $LOG.tmp && mv $LOG.tmp $LOG`
- Auto-selected skills may not always be the best match — review undertriggering skills for description improvements
- Usage count alone doesn't indicate quality — a skill used 100x but failing 50% needs fixing, not celebratingRelated Skills
qe-visual-testing-advanced
Advanced visual regression testing with pixel-perfect comparison, AI-powered diff analysis, responsive design validation, and cross-browser visual consistency. Use when detecting UI regressions, validating designs, or ensuring visual consistency.
qe-verification-quality
Comprehensive truth scoring, code quality verification, and automatic rollback system with 0.95 accuracy threshold for ensuring high-quality agent outputs and codebase reliability.
qe-testability-scoring
AI-powered testability assessment using 10 principles of intrinsic testability with Playwright and optional Vibium integration. Evaluates web applications against Observability, Controllability, Algorithmic Simplicity, Transparency, Stability, Explainability, Unbugginess, Smallness, Decomposability, and Similarity. Use when assessing software testability, evaluating test readiness, identifying testability improvements, or generating testability reports.
qe-test-reporting-analytics
Advanced test reporting, quality dashboards, predictive analytics, trend analysis, and executive reporting for QE metrics. Use when communicating quality status, tracking trends, or making data-driven decisions.
qe-test-idea-rewriting
Transform passive 'Verify X' test descriptions into active, observable test actions. Use when test ideas lack specificity, use vague language, or fail quality validation. Converts to action-verb format for clearer, more testable descriptions.
qe-test-environment-management
Test environment provisioning, infrastructure as code for testing, Docker/Kubernetes for test environments, service virtualization, and cost optimization. Use when managing test infrastructure, ensuring environment parity, or optimizing testing costs.
qe-test-design-techniques
Systematic test design with boundary value analysis, equivalence partitioning, decision tables, state transition testing, and combinatorial testing. Use when designing comprehensive test cases, reducing redundant tests, or ensuring systematic coverage.
qe-test-data-management
Strategic test data generation, management, and privacy compliance. Use when creating test data, handling PII, ensuring GDPR/CCPA compliance, or scaling data generation for realistic testing scenarios.
qe-test-automation-strategy
Design and implement effective test automation with proper pyramid, patterns, and CI/CD integration. Use when building automation frameworks or improving test efficiency.
qe-technical-writing
Write clear, engaging technical content from real experience. Use when writing blog posts, documentation, tutorials, or technical articles.
qe-tdd-london-chicago
Apply London (mock-based) and Chicago (state-based) TDD schools. Use when practicing test-driven development or choosing testing style for your context.
qe-stream-chain
Stream-JSON chaining for multi-agent pipelines, data transformation, and sequential workflows