author-role-propagation-script

Generates bash scripts that propagate persona role manifests and lock-in skills to consumer repositories.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Authoring Martinez Methods personas requires distributing role-manifest YAML and lock-in skill artifacts across multiple consumer repositories, and hand-writing the propagation bash script for each persona is repetitive and error-prone. ## Core Features & Use Cases - Per-role script generation: Produces a dedicated propagate-role-skill-<lastname-kebab>.sh script with target repo list, manifest copy, and lock-in skill copy logic. - Shared-script extension strategy: Recommends extending the shared propagate-role-skill.sh with a role-name argument when the persona follows the standard distribution pattern. - SSOT-wrangler advisory: Detects when daily-sync already covers distribution and exits with an advisory instead of generating a redundant script. - Use Case: During /define-your-role-literal Phase 8 step 4, generate a syntax-validated, executable propagation script that copies a new persona's role-manifest YAML and lock-in skill into three consumer repos. ## Quick Start Ask the assistant to author the role propagation script for a persona, providing the persona slug, lastname-kebab, and list of target consumer repositories.

Frequently Asked Questions about author-role-propagation-script

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

FAQPage Schema
How do I create a script to distribute persona artifacts across multiple git repositories?

Provide the persona slug, lastname-kebab, and list of target consumer repos. The skill generates a bash script that copies the role-manifest YAML and lock-in skill directory into each target, then validates it with bash -n and marks it executable.

When should I use a per-role propagation script versus the shared script?

Use the shared propagate-role-skill.sh extension when the persona has three or fewer targets and follows the standard distribution pattern. Choose a dedicated per-role script when there are more than three targets or persona-specific propagation logic.

Do I need a propagation script if SSOT-wrangler daily-sync is configured?

No. When the role-manifest and lock-in skill already live in the mm-claude-canonical submodule and targets are canonical consumers, daily-sync covers distribution and the skill emits an advisory instead of generating a script.

What are the limitations of the generated propagation scripts?

The v01 template hardcodes paths for a Windows Git Bash environment and does not auto-detect SSOT-wrangler coverage. Post-run verification that artifacts landed at targets is manual, with no automated success report.

How is the generated bash script validated before use?

The skill runs bash -n on the generated script to confirm syntax correctness, then applies chmod +x and writes it to _grand_repo/scripts/ under the persona-specific filename.