[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79H7MPZB0KTWZBDFVN9NKP2":3,"skill-same:01M79H7MPZB0KTWZBDFVN9NKP2":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M79H7MPZB0KTWZBDFVN9NKP2","writing-introduction",null,"Use when drafting or rewriting a paper's Introduction — framing the problem, positioning against prior work, and stating contributions as checkable claims, grounded in the brief, notes, and the library. Reference rhetorical patterns, adapted to the paper — never applied as molds.","yibocat\u002Fprismnext","yibocat","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F98038316?v=4","01M79H3HDXFS2RDP1ED51TDF87","yibo","01M79H3HEG17B8ZH9AD0A06RBK",4,"MIT","https:\u002F\u002Fgithub.com\u002Fyibocat\u002Fprismnext\u002Fblob\u002Fmaster\u002Fresources\u002Fteams\u002Fprismnext.core\u002Fskills\u002Fwriting-introduction\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: writing-introduction\ndescription: Use when drafting or rewriting a paper's Introduction — framing the problem, positioning against prior work, and stating contributions as checkable claims, grounded in the brief, notes, and the library. Reference rhetorical patterns, adapted to the paper — never applied as molds.\nlicense: MIT\n---\n\n# Writing: Introduction\n\nThe Introduction is a contract with the reader: the problem, why it matters,\nwhat this document delivers, and where each promise is kept. Everything in\nit must be deliverable — every citation grounded, every contribution claim\nmapped to a section that proves it.\n\nIf `writing-design` produced `outline.md`, read it first: the story\nparagraph and the promise map are this section's spec. If there is no\noutline and this is a whole new document, propose the outline discussion\nfirst (`writing-design` when enabled); if the user wants to skip it, ask\nwhat the Introduction must promise — never draft from thin air.\n\n## When to use\n\n- Drafting or rewriting an Introduction \u002F opening section\n- Sharpening contributions from a finished draft (reverse-engineering the\n  promises)\n- Checking a draft Introduction against what the paper actually delivers\n\n## Files in this skill\n\n- `templates\u002Fproblem-driven.md` — the problem is widely felt; open with the\n  pain, then the gap, then the key observation.\n- `templates\u002Fcontribution-first.md` — the audience already knows the\n  problem; open with what is new, then situate.\n- `templates\u002Fstory-arc.md` — the contribution needs context to appreciate;\n  open with the evolving understanding that made the answer visible.\n\nThese are **reference patterns, not molds** — study them, take what fits,\nblend or depart as the material demands. The bar is an Introduction that\nreads true for this paper, not one that matches a file.\n\n## Workflow\n\n1. **Read the spec** — `outline.md` when present (story, audience, promise\n   map); otherwise `research-brief-read` plus a user conversation about the\n   document's promise.\n2. **Discuss the pattern with the user** — present the reference patterns with\n   one-line trade-offs. Use `question` when the call is genuinely theirs —\n   e.g. what the reader should remember after one read, anything to\n   emphasize or deliberately avoid; when the conversation already answers\n   these, do not re-ask.\n3. **Gather citations** — `literature-search` \u002F `literature-stage`; every\n   positioning claim gets a real bibkey or staged id. Broad survey-shaped\n   positioning belongs to `writing-related-work` when enabled — cite its\n   output, do not duplicate it.\n4. **Draft** — following the chosen pattern; contributions as one\n   checkable claim each (\"we show X improves Y under Z\"), never adjectives\n   (\"novel\", \"powerful\").\n5. **Consistency pass** — every promise maps to a section that keeps it\n   (the promise map); every section the outline says delivers something is\n   referenced by a promise. Flag mismatches instead of papering over them.\n6. **Verify** — `latex-compile` after edits.\n7. **Report to the outline** — when `outline.md` exists, mark this section\n   `done` with a one-line note; if the draft moved any promise, patch the\n   promise map and tell the user what changed.\n\n## Done when\n\n- Every citation traces to the library \u002F a staged paper this session.\n- Every contribution claim maps to a delivering section.\n- The reader can state the paper's promise after one paragraph.\n- `latex-compile` passes.\n\n## Rules\n\n- Never cite from memory — `literature-search` \u002F `literature-stage` first.\n- No result numbers without a run id (experiment receipts).\n- Promises the paper does not keep get deleted or downgraded to \"future\n  work\" — say which you did.\n","# Writing: Introduction\n\nThe Introduction is a contract with the reader: the problem, why it matters,\nwhat this document delivers, and where each promise is kept. Everything in\nit must be deliverable — every citation grounded, every contribution claim\nmapped to a section that proves it.\n\nIf `writing-design` produced `outline.md`, read it first: the story\nparagraph and the promise map are this section's spec. If there is no\noutline and this is a whole new document, propose the outline discussion\nfirst (`writing-design` when enabled); if the user wants to skip it, ask\nwhat the Introduction must promise — never draft from thin air.\n\n## When to use\n\n- Drafting or rewriting an Introduction \u002F opening section\n- Sharpening contributions from a finished draft (reverse-engineering the\n  promises)\n- Checking a draft Introduction against what the paper actually delivers\n\n## Files in this skill\n\n- `templates\u002Fproblem-driven.md` — the problem is widely felt; open with the\n  pain, then the gap, then the key observation.\n- `templates\u002Fcontribution-first.md` — the audience already knows the\n  problem; open with what is new, then situate.\n- `templates\u002Fstory-arc.md` — the contribution needs context to appreciate;\n  open with the evolving understanding that made the answer visible.\n\nThese are **reference patterns, not molds** — study them, take what fits,\nblend or depart as the material demands. The bar is an Introduction that\nreads true for this paper, not one that matches a file.\n\n## Workflow\n\n1. **Read the spec** — `outline.md` when present (story, audience, promise\n   map); otherwise `research-brief-read` plus a user conversation about the\n   document's promise.\n2. **Discuss the pattern with the user** — present the reference patterns with\n   one-line trade-offs. Use `question` when the call is genuinely theirs —\n   e.g. what the reader should remember after one read, anything to\n   emphasize or deliberately avoid; when the conversation already answers\n   these, do not re-ask.\n3. **Gather citations** — `literature-search` \u002F `literature-stage`; every\n   positioning claim gets a real bibkey or staged id. Broad survey-shaped\n   positioning belongs to `writing-related-work` when enabled — cite its\n   output, do not duplicate it.\n4. **Draft** — following the chosen pattern; contributions as one\n   checkable claim each (\"we show X improves Y under Z\"), never adjectives\n   (\"novel\", \"powerful\").\n5. **Consistency pass** — every promise maps to a section that keeps it\n   (the promise map); every section the outline says delivers something is\n   referenced by a promise. Flag mismatches instead of papering over them.\n6. **Verify** — `latex-compile` after edits.\n7. **Report to the outline** — when `outline.md` exists, mark this section\n   `done` with a one-line note; if the draft moved any promise, patch the\n   promise map and tell the user what changed.\n\n## Done when\n\n- Every citation traces to the library \u002F a staged paper this session.\n- Every contribution claim maps to a delivering section.\n- The reader can state the paper's promise after one paragraph.\n- `latex-compile` passes.\n\n## Rules\n\n- Never cite from memory — `literature-search` \u002F `literature-stage` first.\n- No result numbers without a run id (experiment receipts).\n- Promises the paper does not keep get deleted or downgraded to \"future\n  work\" — say which you did.\n",{"name":5,"license":15,"description":7},"master","bea8e76eec5d154324b095a78e731876fc136f75","resources\u002Fteams\u002Fprismnext.core\u002Fskills\u002Fwriting-introduction",0,"https:\u002F\u002Fgithub.com\u002Fyibocat\u002Fprismnext","https:\u002F\u002Fprismnext.pages.dev\u002F","https:\u002F\u002Fgithub.com\u002Fyibocat","Data Science and Artificial Intelligence","2026-09-05 14:31:57",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add yibocat\u002Fprismnext --skill writing-introduction",{"tool":39,"command":40},"bunx","bunx skills add yibocat\u002Fprismnext --skill writing-introduction",{"tool":42,"command":43},"pnpm","pnpm dlx skills add yibocat\u002Fprismnext --skill writing-introduction","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyibocat\u002Fprismnext\u002Fblob\u002Fmaster\u002Fresources\u002Fteams\u002Fprismnext.core\u002Fskills\u002Fwriting-introduction\u002FSKILL.md",true,[47,53,57],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"templates\u002Fcontribution-first.md","REFERENCE","参考文档",1291,"https:\u002F\u002Fgithub.com\u002Fyibocat\u002Fprismnext\u002Fblob\u002Fmaster\u002Fresources\u002Fteams\u002Fprismnext.core\u002Fskills\u002Fwriting-introduction\u002Ftemplates\u002Fcontribution-first.md",{"path":54,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":55,"sourceHtmlUrl":56},"templates\u002Fproblem-driven.md",1255,"https:\u002F\u002Fgithub.com\u002Fyibocat\u002Fprismnext\u002Fblob\u002Fmaster\u002Fresources\u002Fteams\u002Fprismnext.core\u002Fskills\u002Fwriting-introduction\u002Ftemplates\u002Fproblem-driven.md",{"path":58,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":59,"sourceHtmlUrl":60},"templates\u002Fstory-arc.md",1239,"https:\u002F\u002Fgithub.com\u002Fyibocat\u002Fprismnext\u002Fblob\u002Fmaster\u002Fresources\u002Fteams\u002Fprismnext.core\u002Fskills\u002Fwriting-introduction\u002Ftemplates\u002Fstory-arc.md",[62,70,77,84,91,98],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":66,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M79H88CRCDM6364CQV3AXTX8","demo-multi-file","Local test skill with an extra notes file","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fyibocat\u002Fprismnext\u002Fblob\u002Fmaster\u002Ftests\u002Ffixtures\u002Fskill-registry\u002Fdemo-multi-file\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M79H84P8BEMKYP2EAJEJ12QQ","writing-results","Use when drafting a Results \u002F Experiments \u002F Analysis section — narrating verified evidence from run receipts, with complete statistical reporting, derivation analysis, and honest treatment of negative results. Every number traces to a run; every claim survives the audit.","https:\u002F\u002Fgithub.com\u002Fyibocat\u002Fprismnext\u002Fblob\u002Fmaster\u002Fresources\u002Fteams\u002Fprismnext.core\u002Fskills\u002Fwriting-results\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M79H80M7D6BJJ0NFJ74589E4","writing-related-work","Use when drafting a Related Work \u002F literature review section or a standalone synthesis note — organizing prior work into a grounded, cited narrative or comparing methods across papers, from the project library plus staged external discovery. Never cites from memory.","https:\u002F\u002Fgithub.com\u002Fyibocat\u002Fprismnext\u002Fblob\u002Fmaster\u002Fresources\u002Fteams\u002Fprismnext.core\u002Fskills\u002Fwriting-related-work\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M79H7WTP45W9KJQKQHX22PBR","writing-preliminaries","Use when drafting a Preliminaries \u002F Background \u002F Notation section — definitions, problem setup, and formal statements the rest of the paper builds on, with notation consistency and machine-checked formal claims. Reference patterns, not molds; include only what later sections actually use.","https:\u002F\u002Fgithub.com\u002Fyibocat\u002Fprismnext\u002Fblob\u002Fmaster\u002Fresources\u002Fteams\u002Fprismnext.core\u002Fskills\u002Fwriting-preliminaries\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":19},"01M79H7RYRFZ3J74Z15JNG6FD6","writing-methods","Use when drafting a Methods \u002F Methodology \u002F Approach \u002F Model section — expounding the ideas and the reasoning behind the method, grounded in the project's brief, notes, and prior discussions, with empirical details from run receipts. Structure follows the idea's shape; reference angles, not fixed templates.","https:\u002F\u002Fgithub.com\u002Fyibocat\u002Fprismnext\u002Fblob\u002Fmaster\u002Fresources\u002Fteams\u002Fprismnext.core\u002Fskills\u002Fwriting-methods\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M79H7G95WZCW3VKF7EC5VM44","writing-design","Use when starting to write a paper, report, or any substantial document from the project's research — the outline gate. Discuss the story, audience, and section plan with the user and fix the outline on disk BEFORE any section is drafted. Not for revising a single existing section (use the section skill directly).","https:\u002F\u002Fgithub.com\u002Fyibocat\u002Fprismnext\u002Fblob\u002Fmaster\u002Fresources\u002Fteams\u002Fprismnext.core\u002Fskills\u002Fwriting-design\u002FSKILL.md",[],[]]