Agent skill · Code Review & Quality

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.

BaggaT236github.com/BaggaT236GitHub ↗
claude-codeships scriptsMIT
Install
npx skills add BaggaT236/AI-Trading-Skills --skill dual-axis-skill-reviewer --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 6
SKILL.md size: 4 KB
Bundled scripts: yes
Path: skills/dual-axis-skill-reviewer/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 118
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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 reviewin

What's inside
Steps it walks through
  1. When to Use
  2. Prerequisites
  3. Workflow
  4. Step 1: Run Auto Axis + Generate LLM Prompt
  5. Step 2: Run LLM Review
  6. Step 3: Merge Auto + LLM Axes
  7. Step 4: Optional Controls
  8. Output
  9. Installation (Global)
  10. Resources
Ships with 5 files
  • references/llm_review_schema.md
  • references/scoring_rubric.md
  • scripts/run_dual_axis_review.py
  • scripts/tests/conftest.py
  • scripts/tests/test_run_dual_axis_review.py
Commands it runs
If reviewing from the same project:
If reviewing another project (global install):
uv run "$REVIEWER" \
ln -sfn /path/to/claude-trading-skills/skills/dual-axis-skill-reviewer \
More from AI-Trading-Skills
All skills →
About this skill
What does the dual-axis-skill-reviewer skill do?

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.

How do I install it?

Run `npx skills add BaggaT236/AI-Trading-Skills --skill dual-axis-skill-reviewer --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From BaggaT236/AI-Trading-Skills, a repository with 118 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going