create-verification-skill SKILL.md skillA

create-verification-skill from j-star-films-studios/vibecode-protocol-suite is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add j-star-films-studios/vibecode-protocol-suite/create-verification-skill@git:20260821.1b830a3

Pins git:20260821.1b830a3 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

j-star-films-studios/vibecode-protocol-suite

Path

assets/.agent/skills/agent-engineering/create-verification-skill/SKILL.md

Versions recorded

1

Latest version

git:20260821.1b830a3, committed Aug 21, 2026

Size

5,879 bytes

Repository stars

26

License

ISC

Generate a project-local verification skill that drives your app the way a user does — any language, framework, or platform. Use for /create-verification-skill, "make a control skill for this repo", or when a project has no scripted way to prove UI/CLI/service behavior.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Create a verification skill

Every serious project needs a scripted way to drive the real app and prove behavior: launch it, exercise a feature the way a user would, and capture evidence. This skill generates that as a project-local skill (`.cursor/skills/verify-<app>/`) tailored to the repo. You write the generator's output for the next agent, not for a human: it will be read cold, mid-task, by an agent that has never seen the app.

## 1. Interview the repo, not the user

Answer these from the codebase and only ask the user what you cannot observe:

- **Surface:** what does a user actually touch? A web UI, a CLI/TUI, a desktop app, an API, a mobile app, a library? A repo can have several; pick the primary one and note the rest.
- **Run:** how does the app start locally? Prefer the repo's own documented dev command (package scripts, Makefile, README quickstart). Note ports, env vars, seed data, auth.
…

Read the whole file at its exact version.

How to install

mdr add j-star-films-studios/vibecode-protocol-suite/create-verification-skill@sha256:644f2551403c1bca

[![mdr](https://markdownregistry.com/badge/art_nrhvunk36hjwfznq.svg)](https://markdownregistry.com/a/art_nrhvunk36hjwfznq)

Versions

The registry has recorded 1 version of this file, committed on Aug 21, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_nrhvunk36hjwfznq
GET https://markdownregistry.com/api/v1/resolve?ref=j-star-films-studios/vibecode-protocol-suite/create-verification-skill
GET https://markdownregistry.com/api/v1/blob/644f2551403c1bca01a2855b34611b6e7be0ce0dc5b204514c376c0f6a6e6ac4

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from j-star-films-studios/vibecode-protocol-suite

Every file in j-star-films-studios/vibecode-protocol-suite

Other files named create-verification-skill

Browse by kind, by grade A, or by owner.