mcpbeat

Battle Test

hoangnguyen0403/battle-test

Deep audit of a skills directory against the Skill Creator standard. Produces a scored report and phased remediation plan.

613 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
536
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill battle-test

The instruction itself

9 sections, as written by the author

Battle Test Skill

> [!IMPORTANT]

> Deep audit of a skills directory against the Skill Creator standard. Produces a scored report and phased remediation plan.

Optional args: slug=<feature>, ticket=<id/url>, mode=interactive|autonomous|channel, channel=<id>, auto_continue=true|false, profile=business|hybrid|technical.

Instructions

When the user asks to perform this workflow, execute the following steps:

⚔️ Battle Test Orchestrator

> Goal: Evaluate every SKILL.md in the target directory against common-skill-creator. Deliver a quantified health report and prioritized remediation plan.


Step 1 — Target Discovery & Tech Stack

Identify the tech stack and all skill files.

# Count total skills per category
find . -name "SKILL.md" | sed 's|/[^/]*/SKILL.md||' | sort | uniq -c

Step 2 — Frontmatter Audit (Breadth Scan)

Run scans to detect format and structure violations.

  • Check for missing mandatory sections: grep -rL "triggers:\|priority:\|Anti-Patterns" <SKILLS>/
  • Check for broad glob triggers: grep -r "src/\*\*" <SKILLS>/
  • Check for length limits:

find . -name "SKILL.md" -exec awk 'END{if(NR>100) print FILENAME": "NR" lines"}' {} \;


Step 3 — Deep Audit & Scoring

Pick every P0 (CRITICAL) and a random sample of P1/P2 skills. Evaluate them against the Grading Rubric in:

<SKILLS>/common/common-skill-creator/references/rubric.md when synced.

  • Trigger Accuracy: File patterns + keywords?
  • Format Quality: No X: Do Y. anti-patterns?
  • Verification: Mandatory checklists?
  • Token Efficiency: Under 100 lines? Imperative mood?

Step 4 — Scored Report

Scoring Algorithm: Start at 100 points for each category. Apply deductions for findings (🔴-15 / 🟠-8 / 🟡-3 / 🔵-1).

📊 Report Format

Output the report using the Battle Test Report and Phased Plan templates in:

<SKILLS>/common/common-skill-creator/references/rubric.md when synced.


Step 5 — Interactive Follow-up

  • "Generate a task.md for Phase 1 remediation?"
  • "Fix the worst offender in [category] now?"
  • "Deep-dive audit on a specific category (e.g., security)?"

How to use it

Copy the folder

Take hoangnguyen0403/battle-test from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.