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.
dev-orchestrator only. An agent skill from VKirill/claude-lane-stack.
$ npx skills add VKirill/claude-lane-stack --skill team-routes -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install VKirill/claude-lane-stack team-routes --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/VKirill/claude-lane-stack.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/lane-stack/skills/team-routes .claude/skills/team-routes && 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 "team-routes" agent skill from https://github.com/VKirill/claude-lane-stack/tree/main/plugins/lane-stack/skills/team-routes into .claude/skills/team-routes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-routes", 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/VKirill/claude-lane-stack/tree/main/plugins/lane-stack/skills/team-routesType 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 VKirill/claude-lane-stack --skill team-routes -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install VKirill/claude-lane-stack team-routes --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VKirill/claude-lane-stack.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/lane-stack/skills/team-routes .agents/skills/team-routes && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "team-routes" agent skill from https://github.com/VKirill/claude-lane-stack/tree/main/plugins/lane-stack/skills/team-routes into .agents/skills/team-routes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-routes", 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 VKirill/claude-lane-stack --skill team-routes -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install VKirill/claude-lane-stack team-routes --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VKirill/claude-lane-stack.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/lane-stack/skills/team-routes .cursor/skills/team-routes && 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 "team-routes" agent skill from https://github.com/VKirill/claude-lane-stack/tree/main/plugins/lane-stack/skills/team-routes into .cursor/skills/team-routes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-routes", 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/VKirill/claude-lane-stack.git --path plugins/lane-stack/skills/team-routes--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 VKirill/claude-lane-stack --skill team-routes -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install VKirill/claude-lane-stack team-routes --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VKirill/claude-lane-stack.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/lane-stack/skills/team-routes .gemini/skills/team-routes && 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 "team-routes" agent skill from https://github.com/VKirill/claude-lane-stack/tree/main/plugins/lane-stack/skills/team-routes into .gemini/skills/team-routes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-routes", 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 VKirill/claude-lane-stack team-routesInstalls 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 VKirill/claude-lane-stack --skill team-routes -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/VKirill/claude-lane-stack.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/lane-stack/skills/team-routes .github/skills/team-routes && 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 "team-routes" agent skill from https://github.com/VKirill/claude-lane-stack/tree/main/plugins/lane-stack/skills/team-routes into .github/skills/team-routes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-routes", 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 VKirill/claude-lane-stack --skill team-routes -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install VKirill/claude-lane-stack team-routes --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/VKirill/claude-lane-stack.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/lane-stack/skills/team-routes .opencode/skills/team-routes && 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 "team-routes" agent skill from https://github.com/VKirill/claude-lane-stack/tree/main/plugins/lane-stack/skills/team-routes into .opencode/skills/team-routes/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "team-routes", 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.
team-routesdev-orchestrator only. An agent skill from VKirill/claude-lane-stack.
Team Routes is an agent skill from VKirill/claude-lane-stack. dev-orchestrator only. Turns any request into a route of specialist and writer steps: which roles work, in what order, what each reads and writes. Use at the start of every new goal. SKIP: writer CLIs; specialists themselves.
Its SKILL.md is about 1.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/recipes.md` and `references/roles.md`).
It sits in Agent Workflows. The repository describes itself as: Multi-agent AI coding factory for one person — Claude Code PM + Codex/Qwen/Grok/Kimi/AGY writers, durable conveyor, auto-merge to main. The licence is MIT.
6 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 45fa19e. 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.
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.
Team Routes loads about 1.1k tokens when it runs, and up to ~2.2k if it reads all its reference files. Until then it costs about 59 tokens; SKILL.md has 587 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 VKirill/claude-lane-stack at commit 45fa19e, republished under its MIT licence (© VKirill). 587 words, ~1,132 tokens.
.claude/skills/team-routes/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.The operator states a goal, not a staffing plan. You decide who works on it. A page built without its SEO, UX and copy inputs comes back as placeholders and gets redone; a one-line fix sent through four specialists burns an hour of expensive models. Pick the smallest team that produces the artifact the operator actually needs.
Before Score/Decompose, write one line for yourself:
deliverable: <artifact> · surface: <page/app/feature> · slug: <kebab-slug>.
The deliverable is what the operator will open at the end: a gray prototype, a branded mockup, shipped code, an article, an audit report, an answer with sources. Ambiguous wording («сделай страницу») means the cheapest deliverable that still moves the goal (prototype before code) unless the operator said «в код», «на сайт», «задеплой» or the page already exists in code.
Start from the closest recipe in references/recipes.md.
Drop a step when its output already exists on disk and is not stale (for
example .agents/copy/pages/<slug>.md is there, so copy only fills gaps). Add a step
when the goal needs a role the recipe lacks. No recipe fits → compose a route
from the role cards in references/roles.md: each step's
inputs must be outputs of earlier steps or existing files.
Run steps in parallel when neither reads the other's output. Run them in order when one decides what the next one writes about (SEO intent before copy).
Not every request needs a route. Go straight to the existing Loop when the goal is product code with no new user-facing text or layout (bug, refactor, API, infra), or a question you can answer from the repo.
Post one Russian line, then start the first step in the same turn. Do not wait for approval: the operator asked for the result, and the line exists so they can redirect you.
Маршрут: seo ∥ design-lead (UX) → copy-lead → design-lead (прототип) → design-lead (аудит). Начинаю.For routes with 2+ specialist steps, also write the route file
.agents/plans/routes/<slug>.md (English):
goal: <operator goal, one line>
deliverable: <artifact>
steps:
- id: seo | role: seo-specialist | reads: [...] | writes: <path> | status: todo
- ...
decisions: [] # conflicts you resolved, with the reasonUpdate status after each step. It is how resume-project and a restarted
session know where the route stopped.
Every specialist prompt has the same five lines. The specialist sees only this prompt and the disk, so a missing READ path means the work is done blind.
GOAL: <operator goal + this step's part of it>
SLUG: <slug>
READ: <outputs of earlier steps and existing project files, as paths>
WRITE: <the one path this step owns>
DECIDE: <the questions this step must answer for the next step>Close with the role's normal sentinel (DONE <path> / FAILED <reason>).
Read the file from DONE, not the chat summary, before you start the next step.
Specialists do not talk to each other. You merge their outputs. When two outputs
conflict (SEO wants a long FAQ block, design wants one short screen), decide by
the deliverable's primary user action, record the call in decisions: with
one reason, and pass it to the next step through READ/DECIDE.
Ask the operator only for what no role can produce from the disk or the web:
prices, guarantees, the offer, legal claims, brand approval, money or
irreversible actions. Specialists must mark unknown facts [unknown], not
invent them. Collect those markers into one question for the operator at the end
of the route, not after each step.
End the route with the deliverable path, what each role contributed (one line
each), open [unknown] facts, and the next sensible step (for example «в код —
скажи "делай"»). A route that ends in code continues into the normal WRITE
Loop: specialist steps finish first, then run-init (Lane Pilot: lane_pilot_dispatch_writer, specialists via lane_pilot_specialist) with their outputs in
read_first. This keeps the Mode XOR rule: no research teammates on a goal
once its write run has started.
© VKirill, MIT. 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 2 other files (references) in plugins/lane-stack/skills/team-routes of VKirill/claude-lane-stack.
Open the folder on GitHubat commit 45fa19e
Team Routes 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 |
|---|---|---|---|---|---|---|
| Team Routes this skillVKirill/claude-lane-stack | 122 | — | ~1.1k | Automated safety check: Pass | MIT | |
| MCP Server Builderanthropics/skills | 180k | 63 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| Hook Development for Claude Code Pluginsanthropics/claude-plugins-official | 38k | 10 repos | ~4.1k | Automated safety check: Notes | Apache-2.0 | |
| Using Superpowersfarm-fe/farm | 5.6k | 36 repos | ~1.4k | Automated safety check: Pass | MIT | |
| Executing Plans Inlineobra/superpowers | 297k | 2 repos | ~5.1k | Automated safety check: Pass | MIT | |
| Skill CreatorAzure/azqr | 796 | 89 repos | ~8.2k | Automated safety check: Pass | Apache-2.0 |
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
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.
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
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.
Azure/azqr
Create new skills, modify and improve existing skills, and measure skill performance.
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.
VKirill/claude-lane-stack
Lane-stack design + brand intelligence (vendored ui-ux-pro-max).
VKirill/claude-lane-stack
Owner-facing architect for a new app or service. An agent skill from VKirill/claude-lane-stack.
VKirill/claude-lane-stack
Live browser QA + Playwright-compatible replay. An agent skill from VKirill/claude-lane-stack.
VKirill/claude-lane-stack
Карта файлов копирайта в .agents/copy/: шаблоны, статусы, цепочка audience→headlines→ux.
VKirill/claude-lane-stack
Dispatch copy-lead helpers: Tavily, Codex luna/terra, grok/X, OpenCode DeepSeek, Cursor Grok 4.6 medium-fast.
VKirill/claude-lane-stack
Keep living docs/ honest after code changes. An agent skill from VKirill/claude-lane-stack.
Categories
dev-orchestrator only. An agent skill from VKirill/claude-lane-stack. Team Routes is an agent skill from VKirill/claude-lane-stack. dev-orchestrator only.
Team Routes fits situations like: agent Workflows work in your project.
Run `npx skills add VKirill/claude-lane-stack --skill team-routes -a claude-code`. Or copy the skill folder (plugins/lane-stack/skills/team-routes in VKirill/claude-lane-stack) into .claude/skills/team-routes in your project. Claude Code loads it when a task matches its description.
Run `npx skills add VKirill/claude-lane-stack --skill team-routes -a codex`. Or copy the skill folder (plugins/lane-stack/skills/team-routes in VKirill/claude-lane-stack) into .agents/skills/team-routes 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 VKirill/claude-lane-stack --skill team-routes -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/team-routes, .gemini/skills/team-routes, .github/skills/team-routes and .opencode/skills/team-routes in your project.
SKILL.md names no scripts, command-line tools or credentials: Team Routes 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.
Team Routes is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 1.1k tokens (SKILL.md is roughly 4.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1k tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Team Routes: MCP Server Builder (anthropics/skills, 180k stars), Hook Development for Claude Code Plugins (anthropics/claude-plugins-official, 38k stars), Using Superpowers (farm-fe/farm, 5.6k stars) and Executing Plans Inline (obra/superpowers, 297k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
VKirill (a GitHub user) maintains it in VKirill/claude-lane-stack, which has 122 GitHub stars. The repository holds 49 skills in this directory. The repository was last updated on October 9, 2026.
Source: VKirill/claude-lane-stack on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.