A writing skill for tracking foreshadowing, where an early detail hints at a later event, including the Chekhov's gun idea that an important setup should eventually matter.

It is for logging clues, listing unresolved setups before writing, recording their planned resolution chapters, prioritising major clues, and showing their status in a dashboard.

It helps prevent clues and story promises from being forgotten or left unresolved by recording where each setup appears and where it pays off.

How PTCuong-1102/story-architect-mcp configures Claude Code and Codex

Reuse

Borrowing it

Nothing to install: this file belongs to PTCuong-1102/story-architect-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/PTCuong-1102/story-architect-mcp/main/.agents/skills/arc-planner/SKILL.md

Clone the repo

git clone --depth 1 https://github.com/PTCuong-1102/story-architect-mcp

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/ptcuong-1102/story-architect-mcp/arc-planner/github.svg)](https://agentmods.dev/skills/ptcuong-1102/story-architect-mcp/arc-planner)

Your own site

<a href="https://agentmods.dev/skills/ptcuong-1102/story-architect-mcp/arc-planner"><img src="https://agentmods.dev/badge/skills/ptcuong-1102/story-architect-mcp/arc-planner/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/ptcuong-1102/story-architect-mcp/arc-planner"><img src="https://agentmods.dev/badge/skills/ptcuong-1102/story-architect-mcp/arc-planner.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 0 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,503 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00000	$0.01503
Opus 5	$0.00000	$0.00751
Sonnet 5	$0.00000	$0.00301
Haiku 4.5	$0.00000	$0.00150

Measured 11d ago against content hash ace451f31b04, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

arc-planner scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 11d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.agents/skills/arc-planner/SKILL.md · 97 lines

How it starts

The opening of the file, as written. The whole thing — 97 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Arc Planner — Kiến trúc sư cốt truyện & nhịp độ

Kỹ năng này biến AI thành Nhà thiết kế cấu trúc Arc và nhịp độ chuyên nghiệp: lên kế hoạch từng Arc tiểu thuyết với cấu trúc phân cảnh rõ ràng, đặt chỉ tiêu nhịp độ (Action/Dialogue/Description), kiểm soát đường cong căng thẳng, hỗ trợ nối phân cảnh (story_append_scene) và trực quan hóa toàn bộ Arc bằng HTML Visual Dashboard.

🎯 NGUYÊN TẮC HOẠT ĐỘNG CỐT LÕI

CẤU TRÚC 3 CỤM (Three-beat structure):
- Mỗi Arc có Set-up (thiết lập) → Rising action (leo thang xung đột) → Climax/Resolution (cao trào & hạ màn).
- Mỗi Scene trong Arc theo nhịp Goal → Conflict → Disaster/Turn.
NHỊP ĐỘ THEO LOẠI CẢNH (Pacing by scene type):
- Cảnh hành động/kịch tính: tỷ lệ Action cao, câu ngắn, nhịp gấp.
- Cảnh tâm lý/tả cảnh: tỷ lệ Description cao, câu dài, chậm rãi.
- Không để một chương toàn hành động (mệt) hoặc toàn tả cảnh (chán).
ĐO LƯỜNG & TRỰC QUAN HÓA (Measure & Visualize):
- Dùng story_analyze_pacing và story_analyze_sentiment để so sánh nhịp độ và cảm xúc thực tế với chỉ tiêu đặt ra.
- Dùng story_generate_dashboard để quan sát toàn bộ tiến độ và biểu đồ nhịp độ/cảm xúc của Arc.
QUAN HỆ LÀ ĐỘNG CƠ XUNG ĐỘT (Relationships drive conflict):
- Tham khảo story_map_relationships để biết xung đột tiềm năng nào có thể khai thác trong Arc.

📋 WORKFLOW LẬP KẾ HOẠCH ARC (5 BƯỚC)

Bước 1: Khảo sát hiện trạng (Survey)

Chạy story_stats để nắm tổng số từ, số chương, tiến độ so với targetWordCount.
Truy vấn story_query_context về các tuyến nhân vật và địa điểm sẽ tham gia Arc.

Bước 2: Xác định mục tiêu Arc & Tuyến truyện (Arc Goal & Storyline Threads)

Xác định xung đột trung tâm, mục tiêu nhân vật, và điểm lật (turning point) cuối Arc.
Phân chia các tuyến truyện song song (Threads/Subplots) nếu có.

Bước 3: Phân chia phân cảnh (Scene Breakdown)

Chia Arc thành các chương; mỗi chương 2–4 Scene.
Với mỗi Scene, định nghĩa Goal, Conflict, Disaster/Turn và đặt chỉ tiêu nhịp độ sơ bộ.

Read the full file on GitHub · 97 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

11d ago First seen · 97 lines · 0 tokens per session scan A ace451f31b04

Subscribe to this mod's changes

arc-planner is a skill published in the GitHub repository PTCuong-1102/story-architect-mcp (0 stars, last pushed 8d ago), licensed MIT. It costs nothing until one of its globs matches a file; then it loads 1,503 tokens. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-31.

Writing and docs

systematic-debugging

Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.

obra/superpowers · 21 tokens

local-ai-agents

Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…

microsoft/ai-agents-for-beginners · 200 tokens

next-cache-components-adoption

Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…

vercel/next.js · 95 tokens

insight-error-page

Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…

vercel/next.js · 83 tokens

next-cache-components-optimizer

Drive a Next.js route to instant navigation by setting up an agentic loop, under Cache Components / PPR, on initial load (hard navigation) and client-side navigation (soft navigation). Encode the goal as a failing @next/playwright instant() e2e and work it to green, one verified route at a time; the shipped test then…

vercel/next.js · 170 tokens

next-partial-prefetching-adoption

Turn on Partial Prefetching in a Next.js app and work through the insights it surfaces. Use when the user wants to enable or adopt Partial Prefetching, flip the partialPrefetching flag, opt routes in with export const prefetch = 'partial', audit Link prefetch={true} behavior, preserve existing prefetched UI with…

vercel/next.js · 103 tokens

story-architect-mcp: Skill for Claude Code