skill benchmark

Engineering Community

Skill notes

Instructions

When the user asks to perform this workflow, execute the following steps: 📊 Skill Benchmark Orchestrator Goal: Quantify how much active skills improve implementation quality. Deliver a prioritized compliance delta and skill applicability report.

Step 1 — Project Context & Active Skills

Identify the tech stack and all active skills in AGENTS.md.

Step 2 — Auto-Select a Legacy Trap

Pick the file automatically. Rank candidates by the severity of anti-patterns: 🔴 P0: Hardcoded secrets; Logic inside UI components. 🟠 P1: Wrong Router pattern; Global state for local concerns; Missing design tokens. 🟡 P2: Raw user-facing strings (i18n).

Step 3 — Build Eval-Driven Scorecard

Source your scorecard from evals/evals.json, not from hardcoded patterns. Follow the Scorecard Rubric in <SKILLS>/common/common-skill-creator/references/benchmark.md when synced: Read <SKILLS>/<category>/<skill>/evals/evals.json. Generate columns for Failure Pattern and Success Pattern. Refactor the file, citing the exact skill rule for each change.

Step 4 — Benchmark Report & Compliance Delta

Output the scorecard and compliant score using the templates in <SKILLS>/common/common-skill-creator/references/benchmark.md when synced. Compliance Score Before vs After. Δ Delta: +Z% 🚀. Eval Alignment: How well does the skill teach what the eval tests?

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Engineering
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@HoangNguyen0403 · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1 — Project Context & Active Skills

Identify the tech stack and all active skills in `AGENTS.md`.

02
Step 2 — Auto-Select a Legacy Trap

Pick the file automatically. Rank candidates by the severity of anti-patterns: 🔴 P0: Hardcoded secrets; Logic inside UI components. 🟠 P1: Wrong Router pattern; Global state for local concerns; Missing design tokens. 🟡 P2: Raw user-facing strings (i18n).

03
Step 3 — Build Eval-Driven Scorecard

Source your scorecard from `evals/evals.json`, not from hardcoded patterns. Follow the Scorecard Rubric in `<SKILLS>/common/common-skill-creator/references/benchmark.md` when synced: Read `<SKILLS>/<category>/<skill>/evals/evals.json`. Generate columns for Failure Pattern and Success Pattern. Refactor the file, citing the exact skill rule for each change.

04
Step 4 — Benchmark Report & Compliance Delta

Output the scorecard and compliant score using the templates in `<SKILLS>/common/common-skill-creator/references/benchmark.md` when synced. Compliance Score Before vs After. Δ Delta: +Z% 🚀. Eval Alignment: How well does the skill teach what the eval tests?

05
Step 5 — Skill Applicability & Iteration

For every `❌ FAIL`, identify the root cause using the Iteration Table in: `<SKILLS>/common/common-skill-creator/references/benchmark.md` when synced. Signal not matching file? → Refine trigger. Rule too vague? → Add Anti-Pattern rule. Conflict? → Ensure P0 overrides P1.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.