[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B166KA76QZXT80XXF9AEXP":3,"skill-same:01M7B166KA76QZXT80XXF9AEXP":48},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":47},"01M7B166KA76QZXT80XXF9AEXP","story-defn-builder",null,"Use for an applicable pre-defense or final defense. Plans, builds, and checks the thesis defense narrative, an editable slide deck, and a question bank from `verified` thesis claims, registered evidence, and confirmed timing and rules. For a mock examination report, use story-exam-reviewer.","wanghao9610\u002FSTORY","wanghao9610","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F53857938?v=4","01M7B13CG447X56WQM587XHEVK","Hao Wang","01M7B13CGRSPW02V06T50VYYD1",2,"MIT","https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fstory-defn-builder\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: story-defn-builder\ndisable-model-invocation: true\ndescription: Use for an applicable pre-defense or final defense. Plans, builds, and checks the thesis defense narrative, an editable slide deck, and a question bank from `verified` thesis claims, registered evidence, and confirmed timing and rules. For a mock examination report, use story-exam-reviewer.\nargument-hint: \"[MILESTONE] [DESCRIPTION] [involve=high]\"\n---\n\n# Build the degree defense\n\n**Shared conventions.** Read `docs\u002Fmds\u002Fstory-workflow\u002Fwriting-workflow-conventions.md` in full before acting. Read `.env` once for the `STORY_LANG`, `INVOLVE`, and `STORY_MAIN` values this run needs, and reuse them. Resolve the language of replies and new Markdown under conventions §7: an explicit author request first, then a valid `STORY_LANG`, then the dialogue language, read from the author's latest own prose and never from a bare command or the English this run loads, or the invocation language when there is no user turn. Manuscript prose follows `degree\u002Fprofile.tex`, and an existing file keeps its language. A clear instruction may select the target and scope and authorize the corresponding action within this skill's documented paths, and work already authorized in this run is not asked for again; it never replaces a confirmation point or an `AGENTS.md` §1 ask-first choice (conventions §7).\n\nResolve the degree level and the milestone: the one the invocation names, else the active one, when it is a `pre-defense` or `defense` milestone the confirmed program requires; otherwise ask. Create a missing `milestone.yml` or change its status only per conventions §6 (Milestone lifecycle). Timing, required sections, aspect ratio, deck format, and submission rules come only from `milestone.yml` or the author; an official template only from the author's copy in `template\u002F`; the rubric only from the milestone's `requirements_source`; and the audience from the milestone and the `Confirmed: yes` rows of `degree\u002Fcommittee.md`. Label any other audience or rubric as assumed.\n\n1. Write a defense plan under `miles\u002F\u003Cslug>\u002Fmaterials\u002F`: audience, one central message, timing budget, degree-appropriate contribution sequence, evidence for each major slide, transitions, limitations, and closing claims.\n2. Keep the editable deck source at `materials\u002Fdeck.\u003Cext>`. Build a LaTeX deck with `bash execs\u002Frun.sh --main miles\u002F\u003Cslug>\u002Fmaterials\u002Fdeck.tex` (into a self-ignoring `.build\u002F` beside it) and report its slide count against the timing budget; for another format, report the build as `not applicable` (conventions §8) and name the exported file checked.\n3. Trace every numeric or comparative slide claim to a `verified` claim and its registered evidence (conventions §2); report any other as a defense risk, not a slide. Reuse a thesis figure or table only if it stays legible in presentation conditions; a slide may simplify or redraw it but keeps every value, scale, baseline, and comparison of its evidence.\n4. Cover methods, assumptions, ablations where applicable, limitations, attribution, and future work in an appendix or question bank, then check timing, type size, contrast, source visibility, and consistency with the thesis and the rubric.\n\nPlan, slides, and speaker notes are committee-facing text (conventions §7). Write only under `miles\u002F\u003Cslug>\u002F`, and report unresolved defense risks explicitly.\n","# Build the degree defense\n\n**Shared conventions.** Read `docs\u002Fmds\u002Fstory-workflow\u002Fwriting-workflow-conventions.md` in full before acting. Read `.env` once for the `STORY_LANG`, `INVOLVE`, and `STORY_MAIN` values this run needs, and reuse them. Resolve the language of replies and new Markdown under conventions §7: an explicit author request first, then a valid `STORY_LANG`, then the dialogue language, read from the author's latest own prose and never from a bare command or the English this run loads, or the invocation language when there is no user turn. Manuscript prose follows `degree\u002Fprofile.tex`, and an existing file keeps its language. A clear instruction may select the target and scope and authorize the corresponding action within this skill's documented paths, and work already authorized in this run is not asked for again; it never replaces a confirmation point or an `AGENTS.md` §1 ask-first choice (conventions §7).\n\nResolve the degree level and the milestone: the one the invocation names, else the active one, when it is a `pre-defense` or `defense` milestone the confirmed program requires; otherwise ask. Create a missing `milestone.yml` or change its status only per conventions §6 (Milestone lifecycle). Timing, required sections, aspect ratio, deck format, and submission rules come only from `milestone.yml` or the author; an official template only from the author's copy in `template\u002F`; the rubric only from the milestone's `requirements_source`; and the audience from the milestone and the `Confirmed: yes` rows of `degree\u002Fcommittee.md`. Label any other audience or rubric as assumed.\n\n1. Write a defense plan under `miles\u002F\u003Cslug>\u002Fmaterials\u002F`: audience, one central message, timing budget, degree-appropriate contribution sequence, evidence for each major slide, transitions, limitations, and closing claims.\n2. Keep the editable deck source at `materials\u002Fdeck.\u003Cext>`. Build a LaTeX deck with `bash execs\u002Frun.sh --main miles\u002F\u003Cslug>\u002Fmaterials\u002Fdeck.tex` (into a self-ignoring `.build\u002F` beside it) and report its slide count against the timing budget; for another format, report the build as `not applicable` (conventions §8) and name the exported file checked.\n3. Trace every numeric or comparative slide claim to a `verified` claim and its registered evidence (conventions §2); report any other as a defense risk, not a slide. Reuse a thesis figure or table only if it stays legible in presentation conditions; a slide may simplify or redraw it but keeps every value, scale, baseline, and comparison of its evidence.\n4. Cover methods, assumptions, ablations where applicable, limitations, attribution, and future work in an appendix or question bank, then check timing, type size, contrast, source visibility, and consistency with the thesis and the rubric.\n\nPlan, slides, and speaker notes are committee-facing text (conventions §7). Write only under `miles\u002F\u003Cslug>\u002F`, and report unresolved defense risks explicitly.\n",{"name":5,"description":7,"argument-hint":24,"disable-model-invocation":25},"[MILESTONE] [DESCRIPTION] [involve=high]",true,"main","f76f6207f1ec06664927c7bd35e015ded2492294",".claude\u002Fskills\u002Fstory-defn-builder",0,"https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY","https:\u002F\u002Fwanghao9610.github.io\u002FSTORY\u002F","https:\u002F\u002Fgithub.com\u002Fwanghao9610","Leave the world a little different.","2026-10-11 20:45:09",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":25},[37,40,43],{"tool":38,"command":39},"npx","npx skills add wanghao9610\u002FSTORY --skill story-defn-builder",{"tool":41,"command":42},"bunx","bunx skills add wanghao9610\u002FSTORY --skill story-defn-builder",{"tool":44,"command":45},"pnpm","pnpm dlx skills add wanghao9610\u002FSTORY --skill story-defn-builder","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.claude\u002Fskills\u002Fstory-defn-builder\u002FSKILL.md",[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7B1F8ARGWXHQMPDTMA37GCD","story-tabs-builder","Use to build or revise one thesis table (results, comparisons, mappings, synthesis) from fingerprinted evidence, with a source anchor on every quantitative or comparative row and synchronized claim, outline, and notation records. For a design whose message depends on visual encoding, use story-figs-designer.","https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fstory-tabs-builder\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7B1F51A31HHMFKFZTH15HF9","story-syns-coach","Use before outlining, when the thesis lacks a coherent argument, or to record an author-supplied publication reuse or permission fact. Shapes the thesis problem, central argument, research questions, arc, synthesis, and degree contributions from the author's intent and registered evidence, with the contribution, publication, and claim maps. For chapter architecture, use story-outl-planner.","https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fstory-syns-coach\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7B1F21G24ZDVHBAE3HEJVBC","story-revs-resolver","Use after thesis feedback or an official outcome arrives from supervisors, coauthors, committees, examiners, defenses, corrections, or deposits. Converts it into an immutable-source point ledger, reasoned dispositions, tracked promises, and outcome records, without rewriting chapters. For a simulated review, use story-exam-reviewer.","https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fstory-revs-resolver\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},"01M7B1EY0M541ZQSSYE3KEE83H","story-refs-curator","Use when a thesis needs a trustworthy source record — add, verify, deduplicate, or re-check bibliography entries, write reading notes, or find candidates for a chapter's unsupported literature assertions, verifying only from records fetched in the run. For auditing what the manuscript already cites, use story-cite-auditor.","https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fstory-refs-curator\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},"01M7B1ESPP5X6E3HE3GCHXX34N","story-proj-adopt","Use when an existing thesis draft or Overleaf export should come under STORY. Inventories the draft, confirms a file map, copies (never moves) the source after the author commits a pre-adoption checkpoint, records the draft's claims, and verifies the resulting build without redesigning chapters. After adoption, story-syns-coach frames the thesis story.","https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fstory-proj-adopt\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},"01M7B1EP833P00G858ZEEWP81X","story-outl-planner","Use once the thesis story is finalized or the author chooses a provisional outline, and whenever chapter boundaries change. Turns the story and contribution map into chapter architecture, briefs, figure and table plans, and chapter scaffolds wired into the active entry point, mapping existing drafts instead of replacing them. For the thesis argument itself, use story-syns-coach.","https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fstory-outl-planner\u002FSKILL.md",[],[]]