evidence-report
Produce a standalone HTML report whose every claim is traced to its evidence. Use at a grilling convergence point, when reporting adversarial-review findings, at epic close-out, or whenever a decision, comparison, or set of findings needs to be presented to the user with sources they can check. Output is a single self-contained .html file in the repo, written in Traditional Chinese.
- License 许可
- MIT
- 最近更新
- 2026-11-12
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- evidence-report
- description
- Produce a standalone HTML report whose every claim is traced to its evidence. Use at a grilling convergence point, when reporting adversarial-review findings, at epic close-out, or whenever a decision, comparison, or set of findings needs to be presented to the user with sources they can check. Output is a single self-contained .html file in the repo, written in Traditional Chinese.
02 资源文件 2
- 参考文档agents/openai.yaml42 B
- 许可证LICENSE1.1 KB
03 SKILL.md 正文
Evidence Report
A report the user can audit. Every factual claim carries its source and a confidence tier, so the reader can tell what was verified from what was inferred without re-doing the work.
Reach for it when the output is a decision, a comparison, or a body of findings — the shapes where a reader needs to check the reasoning. Prose in the terminal is right for a status update.
Output contract
- One self-contained
.htmlfile. All CSS and JS inline, images asdata:URIs, zero external requests. Standalone means it opens offline, from a file path, in five years. - System font stack only. A webfont CDN degrades silently offline, which discards the typography
the report was designed with. Use
-apple-system, "Segoe UI", "PingFang TC", "Noto Sans TC", sans-serifand a matching serif or mono stack for secondary roles. - Location. Epic-scoped:
.proj.specs/<NNNN-epic-slug>/reports/<slug>.html. Project-scoped:.proj.specs/_reports/<slug>.html. Committed. - Language. Traditional Chinese, Taiwan usage — see
docs/agents/language.md. Technical terms that Taiwan practice keeps in English stay in English. - Naming. Descriptive:
q1-pipeline-cadence.html, notreport.html. A rewrite becomes<slug>-v2.html; keep the previous version.
The evidence table
Every report ends with a table listing each factual claim, its source, and its tier. Three tiers, and the distinction between them is the point of the report:
| Tier | Meaning |
|---|---|
| 已驗證 | Read the file, ran the command, saw the output. Cite path:line or the command. |
| 推論 | Derived from verified facts, not directly observed. Say what it was derived from. |
| 外部 | From the web or a document outside the repo. Cite the source. |
Two rules make the tiering worth trusting:
- Tier claims, not sentences. If a paragraph mixes an observed fact with an inference, it holds two claims and they get separate rows.
- State what the report does not claim. A short section naming what is out of scope stops an illustrative example from being read as a decision.
Structure
- The answer first. The recommendation or conclusion, before the reasoning.
- The question restated. What is actually being decided, and what depends on the answer.
- The body. Options, findings, or comparison — whatever the report is for.
- The evidence chain. Why the conclusion follows, as a traceable sequence rather than an assertion.
- The cost. What the recommendation gives up. A report that lists only upside is not auditable.
- The evidence table, plus the out-of-scope note.
- The decision the user has to make, stated as a question they can answer in one line.
Design
Design the page for its subject. The report is read once, carefully, by one person deciding something — that calls for typographic hierarchy, considered spacing, and a deliberate palette, not decoration.
- Encode information in structure. Numbered markers belong on an actual sequence; a severity stripe belongs on something with severity. A structural device that encodes nothing is noise.
- Pick the neutral. A grey biased slightly toward the accent reads as chosen; a pure mid-grey reads as a default.
- Spend boldness once. One accent, used where the reader's attention should land — usually the recommendation. Everything else stays quiet.
- Both themes. Define the full light palette on bare
:root, redefine the tokens under@media (prefers-color-scheme: dark), and set an explicitbackgroundonbody. A colour whose only definition sits inside a media query renders one theme's text on the other theme's ground. - Wide content scrolls in its own container. Tables and diagrams get
overflow-x: auto; the page body never scrolls sideways. - Avoid the generated look. Cream grounds with a serif display and terracotta accent, near-black with one acid-green pop, purple-to-blue gradient heroes, Inter or Space Grotesk as the safe face, emoji as section markers, everything centred, rounded cards with an accent rail. Where the user names a direction, follow it exactly.
Before handing it over
Open the file and confirm: it renders with no network, the evidence table's every row maps to a claim in the body, and each tier is honest — an inference labelled 已驗證 is the one failure that makes the whole report worthless.
Give the user the file path.
04 同仓库更多 Skills
writing-for-agents
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.
wizard
Generate an interactive bash wizard that walks a human through steps only they can perform. Use when provisioning infrastructure, setting up credentials or CI secrets, walking an unfamiliar third-party dashboard, or running a one-off migration or cutover. Don't invoke this for steps the agent can perform itself.
wayfinder
Plan a huge chunk of work (more than one agent session can hold) as a shared map of decision tickets on your issue tracker, and resolve them one at a time until the way to the destination is clear.
wait-what
Stop. That last message did not land: re-pitch it.
to-tickets
Break a plan, spec, or the current conversation into a set of tracer-bullet tickets, each declaring its blocking edges, published to the configured tracker (edges as text in one file per ticket locally, or native blocking links on a real tracker).
to-spec
Turn the current conversation into a spec and publish it to the project issue tracker: no interview, just synthesis of what you've already discussed.