shipshitdev/create-verification-skill
skills/create-verification-skill/SKILL.md
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.
$ install --global
skillsauthnpx skillsauth add shipshitdev/library create-verification-skillInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Aug 31, 2026, 2:40 AM283.7s4 files scanned
SKILL.md
- name:
- create-verification-skill
- description:
- 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.
- disable-model-invocation:
- true
- license:
- MIT
- version:
- 1.0.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-08-26
- when_to_use:
- create verification skill, make a verify skill, scripted app proof
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.
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, otherwiseskills/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-skillfor later upkeep verification-before-completionfor the completion gate itself
Steps
- 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.
- 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. - Seed the feature map. Write
features/README.mdplus one file per top user-facing feature (aim for 3-5). Follow references/feature-map-example.md. - 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.
- Offer the maintenance loop. Point at
maintain-verification-skill.
Related Skills
shipshitdev/weekly-review
development
VerifiedTrustedCommunity
Coordinates a weekly engineering review of board accuracy, recent code changes, operational health, and scoped cleanup. Use for a recurring repository health review or a review of the last several days.
35SKILL.mdUpdated Sep 6, 2026
shipshitdev/project-board
testing
VerifiedTrustedCommunity
Audits project board configuration and prepares explicitly requested setup, copy, or normalization changes while preserving the existing workflow and provider boundaries. Use when inspecting a board's fields, columns, scope, or configuration.
35SKILL.mdUpdated Sep 6, 2026
shipshitdev/board-sync
testing
VerifiedTrustedCommunity
Reconciles a project board with current work and delivery evidence, reports incomplete coverage and metadata gaps, and applies only approved provider-supported field changes. Use when auditing board drift, reviewing blocked work, or assessing upcoming delivery.
35SKILL.mdUpdated Sep 6, 2026
shipshitdev/how
development
VerifiedTrustedCommunity
Walk through how a subsystem works. Use for "how does X work", code walkthroughs before changing something, and placement or ownership questions. Explains architecture, runtime flow, and onboarding mental models. Can critique architecture. Use why for motivation.
35SKILL.mdUpdated Aug 31, 2026