Skill Creator
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
Create or update Vetta-compatible Agent Skills. An agent skill from openvetta/open-vetta.
$ npx skills add openvetta/open-vetta --skill create-skill -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install openvetta/open-vetta create-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/openvetta/open-vetta.git skills-src && mkdir -p .claude/skills && cp -r skills-src/packages/skill-presets/create-skill .claude/skills/create-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-skill" agent skill from https://github.com/openvetta/open-vetta/tree/main/packages/skill-presets/create-skill into .claude/skills/create-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-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/openvetta/open-vetta/tree/main/packages/skill-presets/create-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 openvetta/open-vetta --skill create-skill -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install openvetta/open-vetta create-skill --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openvetta/open-vetta.git skills-src && mkdir -p .agents/skills && cp -r skills-src/packages/skill-presets/create-skill .agents/skills/create-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-skill" agent skill from https://github.com/openvetta/open-vetta/tree/main/packages/skill-presets/create-skill into .agents/skills/create-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-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 openvetta/open-vetta --skill create-skill -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install openvetta/open-vetta create-skill --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openvetta/open-vetta.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/packages/skill-presets/create-skill .cursor/skills/create-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-skill" agent skill from https://github.com/openvetta/open-vetta/tree/main/packages/skill-presets/create-skill into .cursor/skills/create-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-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/openvetta/open-vetta.git --path packages/skill-presets/create-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 openvetta/open-vetta --skill create-skill -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install openvetta/open-vetta create-skill --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openvetta/open-vetta.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/packages/skill-presets/create-skill .gemini/skills/create-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-skill" agent skill from https://github.com/openvetta/open-vetta/tree/main/packages/skill-presets/create-skill into .gemini/skills/create-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-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 openvetta/open-vetta create-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 openvetta/open-vetta --skill create-skill -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/openvetta/open-vetta.git skills-src && mkdir -p .github/skills && cp -r skills-src/packages/skill-presets/create-skill .github/skills/create-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-skill" agent skill from https://github.com/openvetta/open-vetta/tree/main/packages/skill-presets/create-skill into .github/skills/create-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-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 openvetta/open-vetta --skill create-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 openvetta/open-vetta create-skill --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/openvetta/open-vetta.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/packages/skill-presets/create-skill .opencode/skills/create-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-skill" agent skill from https://github.com/openvetta/open-vetta/tree/main/packages/skill-presets/create-skill into .opencode/skills/create-skill/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "create-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.
create-skillCreate or update Vetta-compatible Agent Skills. An agent skill from openvetta/open-vetta.
Create Skill is an agent skill from openvetta/open-vetta. Create or update Vetta-compatible Agent Skills. Use when the user asks to create a skill, add a SKILL.md workflow, register a skill in skills-manifest.json, package a skill in a Vetta plugin, or add a built-in Vetta skill preset.
Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 1 other file (for example `ability.json`).
It sits in Agent Workflows, covering Skill authoring. The repository describes itself as: Open-source, local-first AI agent for coding and real work. BYOK models, MCP, skills, plugins, workflows, and private knowledge bases. The licence is Apache-2.0.
6 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit a2d314a. It shows what the files ask for, not the result of running them.
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.
No scripts in the folder and no shell commands in SKILL.md (its code samples are json and markdown).
From the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Create Skill loads about 1.6k tokens when it runs. Until then it costs about 61 tokens; SKILL.md has 721 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.
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.
The full file from openvetta/open-vetta at commit a2d314a, republished under its Apache-2.0 licence (© openvetta). 721 words, ~1,551 tokens.
.claude/skills/create-skill/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.Create focused Agent Skills that Vetta can execute and display. Treat the Skill files and their registration metadata as one change.
Infer the target from the request. If it is ambiguous, ask the user to choose before writing files.
| Target | Skill directory | Required registration |
|---|---|---|
| Global Vetta product skill | ~/.vetta/skills/<skill-name>/ | Update ~/.vetta/skills-manifest.json. |
| Project skill | <project-root>/.vetta/skills/<skill-name>/ | No global manifest entry; project discovery is directory-based. |
| Plugin skill | <plugin-root>/agent/skills/<skill-name>/ | Update plugin.json under agent.skillPaths. |
| Built-in Desktop skill | <vetta-mono>/packages/skill-presets/<skill-name>/ | Update <vetta-mono>/packages/skill-presets/skills-manifest.json. |
Do not place a global product Skill only in ~/.vetta/agent/skills; that directory is Agent-compatible but does not provide the Vetta product registration metadata required by the Skills UI.
Skill and scene roots — ~/.vetta/skills, ~/.vetta/agent/skills, ~/.vetta/scene, <project-root>/.vetta/skills, and the .agents/skills equivalents — are read-only so that generated artifacts never land in them. Creating a new <root>/<skill-name>/ directory is exempt: once this session authors that directory, every file inside it stays writable for the rest of the session.
An already-installed Skill stays read-only. write and edit reject its files, and a shell command that touches them returns a warning to move the output out. To change one, edit the source it was installed from — the plugin, the repository preset, or the project directory — or ask the user to uninstall it first. Never work around the rejection with shell redirection.
name.<skill-directory>/SKILL.md with YAML frontmatter containing name and description.scripts/, references/, or assets/ only when genuinely required. Keep detailed reference material outside SKILL.md and link to it with relative paths.Use this minimal structure:
---
name: example-skill
description: Describe what the Skill does and the user requests that should trigger it.
---
# Example Skill
Concise workflow instructions.Read the full ~/.vetta/skills-manifest.json before editing it. The file is a root-level JSON object keyed by Skill name. Preserve every existing entry and add or update only the target Skill.
Use an entry shaped like this:
{
"example-skill": {
"name": "example-skill",
"version": "1.0.0",
"installedAt": "<current ISO-8601 timestamp>",
"source": "custom",
"enabled": true,
"type": "skill",
"alias": "Optional display name",
"description": "Description aligned with SKILL.md frontmatter"
}
}If the manifest does not exist, create it as {} before adding the entry. Keep it valid JSON and avoid replacing unrelated Skills. Use the actual current timestamp rather than a placeholder.
Read the full packages/skill-presets/skills-manifest.json. Preserve existing entries and add the new Skill with source: "builtin", enabled: true, type: "skill", a version, and display metadata. The manifest key, entry name, directory name, and SKILL.md frontmatter name must all match.
The Desktop build only packages enabled directories registered in this manifest. An unregistered preset is an error.
Only plugin-packaged Skills use plugin.json registration.
plugin.json before editing it.agent field and every existing skillPaths entry."agent/skills" when it intentionally contains all plugin Skills; otherwise add the specific Skill directory.Example:
{
"agent": {
"skillPaths": ["agent/skills"]
}
}description specific enough for reliable triggering; include both the capability and common request language.SKILL.md under 500 lines. Move large examples and domain references into references/.SKILL.md exists and its frontmatter name matches the directory.skills-manifest.json and confirm the target entry is present without losing existing entries.plugin.json contains the correct relative agent.skillPaths entry and remains valid JSON.© openvetta, 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
SKILL.md and 1 other file in packages/skill-presets/create-skill of openvetta/open-vetta.
Open the folder on GitHubat commit a2d314a
Create 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 Skill this skillopenvetta/open-vetta | 290 | — | ~1.6k | Automated safety check: Pass | Apache-2.0 | |
| Skill CreatorAzure/azqr | 794 | 89 repos | ~8.2k | Automated safety check: Pass | Apache-2.0 | |
| Claude Code Skill Developer Guidediet103/claude-code-infrastructure-showcase | 10k | 10 repos | ~3.5k | Automated safety check: Pass | MIT | |
| Darwin Skill Optimizeralchaincyf/darwin-skill | 6.2k | 1 repos | ~4.7k | Automated safety check: Pass | MIT | |
| Claude Code Command Developmentanthropics/claude-plugins-official | 37k | 10 repos | ~4.8k | Automated safety check: Pass | Apache-2.0 | |
| Claude Code Plugin Structureanthropics/claude-plugins-official | 37k | 10 repos | ~3.4k | Automated safety check: Pass | Apache-2.0 |
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
diet103/claude-code-infrastructure-showcase
A guide to creating and managing Claude Code skills with auto-activation: skill-rules.json triggers, hooks, enforcement levels, YAML frontmatter and progressive disclosure.
alchaincyf/darwin-skill
Scores SKILL.md files on a nine-dimension rubric, then improves them in a keep-or-revert loop with independent judge agents, test prompts, git history and human checkpoints.
anthropics/claude-plugins-official
Explains how to write Claude Code slash commands: Markdown files with YAML frontmatter, arguments, file references, bash context and interactive prompts.
anthropics/claude-plugins-official
Explains the directory layout, plugin.json manifest and component organization of a Claude Code plugin, including auto-discovery and portable paths.
rohitg00/ai-engineering-from-scratch
Evaluates an Agent Skill bundle before release for structure, trigger quality, artifact improvement, script correctness, safety, installed-tree integrity and host portability.
openvetta/open-vetta
Master Material Design 3 and Jetpack Compose patterns for building native Android apps.
openvetta/open-vetta
Publish a skill, scene, MCP server, plugin, or bundle to the Vetta ability marketplace.
openvetta/open-vetta
Create, implement, build, pack, install, reload, and manage Vetta desktop plugins for non-developers.
openvetta/open-vetta
Design mobile-style HTML pages (iOS / Android) for preview in the Mobile UI Preview panel.
openvetta/open-vetta
Create, modify, and render Remotion React video projects in the current Vetta conversation workspace.
openvetta/open-vetta
Build and edit design documents (.vetd) on the Vetta design canvas — app screens, landing pages, slides, posters, infographics.
Categories
Create or update Vetta-compatible Agent Skills. An agent skill from openvetta/open-vetta. Create Skill is an agent skill from openvetta/open-vetta. Create or update Vetta-compatible Agent Skills.
Create Skill fits situations like: the user asks to create a skill; add a SKILL.md workflow; register a skill in skills-manifest.json; package a skill in a Vetta plugin.
Run `npx skills add openvetta/open-vetta --skill create-skill -a claude-code`. Or copy the skill folder (packages/skill-presets/create-skill in openvetta/open-vetta) into .claude/skills/create-skill in your project. Claude Code loads it when a task matches its description.
Run `npx skills add openvetta/open-vetta --skill create-skill -a codex`. Or copy the skill folder (packages/skill-presets/create-skill in openvetta/open-vetta) into .agents/skills/create-skill in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openvetta/open-vetta --skill create-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-skill, .gemini/skills/create-skill, .github/skills/create-skill and .opencode/skills/create-skill in your project.
SKILL.md names no scripts, command-line tools or credentials: Create Skill is instructions for the agent only.
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.
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.
Create 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.
About 1.6k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Create Skill: Skill Creator (Azure/azqr, 794 stars), Claude Code Skill Developer Guide (diet103/claude-code-infrastructure-showcase, 10k stars), Darwin Skill Optimizer (alchaincyf/darwin-skill, 6.2k stars) and Claude Code Command Development (anthropics/claude-plugins-official, 37k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
openvetta (a GitHub organization) maintains it in openvetta/open-vetta, which has 290 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 4, 2026.
Source: openvetta/open-vetta on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.