[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77STYHHX32FZAWDAK59MGGP":3,"skill-same:01M77STYHHX32FZAWDAK59MGGP":81},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":13,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M77STYHHX32FZAWDAK59MGGP","manuscript-engagement-analytics",null,"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.","ConcertoNotes\u002Fcodex-plugins","ConcertoNotes","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F249301288?v=4","01M77NJ0BK2KN5YW0D8RHD99TB","01M77NJ0CCEDPATAY3JTXEWNK5",0,"MIT","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fmanuscript-engagement-analytics\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: manuscript-engagement-analytics\ndescription: 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.\nlicense: MIT\ncompatibility: Codex, Claude Code, and other Agent Skills-compatible clients.\nmetadata:\n  version: \"0.1.0\"\n  displayName: Manuscript Engagement Analytics\n  category: Writing\n  tags: writing,books,nonfiction,analytics,reader-experience\n---\n\n# Manuscript Engagement Analytics\n\n## Core Lens\n\nReader 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.\n\nUse this skill to:\n\n- Generate heading-level word-count maps.\n- Find slow starts and long slogs.\n- Audit whether headings promise reader takeaways.\n- Interpret beta-reader comment locations and abandonment.\n- Produce a revision queue for value pacing.\n\n## Reference Routing\n\n| Need | Read |\n|------|------|\n| Engagement analytics concepts | `references\u002Fcore\u002Fknowledge.md` |\n| Analysis rules and thresholds | `references\u002Fcore\u002Frules.md` |\n| Example maps and findings | `references\u002Fcore\u002Fexamples.md` |\n| Fast audit checklist | `references\u002Fcore\u002Fchecklist.md` |\n| Step-by-step engagement audit | `workflows\u002Faudit-engagement.md` |\n\n## Script\n\nUse `scripts\u002Fanalyze_manuscript.py` for deterministic Markdown structure analysis:\n\n```bash\npython3 skills\u002Fmanuscript-engagement-analytics\u002Fscripts\u002Fanalyze_manuscript.py manuscript.md\n```\n\nIt 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.\n\n## Workflow\n\n### 1. Establish The Reader Promise\n\nIdentify the target reader, book promise, and first meaningful payoff. If these are unclear, use `book-toc-lab` first.\n\n### 2. Generate A Structure Map\n\nRun the script or manually build a table:\n\n```text\nSection | Line | Words | Cumulative words | Reader takeaway | Risk\n```\n\n### 3. Mark Value Events\n\nMark where the reader gets:\n\n- A usable idea.\n- A decision frame.\n- A checklist.\n- A worked example.\n- A lab or exercise.\n- A troubleshooting answer.\n\n### 4. Diagnose Engagement Risks\n\nLook for:\n\n- Too many words before first payoff.\n- Long sections with weak takeaways.\n- Back-to-back setup sections.\n- Vague headings that hide the reader value.\n- Beta-reader comments stopping near the same section.\n\n### 5. Recommend Revision Actions\n\nPrefer structural fixes:\n\n- Move value earlier.\n- Cut or compress low-payoff setup.\n- Rename headings around reader outcomes.\n- Split long sections.\n- Convert theory into examples, checklists, labs, or decisions.\n\n## Output Format\n\nWhen auditing engagement, return:\n\n1. Promise and first-payoff diagnosis.\n2. Value map or script output summary.\n3. Highest-risk sections.\n4. Revision recommendations ordered by expected engagement impact.\n5. Beta-reader comment\u002Fdropoff interpretation when data exists.\n6. Follow-up checks after revision.\n\n## Quality Bar\n\nUse 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.\n","# Manuscript Engagement Analytics\n\n## Core Lens\n\nReader 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.\n\nUse this skill to:\n\n- Generate heading-level word-count maps.\n- Find slow starts and long slogs.\n- Audit whether headings promise reader takeaways.\n- Interpret beta-reader comment locations and abandonment.\n- Produce a revision queue for value pacing.\n\n## Reference Routing\n\n| Need | Read |\n|------|------|\n| Engagement analytics concepts | `references\u002Fcore\u002Fknowledge.md` |\n| Analysis rules and thresholds | `references\u002Fcore\u002Frules.md` |\n| Example maps and findings | `references\u002Fcore\u002Fexamples.md` |\n| Fast audit checklist | `references\u002Fcore\u002Fchecklist.md` |\n| Step-by-step engagement audit | `workflows\u002Faudit-engagement.md` |\n\n## Script\n\nUse `scripts\u002Fanalyze_manuscript.py` for deterministic Markdown structure analysis:\n\n```bash\npython3 skills\u002Fmanuscript-engagement-analytics\u002Fscripts\u002Fanalyze_manuscript.py manuscript.md\n```\n\nIt 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.\n\n## Workflow\n\n### 1. Establish The Reader Promise\n\nIdentify the target reader, book promise, and first meaningful payoff. If these are unclear, use `book-toc-lab` first.\n\n### 2. Generate A Structure Map\n\nRun the script or manually build a table:\n\n```text\nSection | Line | Words | Cumulative words | Reader takeaway | Risk\n```\n\n### 3. Mark Value Events\n\nMark where the reader gets:\n\n- A usable idea.\n- A decision frame.\n- A checklist.\n- A worked example.\n- A lab or exercise.\n- A troubleshooting answer.\n\n### 4. Diagnose Engagement Risks\n\nLook for:\n\n- Too many words before first payoff.\n- Long sections with weak takeaways.\n- Back-to-back setup sections.\n- Vague headings that hide the reader value.\n- Beta-reader comments stopping near the same section.\n\n### 5. Recommend Revision Actions\n\nPrefer structural fixes:\n\n- Move value earlier.\n- Cut or compress low-payoff setup.\n- Rename headings around reader outcomes.\n- Split long sections.\n- Convert theory into examples, checklists, labs, or decisions.\n\n## Output Format\n\nWhen auditing engagement, return:\n\n1. Promise and first-payoff diagnosis.\n2. Value map or script output summary.\n3. Highest-risk sections.\n4. Revision recommendations ordered by expected engagement impact.\n5. Beta-reader comment\u002Fdropoff interpretation when data exists.\n6. Follow-up checks after revision.\n\n## Quality Bar\n\nUse 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.\n",{"name":5,"license":14,"metadata":23,"description":7,"compatibility":28},{"tags":24,"version":25,"category":26,"displayName":27},"writing,books,nonfiction,analytics,reader-experience","0.1.0","Writing","Manuscript Engagement Analytics","Codex, Claude Code, and other Agent Skills-compatible clients.","main","9ba3c9fadff1092395837bf1502e1b8a7f98b1e1","plugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fmanuscript-engagement-analytics","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins","https:\u002F\u002Fgithub.com\u002FConcertoNotes","2026-06-26 10:13:54",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add ConcertoNotes\u002Fcodex-plugins --skill manuscript-engagement-analytics",{"tool":41,"command":42},"bunx","bunx skills add ConcertoNotes\u002Fcodex-plugins --skill manuscript-engagement-analytics",{"tool":44,"command":45},"pnpm","pnpm dlx skills add ConcertoNotes\u002Fcodex-plugins --skill manuscript-engagement-analytics","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fmanuscript-engagement-analytics\u002FSKILL.md",true,[49,55,59,63,67,71,77],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"agents\u002Fopenai.yaml","REFERENCE","参考文档",243,"https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fmanuscript-engagement-analytics\u002Fagents\u002Fopenai.yaml",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fcore\u002Fchecklist.md",2165,"https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fmanuscript-engagement-analytics\u002Freferences\u002Fcore\u002Fchecklist.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fcore\u002Fexamples.md",2853,"https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fmanuscript-engagement-analytics\u002Freferences\u002Fcore\u002Fexamples.md",{"path":64,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Fcore\u002Fknowledge.md",3644,"https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fmanuscript-engagement-analytics\u002Freferences\u002Fcore\u002Fknowledge.md",{"path":68,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":69,"sourceHtmlUrl":70},"references\u002Fcore\u002Frules.md",2881,"https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fmanuscript-engagement-analytics\u002Freferences\u002Fcore\u002Frules.md",{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"scripts\u002Fanalyze_manuscript.py","SCRIPT","脚本",4819,"https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fmanuscript-engagement-analytics\u002Fscripts\u002Fanalyze_manuscript.py",{"path":78,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":79,"sourceHtmlUrl":80},"workflows\u002Faudit-engagement.md",2220,"https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fcommunity\u002Flvtd-skills\u002Fskills\u002Fmanuscript-engagement-analytics\u002Fworkflows\u002Faudit-engagement.md",[82,91,98,106,113,120],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":86,"licenseFileUrl":87,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M77YB7WW36DS9AERTWP673E0","android-emulator-qa","Use when validating Android feature flows in an emulator with adb-driven launch, input, UI-tree inspection, screenshots, and logcat capture.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Ftest-android-apps\u002Fskills\u002Fandroid-emulator-qa\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M77Y7AA8N45G6NM0WJSS2W9C","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.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsupabase\u002Fskills\u002Fsupabase-postgres-best-practices\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":86,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":18},"01M77Y2W5H5YGSW7MYWEJ8HYXD","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`.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsentry\u002Fskills\u002Fsentry\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Fsentry\u002Fskills\u002Fsentry\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":18},"01M77Y06GV1DAME7PN9KBFHWRX","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.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-workflows\u002FSKILL.md",[],[],{"skillNo":114,"name":115,"nameZh":6,"description":116,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":117,"categories":118,"keywords":119,"publishedAt":18},"01M77Y01A6RJA8VYT7CZ2TVETF","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.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-web-services\u002FSKILL.md",[],[],{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":18},"01M77XZW1AZ6B6NZTWWFVY72T3","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\u002FVue\u002FHugo\u002FGatsby 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.","https:\u002F\u002Fgithub.com\u002FConcertoNotes\u002Fcodex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fofficial\u002Frender\u002Fskills\u002Frender-static-sites\u002FSKILL.md",[],[]]