story-clms-auditor
Use before reviews, defense, or deposit, or after evidence changes, to audit a thesis's numbers, comparisons, and degree-contribution claims against source anchors, the claim ledger, and fingerprinted evidence. Read-only on the manuscript and evidence. For citation keys and literature assertions, use story-cite-auditor.
- License 许可
- MIT
- 最近更新
- 2026-10-11
- Stars
- ★ 2
- Forks
- 0
01 前言 Front Matter
- name
- story-clms-auditor
- description
- Use before reviews, defense, or deposit, or after evidence changes, to audit a thesis's numbers, comparisons, and degree-contribution claims against source anchors, the claim ledger, and fingerprinted evidence. Read-only on the manuscript and evidence. For citation keys and literature assertions, use story-cite-auditor.
02 资源文件 1
- 参考文档agents/openai.yaml63 B
03 SKILL.md 正文
Audit claims and numbers
Shared conventions. Read docs/mds/story-workflow/writing-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/profile.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).
Read-only on manus/ and mates/. Audit the named chapter, one claim ID or a comma-separated list (C003,C007), or the whole thesis (full or no target).
- Follow each quantitative or comparative statement's source anchor and claim-ledger row (conventions §2), confirm the cited file is registered evidence, and re-read the value and its context in this run.
- For each imported slug the audited claims cite, run
bash execs/scpts/import.sh --diff --source <dir> --slug <slug>and read its per-file lines as conventions §3 does;<dir>is the entry's- source:minus the file's path undermates/<slug>/(## proj/results/a.csvwith- source: /work/proj/results/a.csvgives/work/proj). Route astale,tampered, ormissingfile tostory-evid-curator. - Set claim status by verdict (conventions §3, Who sets each status):
matched→verified, with the §3Notesstamp;mismatchedwith an author-confirmed narrower scope →weakened, noting the narrowing and the audit date, and still a failure line in## Claimsuntil a rerun finds the narrowed wordingmatched;unsourced, or any othermismatched→unsourceduntil the wording or evidence is corrected. Atlow, an unconfirmed narrower scope staysunsourced, with the proposed wording in the report. - Check that each degree contribution is supported across its mapped chapters, does not overstate the candidate's individual role, and uses claim strength fit for the confirmed degree level (conventions §1, Degree-level contract). Move its
Statusbetweenconfirmedandevidencedas §3 directs, promoting only in a thesis-wide run.
In the ledgers, change only the Status and Notes cells of notes/claims.md and a contribution's Status, routing every other fix to its owner (conventions §7, Ownership). Put detailed findings under wkdrs/reports/, and one checkbox per failure, keyed by claim ID or location, in ## Claims of tasks/audits.md, created on first use and reconciled for the keys this run audited (conventions §6, Feedback and promises); only a thesis-wide run sets its Last full run: to the system date.
04 同仓库更多 Skills
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.
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.
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.
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.
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.
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.