Skip to content
Skills Library
Programming · Testing

verify-examples

/verify-examples

Runs documentation examples, such as commands, code snippets, curl calls, and quickstarts, from their stated setup and checks the promised output. Use whenever someone asks whether the examples in a guide, README, or tutorial still work, without rewriting the whole document.

Repository
brundlefly ↗
Licence
MIT
Last repository change
14.10.2026

Assessment and security

95/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content30 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
2
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 14.10.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Runs documentation examples, such as commands, code snippets, curl calls, and quickstarts, from their stated setup and checks the promised output. Use whenever someone asks whether the examples in a guide, README, or tutorial still work, without rewriting the whole document.

Original author description

Runs documentation examples, such as commands, code snippets, curl calls, and quickstarts, from their stated setup and checks the promised output. Use whenever someone asks whether the examples in a guide, README, or tutorial still work, without rewriting the whole document.

How it works

  1. Establish the example contract
  2. Run the reader's path
  3. Repair and repeat
  4. Return the evidence
Original SKILL.md headings · 62 lines, 556 words
SKILL.md preview
---
name: verify-examples
description: "Runs documentation examples, such as commands, code snippets, curl calls, and quickstarts, from their stated setup and checks the promised output. Use whenever someone asks whether the examples in a guide, README, or tutorial still work, without rewriting the whole document."
license: MIT
---

# Verify examples

Check a reader's runnable examples against the documented starting state and promised result.
This pass owns example verification and requested repairs. It does not write or review the whole guide.
Follow the target's instructions, supported version, package manager, and documented checks.

## Establish the example contract

Read the example, surrounding instructions, prerequisites, and expected result.
If no example or document location is supplied, ask for it. Do not search for a replacement task.
Identify the runtime, package version, working directory, configuration, inputs, and required access.
Separate runnable code from pseudocode, schematic output, and illustrative fixtures.
If a core input is missing, report it before dependent execution.
Read matching source, exports, versioned CLI help, tests, and official documentation where needed.
Reconcile checkout behavior with the release the reader can install.
Use small private evidence notes for sources, checked revision, expected result, and unresolved questions.
Keep these evidence notes outside public content and generated downloads.

## Run the reader's path

Use a clean scratch project or the target's documented fixture where available.
Match the stated starting state. Do not rely on prior session setup.
Run the actual documented setup, commands, and inputs in order.
Use read-only inspection until state-changing execution is authorized.
Writing documentation does not authorize production writes, spending, installation, or sending messages.
For authorized changes, use an isolated environment where possible. Keep credentials out of code and captured output.

Observe exit status, output, and relevant side effects. Compare them with the promised result.
Check consequential conditions and response metadata, rather than only a successful command.
For a protocol example, inspect applicable status, headers, body, and conditions against its official specification.
Check documented cleanup and recovery for observed failures.
Derive checks from the requested scope and supporting evidence. Do not invent a broad edge-case suite.
Source inspection, lint, and builds cannot substitute for execution of the example.
A successful common path does not establish every supported platform or condition.

## Repair and repeat

For each failure, record expected behavior, actual observation, evidence, and the affected passage.
Distinguish a wrong instruction from unavailable access, tooling, or environment.
If repair is authorized, fix the smallest underlying mismatch in the example and dependent explanation.
If only a review was requested, return the repair proposal without editing files.
Keep the original example and observed failure in private evidence.
Repeat the failed check and any checks affected by the repair.
After editorial edits change a verified command or claim, repeat its affected checks.
Do not reuse an earlier revision's result to claim the final example works.

If execution is unavailable, inspect the best available evidence and name the untested path.
Do not fabricate output, silently substitute a different interface, or hide a failed check.
Report only actions actually performed. A tool with no result supplies no inspection evidence.
Mark illustrative output as illustrative. Keep an unsupported core reader path identified as a draft.

## Return the evidence

Predict attention for the handoff. Lead with failed reader paths and consequential limits; summarize routine successful checks.
Keep the verification thorough even when the report is brief.

State the version or revision, path that ran, observed outcome, and remaining limits.
Distinguish executed examples from examples checked only against source.
Keep detailed transcripts outside the public document. Report meaningful repairs when requested.
Verification does not grant permission to publish or deploy the result.
Files in this package (2)
  • LICENSE.txt 1 KB
  • SKILL.md 4 KB

Versions

The database has no other skills named verify-examples.

Database snapshot: 13.11.2026 · package version ec1359026fa6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100code-examples-sync
    Synchronize and verify code examples in documentation. Use when function signatures change, API interfaces update, imports shift, or documentation snippets become outdated and need correction.
  • 100audit-docs
    Audit README.md and docs/ for accuracy. Runs every documented code example, checks links, anchors, and prose rules, and verifies the CLI examples against the built gem. Use when documentation changes, before a release, or when the user asks to check the docs, verify code…
  • 100docs-and-examples
    Use when writing or updating README content, API examples, installation instructions, migration notes, or developer-facing documentation for a TypeScript library.
  • 100doc-generation
    Generates documentation for trading and financial code: strategy documentation, API references, usage examples, README files, and inline code comments. Trigger when the user wants to document trading code or generate project documentation.
  • 95readme
    When the user wants to create or update a README.md file for a project. Also use when the user says 'write readme,' 'create readme,' 'document this project,' 'project documentation,' or asks for he...
  • 100documentation-lookup
    Use when the user needs current library, framework, or API documentation and version-specific code examples.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.