define-your-role-literal

Derives and defends canonical compound-word persona names for Martinez Methods thread roles.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Naming AI thread personas consistently across sessions is ad hoc and unverifiable. This Skill enforces a verbatim naming spec (first name, middle initial, multiplicative-meaning compound last name, version tag) with structured defense, rejected alternatives, and approval gates before any commit or propagation. ## Core Features & Use Cases - Structured name derivation: Determines first name (Claudette for coding, Clauda otherwise), middle initial from platform (W/L), and a compound last name whose meaning is multiplicative rather than additive. - Axis-by-axis defense: Evaluates the chosen name against 8 structural-genius properties with claim-plus-evidence tables, plus at least 6 rejected alternatives with refusal rationale and at least 4 honest gaps. - Gated execution pipeline: Three explicit approval gates separate presentation, artifact authoring with ASAE strict-3 audit and commit, and cross-repo propagation via shell scripts. - Use Case: When starting a new Martinez Methods workstream thread, invoke the skill to produce a canonical persona name like "Clauda W. Value Genius v03" with full lineage documentation, then commit and propagate the lock-in skill to other repos. ## Quick Start Invoke the skill by typing "/define your role - literal" to derive and defend a canonical persona name for the current thread.

Frequently Asked Questions about define-your-role-literal

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

FAQPage Schema
How do I define a canonical persona name for an AI thread?

Invoke the skill with "/define your role - literal" and it derives a full name from the naming spec: first name by workstream type, middle initial by platform, and a compound last name with multiplicative meaning. It presents the defense and waits for approval before committing anything.

What is multiplicative meaning in compound name design?

Multiplicative meaning means the compound creates a new concept neither word names alone, so losing either leg collapses the role's purpose. Names that read too plausibly as simple adjective-noun combinations are rejected as additive.

When should I skip the role-definition skill?

Skip it for utility threads where naming overhead exceeds task value, threads invoking an existing locked-in role, or when Krystal explicitly directs a different naming approach. Lightweight Clauda or Claudette without a compound last name suffices for one-off tasks.

Does the skill commit changes without approval?

No. Three explicit approval gates separate presentation, artifact authoring with commit, and cross-repo propagation. The skill refuses to proceed past each phase without Krystal's explicit confirmation.

What commit requirements does the role-definition workflow enforce?

Commits require a Clauda or Claudette persona trailer, an ASAE-Gate strict-3-PASS trailer, and a staged audit log with identical-pass markers across three consecutive evaluation blocks, enforced by the commit-msg hook.