manuscript-engagement-analytics
Analyze nonfiction manuscripts for reader engagement signals, including heading-level word counts, slow starts, long slogs, weak takeaway titles, value pacing, beta-reader comment dropoff, and abandonment risks. Use when auditing a book, guide, manual, course-like draft, or technical manuscript for value density, reader experience, or beta-feedback engagement patterns.
- License 许可
- MIT
- 最近更新
- 2026-06-26
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- manuscript-engagement-analytics
- license
- MIT
- metadata
- { "tags": "writing,books,nonfiction,analytics,reader-experience", "version": "0.1.0", "category": "Writing", "displayName": "Manuscript Engagement Analytics" }
- description
- Analyze nonfiction manuscripts for reader engagement signals, including heading-level word counts, slow starts, long slogs, weak takeaway titles, value pacing, beta-reader comment dropoff, and abandonment risks. Use when auditing a book, guide, manual, course-like draft, or technical manuscript for value density, reader experience, or beta-feedback engagement patterns.
- compatibility
- Codex, Claude Code, and other Agent Skills-compatible clients.
02 资源文件 7
- 参考文档agents/openai.yaml243 B
- 参考文档references/core/checklist.md2.1 KB
- 参考文档references/core/examples.md2.8 KB
- 参考文档references/core/knowledge.md3.6 KB
- 参考文档references/core/rules.md2.8 KB
- 脚本scripts/analyze_manuscript.py4.7 KB
- 参考文档workflows/audit-engagement.md2.2 KB
03 SKILL.md 正文
Manuscript Engagement Analytics
Core Lens
Reader engagement can be approximated by mapping value over reading time. A manuscript with long stretches between useful payoffs, vague topic headings, or reader-comment dropoff is signaling where readers may get bored, confused, or stuck.
Use this skill to:
- Generate heading-level word-count maps.
- Find slow starts and long slogs.
- Audit whether headings promise reader takeaways.
- Interpret beta-reader comment locations and abandonment.
- Produce a revision queue for value pacing.
Reference Routing
| Need | Read |
|---|---|
| Engagement analytics concepts | references/core/knowledge.md |
| Analysis rules and thresholds | references/core/rules.md |
| Example maps and findings | references/core/examples.md |
| Fast audit checklist | references/core/checklist.md |
| Step-by-step engagement audit | workflows/audit-engagement.md |
Script
Use scripts/analyze_manuscript.py for deterministic Markdown structure analysis:
python3 skills/manuscript-engagement-analytics/scripts/analyze_manuscript.py manuscript.md
It outputs a table of headings, line numbers, word counts, cumulative words, and heuristic flags. Use the script output as evidence, then apply judgment from the references.
Workflow
1. Establish The Reader Promise
Identify the target reader, book promise, and first meaningful payoff. If these are unclear, use book-toc-lab first.
2. Generate A Structure Map
Run the script or manually build a table:
Section | Line | Words | Cumulative words | Reader takeaway | Risk
3. Mark Value Events
Mark where the reader gets:
- A usable idea.
- A decision frame.
- A checklist.
- A worked example.
- A lab or exercise.
- A troubleshooting answer.
4. Diagnose Engagement Risks
Look for:
- Too many words before first payoff.
- Long sections with weak takeaways.
- Back-to-back setup sections.
- Vague headings that hide the reader value.
- Beta-reader comments stopping near the same section.
5. Recommend Revision Actions
Prefer structural fixes:
- Move value earlier.
- Cut or compress low-payoff setup.
- Rename headings around reader outcomes.
- Split long sections.
- Convert theory into examples, checklists, labs, or decisions.
Output Format
When auditing engagement, return:
- Promise and first-payoff diagnosis.
- Value map or script output summary.
- Highest-risk sections.
- Revision recommendations ordered by expected engagement impact.
- Beta-reader comment/dropoff interpretation when data exists.
- Follow-up checks after revision.
Quality Bar
Use metrics as signals, not verdicts. Word counts and comment dropoff show where to inspect; the final recommendation should explain what reader value is missing, delayed, or unclear.
04 同仓库更多 Skills
android-emulator-qa
Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.
supabase-postgres-best-practices
Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.
sentry
Use when the user asks to inspect Sentry issues or events, summarize recent production errors, or pull basic Sentry health data via the Sentry API; perform read-only queries with the bundled script and require `SENTRY_AUTH_TOKEN`.
render-workflows
Sets up, develops, tests, and deploys Render Workflows. Covers first-time scaffolding (via CLI or manual), SDK installation (Python or TypeScript), task patterns (retries, subtasks, fan-out), local development, Dashboard deployment, and troubleshooting. Use when a user wants to set up Render Workflows for the first time, scaffold a workflow service, add or modify workflow tasks, test workflows locally, or deploy workflows to Render.
render-web-services
Configures Render web services—port binding, TLS, health checks, custom domains, auto-deploy, PR previews, persistent disks, and deploy lifecycle. Use when the user needs to set up a web service, fix health check failures, add a custom domain, configure zero-downtime deploys, or troubleshoot port binding issues.
render-static-sites
Deploys and configures static sites on Render's global CDN—build commands, publish paths, SPA routing, redirects, custom headers, and PR previews. Use when the user needs to deploy a static site, set up a React/Vue/Hugo/Gatsby frontend, configure SPA fallback routing, add redirect rules, customize response headers, or choose between a static site and a web service for their frontend. Trigger terms: static site, CDN, SPA, single-page app, React deploy, Vue deploy, Hugo, Gatsby, Docusaurus, Jekyll, staticPublishPath.