This example uses a fictional bookmark so that the evidence boundary is explicit. The bookmark describes a source-backed review process for technical workflows. It does not represent a customer result or claim measured product performance.
Start with the saved claim
Before adopting a technical workflow from social media, separate the instructions from the claims, verify the claims with primary sources, and write a checklist that records the evidence.
The post contains a repeatable outcome, but it omits the evidence standard, report format, and stopping conditions. It needs research before it can become a reliable skill.
Qualify the candidate
| Category | Score | Reason |
|---|---|---|
| Repeatability | 2 | The post names an ordered review pattern. |
| Evidence | 1 | The source standard needs definition. |
| Safety | 2 | The workflow reviews information and does not install it. |
| Specificity | 1 | The output format is missing. |
| Reuse value | 2 | The review applies to many saved workflows. |
The candidate scores 8 out of 10 and has no automatic rejection. The missing evidence and output details must be resolved during research.
Define the evidence rules
The compiled workflow adds the following boundaries:
- Prefer official documentation and original research.
- Connect each material instruction to a source.
- Label an inference instead of presenting it as a sourced fact.
- Stop when a required claim cannot be verified.
- Do not execute or install the reviewed workflow.
Package the workflow
The resulting skill contains a short activation description, the review procedure, a report template, and the original source note:
x-bookmark-workflow-review/
├── SKILL.md
├── manifest.json
└── references/
├── report-template.md
└── source.mdTest the activation boundary
- Activate: “Review this saved deployment workflow and verify it before I use it.”
- Activate: “Separate the claims from the instructions in this technical thread.”
- Ask for input: “Review my bookmark” without a URL, export, or quoted content.
- Do not activate: “Summarize my bookmarks by topic.”
- Stop: A required claim has no reliable source.
Review the exact package
The reviewer inspects all files and approves the package checksum. A later change to the instructions, template, source note, or manifest produces a different checksum and requires another review.
View the public X bookmark workflow review repository, inspect the complete sample SKILL.md file and its review report template. To evaluate another candidate, use the bookmark qualification rubric.