Individual skill

create-verification-skill

Generate and prove a project-local verify skill that tells a later agent how to start this repo's real app, drive it through its user interface, capture evidence, and tear down, seeded with a feature map. Use on /create-verification-skill or "make a verify skill for this repo".

plugins/requie/endostack/skills/create-verification-skill/SKILL.md

Read pinned source

Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 4, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
1,532
Repository last updated
Nov 6, 2026
License
Apache-2.0

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# create-verification-skill

Write a skill inside the user's repo that lets a later agent start the real application, operate it the way a user does, and collect proof that a behavior works. The reader of the generated skill is an agent that opens it mid-task and knows nothing about the app. It works for any stack: web, terminal, desktop, HTTP service, mobile, or library.

A repo that already contains a verify skill with a feature map needs updating, not creation: switch to the [`maintain-verification-skill` skill](../maintain-verification-skill/SKILL.md).

Ask the user only for facts the code cannot tell you (a license key, which of two products matters more). Find everything else by reading the repo.

A worked example of a seeded feature map is in [references/example-feature-map/](references/example-feature-map/README.md).

## Phase A: study the repo

Answer five questions from the code and docs. Write the answers down; Phase B uses every one.