Iconify Icons
oomol-lab/open-flow
Search local Iconify JSON and use UnoCSS icon classes in the Open Flow repository.
Create one skill that teaches a bot how to launch, drive, and verify a specific app or project.
Install Create Verification Skill
$ npx skills add milind-soni/OpenMausBot --skill create-verification-skill -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install milind-soni/OpenMausBot create-verification-skill --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/milind-soni/OpenMausBot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/create-verification-skill .claude/skills/create-verification-skill && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "create-verification-skill" agent skill from https://github.com/milind-soni/OpenMausBot/tree/main/skills/create-verification-skill into .claude/skills/create-verification-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-verification-skill", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/milind-soni/OpenMausBot/tree/main/skills/create-verification-skillType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add milind-soni/OpenMausBot --skill create-verification-skill -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install milind-soni/OpenMausBot create-verification-skill --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/milind-soni/OpenMausBot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/create-verification-skill .agents/skills/create-verification-skill && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "create-verification-skill" agent skill from https://github.com/milind-soni/OpenMausBot/tree/main/skills/create-verification-skill into .agents/skills/create-verification-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-verification-skill", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add milind-soni/OpenMausBot --skill create-verification-skill -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install milind-soni/OpenMausBot create-verification-skill --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/milind-soni/OpenMausBot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/create-verification-skill .cursor/skills/create-verification-skill && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "create-verification-skill" agent skill from https://github.com/milind-soni/OpenMausBot/tree/main/skills/create-verification-skill into .cursor/skills/create-verification-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-verification-skill", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/milind-soni/OpenMausBot.git --path skills/create-verification-skill--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add milind-soni/OpenMausBot --skill create-verification-skill -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install milind-soni/OpenMausBot create-verification-skill --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/milind-soni/OpenMausBot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/create-verification-skill .gemini/skills/create-verification-skill && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "create-verification-skill" agent skill from https://github.com/milind-soni/OpenMausBot/tree/main/skills/create-verification-skill into .gemini/skills/create-verification-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-verification-skill", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install milind-soni/OpenMausBot create-verification-skillInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add milind-soni/OpenMausBot --skill create-verification-skill -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/milind-soni/OpenMausBot.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/create-verification-skill .github/skills/create-verification-skill && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "create-verification-skill" agent skill from https://github.com/milind-soni/OpenMausBot/tree/main/skills/create-verification-skill into .github/skills/create-verification-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-verification-skill", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add milind-soni/OpenMausBot --skill create-verification-skill -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install milind-soni/OpenMausBot create-verification-skill --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/milind-soni/OpenMausBot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/create-verification-skill .opencode/skills/create-verification-skill && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "create-verification-skill" agent skill from https://github.com/milind-soni/OpenMausBot/tree/main/skills/create-verification-skill into .opencode/skills/create-verification-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-verification-skill", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
create-verification-skill- GitHub stars
- 4.2k
- Token cost
- ~758 tokens
- SKILL.md length
- 423 words
- Files
- 2
- Skills in repo
- 3
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
Create one skill that teaches a bot how to launch, drive, and verify a specific app or project.
- Works in 4 steps: Inspect before drafting → Prove one workflow → Draft one self-contained skill → …
- Explicitly asks for a verification skill
- SKILL.md covers 1. Inspect before drafting, 2. Prove one workflow, 3. Draft one self-contained… and 4. Save it
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Create Verification Skill is an agent skill from milind-soni/OpenMausBot. Create one 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.
Its SKILL.md is about 760 tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `manifest.json`).
It sits in Productivity & Automation. It works with Docker, Expo and TypeScript. The repository describes itself as: Open-source Grok Bot alternative with a virtual machine that bots can use. The licence is Apache-2.0.
When your agent uses it
- Explicitly asks for a verification skill
Example prompts
- “/create-verification-skill”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 6ba128a. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Create Verification Skill loads about 758 tokens when it runs. Until then it costs about 47 tokens; SKILL.md has 423 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from milind-soni/OpenMausBot at commit 6ba128a, republished under its Apache-2.0 licence (© milind-soni). 423 words, ~758 tokens.
Download SKILL.mdSave it as
.claude/skills/create-verification-skill/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- create-verification-skill
- description
- Create one 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 skill_manage, which
shows the person every change with an Undo. Do not install skill files
directly 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.
Show full SKILL.md (225 more words)Show less
3. Draft one self-contained skill
The proposed SKILL.md must contain YAML frontmatter and these sections:
- Launch — exact command, isolated data/profile, ready signal.
- Doctor — one read-only check with an actionable failure message.
- Drive — stable names, accessibility targets, routes, refs, or commands; never recorded screen coordinates.
- Evidence — action plus resulting state and any important side effect.
- Cleanup — stop only what this run started; preserve the evidence.
- Feature map — at most three proven workflows, each with the user path, control recipe, success proof, and known gotcha.
- 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. Save it
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).
Read the skill_manage result. If it applied, tell the user the skill's name,
that it is on, and that they can undo it from the chat. Only if it is pending,
tell them it stays inactive until they decide on the in-app card. Never claim
it was enabled without an applied result.
© milind-soni, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
SKILL.md and 1 other file in skills/create-verification-skill of milind-soni/OpenMausBot.
- SKILL.md
- manifest.json
Open the folder on GitHubat commit 6ba128a
Compare with similar skills
Create Verification Skill next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Create Verification Skill this skillmilind-soni/OpenMausBot | 4.2k | — | ~758 | Automated safety check: Pass | Apache-2.0 | |
| Iconify Iconsoomol-lab/open-flow | 226 | — | ~850 | Automated safety check: Pass | Apache-2.0 | |
| Expo Modulebbplayer-app/BBPlayer | 1.1k | 3 repos | ~1.4k | Automated safety check: Pass | MIT | |
| React Native Healthkitkingstinct/react-native-healthkit | 716 | — | ~1.6k | Automated safety check: Pass | MIT | |
| Code Review React Nativetalsec/Free-RASP-ReactNative | 175 | — | ~3.7k | Automated safety check: Pass | MIT | |
| Project Pull Requestswimmwatch/cloakbrowser-mcp | 161 | — | ~1k | Automated safety check: Pass | MIT |
Similar skills
Expo Module
bbplayer-app/BBPlayer
Guide for creating and writing Expo native modules and views using the Expo Modules API (Swift, Kotlin, TypeScript).
React Native Healthkit
kingstinct/react-native-healthkit
How to use @kingstinct/react-native-healthkit (and its sibling @react-native-healthkit/health-records) to read, write and subscribe to Apple HealthKit data from React Native / Expo apps.
Code Review React Native
talsec/Free-RASP-ReactNative
Performs strict code reviews on React Native plugin projects covering TypeScript, the Kotlin (Android) and Swift (iOS) native bridges, and the Expo config plugin.
Project Pull Request
swimmwatch/cloakbrowser-mcp
Create, update, prepare, or review a cloakbrowser-mcp GitHub Pull Request only when the user explicitly requests PR work.
- Official
Expo Module
expo/skills
Guide for creating and writing Expo native modules and views using the Expo Modules API (Swift, Kotlin, TypeScript).
More from milind-soni/OpenMausBot
Windows Release
milind-soni/OpenMausBot
Build and verify the Windows desktop build (NSIS installer + latest.yml) for the canonical OpenMausBot release and its legacy updater mirror.
Phone Harness
milind-soni/OpenMausBot
Control, inspect, test, or automate a physical Android phone connected to OpenMausBot over authorized USB debugging.
Related
Works with
Categories
Questions about Create Verification Skill
What does Create Verification Skill do?
Create one skill that teaches a bot how to launch, drive, and verify a specific app or project. Create Verification Skill is an agent skill from milind-soni/OpenMausBot. Create one skill that teaches a bot how to launch, drive, and verify a specific app or project.
When should I use Create Verification Skill?
Create Verification Skill fits situations like: explicitly asks for a verification skill.
How do I install Create Verification Skill in Claude Code?
Run `npx skills add milind-soni/OpenMausBot --skill create-verification-skill -a claude-code`. Or copy the skill folder (skills/create-verification-skill in milind-soni/OpenMausBot) into .claude/skills/create-verification-skill in your project. Claude Code loads it when a task matches its description.
How do I install Create Verification Skill in Codex?
Run `npx skills add milind-soni/OpenMausBot --skill create-verification-skill -a codex`. Or copy the skill folder (skills/create-verification-skill in milind-soni/OpenMausBot) into .agents/skills/create-verification-skill in your project. Codex loads it when a task matches its description.
Can I use Create Verification Skill in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add milind-soni/OpenMausBot --skill create-verification-skill -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-verification-skill, .gemini/skills/create-verification-skill, .github/skills/create-verification-skill and .opencode/skills/create-verification-skill in your project.
What does Create Verification Skill need to run?
SKILL.md names no scripts, command-line tools or credentials: Create Verification Skill is instructions for the agent only.
Does Create Verification Skill access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Create Verification Skill safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Create Verification Skill use?
Create Verification Skill is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Create Verification Skill use?
About 758 tokens (SKILL.md is roughly 3k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Create Verification Skill?
Skills that share tags, products or a category with Create Verification Skill: Iconify Icons (oomol-lab/open-flow, 226 stars), Expo Module (bbplayer-app/BBPlayer, 1.1k stars), React Native Healthkit (kingstinct/react-native-healthkit, 716 stars) and Code Review React Native (talsec/Free-RASP-ReactNative, 175 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Create Verification Skill?
milind-soni (a GitHub user) maintains it in milind-soni/OpenMausBot, which has 4,161 GitHub stars. The repository holds 3 skills in this directory. The repository was last updated on October 8, 2026.
Source: milind-soni/OpenMausBot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.