aevatarai/story-control-panel
experimental/novel/agent_skills/story-control-panel/SKILL.md
Define what the Story Control Panel shows, how to compute signals, and how the author should act on alerts.
$ install --global
skillsauthnpx skillsauth add aevatarai/aevatar-agent-framework story-control-panelInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Mar 30, 2026, 5:37 PM55.0s1 file scanned
SKILL.md
- name:
- story-control-panel
- description:
- Define what the Story Control Panel shows, how to compute signals, and how the author should act on alerts.
When to use
- Author asks: “我现在这本书/这个 story 的状态怎样？后面哪里危险？哪些伏笔欠债？设定是否失控？”
Inputs (SSOT)
- Chapter text:
.txt - Other artifacts:
.md（大纲/台账/测试报告/偏离影响分析/会话日志） - SQLite: index only (rebuildable)
Output
- A dashboard-ready summary (for UI) with:
- Progress (Volume/Story/Chapter)
- Alerts (timeline/canon/test failures)
- Hotspots (canon rule usage heat, repeated confusion points)
- Backlog (setup/payoff debts)
Signals (v1 minimal)
- Progress
- Chapters drafted / reviewed / finalized
- Hard Alerts (must block auto-continue)
- Timeline contradiction
- Canon rule violation (explicitly tested)
- Narrative Tests failed (severity=ERROR)
- Soft Alerts (should suggest options)
- Too many unresolved setups (debt ratio)
- Persona “confusion” score spikes
Procedure (how to reason)
- Start from hard alerts → locate where it breaks → propose minimal fix vs branch rewrite.
- Then handle debt/backlog → propose payoff roadmap.
- Finally handle optimization signals (persona/style/pacing).
Related Skills
aevatarai/writing-journal
data-ai
VerifiedTrustedCommunity
Aggregate a writing session into a readable log + a reusable author-intent prompt.
11SKILL.mdUpdated Mar 27, 2026
aevatarai/setup-payoff-ledger
data-ai
VerifiedTrustedCommunity
Maintain a structured Setup/Payoff ledger (promises, debts, payoffs) and generate a payoff roadmap.
11SKILL.mdUpdated Mar 27, 2026
aevatarai/experimental/novel/agent_skills/rewrite-branch-merge
documentation
VerifiedTrustedCommunity
--- name: rewrite-branch-merge description: Manage rewrite branches: when to branch, how to compare, and how to merge back with minimal chaos. --- ## When to use - A change is risky (canon/timeline/payoff) and might break the mainline. - Author wants to explore multiple routes in parallel. ## Branching rules (simple, strict) - Branch if: - canon changes would require editing many existing chapters - timeline constraints are violated and fix is non-local - payoff plan changes the story’s
11SKILL.mdUpdated Mar 27, 2026
aevatarai/reader-personas
tools
VerifiedTrustedCommunity
Simulate multiple reader personas to score a chapter (爽点/困惑/信息负荷) and propose actionable alternatives.
11SKILL.mdUpdated Mar 27, 2026