Agent skill

Create Skill

by openvetta in openvetta/open-vetta

Create or update Vetta-compatible Agent Skills. An agent skill from openvetta/open-vetta.

Apache-2.0Auto-check passedAgent Workflows

Install Create Skill

skills CLI
$ npx skills add openvetta/open-vetta --skill create-skill -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install openvetta/open-vetta create-skill --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ 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-src

Use ~/.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/

Facts

Skill name
create-skill
GitHub stars
290
Token cost
~1.6k tokens
SKILL.md length
721 words
Files
2
Skills in repo
21
Repo updated
First seen
Licence
Apache-2.0

At a glance

Create or update Vetta-compatible Agent Skills. An agent skill from openvetta/open-vetta.

  • Works in 6 steps: Convert the requested name to lowercase… → Inspect nearby Skills and relevant… → Create /SKILL.md with YAML frontmatter… → …
  • The user asks to create a skill
  • SKILL.md covers Choose the target, Understand the directory…, Create the Skill and Register a global Vetta Skill, plus 4 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

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.

When your agent uses it

  • 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

Example prompts

  • “/create-skill”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Convert the requested name to lowercase kebab-case. It must be 1-64 characters containing only lowercase letters, digits, and hyphens. The…
  2. Inspect nearby Skills and relevant project documentation before writing. Reuse established terminology and tool names without copying…
  3. Create /SKILL.md with YAML frontmatter containing name and description.
  4. Write the body as imperative workflow instructions. State when to inspect context, when to ask a question, what files to create or edit…
  5. Add scripts/, references/, or assets/ only when genuinely required. Keep detailed reference material outside SKILL.md and link to it with…
  6. Do not overwrite an existing Skill or unrelated configuration without reading it first. Ask before replacing intentional behavior. Inside…

What it can do on your machine

Read from SKILL.md and the folder at commit a2d314a. 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 (its code samples are json and markdown).

    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 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.

Always · name and description, kept in context so the agent knows when to use it
~61
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k

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 openvetta/open-vetta at commit a2d314a, republished under its Apache-2.0 licence (© openvetta). 721 words, ~1,551 tokens.

Download SKILL.mdSave it as .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.
name
create-skill
description
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.

Create a Vetta Skill

Create focused Agent Skills that Vetta can execute and display. Treat the Skill files and their registration metadata as one change.

Choose the target

Infer the target from the request. If it is ambiguous, ask the user to choose before writing files.

TargetSkill directoryRequired 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.

Understand the directory protection

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.

Create the Skill

  1. Convert the requested name to lowercase kebab-case. It must be 1-64 characters containing only lowercase letters, digits, and hyphens. The directory name must match the frontmatter name.
  2. Inspect nearby Skills and relevant project documentation before writing. Reuse established terminology and tool names without copying unrelated instructions.
  3. Create <skill-directory>/SKILL.md with YAML frontmatter containing name and description.
  4. Write the body as imperative workflow instructions. State when to inspect context, when to ask a question, what files to create or edit, and how to verify completion.
  5. Add scripts/, references/, or assets/ only when genuinely required. Keep detailed reference material outside SKILL.md and link to it with relative paths.
  6. Do not overwrite an existing Skill or unrelated configuration without reading it first. Ask before replacing intentional behavior. Inside a protected root, an existing Skill directory cannot be overwritten at all — see the directory protection above.

Use this minimal structure:

markdown
---
name: example-skill
description: Describe what the Skill does and the user requests that should trigger it.
---

# Example Skill

Concise workflow instructions.

Register a global Vetta Skill

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:

