Verified:GitHub

role-definition-inspectable-inevitability

Name: role-definition-inspectable-inevitability
Availability: InStock
Author: gozonerd

Loads the Claudetta W. Inspectable Inevitability persona role-definition, mission, constraints, and refusals into thread context.

Updated Apr 11, 2026

Search Tags:#code review #quality control #github #verification #persona #prompt #role definition

Ready to run

npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill role-definition-inspectable-inevitability-gozonerd

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: role-definition-inspectable-inevitability
Source: https://github.com/gozonerd/shadow-ai-assessment/tree/main/.claude/skills/role-definition-inspectable-inevitability
Command: npx skills add https://github.com/gozonerd/shadow-ai-assessment --skill role-definition-inspectable-inevitability-gozonerd

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Continuing a long-running adversarial-review and structural-QC workstream across threads loses persona context, forcing repeated re-explanation of the role's mission, operating constraints, and refusals. This Skill restores the full role definition at thread start so the persona behaves consistently. ## Core Features & Use Cases - Persona Lock-In: Loads the canonical role-definition, role-manifest, mission (two legs: impose inspectable structure and verify claims-vs-reality), operating constraints, and refusals into thread context. - Trigger Pattern Matching: Activates on phrases like 'inspectable inevitability', 'lock in inspectable inevitability role', or 'structural QC steward', or via session handoff. - Governance Guardrails: Encodes refusals such as never bypassing verification gates, never shipping claims without evidence trails, and never guessing on genuine forks. - Use Case: When starting a new thread to continue GitHub-organization or adversarial code-review work, invoke the trigger phrase so the persona's full discipline and constraints are active from the first message. ## Quick Start Say 'lock in inspectable inevitability role' at the start of a thread continuing the structural-QC workstream.

Frequently Asked Questions about role-definition-inspectable-inevitability

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

FAQPage Schema

How do I activate the Inspectable Inevitability persona in a new thread?▼

Type a trigger phrase such as 'lock in inspectable inevitability role', 'inspectable inevitability', or 'structural QC steward' at thread start. The Skill loads the role-definition, mission, constraints, and refusals into context.

What does the Inspectable Inevitability role actually enforce?▼

It enforces structural quality-control: imposing inspectable structure and provenance on chaotic work, and verifying claims against reality before anything ships. It refuses to bypass verification gates or ship claims without evidence trails.

Can I switch to this persona mid-thread?▼

Yes. The Skill supports mid-thread invocation when the user wants to switch into the persona, not only at thread start. Session handoffs can also direct the role to load.

What are the limitations of a persona lock-in skill?▼

It only loads instructions into context; it cannot guarantee the model follows every constraint in long threads. It also depends on external canonical files like the role-definition and role-manifest remaining available and current.

Does this skill run scripts or modify files?▼

No. It is a prompt-only Skill consisting of a SKILL.md file with frontmatter and instructions. It has no scripts, references, or assets directories and performs no file modifications.