Deep audit of a skills directory against the Skill Creator standard. Produces a scored report and phased remediation plan.
npx skills add https://github.com/HoangNguyen0403/agent-skills-standard --skill battle-test
> [!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.
When the user asks to perform this workflow, execute the following steps:
> Goal: Evaluate every SKILL.md in the target directory against common-skill-creator. Deliver a quantified health report and prioritized remediation plan.
Identify the tech stack and all skill files.
# Count total skills per category
find . -name "SKILL.md" | sed 's|/[^/]*/SKILL.md||' | sort | uniq -c
Run scans to detect format and structure violations.
grep -rL "triggers:\|priority:\|Anti-Patterns" <SKILLS>/grep -r "src/\*\*" <SKILLS>/find . -name "SKILL.md" -exec awk 'END{if(NR>100) print FILENAME": "NR" lines"}' {} \;
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.
No X: Do Y. anti-patterns?Scoring Algorithm: Start at 100 points for each category. Apply deductions for findings (🔴-15 / 🟠-8 / 🟡-3 / 🔵-1).
Output the report using the Battle Test Report and Phased Plan templates in:
<SKILLS>/common/common-skill-creator/references/rubric.md when synced.
task.md for Phase 1 remediation?"security)?"Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
Use when implementing any feature or bugfix, before writing implementation code
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes
Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always
Expert guidance for systematic backtesting of trading strategies. Use when developing, testing, stress-testing, or validating quantitative trading strategies. Covers "beating ideas to death" methodology, parameter robustness testing, slippage modeling, bias prevention, and interpreting backtest results. Applicable when user asks about backtesting, strategy validation, robustness testing, avoiding overfitting, or systematic trading development.
Cloud laboratory platform for automated protein testing and validation. Use when designing proteins and needing experimental validation including binding assays, expression testing, thermostability measurements, enzyme activity assays, or protein sequence optimization. Also use for submitting experiments via API, tracking experiment status, downloading results, optimizing protein sequences for better expression using computational tools (NetSolP, SoluProt, SolubleMPNN, ESM), or managing protein design workflows with wet-lab validation.
This skill should be used for time series machine learning tasks including classification, regression, clustering, forecasting, anomaly detection, segmentation, and similarity search. Use when working with temporal data, sequential patterns, or time-indexed observations requiring specialized algorithms beyond standard ML approaches. Particularly suited for univariate and multivariate time series analysis with scikit-learn compatible APIs.
Take hoangnguyen0403/battle-test from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
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.