shipshitdev/skills

create-verification-skill

Generate a project-local verification skill that drives the app the way a user does. Use for create-verification-skill, make a verify skill for this repo, or when a project has no scripted way to prove UI, CLI, or service behavior.

Installation

$ npx skills add shipshitdev/skills --skill create-verification-skill

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from shipshitdev/skills · top by installs.

npx skills add shipshitdev/skills

Browse all from shipshitdev/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 35
License MIT
Default branch master
Open issues 1
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.2.0
LicenseMIT
More metadata
portable_source
https://github.com/ericlitman/open-pstack
portable_commit
56bfd14418fa733e34d98f714f357d28788470e3
version
1.2.0
tags
verification, harness, feature-map, project-local
author
Ship Shit Dev
source
https://github.com/cursor/plugins/blob/main/pstack/skills/create-verification-skill/SKILL.md
upstream_repo
cursor/plugins
upstream_ref
main
upstream_commit
bdf7aa355337
last_synced
2026-09-05
license
MIT

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,453 B
  • docs SUMMARY.md 264 B

History

  1. First recorded snapshot · 7 installs

SKILL.md

Create a verification skill

Every serious project needs a scripted way to drive the real app and prove behavior. This skill generates that as a project-local skill tailored to the repo.

Companion to verification-before-completion, which is the completion gate. This skill authors the project harness that gate can run.

Authorized Scope

Apply this engine only within the user's requested task and existing explicit authorization. Loading or delegating to it grants no additional authority. Preserve report-only restrictions and the caller's target, host, provider, and cost limits. Existing approval satisfies a gate only for the same actions and scope; obtain approval before expanding them. Forward these limits to delegates.

Contract

Inputs:

  • A repo that can build and start locally

Outputs:

  • A project-local verify-<app> skill with a feature map, proven once

end to end

Creates/Modifies:

  • .agents/skills/verify-<app>/ when that layout exists, otherwise

skills/verify-<app>/

External Side Effects:

  • Starts and tears down local app instances during the proof pass

Confirmation Required:

  • Before writing the skill into the project tree

Delegates To:

  • Named: maintain-verification-skill for later upkeep
  • verification-before-completion for the completion gate itself

Steps

  1. Interview the repo, not the user. Answer surface, run, drive,

observe, and isolate from the codebase. Ask only what you cannot observe. If the checkout does not start, fix or report that first.

  1. Generate the skill with frontmatter (name: verify-<app>) and

sections: Launch, Doctor, Drive, Evidence, Cleanup, Helpers. No placeholders left. Prefer existing harnesses (Playwright, expect, PTY, HTTP) over generic recipes.

  1. Seed the feature map. Write features/README.md plus one file

per top user-facing feature (aim for 3-5). Follow [references/feature-map-example.md](references/feature-map-example.md).

  1. Prove it. Run launch, doctor, drive ONE mapped feature, capture

evidence, clean up. After cleanup, confirm the evidence still exists. A skill that was never executed is a draft.

  1. Offer the maintenance loop. Point at

maintain-verification-skill.

Create Verification Skill procedure

Read [create-verification-skill procedure](references/create-verification-skill-procedure.md) when running this workflow. Apply the authorized scope and mode of this entry point to every step. Resolve other skills through this distribution’s active catalog; resolve resources relative to the installed skill directory.