Skip to content
SkillScript-led837 tokens in use

skill-integration-tester

Validates multi-skill workflows defined in CLAUDE.md: skill existence, JSON data contracts between steps, file naming and handoff integrity.

7,430 stars on the repository MIT Licensetradermonty/claude-trading-skills · skills/skill-integration-tester

Skill label

measured from its files

What installing skill-integration-tester costs

58tokens idle
837tokens in use
1,643tokens, up to

Idle is what sits in context while the skill is installed. In use is its instructions, loaded when it runs. Up to adds the files its instructions link. Counts are approximate, made offline with cl100k_base.

Model dependence Script-led

Script-ledMixedModel-led

Most of this skill is scripts, so it behaves much the same whichever model runs it.

This describes the skill's structure, how much of it is scripts. It does not say how well it works. Scripts: scripts/validate_workflows.py.

Touches

shelldetectedwrites filesdetected

Declared tags come from the skill's frontmatter; detected ones from its scripts, its code blocks and the commands it names in inline code. This is detected, not audited.

How it scores

Quality

How well the skill is written, counted from its own files: its frontmatter, its steps, examples, stated output and constraints, its size and whether every file it ships is one it names.How we score it →
Excellent
  • Frontmatter12/15
  • Structure22/25
  • Examples9/15
  • Output15/15
  • Size15/15
  • Resources10/15

Security

Starts at 100 and loses points for each thing in the skill's files that a reader should look at first.How we score it →
Excellent
  • Runs shell commands−5

    does this on the machine, and the frontmatter does not say so

    SKILL.md, line 38
  • Writes files−8

    does this on the machine, and the frontmatter does not say so

    scripts/validate_workflows.py, line 429

Repository health

Pre-computed score based on development activity, maintenance, community, maturity, and trend momentum.How we score it →
Good
  • Development activity100
  • Maintenance52
  • Community68
  • Maturity36
  • Momentum40

Skill Integration Tester parses the Multi-Skill Workflows section of a project’s CLAUDE.md, resolves each step to a skill directory and checks that the output of step N fits the input of step N+1. It also reports file naming violations and marks every workflow as valid, broken or warning.

A dry-run mode writes synthetic fixture JSON files so contracts can be checked without real data. It runs offline with the standard library, needs no API keys and only reads SKILL.md and CLAUDE.md files.

What You Get

  • A JSON report with totals of valid, broken and warning workflows
  • A Markdown report with step checks, handoff results (PASS, FAIL or N/A) and naming violations
  • Synthetic fixture files under reports/fixtures when run in dry-run mode
  • A contract reference describing handoff patterns between skills

Common Use Cases

  • Verifying pipeline health before releasing new skills
  • Debugging a broken handoff after changing a skill’s output format
  • Running as a pre-check in CI for pull requests that touch skill scripts

What Makes It Unique

It treats the workflow list in CLAUDE.md as the specification and tests the handoffs between skills deterministically, so the same inputs always give the same verdict. It never modifies any skill.

Under The Hood

A standard-library Python script reads CLAUDE.md and the SKILL.md files of the skills it resolves, with no network access. It writes timestamped JSON and Markdown reports, and in dry-run mode fixture JSON files, into a reports folder. The SKILL.md has the model run the script from the shell.

Join founders building with open source

Opinionated takes, migration guides, cost-saving tips, and insights from the open source ecosystem.

Subscribe on SubstackJoin 750+ subscribers