Best for
- Need reproducible scoring for one skill in skills//SKILL.md.
- Need improvement items when final score is below 90.
- Need both deterministic checks and qualitative LLM code/content review.
tradermonty/claude-trading-skills/skills/dual-axis-skill-reviewer/SKILL.md
Review skills in any project using a dual-axis method: (1) deterministic code-based checks (structure, scripts, tests, execution safety) and (2) LLM deep review findings. Use when you need reproducible quality scoring for `skills/*/SKILL.md`, want to gate merges with a score threshold (for example 90+), or need concrete improvement items for low-scoring skills. Works across projects via --project-root.
Decision brief
Run the dual-axis reviewer script and save reports to reports/.
Compatibility matrix
| Platform | Status | Evidence | What to check |
|---|---|---|---|
| Codex | Not declared | No explicit evidence | Portability before use |
| Claude Code | Not declared | No explicit evidence | Portability before use |
| Cursor | Not declared | No explicit evidence | Portability before use |
| Gemini CLI | Not declared | No explicit evidence | Portability before use |
Installation
The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.
npx skills add https://github.com/tradermonty/claude-trading-skills --skill "skills/dual-axis-skill-reviewer"Inspect the Agent Skill "dual-axis-skill-reviewer" from https://github.com/tradermonty/claude-trading-skills/blob/51c790740048c4cbc9b7cc82a7f3ddc7b12d31d0/skills/dual-axis-skill-reviewer/SKILL.md at commit 51c790740048c4cbc9b7cc82a7f3ddc7b12d31d0. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.
Workflow
Determine the correct script path based on your context:
When reviewing a different project, point --project-root to it:
Use the generated prompt file in reports/skillreviewprompt.md.
Review the “Step 3: Merge Auto + LLM Axes” section in the pinned source before continuing.
Fix selection for reproducibility: --skill or --seed
Permission review
The documentation asks the agent to run terminal commands or scripts.
Run the dual-axis reviewer script and save reports to `reports/`.Evidence record
| Signal | Value | Evidence type | Meaning |
|---|---|---|---|
| Quality score | 92/100 | Computed | Documentation, specificity, maintenance, and trust rules |
| Repository stars | 2,715 | Source | Repository attention, not individual Skill quality |
| Compatibility | 0 platforms | Source | Declared in the catalog source record |
| Usage guide | automated source guide | Editorial | Generated or reviewed according to the visible evidence level |
Pinned source
Run the dual-axis reviewer script and save reports to reports/.
The script supports:
--project-rootskills-index.yaml production verification declarationsskills/*/SKILL.md.uv (recommended — auto-resolves pyyaml dependency via inline metadata)uv sync --extra dev or equivalent in the target projectDetermine the correct script path based on your context:
skills/dual-axis-skill-reviewer/scripts/run_dual_axis_review.py~/.claude/skills/dual-axis-skill-reviewer/scripts/run_dual_axis_review.pyThe examples below use REVIEWER as a placeholder. Set it once:
# If reviewing from the same project:
REVIEWER=skills/dual-axis-skill-reviewer/scripts/run_dual_axis_review.py
# If reviewing another project (global install):
REVIEWER=~/.claude/skills/dual-axis-skill-reviewer/scripts/run_dual_axis_review.py
uv run "$REVIEWER" \
--project-root . \
--emit-llm-prompt \
--output-dir reports/
When reviewing a different project, point --project-root to it:
uv run "$REVIEWER" \
--project-root /path/to/other/project \
--emit-llm-prompt \
--output-dir reports/
reports/skill_review_prompt_<skill>_<timestamp>.md.uv run "$REVIEWER" \
--project-root . \
--skill <skill-name> \
--llm-review-json <path-to-llm-review.json> \
--auto-weight 0.5 \
--llm-weight 0.5 \
--output-dir reports/
--skill <name> or --seed <int>--all--skip-tests--output-dir <dir>--auto-weight for stricter deterministic gating.--llm-weight when qualitative/code-review depth is prioritized.reports/skill_review_<skill>_<timestamp>.jsonreports/skill_review_<skill>_<timestamp>.mdreports/skill_review_prompt_<skill>_<timestamp>.md (when --emit-llm-prompt is enabled)When the target project has a skills-index.yaml entry with a complete verification block, JSON
and Markdown reports also show its declared axes, not_verified gaps, non-applicable axes, and
all_applicable_axes_passed. This section is informational only. It is excluded from auto/LLM/final
scores and does not replace a live high-severity issue check.
To use this skill from any project, symlink it into ~/.claude/skills/:
ln -sfn /path/to/claude-trading-skills/skills/dual-axis-skill-reviewer \
~/.claude/skills/dual-axis-skill-reviewer
After this, Claude Code will discover the skill in all projects, and the script is accessible at ~/.claude/skills/dual-axis-skill-reviewer/scripts/run_dual_axis_review.py.
knowledge_only skills and adjusts script/test expectations to avoid unfair penalties.skills/dual-axis-skill-reviewer/scripts/run_dual_axis_review.pyreferences/llm_review_schema.mdreferences/scoring_rubric.mdFrequently asked questions
Run the dual-axis reviewer script and save reports to reports/.
The source record exposes this install command: npx skills add https://github.com/tradermonty/claude-trading-skills --skill "skills/dual-axis-skill-reviewer". Inspect the command and pinned source before running it.
Static rules flagged exec-script in the source; the page lists the matching lines and excerpts.
Alternatives
garrytan/gbrain
End-to-end discipline for turning any large data source (audio libraries, email takeouts, document corpora, chat exports, API dumps) into brain pages at scale. The lifecycle spine: SCHEMA → ACCESS → TRIAL → EVALUATE → IMPROVE → CODIFY → TEST → SKILLIFY → BULK → MONITOR. State is tracked in a durable JSON manifest (see MANIFEST-PATTERN.md) so any crash, session boundary, or subagent fan-out resumes from ground truth instead of memory.
alirezarezvani/claude-skills
App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist
dotnet/skills
Migrates .NET test projects from VSTest to Microsoft.Testing.Platform (MTP). Use when user asks to "migrate to MTP", "switch from VSTest", "enable Microsoft.Testing.Platform", "use MTP runner", set OutputType=Exe only for test projects in Directory.Build.props, or mentions EnableMSTestRunner, EnableNUnitRunner, or UseMicrosoftTestingPlatformRunner. USE FOR: MTP behavioral differences vs VSTest (exit code 8, zero tests discovered, --ignore-exit-code, TESTINGPLATFORM_EXITCODE_IGNORE); centralizing
oaustegard/claude-skills
Generate hierarchical _FEATURES.md files that describe what a codebase DOES from a user/consumer perspective, anchored to source symbols via tree-sitting. Supports large complex codebases through feature-driven decomposition into sub-feature files. Uses a multi-pass synthesis: orientation → detail → overview rewrite. Use when someone says "what does this do", "document features", "feature inventory", "_FEATURES.md", or needs to understand a codebase's purpose before modifying it. Complements tre