json
{
  "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.

Show full SKILL.md (273 more words)Show less

Register a built-in Desktop Skill

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.

Update plugin configuration

Only plugin-packaged Skills use plugin.json registration.

  1. Read the full plugin.json before editing it.
  2. Preserve every existing agent field and every existing skillPaths entry.
  3. Add a plugin-relative path. Prefer a shared parent such as "agent/skills" when it intentionally contains all plugin Skills; otherwise add the specific Skill directory.
  4. Do not add duplicate paths.

Example:

json
{
  "agent": {
    "skillPaths": ["agent/skills"]
  }
}

Quality rules

  • Keep the frontmatter valid YAML at the start of the file.
  • Make description specific enough for reliable triggering; include both the capability and common request language.
  • Keep SKILL.md under 500 lines. Move large examples and domain references into references/.
  • Use relative links for files inside the Skill directory.
  • Do not hardcode secrets, machine-specific absolute paths, or destructive commands.
  • Prefer the minimum files and instructions needed for the requested workflow.

Verify

  1. Confirm the final directory matches the selected target.
  2. Confirm SKILL.md exists and its frontmatter name matches the directory.
  3. Confirm the description clearly states when the Skill should run.
  4. For global or built-in Skills, parse the complete skills-manifest.json and confirm the target entry is present without losing existing entries.
  5. For plugin Skills, confirm plugin.json contains the correct relative agent.skillPaths entry and remains valid JSON.
  6. Report created or modified files and any validation that was not run.

© 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

Files

SKILL.md and 1 other file in packages/skill-presets/create-skill of openvetta/open-vetta.

  • SKILL.md
  • ability.json

Open the folder on GitHubat commit a2d314a

Compare with similar skills

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.

Create Skill compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Create Skill this skillopenvetta/open-vetta290—~1.6kAutomated safety check: PassApache-2.0
Skill CreatorAzure/azqr79489 repos~8.2kAutomated safety check: PassApache-2.0
Claude Code Skill Developer Guidediet103/claude-code-infrastructure-showcase10k10 repos~3.5kAutomated safety check: PassMIT
Darwin Skill Optimizeralchaincyf/darwin-skill6.2k1 repos~4.7kAutomated safety check: PassMIT
Claude Code Command Developmentanthropics/claude-plugins-official37k10 repos~4.8kAutomated safety check: PassApache-2.0
Claude Code Plugin Structureanthropics/claude-plugins-official37k10 repos~3.4kAutomated safety check: PassApache-2.0

Similar skills

  • Skill Creator

    Azure/azqr

    Official

    Create new skills, modify and improve existing skills, and measure skill performance.

    794 GitHub starsUsed in 89 repos~8.2k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Skill Developer Guide

    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.

    10k GitHub starsUsed in 10 repos~3.5k tokens
    Agent WorkflowsAuto-check passed
  • Darwin Skill Optimizer

    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.

    6.2k GitHub starsUsed in 1 repo~4.7k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Command Development

    anthropics/claude-plugins-official

    Official

    Explains how to write Claude Code slash commands: Markdown files with YAML frontmatter, arguments, file references, bash context and interactive prompts.

    37k GitHub starsUsed in 10 repos~4.8k tokens
    Agent WorkflowsAuto-check passed
  • Claude Code Plugin Structure

    anthropics/claude-plugins-official

    Official

    Explains the directory layout, plugin.json manifest and component organization of a Claude Code plugin, including auto-discovery and portable paths.

    37k GitHub starsUsed in 10 repos~3.4k tokens
    Agent WorkflowsAuto-check passed
  • Skill Release Gate

    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.

    65k GitHub stars~1k tokensUpdated yesterday
    Agent WorkflowsAuto-check passed

More from openvetta/open-vetta

All 21 skills in this repo
  • Mobile Android Design

    openvetta/open-vetta

    Master Material Design 3 and Jetpack Compose patterns for building native Android apps.

    290 GitHub starsUsed in 3 repos~950 tokens
    Auto-check passed
  • Publish Ability

    openvetta/open-vetta

    Publish a skill, scene, MCP server, plugin, or bundle to the Vetta ability marketplace.

    290 GitHub stars~1.6k tokensUpdated 3 days ago
    Auto-check passed
  • Plugin Workbench

    openvetta/open-vetta

    Create, implement, build, pack, install, reload, and manage Vetta desktop plugins for non-developers.

    290 GitHub stars~1.9k tokensUpdated 3 days ago
    Auto-check passed
  • Mobile UI Design

    openvetta/open-vetta

    Design mobile-style HTML pages (iOS / Android) for preview in the Mobile UI Preview panel.

    290 GitHub stars~1.6k tokensUpdated 3 days ago
    Auto-check passed
  • Remotion Video

    openvetta/open-vetta

    Create, modify, and render Remotion React video projects in the current Vetta conversation workspace.

    290 GitHub stars~744 tokensUpdated 3 days ago
    Auto-check passed
  • Vetta UI Design

    openvetta/open-vetta

    Build and edit design documents (.vetd) on the Vetta design canvas — app screens, landing pages, slides, posters, infographics.

    290 GitHub stars~7.3k tokensUpdated 3 days ago
    Auto-check passed

Categories

Questions about Create Skill

What does Create Skill do?

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.

When should I use Create Skill?

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.

How do I install Create Skill in Claude Code?

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.

How do I install Create Skill in Codex?

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.

Can I use Create 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 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.

What does Create Skill need to run?

SKILL.md names no scripts, command-line tools or credentials: Create Skill is instructions for the agent only.

Does Create 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 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 Skill use?

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.

How many tokens does Create Skill use?

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.

What are the alternatives to Create Skill?

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.

Who maintains Create Skill?

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.