author-role-manifest

Generates role-manifest YAML files defining persona scope bounds and allowed operations.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Personas in the Martinez Methods workflow need a machine-readable YAML manifest declaring their scope bounds, allowed paths, forbidden paths, and permitted operations so that commit-msg hooks can verify and enforce persona scope automatically. ## Core Features & Use Cases - Manifest Authoring: Produces a ~125-line role-manifest YAML with persona metadata, scope_bounds, allowed_repos, allowed_paths, forbidden_paths, and allowed_operations. - Scope-Bounds Heuristics: Applies family-based defaults (Clauda for non-coding docs paths, Claudette for coding repo paths) plus universal forbidden paths like secrets files. - YAML Validation: Validates the generated manifest with a YAML parser before writing it to the canonical role-manifests path. - Use Case: When defining a new persona via /define-your-role-literal Phase 8, invoke this skill to generate the manifest at role-manifests/<persona-slug>.yaml so Hook v05+ Tier 5 can verify its presence. ## Quick Start Ask the assistant to author a role-manifest YAML for a new persona, providing the persona slug, family, workstream, and scope bounds.

Frequently Asked Questions about author-role-manifest

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

FAQPage Schema
How do I create a role-manifest YAML for a new persona?

Invoke the skill with the persona slug, display name, family, version, and workstream. It applies family-based scope-bounds heuristics, composes the YAML, validates syntax, and writes it to role-manifests/<persona-slug>.yaml.

What fields does a persona role-manifest YAML contain?

The manifest contains persona metadata (slug, display_name, family, version, workstream) plus scope_bounds with allowed_repos, allowed_paths, forbidden_paths, and allowed_operations. Optional fields include audit_threshold, session_start_hooks, and related_personas.

Can I migrate an existing persona to the manifest format?

Yes, the skill supports standalone invocation for personas that already have a role-definition document but lack the YAML manifest. It prompts for missing context such as workstream and scope bounds before authoring.

How is the generated YAML validated?

The skill runs a YAML parser, either Node.js yaml.parse or Python yaml.safe_load, to confirm the file is syntactically valid before writing it to the canonical path.

What are the limitations of the default scope-bounds heuristics?

The family-based defaults (Clauda for docs paths, Claudette for code repos) are coarse starting points requiring per-persona refinement. The skill also does not validate that declared paths actually exist in the repository.