Automated summary

This skill enforces a strict verification gate after implementation by running the smallest strong set of checks and reporting the resulting evidence.

Strengths

Requires concrete evidence from tests and checks instead of a bare claim that work is done
Defines a clear loop: verify, report gaps, return to implementation on any blocking issue
Leverages `/verifier` to pick the most relevant checks without running everything
Establishes an explicit quality gate once a task has been marked complete

Limitations

Relies on `/verifier` being available along with the project's test commands
Does not specify which checks count as blocking or how to prioritize them
Kept deliberately short, with little guidance on how to format the evidence report

When to use it

Use it immediately after declaring a task done, to confirm with evidence that the implementation actually holds up.

When not to use it

Avoid it during exploration or fast prototyping, where the goal is to iterate rather than pass a strict verification gate.

Security analysis

Safe

Quality score78/100

The skill only provides procedural guidance for running verification checks and reporting results. It declares no tools, executes no commands, and contains no destructive, exfiltrating, or obfuscated behavior.

No concerns found

How this analysis is made

Examples

Verify a finished feature

I've finished the retry logic for the upload service and marked the task done. Run the verification gate now and tell me what passed and what's still missing.

Confirm before handing off

Before I open the PR, use /verifier to run the smallest strong set of checks on my changes and report the evidence, flagging anything blocking.

Back to implementation

Verification flagged a failing integration test. Show me the evidence, then tell me I need to return to implementation and what to fix.

name: verify-code description: Run a strict verification gate after implementation; provide evidence from tests/checks.

Verify Code

Name: Verify Code
Author: Skills Guide Bot

When to use

After tasks are marked done.

Instructions

Use /verifier to run the smallest strong set of checks.
Report what passed and what is missing.
If any blocking issue exists, return to implementation.

From the file to a first result

The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.

View the source and supporting files

This download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.

1. Download the file

Download SKILL.md

From the root of a test project, save the file as .skill-downloads/verify-code-mrzxur4s/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.

Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.

mkdir -p '.skill-downloads/verify-code-mrzxur4s' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/verify-code-mrzxur4s/download' --output '.skill-downloads/verify-code-mrzxur4s/SKILL.md.part' && mv '.skill-downloads/verify-code-mrzxur4s/SKILL.md.part' '.skill-downloads/verify-code-mrzxur4s/SKILL.md'

2. Check prerequisites

Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.

No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.

The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.

3. Load the skill

After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.

Claude Code

test -f '.skill-downloads/verify-code-mrzxur4s/SKILL.md' && test -s '.skill-downloads/verify-code-mrzxur4s/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/verify-code' && cp -R '.skill-downloads/verify-code-mrzxur4s' '.claude/skills/verify-code'

OpenSkills

OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.

Official OpenSkills installation

openskills install './.skill-downloads/verify-code-mrzxur4s'

openskills read 'verify-code-mrzxur4s'

Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.

For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.

openskills sync

Manual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.

4. Try a first task

Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:

Read .skill-downloads/verify-code-mrzxur4s/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.

Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.