create-verification-skill
/create-verification-skill
Create one reviewed skill that teaches a bot how to launch, drive, and verify a specific app or project. Use only when the user explicitly asks for a verification skill.
- Author
- erenseret56-del ↗
- Repository
- aster ↗
- Licence
- Apache-2.0
- Last repository change
- 01.11.2026
Assessment and security
- Files in this package
- 2
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 01.11.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Create one reviewed skill that teaches a bot how to launch, drive, and verify a specific app or project. Use only when the user explicitly asks for a verification skill.
Original author description
Create one reviewed skill that teaches a bot how to launch, drive, and verify a specific app or project. Use only when the user explicitly asks for a verification skill.
How it works
- 1. Inspect before drafting
- 2. Prove one workflow
- 3. Draft one self-contained skill
- 4. Stage it for review
SKILL.md preview
--- name: create-verification-skill description: "Create one reviewed skill that teaches a bot how to launch, drive, and verify a specific app or project. Use only when the user explicitly asks for a verification skill." --- # Create a verification skill Create one compact, project-specific `SKILL.md` through OpenMausBot's normal skill review flow. Do not install files directly, enable a skill yourself, or silently add scripts to the user's project. ## 1. Inspect before drafting Use the tools already mounted on this bot to establish: - the exact project or app being verified; - its existing launch command and reliable ready signal; - the safest available control surface: existing project CLI, browser, computer, phone, or shell; - one read-only health check; - up to three important user workflows and the observable result that proves each one worked; - how to stop only the process or resource started by the verification run. Prefer an existing control surface. If the project has no dependable way to launch or drive the relevant workflow, report that prerequisite instead of inventing commands, selectors, APIs, or a new control program. ## 2. Prove one workflow Run the real launch, health check, one representative workflow, evidence capture, and cleanup once. Use an isolated test profile or temporary data when available; never drive the user's live data merely to author the skill. If the workflow cannot be proved with the tools currently mounted, stop and explain which capability is missing. ## 3. Draft one self-contained skill The proposed `SKILL.md` must contain YAML frontmatter and these sections: 1. **Launch** — exact command, isolated data/profile, ready signal. 2. **Doctor** — one read-only check with an actionable failure message. 3. **Drive** — stable names, accessibility targets, routes, refs, or commands; never recorded screen coordinates. 4. **Evidence** — action plus resulting state and any important side effect. 5. **Cleanup** — stop only what this run started; preserve the evidence. 6. **Feature map** — at most three proven workflows, each with the user path, control recipe, success proof, and known gotcha. 7. **Maintenance** — re-run Doctor and the affected workflow when the app changes; update drifted instructions but never hide a product failure. Keep it concise. Evidence about the user path is input to the draft—not permission to retain secrets, audio, screenshots, or coordinates. ## 4. Stage it for review Call `skills_list` first. If an existing skill already covers the project, report that and do not overwrite it. Otherwise call `skill_manage` with `action="create"`, the complete `skill_md`, a short `gist`, and the exact source used (repository path, URL, or `conversation`). `skill_manage` only stages the proposal. Tell the user its name and that it is inactive until they approve the in-app review card. Never claim it was enabled or scheduled automatically.
Files in this package (2)
- SKILL.md 3 KB
- manifest.json 1 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · erenseret56-del/aster | 90 | Apache-2.0 |
| e2e-inc/e2e | 100 | Apache-2.0 |
| tester-army/e2e | 100 | Apache-2.0 |
| TimothyVang/deepmodebot | 100 | MIT |
| Calvin-LLC/skills | 100 | MIT |
| arjitj2/open-pstack | 100 | MIT |
| paperclipai/paperclip | 100 | MIT |
| backnotprop/pstack | 100 | MIT |
| kriscard/Skills | 100 | MIT |
Database snapshot: 13.11.2026 · package version a0edc35340eb (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100verification-skill
Create, adopt or maintain a project's own verify-<app> skill, the scripted way for any agent to launch the real app, drive a feature the way a user does, and capture proof. Use for "create a verification skill", "make a control skill for this repo", "set up verification for this… - 86verify-create
Build a project's own verify skill that launches the real app, drives each user-facing feature in a real browser, and keeps a feature map. Use when a project has a UI or front end and no scripted way to prove it works, or when the user asks for a verification skill. - 100create-discord-bot
Create a Discord server and bot application with browser automation, collect the bot token, server ID, and user ID, then save credentials to .env via the keys-safe-guard skill. Skip if OPENCLAW_DISCORD_BOT_TOKEN is already set. Use for any project that needs a Discord bot. - 90agents-create-verification-skill
Generate a project-local verify skill that drives the app like a user through a browser with Playwright, a CLI, or HTTP. Use for /agents-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. - 100create-verify-skill
Create a project verify-<app> skill that drives the running app the way a user does, with agent-browser for web apps and tuistory for terminal apps. Use when a project has no verify skill yet; not to refresh a drifted one (use maintain-verify-skill), not to draft a generic skill… - 100create-verification
Writes a repo's own verification skill (how to launch the app, check its health, drive each feature, keep evidence, clean up) plus the exemplar set for every work profile the repo uses, then runs it once end to end and records PASS or FAIL. Load only when a mend-autopilot lead…