team-narrative — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited team-narrative (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
When this skill is invoked, orchestrate the narrative team through a structured pipeline.
Decision Points: At each phase transition, use AskUserQuestion to present the user with the subagent's proposals as selectable options. Write the agent's full analysis in conversation, then capture the decision with concise labels. The user must approve before moving to the next phase.
Use the Task tool to spawn each team member as a subagent:
subagent_type: narrative-director — Story arcs, character design, narrative visionsubagent_type: writer — Dialogue writing, lore entries, in-game textsubagent_type: world-builder — World rules, faction design, history, geographysubagent_type: level-designer — Level layouts that serve the narrative, pacingAlways provide full context in each agent's prompt (narrative brief, lore dependencies, character profiles). Launch independent agents in parallel where the pipeline allows it (e.g., Phase 2 agents can run simultaneously).
Delegate to narrative-director:
Delegate in parallel:
Delegate to level-designer:
Delegate to narrative-director:
A summary report covering: narrative brief status, lore entries created/updated, dialogue lines written, level narrative integration points, consistency review results, and any unresolved contradictions.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.