Skill Trigger Doctor

    1

    Measure why a skill doesn't fire, rewrite its description with rules proven by before/after runs, and prove the fix.

    $7

    Secure checkout via Stripe

    Money-back guarantee

    Converts to your local currency at checkout

    Security scanned

    Works with the AI Agents you already use

    Claude CodeClaude CodeCursorCursorCodex CLICodex CLIMuseMuseDotsDots+21 more

    Skill Trigger Doctor

    Example session with this skill installed

    Two of my Claude Code skills never seem to fire. Find out why and fix what you can.

    • Read your context and instructions
    • Compiled the trigger doctor

    Summary

    Step 1 (triage) of the Doctor workflow: python3 scripts/skillcheck.py scan, static checks with no model calls. Both skills are switched off in settings, so this is a static problem, not wording. Output below is from a real run, paths shortened.

    == claude: 17 skills
      !   EASY                         ~/.claude/skills/EASY
           [info] Agent Skills spec (agentskills.io) names are lowercase letters, digits and hyphens; other agents may reject this name
      !   code-ref                     ~/.claude/skills/code-ref
           [info] settings.json skillOverrides is 'off': this skill is turned off
      !   search                       ~/.claude/skills/search
           [info] settings.json skillOverrides is 'off': this skill is turned off
      OK  deep-research                ~/.claude/skills/deep-research
      ...
    
    SkillFindingDoctor's next step (references/static-failures.md)
    code-refoff via skillOverridesthe user turned it off: ask before turning it back on
    searchoff via skillOverridessame
    EASYuppercase namefine in Claude Code; lowercase-hyphen if shared with other agents

    Next steps

    • Once a skill is back on, measure before touching wording: gen a suite with your own phrasings, run --tag before --runs 3.
    • A miss with "taken by: X" → rule R3 (state the boundary in both skills). A miss with nothing taken → R1 (slash-only wording) then R2 (literal phrasings).
    • Re-run on held-out prompts with --tag after and compare; revert anything that made another skill worse.

    Connects securely to your tools. The creator never sees your data.

    About this skill

    For skill authors and heavy users whose skills don't trigger, trigger on the wrong requests, or lose to another installed skill.

    What you get

    • A guided workflow the agent follows: triage → build a prompt set with your real phrasings → measure the baseline → rewrite → re-run on held-out prompts → before/after report.
    • Rewrite rules measured with real claude -p runs, applied in order. For example: slash-only wording (0/4 → 4/4 on held-out prompts), abstract categories vs literal phrasings (1/4 → 4/4), boundaries stated in both competing skills (2/3 → 3/3).
    • Description templates for task, gate/review and explain/style skills.
    • A guide to reading the report: boundary vs wording vs over-reach problems.
    • A preflight step: check a new skill against your installed ones before installing it.
    • The measuring tool (skillcheck, MIT, stdlib-only Python) bundled in scripts/.

    Rules the agent follows: change one description at a time, never claim a fix without a re-run, revert any edit that makes another skill worse.

    Limits

    • Measurement runs on your own Claude Code / Codex subscription, about a minute per prompt run; 5 skills × 6 prompts × 3 runs is roughly 90 minutes in the background.
    • The rules come from a limited set of measured cases; they say what to try first, not a guarantee.
    • Free version (measurement only): skillcheck on Agensi, or https://github.com/Noem836/skillcheck

    Requires Python 3 and your own Claude Code or Codex CLI. Fixes triggering through the description only, not the skill's internal logic. Claude runs load your installed skills and plugins but allow only the Skill tool; Codex runs skip your config, MCP, web and plugins, so Codex-plugin conflicts aren't measured.

    How to use

    1. 1

      Connect your agent to the Agensi MCP

      Copy the prompt and paste it into Claude, ChatGPT, Cursor or any agent that supports MCP. It sets up the connection for you. Manual setup

    2. 2

      Sign in to Agensi

      Your agent shows a sign-in link. Sign in and click Allow.

    3. 3

      Ask for what you need

      Your agent loads this skill and uses it on your task. It always asks before any payment.

    Reviews

    No reviews yet

    Be one of the first to try it. Every listed skill goes through the trust checks below.

    Security scanned

    Checked by our 8-point scan before listing

    Fresh listing

    Recently published to Agensi

    Money-back guarantee

    Doesn't do what its page promises? You get your money back.

    Trust & safety

    Security scan

    Security scan passed 20 days ago

    Requires

    GitHub
    Vercel
    Python 3
    Claude Code CLI or Codex CLI

    Permissions

    Terminal / Shell
    Network Access
    Read Files
    Write Files

    Allowed Hosts

    skillcheck-alpha.vercel.app
    github.com
    raw.githubusercontent.com

    Shell: runs python3 scripts/skillcheck.py and your claude/codex CLI. Reads your skill folders; writes suite.json, results and the HTML report in the current folder, and edits a SKILL.md description only after you agree. Network: only if the bundled script is missing (pinned download from GitHub), or a report upload when you run the upload command yourself.

    Listed20 days ago

    What's inside

    Frequently Asked Questions

    This skill is specifically optimized for Claude Code and Codex environments, focusing on the unique ways these CLI-based agents interpret skill descriptions and trigger logic.

    No, the tool is designed to diagnose and fix triggering reliability and conflicts via the description and metadata; it does not modify the underlying Python or JavaScript logic of your skill.

    You will receive the diagnostic workflow, the specialized `skillcheck.py` Python utility for CLI measurement, and a library of description refactoring templates.

    Yes. `preflight path/to/new-skill` lists likely clashes with your installed skills without any model calls (names, overlapping descriptions, listing budget). Add `--measure` to run the same prompts with and without the new skill in your real CLI and see if it takes requests away.

    Yes, the `skillcheck.py` utility requires a Python 3 environment to run the measurement tests and generate the comparative reliability reports.

    Unlike general prompting, this skill uses a data-driven measurement tool to provide empirical firing rates, ensuring your fixes are based on actual performance rather than guesswork.

    New in Prompt & Skill Engineering