role-definition-reliability-compositor

Activates the Reliability Compositor persona and loads its canonical role-definition artifact for methodology-stack sessions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams working on the Martinez Methods methodology stack need a consistent, enforceable AI persona with explicit authority, constraints, and commit attribution. This Skill locks in the Clauda/Claudette W/L Reliability Compositor role so every session operates under the same governance rules instead of ad-hoc prompting. ## Core Features & Use Cases - Trigger-based persona derivation: Parses triggers like clauda_w_reliability_compositor to set first name (Clauda for non-coding, Claudette for coding), middle initial (W/L platform), and thread continuation version. - Invocation gate checks: Verifies the canonical role-definition artifact, session handoff docs, commit-msg hook v04, and environment/persona alignment before substantive work begins. - Operating constraints and refusals: Enforces branded terminology (FIXES, D2R 5-doc, ASAE-Gate trailers), axis-by-axis discipline, and explicit refusal of nearest-named-pattern flattening such as "AI SRE" shorthand. - Use Case: When starting a thread on FM enumeration, RATE design, or D2R specification, invoke the trigger so the session loads the canonical artifact, applies ASAE-Gate commit trailers, and authors producer-flavored methodology deliverables under the correct persona. ## Quick Start Invoke the skill by typing clauda_w_reliability_compositor at the start of a methodology-stack thread so the persona, constraints, and canonical role artifact are loaded before any work begins.

Frequently Asked Questions about role-definition-reliability-compositor

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

FAQPage Schema
How do I invoke the Reliability Compositor role in a thread?

Invoke it with a trigger matching clauda or claudette, then w or l, then reliability_compositor, such as clauda_w_reliability_compositor. The skill derives the persona from the trigger, loads the canonical role-definition artifact, and activates the operating constraints for the session.

What is the difference between Clauda and Claudette personas?

Clauda is the non-coding-dominant workstream persona used for taxonomy, governance, channel, and synthesis threads. Claudette is the coding-dominant persona used when implementing ASAE hooks or D2R-conformant code. The middle initial W or L indicates Windows or Linux platform.

When should I use Value Genius instead of Reliability Compositor?

Use role-definition-value-genius for defender-flavored work such as valuation defense, buyer-pitch artifacts, and IP discipline enforcement. Reliability Compositor authors producer-flavored deliverables like FM taxonomies, FIXES design, RATE primitives, and DRR evidence collection.

What happens if the canonical role-definition artifact is missing?

The invocation gate halts and surfaces the missing file path instead of proceeding. The skill expects the artifact at _grand_repo/docs following the Role_Definition_Clauda_W_Reliability_Compositor naming convention with date and version.

Why does the skill check for commit-msg hook v04?

The hook enforces persona attribution in Co-Authored-By trailers and ASAE-Gate compliance on every commit. Without core.hooksPath set to .githooks and the hook present, persona and ASAE enforcement is structurally absent, so the skill surfaces this to the user.