Dual Axis Skill Reviewer
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.
MCP get_skill({ skillId: "dual-axis-skill-reviewer-e8dffebb" })Use this skill with your agent
Create a free account and connect via MCP
# Dual Axis Skill Reviewer Run the dual-axis reviewer script and save reports to `reports/`. The script supports: - Random or fixed skill selection - Auto-axis scoring with optional test execution - LLM prompt generation - LLM JSON review merge with weighted final score - Cross-project review via `--project-root` ## When to Use - 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. - Need to review skills in a **different project** from the command line. ## Prerequisites - Python 3.9+ - `uv` (recommended — auto-resolves `pyyaml` dependency via inline metadata) - For tests: `uv sync --extra dev` or equivalent in the target project - For LLM-axis merge: JSON file that follows the LLM review schema (see Resources) ## Workflow Determine the correct script path based on your context: - **Same project**: `skills/dual-axis-skill-reviewer/scripts/run_dual_axis_review.py` - **Global install**: `~/.claude/skills/dual-axis-skill-reviewer/scripts/run_dual_axis_review.py` The examples below use `REVIEWER` as a placeholder. Set it once: ```bash # 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 ``` ### Step 1: Run Auto Axis + Generate LLM Prompt ```bash uv run "$REVIEWER" \ --project-root . \ --emit-llm-prompt \ --output-dir reports/ ``` When reviewing a different project, point `--project-root` to it: ```bash uv run "$REVIEWER" \ --project-root /path/to/other/project \ --emit-llm-prompt \ --output-dir reports/ ``` ### Step 2: Run LLM Review - Use the generated prompt file in `reports/skill_review_prompt_<skill>_<timestamp>.md`. - Ask the LLM to return strict JSON output. - When running inside Claude Code, let Claude act as orchestrator: read the generated prompt, produce the LLM review JSON, and save it for the merge step. ### Step 3: Merge Auto + LLM Axes ```bash 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/ ``` ### Step 4: Optional Controls - Fix selection for reproducibility: `--skill <name>` or `--seed <int>` - Review all skills at once: `--all` - Skip tests for quick triage: `--skip-tests` - Change report location: `--output-dir <dir>` - Increase `--auto-weight` for stricter deterministic gating. - Increase `--llm-weight` when qualitative/code-review depth is prioritized. ## Output - `reports/skill_review_<skill>_<timestamp>.json` - `reports/skill_review_<skill>_<timestamp>.md` - `reports/skill_review_prompt_<skill>_<timestamp>.md` (when `--emit-llm-prompt` is enabled) ## Installation (Global) To use this skill from any project, symlink it into `~/.claude/skills/`: ```bash 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`. ## Resources - Auto axis scores metadata, workflow coverage, execution safety, artifact presence, and test health. - Auto axis detects `knowledge_only` skills and adjusts script/test expectations to avoid unfair penalties. - LLM axis scores deep content quality (correctness, risk, missing logic, maintainability). - Final score is weighted average. - If final score is below 90, improvement items are required and listed in the markdown report. - Script: `skills/dual-axis-skill-reviewer/scripts/run_dual_axis_review.py` - LLM schema: `references/llm_review_schema.md` - Rubric detail: `references/scoring_rubric.md`
Related Skills
More skills in Software Engineering
Accessibility Standards
Comprehensive web accessibility standards based on WCAG 2.2 AA, with 38+ anti-patterns, legal enforcement context (EAA, ADA Title II), WAI-ARIA patterns, and framework-specific fixes for modern web frameworks and libraries.
Accord
Authoring unified specification packages across Business/Development/Design teams via staged elaboration (L0 Vision → L1 Requirements → L2 Team Detail → L3 Acceptance Criteria). No code. Use when authoring cross-team specs, building L0-L3 packages, or aligning Biz/Dev/Design on a single source of truth.
Acquire Codebase Knowledge
Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
Acreadiness Assess
Run the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when asked to assess, audit, or score the AI readiness of a repo.
Acreadiness Generate Instructions
Generate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in the AI Tooling pillar.
Acreadiness Policy
Help the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights, CI gating, or wants org-wide standardisation.
Explore Other Categories
Skills from other categories with shared topics
Backtest Expert
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.
Breadth Chart Analyst
This skill should be used when analyzing market breadth charts, specifically the S&P 500 Breadth Index (200-Day MA based) and the US Stock Market Uptrend Stock Ratio charts. Use this skill when the user provides breadth chart images for analysis, requests market breadth assessment, positioning strategy recommendations, or wants to understand medium-term strategic and short-term tactical market outlook based on breadth indicators. Also works WITHOUT chart images by fetching CSV data directly from public sources. All analysis and output are conducted in English.
Breakout Trade Planner
Generate Minervini-style breakout trade plans from VCP screener output with worst-case risk calculation, portfolio heat management, and Alpaca-compatible order templates (stop-limit bracket for pre-placement, limit bracket for post-confirmation). Use when user has VCP screener results and wants actionable trade plans with entry/stop/target levels and position sizing.