skill-stats

Name: skill-stats
Author: proffesor-for-testing

Engineering Community

Repo stars 353
Author updated Live
Author repo agentic-qe

Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network

Domain: Engineering
Compatible agents: Claude Code
Cursor
Cline
Codex
Windsurf
Gemini CLI

+20
Trust score: 88 / 100 · community maintained
Author / version / license: @proffesor-for-testing · no license declared
Token usage: Lean
Setup complexity: Plug-and-play
External API key: Not required
Operating systems: Unspecified (assume cross-platform)
Runtime requirements: No special requirements
Permissions: Read-only
Write / modify
Network behavior: Local-only
Install commands: 26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview skill-stats.preview

---
name: skill-stats
description: Use when reviewing which QE skills are being used, finding undertriggering skills, or analyzing…
category: engineering
runtime: no special runtime
---

# skill-stats output preview

## PART A: Task fit
- Use case: Use when reviewing which QE skills are being used, finding undertriggering skills, or analyzing skill effectiveness. Shows usage patterns and recommendations. View QE skill usage patterns to identify popular skills, undertriggering skills, and optimization opportunities. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Activation / What It Reports / Usage Log Format” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Use when reviewing which QE skills are being used, finding undertriggering skills, or analyzing skill effectiveness. Shows usage patterns and recommendations. View QE skill usage patterns to identify popular skills, undertriggering skills, and optimization opportunities. runs entirely locally. Works with Claude Code, Cursor, Cline and 23 more.”.
- **02** When the source has headings, the agent prioritizes “Activation / What It Reports / Usage Log Format” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.

SKILL.md SKILL.md

---
name: skill-stats
description: Use when reviewing which QE skills are being used, finding undertriggering skills, or analyzing…
category: engineering
source: proffesor-for-testing/agentic-qe
---

# skill-stats

## When to use
- Use when reviewing which QE skills are being used, finding undertriggering skills, or analyzing skill effectiveness. S…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.

## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.

## Execution rules
- Organize steps around “Activation / What It Reports / Usage Log Format” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.

## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.

Evidence boundary and execution chain

The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.

skill "skill-stats" {
  input      -> user goal + target files + boundaries + acceptance criteria
  context    -> Activation / What It Reports / Usage Log Format
  rules      -> SKILL.md triggers / order / output contract
  runtime    -> no special runtime | read files, write/modify files | mostly runs locally
  guardrails -> usually needs no extra API key + small-sample validation + diff/log review
  output     -> copyable result + checklist + next iteration
}

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Use when reviewing which QE skills are being used, finding undertriggering skills, or analyzing skill effectiveness. Shows usage…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Activation”, “What It Reports”, “Usage Log Format”, “Hook Configuration”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name skill-stats directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Activation / What It Reports / Usage Log Format” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

Skill Usage Statistics

View QE skill usage patterns to identify popular skills, undertriggering skills, and optimization opportunities.

Activation

/skill-stats

What It Reports

Most Used Skills — Top 10 skills by invocation count
Undertriggering Skills — Skills with good descriptions but low usage
Never Used Skills — Skills that have never been triggered
Trigger Method — How skills are activated (explicit /command vs auto-selected)
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

{
  "hooks": {
    "PreToolUse": [
      {
        "matcher": "Skill",
        "hook": ".claude/skills/skill-stats/scripts/log-usage.sh"
      }
    ]
  }
}

Analysis Script

#!/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 celebrating

Install command

One-click installPick a runner, click Copy, paste into your terminal, press enter

npx skills add proffesor-for-testing/agentic-qe/.claude/skills/skill-stats -y

Open general install guide

View skill source

Works with

Claude Code
Cursor
Cline
Codex
Windsurf
Gemini
OpenCode
Roo Code
AAide
+Augment
GitHub Copilot
OpenClaw
KKiro
Junie
WWarp
Goose
Trae
Kilo Code
OpenHands
Amp
Zencoder
CContinue
AIAider
CodeBuddy
CodeGeeX
Replit Agent

Security audit

88 / 100

Community

未声明 license/许可。
未声明 version。
未限定 allowed-tools，默认拥有全部工具权限。

Metadata

Source: github
proffesor-for-testing/agentic-qe
中文

More by @proffesor-for-testing

A Skill Builder 88

Category & tags

Category Engineering