All authors
Claude Skills by MrBinnacle
github.com/MrBinnacle15 skills0 installs9 views
- Declared Synthetic Positive ControlDeclared synthetic positive control. Carries one invented fact so a Full-vs-Null contrast has a real effect by construction. Instrument validation only.Votes: 0GitHub stars: 13
- Pull RebaseUse before `git pull` where `pull.rebase` may be `true`. `--no-ff` does NOT stop a rebase under `pull.rebase=true` (silently ignored); it rewrites every local commit SHA. Check config first.Votes: 0GitHub stars: 12
- Push Secret ScanUse before `git push` where the repository holds config files. A `.gitignore` entry does NOT stop `git add -f` (silently accepted); a tracked `.env` publishes its credential to every clone. Scan tracked files first.Votes: 0GitHub stars: 12
- Parse CsvUse before opening a CSV where a column may hold IDs. Quoting does NOT stop a spreadsheet's number parse (silently applied); it drops every leading zero. Check the column type first.Votes: 0GitHub stars: 12
- Gap ScannerAudits AZIMUTH's coverage completeness. Cross-references what SKILL.md claims to handle against what reference, diagnostic, and domain-policy files actually cover. Identifies thin coverage, missing domains, and structural inconsistencies. Run before major version planning.Votes: 0GitHub stars: 8
- Reference AuthoringAuthoring discipline for new AZIMUTH reference files and templates. Use when adding a new domain reference file, extending an existing one, or creating a new template. Covers: (1) EXTEND vs. CREATE decision heuristic, (2) the Module 7 vocabulary header pattern that prevents domain-gap recurrence, (3) the sourcing caveat pattern for narrow-evidence-base files, (4) pre-verdict gate structure for templates. Validated by research-mpbaese4 (2026-05-18).Votes: 0GitHub stars: 8
- Research ScoutTracks AZIMUTH's 8 primary citation source families for new publications or significant updates. Stages validated findings in research/staged-findings.md for human review before promotion to references/base-rates.md. Invoke with 'run the research scout' or 'promote staged findings'.Votes: 0GitHub stars: 8
- Verdict AuditorStress-tests an AZIMUTH output against the skill's own structural rules. Paste an AZIMUTH output and invoke to get a severity-rated diagnostic. Diagnoses only — does not rewrite. Use after any real AZIMUTH session to detect quality drift.Votes: 0GitHub stars: 8
- EvalsDecision-quality pre-commitment analysis for initiative-level go/no-go calls with meaningful downside and limited reversibility — launches, rewrites, key hires, partnerships, strategic bets, timelines. Invoke when the user explicitly asks to pressure test, validate, or evaluate such a decision (e.g. 'should we do this,' 'pressure test,' 'go/no-go,' 'are we ready'). Do NOT invoke for routine code review, sub-task planning, reversible tactical choices, or pure ideation.Votes: 0GitHub stars: 8
- AzimuthDecision-quality pre-commitment analysis for initiative-level go/no-go calls with meaningful downside and limited reversibility — launches, rewrites, key hires, partnerships, strategic bets, timelines. Invoke when the user explicitly asks to pressure test, validate, or evaluate such a decision (e.g. 'should we do this,' 'pressure test,' 'go/no-go,' 'are we ready'). Do NOT invoke for routine code review, sub-task planning, reversible tactical choices, or pure ideation.Votes: 0GitHub stars: 8
- EvalsDecision-quality pre-commitment analysis for initiative-level go/no-go calls with meaningful downside and limited reversibility — launches, rewrites, key hires, partnerships, strategic bets, timelines. Invoke when the user explicitly asks to pressure test, validate, or evaluate such a decision (e.g. 'should we do this,' 'pressure test,' 'go/no-go,' 'are we ready'). Do NOT invoke for routine code review, sub-task planning, reversible tactical choices, or pure ideation.Votes: 0GitHub stars: 8
- EvalsDecision-quality pre-commitment analysis for initiative-level go/no-go calls with meaningful downside and limited reversibility — launches, rewrites, key hires, partnerships, strategic bets, timelines. Invoke when the user explicitly asks to pressure test, validate, or evaluate such a decision (e.g. 'should we do this,' 'pressure test,' 'go/no-go,' 'are we ready'). Do NOT invoke for routine code review, sub-task planning, reversible tactical choices, or pure ideation.Votes: 0GitHub stars: 8
- EvalsDecision-quality pre-commitment analysis for initiative-level go/no-go calls with meaningful downside and limited reversibility — launches, rewrites, key hires, partnerships, strategic bets, timelines. Invoke when the user explicitly asks to pressure test, validate, or evaluate such a decision (e.g. 'should we do this,' 'pressure test,' 'go/no-go,' 'are we ready'). Do NOT invoke for routine code review, sub-task planning, reversible tactical choices, or pure ideation.Votes: 0GitHub stars: 8
- EvalsDecision-quality pre-commitment analysis for initiative-level go/no-go calls with meaningful downside and limited reversibility — launches, rewrites, key hires, partnerships, strategic bets, timelines. Invoke when the user explicitly asks to pressure test, validate, or evaluate such a decision (e.g. 'should we do this,' 'pressure test,' 'go/no-go,' 'are we ready'). Do NOT invoke for routine code review, sub-task planning, reversible tactical choices, or pure ideation.Votes: 0GitHub stars: 8
- EvalsDecision-quality pre-commitment analysis for initiative-level go/no-go calls with meaningful downside and limited reversibility — launches, rewrites, key hires, partnerships, strategic bets, timelines. Invoke when the user explicitly asks to pressure test, validate, or evaluate such a decision (e.g. 'should we do this,' 'pressure test,' 'go/no-go,' 'are we ready'). Do NOT invoke for routine code review, sub-task planning, reversible tactical choices, or pure ideation.Votes: 0GitHub stars: 8