Official Agent Skills for the DevSpeak technical translation platform. Use these skills in Claude Code, Claude Desktop, Cursor, Windsurf, VS Code Copilot, Zed, or any MCP-compatible agent environment.
DevSpeak converts informal stakeholder requirements into formal, audience-specific technical specifications — Technical Specs, Jira Tickets, API Designs, RFCs, Data Models, and more.
| Skill | Trigger phrases |
|---|---|
devspeak-readme |
"Translate this README", "Rewrite the README for Senior Devs" |
devspeak-docs |
"Translate these API docs", "Formalize this onboarding guide" |
devspeak-comments |
"Translate the comments in this file", "Fix these docstrings" |
devspeak-release-notes |
"Draft release notes from these commits", "Translate this changelog" |
Each skill's SKILL.md instructs the agent on when and how to invoke the DevSpeak MCP tools.
- A DevSpeak account at devspeak.dev
- An API key — generate one from Settings → API Keys in the DevSpeak dashboard
- The DevSpeak MCP server installed in your agent environment (see below)
- Node.js 18 or later
Add the following config to your agent IDE. Replace dsk_live_your_key_here with your actual API key.
~/.claude/settings.json (user-level) or .claude/settings.json (project-level):
{
"mcpServers": {
"devspeak": {
"command": "npx",
"args": ["-y", "-p", "@devspeak/mcp", "devspeak-mcp"],
"env": {
"DEVSPEAK_API_KEY": "dsk_live_your_key_here"
}
}
}
}~/Library/Application Support/Claude/claude_desktop_config.json (macOS)
%APPDATA%\Claude\claude_desktop_config.json (Windows)
{
"mcpServers": {
"devspeak": {
"command": "npx",
"args": ["-y", "-p", "@devspeak/mcp", "devspeak-mcp"],
"env": {
"DEVSPEAK_API_KEY": "dsk_live_your_key_here"
}
}
}
}.cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
{
"mcpServers": {
"devspeak": {
"command": "npx",
"args": ["-y", "-p", "@devspeak/mcp", "devspeak-mcp"],
"env": {
"DEVSPEAK_API_KEY": "dsk_live_your_key_here"
}
}
}
}~/.codeium/windsurf/mcp_config.json:
{
"mcpServers": {
"devspeak": {
"command": "npx",
"args": ["-y", "-p", "@devspeak/mcp", "devspeak-mcp"],
"env": {
"DEVSPEAK_API_KEY": "dsk_live_your_key_here"
}
}
}
}.vscode/mcp.json at the workspace root:
{
"servers": {
"devspeak": {
"type": "stdio",
"command": "npx",
"args": ["-y", "-p", "@devspeak/mcp", "devspeak-mcp"],
"env": {
"DEVSPEAK_API_KEY": "dsk_live_your_key_here"
}
}
}
}Zed → Settings → Assistant → assistant.json:
{
"context_servers": {
"devspeak": {
"command": {
"path": "npx",
"args": ["-y", "-p", "@devspeak/mcp", "devspeak-mcp"],
"env": {
"DEVSPEAK_API_KEY": "dsk_live_your_key_here"
}
}
}
}
}Install all DevSpeak skills at once:
claw install devspeak-dev/devspeak-skillsInstall a single skill:
claw install devspeak-dev/devspeak-skills/devspeak-readme
claw install devspeak-dev/devspeak-skills/devspeak-docs
claw install devspeak-dev/devspeak-skills/devspeak-comments
claw install devspeak-dev/devspeak-skills/devspeak-release-notesPoint your skill loader at this repository:
https://github.com/devspeak-dev/devspeak-skills
Each skill lives at skills/<skill-name>/SKILL.md.
After installing the MCP server and at least one skill, ask your agent:
Run auth_confirm on the DevSpeak MCP server.
A successful response confirms the API key is valid and the server is reachable.
The DevSpeak MCP server is published on npm as @devspeak/mcp.
Tools exposed:
| Tool | Purpose |
|---|---|
translate_text |
Translate informal input into a formal technical spec |
translate_markdown |
Translate README / docs preserving Markdown structure |
refine_translation |
Iteratively refine generated output from feedback |
detect_language |
Detect the natural language of input text |
list_languages |
Return supported natural languages |
auth_confirm |
Verify API credentials |
patch_translation_note |
Surgically update a note in the DevSpeak Notes Workspace |
- Platform: devspeak.dev
- MCP server on npm: @devspeak/mcp
- CLI: @devspeak/cli
- VS Code Extension: search DevSpeak in the VS Code Marketplace
- API Reference: devspeak.dev/docs