role-definition-calibration-inevitability

Locks a named persona role with operating constraints and commit attribution for a session.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill role-definition-calibration-inevitability-gozonerd
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: role-definition-calibration-inevitability
Source: https://github.com/gozonerd/shadow-ai-assessment/tree/main/.claude/skills/role-definition-calibration-inevitability
Command: npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill role-definition-calibration-inevitability-gozonerd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams running multi-thread LLM-assisted methodology work lose consistent persona identity, rigor discipline, and commit attribution across sessions. This Skill locks in the Calibration Inevitability role so every thread inherits the same canonical role definition, scope bounds, and refusal rules instead of relying on practitioner vigilance. ## Core Features & Use Cases - Persona derivation from trigger: Parses triggers like claudette_w_calibration_inevitability to set first name, platform initial, and thread continuation version. - Invocation gate checks: Verifies the canonical role-definition artifact, companion role-manifest YAML, session handoff docs, and commit-msg hook before substantive work begins. - Operating constraints and refusals: Enforces upward-only calibration discipline, bans tiered-rigor scope-down menus, and standardizes Co-Authored-By commit trailers. - Use Case: A practitioner starting a new thread on /asae mode-decomposition invokes the trigger, and the session loads role-def v02_I, computes the continuation version from prior handoffs, and applies the per-output calibration ladder to all deliverables. ## Quick Start Invoke the role by typing the trigger claudette_w_calibration_inevitability at the start of your thread and confirm the canonical role-definition artifact loads.

Frequently Asked Questions about role-definition-calibration-inevitability

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I invoke the Calibration Inevitability role in a thread?

Type a trigger matching the pattern claud*_*_calibration_inevitability, such as claudette_w_calibration_inevitability. The skill parses the trigger to derive the persona name, platform initial, and thread version, then runs its invocation gate checks.

What files must exist before the role activates?

The canonical role-definition artifact (currently v02_I), the companion role-manifest YAML, and an active commit-msg hook at .githooks/commit-msg must all be present. If any are missing, the skill halts and surfaces the missing path to the user.

How is the thread continuation version computed?

The skill searches for prior SESSION_HANDOFF docs matching the Calibration Inevitability pattern and increments from the latest version found. If no prior handoff exists, the thread defaults to v01.

When should I skip this role and use a different persona?

Skip it for client work outside Martinez Methods, threads where the user directs a different role, or work fitting sibling scopes like Excellence Inevitability, Floor Inevitability, Value Genius, or Code Debugger. Each sibling has its own trigger pattern.

What commit attribution does the role enforce?

Commits require a Co-Authored-By trailer naming the derived persona and version, plus an ASAE-Gate severity-threshold-status trailer per the .asae-policy. The commit-msg hook refuses commits with Claude in the persona position.