[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7B1C2HA15KFH7WH50VTZ4CS":3,"skill-same:01M7B1C2HA15KFH7WH50VTZ4CS":47},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":46},"01M7B1C2HA15KFH7WH50VTZ4CS","story-revs-resolver",null,"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.","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.kimi-code\u002Fskills\u002Fstory-revs-resolver\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: story-revs-resolver\ndisable-model-invocation: true\ndescription: 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.\n---\n\n# Resolve thesis feedback\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 milestone: the one the invocation names, else the active one, else ask; informal supervisor or coauthor feedback tied to no institutional event goes to `miles\u002Fsupervision\u002F` (conventions §6, Milestone lifecycle). When it is unclear which applies, ask at every level: copied feedback is never moved. Create a missing `milestone.yml`, change a milestone's status, or record an official outcome the author supplies only as that section says.\n\nCopy what the author supplies into `feedback\u002F` unchanged — never retyped, trimmed, or summarized — then read every file without editing it (conventions §6, Feedback and promises). A generated review enters the ledger only when the author explicitly asks, and a kept `wkdrs\u002Freports\u002FSIM_EXAM_\u003Cdate>.md` is first copied unchanged into `simulations\u002F`.\n\nIn the point ledger under `miles\u002F\u003Cslug>\u002Fresponse\u002F`, give each actionable point a stable ID, its exact source location, the affected chapters, claims, and contributions, one disposition, a rationale, an owner skill, and completion evidence; open and tick promise boxes in `tasks\u002F\u003Cslug>_promises.md`, keyed by point ID, as conventions §6 says. On a rerun, copy a ticked box's evidence into the point that becomes `completed`; record the disposition the author settles for a `needs-author` point, and tick its box unless the point became `planned`. Handle a conceded claim as conventions §3 (Who sets each status) assigns this skill.\n\nAsk before recording a `disagreed` point, conceding a claim mapped to a confirmed contribution, or finalizing committee-facing text (conventions §7); at `low`, record such a point as `needs-author`, leave such a claim unchanged, keep such text as a draft, and say so.\n\nNever rewrite chapters or alter received comments.\n","# Resolve thesis feedback\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 milestone: the one the invocation names, else the active one, else ask; informal supervisor or coauthor feedback tied to no institutional event goes to `miles\u002Fsupervision\u002F` (conventions §6, Milestone lifecycle). When it is unclear which applies, ask at every level: copied feedback is never moved. Create a missing `milestone.yml`, change a milestone's status, or record an official outcome the author supplies only as that section says.\n\nCopy what the author supplies into `feedback\u002F` unchanged — never retyped, trimmed, or summarized — then read every file without editing it (conventions §6, Feedback and promises). A generated review enters the ledger only when the author explicitly asks, and a kept `wkdrs\u002Freports\u002FSIM_EXAM_\u003Cdate>.md` is first copied unchanged into `simulations\u002F`.\n\nIn the point ledger under `miles\u002F\u003Cslug>\u002Fresponse\u002F`, give each actionable point a stable ID, its exact source location, the affected chapters, claims, and contributions, one disposition, a rationale, an owner skill, and completion evidence; open and tick promise boxes in `tasks\u002F\u003Cslug>_promises.md`, keyed by point ID, as conventions §6 says. On a rerun, copy a ticked box's evidence into the point that becomes `completed`; record the disposition the author settles for a `needs-author` point, and tick its box unless the point became `planned`. Handle a conceded claim as conventions §3 (Who sets each status) assigns this skill.\n\nAsk before recording a `disagreed` point, conceding a claim mapped to a confirmed contribution, or finalizing committee-facing text (conventions §7); at `low`, record such a point as `needs-author`, leave such a claim unchanged, keep such text as a draft, and say so.\n\nNever rewrite chapters or alter received comments.\n",{"name":5,"description":7,"disable-model-invocation":24},true,"main","f76f6207f1ec06664927c7bd35e015ded2492294",".kimi-code\u002Fskills\u002Fstory-revs-resolver",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":35,"prompt":45,"zipAvailable":24},[36,39,42],{"tool":37,"command":38},"npx","npx skills add wanghao9610\u002FSTORY --skill story-revs-resolver",{"tool":40,"command":41},"bunx","bunx skills add wanghao9610\u002FSTORY --skill story-revs-resolver",{"tool":43,"command":44},"pnpm","pnpm dlx skills add wanghao9610\u002FSTORY --skill story-revs-resolver","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.kimi-code\u002Fskills\u002Fstory-revs-resolver\u002FSKILL.md",[],[48,55,62,67,74,81],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"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":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"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":63,"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":64,"categories":65,"keywords":66,"publishedAt":19},"01M7B1F21G24ZDVHBAE3HEJVBC","https:\u002F\u002Fgithub.com\u002Fwanghao9610\u002FSTORY\u002Fblob\u002Fmain\u002F.qwen\u002Fskills\u002Fstory-revs-resolver\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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",[],[]]