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.
npx skills add https://github.com/BaggaT236/AI-Trading-Skills --skill dual-axis-skill-reviewer
Run the dual-axis reviewer script and save reports to reports/.
The script supports:
--project-rootskills/*/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)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.mdCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
Use when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies
Replace with description of the skill and when Claude should use it.
Use when creating new skills, editing existing skills, or verifying skills work before deployment
This skill should be used when the user wants to "create a skill", "add a skill to plugin", "write a new skill", "improve skill description", "organize skill content", or needs guidance on skill structure, progressive disclosure, or skill development best practices for Claude Code plugins.
Use when executing implementation plans with independent tasks in the current session
Take baggat236/dual-axis-skill-reviewer 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.