MCP Server Builder
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
Evolve new skills from project experience. An agent skill from HKUDS/OpenOPC.
Install Skill Evolution
$ npx skills add HKUDS/OpenOPC --skill skill-evolution -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install HKUDS/OpenOPC skill-evolution --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/HKUDS/OpenOPC.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.opc/skills/skill-evolution .claude/skills/skill-evolution && 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 "skill-evolution" agent skill from https://github.com/HKUDS/OpenOPC/tree/main/.opc/skills/skill-evolution into .claude/skills/skill-evolution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-evolution", 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/HKUDS/OpenOPC/tree/main/.opc/skills/skill-evolutionType 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 HKUDS/OpenOPC --skill skill-evolution -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install HKUDS/OpenOPC skill-evolution --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HKUDS/OpenOPC.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.opc/skills/skill-evolution .agents/skills/skill-evolution && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "skill-evolution" agent skill from https://github.com/HKUDS/OpenOPC/tree/main/.opc/skills/skill-evolution into .agents/skills/skill-evolution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-evolution", 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 HKUDS/OpenOPC --skill skill-evolution -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install HKUDS/OpenOPC skill-evolution --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HKUDS/OpenOPC.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.opc/skills/skill-evolution .cursor/skills/skill-evolution && 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 "skill-evolution" agent skill from https://github.com/HKUDS/OpenOPC/tree/main/.opc/skills/skill-evolution into .cursor/skills/skill-evolution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-evolution", 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/HKUDS/OpenOPC.git --path .opc/skills/skill-evolution--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 HKUDS/OpenOPC --skill skill-evolution -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install HKUDS/OpenOPC skill-evolution --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HKUDS/OpenOPC.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.opc/skills/skill-evolution .gemini/skills/skill-evolution && 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 "skill-evolution" agent skill from https://github.com/HKUDS/OpenOPC/tree/main/.opc/skills/skill-evolution into .gemini/skills/skill-evolution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-evolution", 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 HKUDS/OpenOPC skill-evolutionInstalls 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 HKUDS/OpenOPC --skill skill-evolution -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/HKUDS/OpenOPC.git skills-src && mkdir -p .github/skills && cp -r skills-src/.opc/skills/skill-evolution .github/skills/skill-evolution && 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 "skill-evolution" agent skill from https://github.com/HKUDS/OpenOPC/tree/main/.opc/skills/skill-evolution into .github/skills/skill-evolution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-evolution", 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 HKUDS/OpenOPC --skill skill-evolution -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install HKUDS/OpenOPC skill-evolution --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/HKUDS/OpenOPC.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.opc/skills/skill-evolution .opencode/skills/skill-evolution && 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 "skill-evolution" agent skill from https://github.com/HKUDS/OpenOPC/tree/main/.opc/skills/skill-evolution into .opencode/skills/skill-evolution/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "skill-evolution", 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
skill-evolution- GitHub stars
- 1.8k
- Token cost
- ~641 tokens
- SKILL.md length
- 300 words
- Files
- 1
- Skills in repo
- 7
- Repo updated
- First seen
- Licence
- MIT
At a glance
Evolve new skills from project experience. An agent skill from HKUDS/OpenOPC.
- Works in 2 steps: Automatic: The system promotes playbook… → Agent-driven (this skill): You…
- A repeating pattern
- SKILL.md covers Two evolution paths, When to evolve a skill…, Process and Skill location, plus 2 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Skill Evolution is an agent skill from HKUDS/OpenOPC. Evolve new skills from project experience. Use when a repeating pattern, useful workflow, or hard-won knowledge should be captured as a reusable skill for the current project.
Its SKILL.md is about 640 tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Agent Workflows. The repository describes itself as: OpenOPC: Build Your Personal AI-Native Company — Self-Built, Self-Run, Self-Grown. The licence is MIT.
When your agent uses it
- A repeating pattern
- Useful workflow
- Hard-won knowledge should be captured as a reusable skill for the current project
Example prompts
- “/skill-evolution”
Workflow steps
2 steps, taken from the first numbered list in SKILL.md.
- Automatic: The system promotes playbook skills when an employee's pattern reaches 2 project reflections with recurring behaviors…
- Agent-driven (this skill): You proactively identify valuable patterns and create skills manually. Use this when domain knowledge…
What it can do on your machine
Read from SKILL.md and the folder at commit b14e85d. 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
Skill Evolution loads about 641 tokens when it runs. Until then it costs about 48 tokens; SKILL.md has 300 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 HKUDS/OpenOPC at commit b14e85d, republished under its MIT licence (© HKUDS). 300 words, ~641 tokens.
Download SKILL.mdSave it as
.claude/skills/skill-evolution/SKILL.md (or your agent's skills folder).- name
- skill-evolution
- description
- Evolve new skills from project experience. Use when a repeating pattern, useful workflow, or hard-won knowledge should be captured as a reusable skill for the current project.
Skill Evolution
Distill project experience into reusable skills that live under the current project.
Two evolution paths
- Automatic: The system promotes playbook skills when an employee's pattern reaches 2 project reflections with recurring behaviors, checklists, or preferences. These are saved as
<employee>-<role>-<domain>-playbookand require no manual action. - Agent-driven (this skill): You proactively identify valuable patterns and create skills manually. Use this when domain knowledge, workflows, or tool sequences should be preserved before the auto-promotion threshold is reached, or when the knowledge is not tied to a specific employee pattern.
When to evolve a skill (agent-driven)
- A task required non-obvious steps that will likely recur
- You discovered a workflow that worked well and should be preserved
- Domain-specific knowledge was gathered that future tasks will need
- A sequence of tool calls forms a reliable pattern worth codifying
Process
- Identify the pattern: What knowledge or workflow is worth preserving?
- Read the skill-creator skill:
file_readtheskill-creator/SKILL.mdfor format and naming guidelines - Name the skill: Lowercase letters, digits, and hyphens only, under 64 characters (e.g.,
api-validation-workflow) - Create the skill directory: Under
.opc/projects/<project_id>/skills/<skill-name>/ - Write SKILL.md with proper frontmatter (
name,description) and concise instructions - Add scripts/references/assets if the skill benefits from bundled resources
Skill location
Evolved skills belong to the project that produced them:
.opc/projects/<project_id>/skills/<skill-name>/SKILL.mdGuidelines
- Keep it concise: only include what the agent doesn't already know
- Use concrete examples over abstract explanations
- Include the minimal set of steps needed to reproduce the workflow
- Add
scripts/for deterministic operations that get rewritten repeatedly - Add
references/for domain docs the agent should consult - Follow the same naming conventions as auto-promoted skills (hyphen-case)
Cross-project reuse
Other projects can reference this project's skills via file_read when the secretary recommends them. Do not duplicate skills across projects; read from the source project instead.
© HKUDS, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in .opc/skills/skill-evolution of HKUDS/OpenOPC.
Open the folder on GitHubat commit b14e85d
Compare with similar skills
Skill Evolution 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 |
|---|---|---|---|---|---|---|
| Skill Evolution this skillHKUDS/OpenOPC | 1.8k | — | ~641 | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 62 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 37k | 11 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 34 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 296k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Claude Code Agent Developmentanthropics/claude-plugins-official | 37k | 8 repos | ~2.8k | Automated safety check: Pass | Apache-2.0 |
Similar skills
- Official
- Official
Hook Development for Claude Code Plugins
anthropics/claude-plugins-official
Explains how to write Claude Code plugin hooks, both prompt-based checks and bash commands, for events such as PreToolUse, Stop and SessionStart.
Using Superpowers
farm-fe/farm
A skill your agent uses when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Executing Plans Inline
obra/superpowers
Has the agent carry out an implementation plan itself, task by task in the current session, keeping a ledger, proving each step with a test and ending with one whole-branch review.
- Official
Claude Code Agent Development
anthropics/claude-plugins-official
Explains how to write agents for Claude Code plugins: the markdown file with YAML frontmatter, trigger descriptions, model and color settings, and system prompt design.
- Official
Skill Creator
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
More from HKUDS/OpenOPC
Skill Creator
HKUDS/OpenOPC
Create or update skills. An agent skill from HKUDS/OpenOPC.
Clawhub
HKUDS/OpenOPC
Search and install agent skills from ClawHub, the public skill registry.
Collaboration Playbook
HKUDS/OpenOPC
Standing rules for how any role in an OpenOPC company coordinates with its peers — work-item discipline, messaging, meetings, and blocking collaboration.
Opc Collab
HKUDS/OpenOPC
Collaborate with other agents in OpenOPC company mode via the opc-collab CLI — send messages, request user input, delegate work, read the manager board, respond in meetings, propose task adjustments.
Cron
HKUDS/OpenOPC
Schedule reminders, recurring tasks, and one-time jobs using system crontab.
Memory
HKUDS/OpenOPC
Manage durable global/project memory in .opc/memory/global.md and .opc/memory/projects/<currentprojectid.md.
Related
Categories
Questions about Skill Evolution
What does Skill Evolution do?
Evolve new skills from project experience. An agent skill from HKUDS/OpenOPC. Skill Evolution is an agent skill from HKUDS/OpenOPC. Evolve new skills from project experience.
When should I use Skill Evolution?
Skill Evolution fits situations like: A repeating pattern; useful workflow; hard-won knowledge should be captured as a reusable skill for the current project.
How do I install Skill Evolution in Claude Code?
Run `npx skills add HKUDS/OpenOPC --skill skill-evolution -a claude-code`. Or copy the skill folder (.opc/skills/skill-evolution in HKUDS/OpenOPC) into .claude/skills/skill-evolution in your project. Claude Code loads it when a task matches its description.
How do I install Skill Evolution in Codex?
Run `npx skills add HKUDS/OpenOPC --skill skill-evolution -a codex`. Or copy the skill folder (.opc/skills/skill-evolution in HKUDS/OpenOPC) into .agents/skills/skill-evolution in your project. Codex loads it when a task matches its description.
Can I use Skill Evolution 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 HKUDS/OpenOPC --skill skill-evolution -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/skill-evolution, .gemini/skills/skill-evolution, .github/skills/skill-evolution and .opencode/skills/skill-evolution in your project.
What does Skill Evolution need to run?
SKILL.md names no scripts, command-line tools or credentials: Skill Evolution is instructions for the agent only.
Does Skill Evolution 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 Skill Evolution 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 Skill Evolution use?
Skill Evolution is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Skill Evolution use?
About 641 tokens (SKILL.md is roughly 2.6k 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 Skill Evolution?
Skills that share tags, products or a category with Skill Evolution: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 37k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 296k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Skill Evolution?
HKUDS (a GitHub organization) maintains it in HKUDS/OpenOPC, which has 1,808 GitHub stars. The repository holds 7 skills in this directory. The repository was last updated on September 11, 2026.
Source: HKUDS/OpenOPC on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.