Back to catalog
Human reviewedOther

Skill dossier

verification-before-completion

Source declaration

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

The author's original description, preserved in English. It describes intent, not verified performance.

Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always

Research summary

Human reviewed

Skill Atlas editorial baseline · editorial-0.1.0

A completion-gate Skill: before claiming success, require fresh evidence from tests, builds or observed behavior. It is designed to reduce unsupported completion claims.

Review scope

Deterministic static analysis of collected SKILL.md and supporting text/code. Machine-assisted candidates and findings await human editorial review; no dynamic behavior or effect is assessed.

Observable capabilities

  • Defines evidence before completion claims.
  • Separates implementation from verification.
  • Can be applied across code, docs and UI tasks.
  • Requires recorded commands or observations.

Limitations & scope

  • Evidence requirements can be misapplied if criteria are unclear.
  • May add extra steps to trivial tasks.
  • Actual agent compliance is not verified here.

Relevant for

  • Agents and teams that over-report completion
  • Code review workflows
  • Quality-focused development processes

What ships with the skill

The file inventory comes from the collected source at the recorded commit. Paths and sizes are structural observations, not a measure of quality.

files
1
Markdown files
1
scripts
0
references
0
Size
3.6 KB
Structural complexity
Low

File inventory

PathTypeBytes
skills/verification-before-completion/SKILL.mdInstruction3.6 KB

SKILL.md frontmatter

{
  "name": "verification-before-completion",
  "description": "Use when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions always"
}

A reading of the operating sequence

This workflow reconstructs the apparent sequence from source material. Unless controlled evaluation is explicitly recorded, it is provisional—not an observed trace.

  1. 01
    Input

    Confirm scope

    Read the trigger conditions and decide whether this skill matches the current task.

  2. 02
    Action

    Load instructions

    Claude Code reads the full SKILL.md when the skill is selected.

  3. 03
    Decision

    Use resources deliberately

    Read references or run scripts only when the documented workflow requires them.

  4. 04
    Output

    Deliver and verify

    Produce the requested artifact and verify it against the source-described acceptance criteria.

Potential risk surfaces

Static findings identify points to inspect before installation. They do not establish that a skill is safe, malicious, or effective.

No findings in static review

No configured lexical security patterns matched the collected text. This is not a security guarantee: obfuscation, binary-only files, dynamic behavior, and unknown risks remain unassessed.

Network accessNot observed
File writesNot observed
Credential useNot observed
No specific static findings recorded.

This does not prove the absence of risk. Review the source and choose an appropriate execution environment.

Editorial security note

No special runtime concern is apparent from the stated workflow; still inspect referenced scripts.

Where context can be spent

Discovery, activation, and resource layers have different meanings. Exact values appear only when the official token-counting method was run with a named model.

Exact token counts unavailable

All token values, including per-file inventory, are null until the pipeline performs an official exact count with an explicit model.

No token measurement was recorded with the required official method. This dossier does not substitute character counts, file sizes, or estimates.

Controlled evaluation

No controlled evaluation

This skill has only the evidence identified above. No task success, token efficiency, latency, or quality advantage is claimed.

Not tested

Use with the source in view

Install command
git clone https://github.com/obra/superpowers.git cd superpowers # Copy this skill directory into one of: # ~/.claude/skills/verification-before-completion # .claude/skills/verification-before-completion
  1. Open the immutable source at https://github.com/obra/superpowers/tree/22f0b463e7a5e579904dd6211a520321035526f7/skills/verification-before-completion/SKILL.md.
  2. Review the license, prerequisites and all bundled resources.
  3. Install the skill into a personal or project-level Claude Code skills directory.
  4. Restart or refresh Claude Code so the skill can be discovered.
Verify installation

Check that SKILL.md is discoverable at the destination, then ask Claude Code to use the named skill on a test task.

Prerequisites

  • Evidence requirements can be misapplied if criteria are unclear.
  • May add extra steps to trivial tasks.
  • Actual agent compliance is not verified here.

Example prompts

Representative task

Use the verification-before-completion skill to help with this task. First summarize what the skill will do, then execute its documented workflow and show the source-linked evidence for each major decision.

Inspect before use

Read the verification-before-completion skill files at https://github.com/obra/superpowers/tree/22f0b463e7a5e579904dd6211a520321035526f7/skills/verification-before-completion/SKILL.md. Explain its workflow, required tools, permissions and the main risks before I decide whether to install it.

A decision, with its limits attached

Strengths

  • Directly targets unsupported success claims.
  • Simple, reusable process rule.

Considerations

  • Needs clear acceptance criteria.
  • Can become ceremonial if evidence is not inspected.
Research conclusion

A worthwhile process guardrail when paired with concrete success criteria and real verification steps.

Traceable by construction

The dossier is a time-bound reading of a public artifact, not an endorsement. Use the source link to inspect the exact upstream material.

obrasuperpowersskills/verification-before-completion
Source type
Community
Commit
22f0b463e7a5e579904dd6211a520321035526f7
Collected
20 Nov 2026
Last checked
20 Nov 2026
Upstream license
MIT
Repository stars
322,183
Content basis

Deterministic lexical parsing, YAML frontmatter validation, file inventory, source-described workflow extraction, and heuristic provisional classification of the supplied files only. Generated by machine; no LLM, execution, dynamic testing, or human editorial approval.