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.
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
$ npx skills add griddynamics/rosetta --skill specflow-use -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install griddynamics/rosetta specflow-use --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/griddynamics/rosetta.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/core-claude/skills/specflow-use .claude/skills/specflow-use && 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 "specflow-use" agent skill from https://github.com/griddynamics/rosetta/tree/main/plugins/core-claude/skills/specflow-use into .claude/skills/specflow-use/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specflow-use", 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/griddynamics/rosetta/tree/main/plugins/core-claude/skills/specflow-useType 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 griddynamics/rosetta --skill specflow-use -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install griddynamics/rosetta specflow-use --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/griddynamics/rosetta.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/core-claude/skills/specflow-use .agents/skills/specflow-use && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "specflow-use" agent skill from https://github.com/griddynamics/rosetta/tree/main/plugins/core-claude/skills/specflow-use into .agents/skills/specflow-use/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specflow-use", 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 griddynamics/rosetta --skill specflow-use -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install griddynamics/rosetta specflow-use --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/griddynamics/rosetta.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/core-claude/skills/specflow-use .cursor/skills/specflow-use && 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 "specflow-use" agent skill from https://github.com/griddynamics/rosetta/tree/main/plugins/core-claude/skills/specflow-use into .cursor/skills/specflow-use/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specflow-use", 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/griddynamics/rosetta.git --path plugins/core-claude/skills/specflow-use--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 griddynamics/rosetta --skill specflow-use -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install griddynamics/rosetta specflow-use --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/griddynamics/rosetta.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/core-claude/skills/specflow-use .gemini/skills/specflow-use && 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 "specflow-use" agent skill from https://github.com/griddynamics/rosetta/tree/main/plugins/core-claude/skills/specflow-use into .gemini/skills/specflow-use/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specflow-use", 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 griddynamics/rosetta specflow-useInstalls 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 griddynamics/rosetta --skill specflow-use -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/griddynamics/rosetta.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/core-claude/skills/specflow-use .github/skills/specflow-use && 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 "specflow-use" agent skill from https://github.com/griddynamics/rosetta/tree/main/plugins/core-claude/skills/specflow-use into .github/skills/specflow-use/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specflow-use", 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 griddynamics/rosetta --skill specflow-use -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install griddynamics/rosetta specflow-use --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/griddynamics/rosetta.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/core-claude/skills/specflow-use .opencode/skills/specflow-use && 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 "specflow-use" agent skill from https://github.com/griddynamics/rosetta/tree/main/plugins/core-claude/skills/specflow-use into .opencode/skills/specflow-use/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "specflow-use", 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.
specflow-useTo connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
Specflow Use is an agent skill from griddynamics/rosetta. To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
Its SKILL.md is about 780 tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `README.md`, `references/specflow-mcp-tools.md` and `references/specflow-schema.md`).
It sits in Agent Workflows, covering MCP servers. It works with Model Context Protocol. The repository describes itself as: An instruction layer for AI coding agent. The licence is Apache-2.0.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 5441232. 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.
Specflow Use loads about 780 tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 31 tokens; SKILL.md has 324 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 griddynamics/rosetta at commit 5441232, republished under its Apache-2.0 licence (© griddynamics). 324 words, ~780 tokens.
.claude/skills/specflow-use/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.This skill helps you drive Grid Dynamics SpecFlow from a local workspace via SpecFlow MCP. Rosetta stays local; SpecFlow runs everything remotely. The skill loads project context from gain.json and guides the user through SpecFlow MCP tool usage.
SpecFlow MCP is the only user interface to SpecFlow: you order work and download outputs. You do not connect to or operate on the remote workspaces directly.
When the user mentions SpecFlow or works in a SpecFlow-enabled project:
gain.json at the workspace root (and up to 2 parents). If missing, SpecFlow MCP will create it on the first tool call (together with specflow_session.json).references/specflow-mcp-tools.md.Check for gain.json at the current workspace root. If not found, check parent directories up to 2 levels. If still missing, tell the user this workspace is not yet initialized for SpecFlow — the first SpecFlow MCP tool call will create both gain.json and specflow_session.json.
When gain.json is found, present a compact summary:
## SpecFlow Project Context
**Description**: [gain.json.description]
**Services**: specflow — [gain.json.servicesDescription.specflow]
rosetta — [gain.json.servicesDescription.rosetta]
**Supported Coding Agents**: [gain.json.codingAgents]
**Versions**:
- rosetta: [gain.json.versions.rosetta]
- specflow: [gain.json.versions.specflow]
**Vocabulary overrides** (if present in gain.json.vocabulary):
- (See references/specflow-vocabulary.md for defaults.)Compare gain.json.versions.rosetta with the current Rosetta version:
APPLY SKILL FILE references/specflow-mcp-tools.md to route the user to the correct phase (pregeneration, generation, or post-run).
When SpecFlow returns a review report and the user wants to fix their specs before another iteration, delegate to Rosetta core:
skills/requirements-authoringworkflows/requirements-authoring-flow.mdThat skill handles iterative requirement updates with explicit user approval — matching the "consolidate the review report into updated specs" loop.
Read as needed:
references/specflow-mcp-tools.md — Phase routing and post-run skill bootstrap.references/specflow-vocabulary.md — Status values and checkpoint gates users encounter in responses.references/specflow-schema.md — Session files, version channels, and status enum quick lookup.© griddynamics, 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 4 other files (references) in plugins/core-claude/skills/specflow-use of griddynamics/rosetta.
Open the folder on GitHubat commit 5441232
Specflow Use 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 |
|---|---|---|---|---|---|---|
| Specflow Use this skillgriddynamics/rosetta | 353 | — | ~780 | Automated safety check: Pass | Apache-2.0 | |
| MCP Server Builderanthropics/skills | 180k | 62 repos | ~2.3k | Automated safety check: Pass | Apache-2.0 | |
| MCP Server BuildershareAI-lab/learn-claude-code | 78k | 5 repos | ~1.2k | Automated safety check: Pass | MIT | |
| MCP Integration for Pluginsanthropics/claude-plugins-official | 37k | 11 repos | ~3.1k | Automated safety check: Pass | Apache-2.0 | |
| Fastmcp Client CLIPrefectHQ/fastmcp | 28k | 1 repos | ~823 | Automated safety check: Pass | Apache-2.0 | |
| Crush Configurationcharmbracelet/crush | 29k | — | ~3.7k | Automated safety check: Pass | Custom licence |
anthropics/skills
Guides the design and implementation of Model Context Protocol servers in TypeScript or Python, from tool naming and error messages to evaluation.
shareAI-lab/learn-claude-code
Walks through building MCP servers in Python or TypeScript that expose tools, resources and prompts to Claude, with templates, registration and testing.
anthropics/claude-plugins-official
Explains how to bundle Model Context Protocol servers in a Claude Code plugin, covering config files, stdio, SSE, HTTP and WebSocket server types, and authentication.
PrefectHQ/fastmcp
Query and invoke tools on MCP servers using fastmcp list and fastmcp call.
charmbracelet/crush
Explains how to configure the Crush coding agent with crushrc or crush.json, covering providers, models, LSPs, MCP servers, hooks, permissions and config precedence.
mksglu/context-mode
Routes large command, file, API and browser output through context-mode tools so only the needed result enters the agent's context, instead of dumping it via Bash.
griddynamics/rosetta
Collect GitHub repo health/usage stats into merged JSON. An agent skill from griddynamics/rosetta.
griddynamics/rosetta
Workflow for onboarding an external private library so AI can use it without source access.
griddynamics/rosetta
To build an AI harness: run, observe, validate, automate repeated work faster — CLI/MCP actions, devcontainers, skills, subagents, hooks, pipelines, automations.
griddynamics/rosetta
To orchestrate parallel coding-agent farms (Claude, Codex, Copilot, Gemini, etc.) on isolated git worktrees.
griddynamics/rosetta
To author, register, and test Rosetta hooks, add a SemanticKind, or debug a hook that won't fire.
griddynamics/rosetta
Compress a Rosetta KB prompt artifact (skill · workflow · phase · rule · agent · template · generic) by stripping structural tautology and ineffective scaffolding while preserving every…
Works with
Categories
To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed. Specflow Use is an agent skill from griddynamics/rosetta. To connect Rosetta with Grid Dynamics SpecFlow MCP; only when SpecFlow is mentioned and the MCP is installed.
Specflow Use fits situations like: tasks that involve MCP servers.
Run `npx skills add griddynamics/rosetta --skill specflow-use -a claude-code`. Or copy the skill folder (plugins/core-claude/skills/specflow-use in griddynamics/rosetta) into .claude/skills/specflow-use in your project. Claude Code loads it when a task matches its description.
Run `npx skills add griddynamics/rosetta --skill specflow-use -a codex`. Or copy the skill folder (plugins/core-claude/skills/specflow-use in griddynamics/rosetta) into .agents/skills/specflow-use 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 griddynamics/rosetta --skill specflow-use -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/specflow-use, .gemini/skills/specflow-use, .github/skills/specflow-use and .opencode/skills/specflow-use in your project.
SKILL.md names no scripts, command-line tools or credentials: Specflow Use 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.
Specflow Use is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
About 780 tokens (SKILL.md is roughly 3.1k 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 937 tokens, read only when the agent opens those files.
Skills that share tags, products or a category with Specflow Use: MCP Server Builder (anthropics/skills, 180k stars), MCP Server Builder (shareAI-lab/learn-claude-code, 78k stars), MCP Integration for Plugins (anthropics/claude-plugins-official, 37k stars) and Fastmcp Client CLI (PrefectHQ/fastmcp, 28k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
griddynamics (a GitHub organization) maintains it in griddynamics/rosetta, which has 353 GitHub stars. The repository holds 12 skills in this directory. The repository was last updated on September 29, 2026.
Source: griddynamics/rosetta on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.