All Skills Library · Handover
sample-case-authoring
Labelled samples with inspectable limits.
- Version
- 1.0.0
- Lifecycle
- reference
- License
- Apache-2.0
- Published
- 2026-08-27
- Reviewed
- 2026-08-27
- Source
- witnessops/witnessops-web
content/witnessops/skills/sample-case-authoring/SKILL.md - Bytes
- 1014
- SHA-256
24b8897ab1dd242ada7d344abff1bc42c2db7ec99524f9d8306e1e427b761e2c
Plain view · SKILL.mdUTF-8 · exact download bytes
--- name: sample-case-authoring description: > Use when writing a public sample case or illustrative report. Every sample is labelled. It is not a live customer artifact. --- # Sample case authoring Examples exist so a buyer can inspect the shape before requesting work. ## Required labels - Labelled sample or illustration - Not a live customer artifact - Not a pentest, certification, or proof the system is secure ## Workflow 1. Pick one situation (launch, questionnaire, exposure, access change). 2. Write scope, evidence references, and limits. 3. Keep identifiers synthetic. 4. Link Verify a receipt or Check a Skill where a reader can actually try it. 5. Restate the example boundary at the foot of the page. ## Guardrails - Do not reuse real customer names, hosts, or hashes. - Do not hide the limitation in a footnote the reader will miss. - Do not imply the sample was independently re-verified in production. ## Outputs - sample page copy - synthetic artifacts - example boundary sentence