Spikard
Goldziher/spikard
Scaffold Spikard projects and generate code from OpenAPI, AsyncAPI, OpenRPC, GraphQL, and Protobuf schemas using the Spikard CLI or its MCP server.
A skill your agent uses when adding or changing Archestra backend routes, models, services, API request/response schemas, endpoint permissions, or OpenAPI/codegen for the generated API client.
Install Archestra Dev Backend
$ npx skills add archestra-ai/archestra --skill archestra-dev-backend -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install archestra-ai/archestra archestra-dev-backend --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/archestra-ai/archestra.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/archestra-dev-backend .claude/skills/archestra-dev-backend && 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 "archestra-dev-backend" agent skill from https://github.com/archestra-ai/archestra/tree/main/.agents/skills/archestra-dev-backend into .claude/skills/archestra-dev-backend/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "archestra-dev-backend", 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/archestra-ai/archestra/tree/main/.agents/skills/archestra-dev-backendType 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 archestra-ai/archestra --skill archestra-dev-backend -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install archestra-ai/archestra archestra-dev-backend --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/archestra-ai/archestra.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/archestra-dev-backend .agents/skills/archestra-dev-backend && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "archestra-dev-backend" agent skill from https://github.com/archestra-ai/archestra/tree/main/.agents/skills/archestra-dev-backend into .agents/skills/archestra-dev-backend/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "archestra-dev-backend", 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 archestra-ai/archestra --skill archestra-dev-backend -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install archestra-ai/archestra archestra-dev-backend --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/archestra-ai/archestra.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/archestra-dev-backend .cursor/skills/archestra-dev-backend && 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 "archestra-dev-backend" agent skill from https://github.com/archestra-ai/archestra/tree/main/.agents/skills/archestra-dev-backend into .cursor/skills/archestra-dev-backend/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "archestra-dev-backend", 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/archestra-ai/archestra.git --path .agents/skills/archestra-dev-backend--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 archestra-ai/archestra --skill archestra-dev-backend -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install archestra-ai/archestra archestra-dev-backend --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/archestra-ai/archestra.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/archestra-dev-backend .gemini/skills/archestra-dev-backend && 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 "archestra-dev-backend" agent skill from https://github.com/archestra-ai/archestra/tree/main/.agents/skills/archestra-dev-backend into .gemini/skills/archestra-dev-backend/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "archestra-dev-backend", 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 archestra-ai/archestra archestra-dev-backendInstalls 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 archestra-ai/archestra --skill archestra-dev-backend -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/archestra-ai/archestra.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/archestra-dev-backend .github/skills/archestra-dev-backend && 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 "archestra-dev-backend" agent skill from https://github.com/archestra-ai/archestra/tree/main/.agents/skills/archestra-dev-backend into .github/skills/archestra-dev-backend/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "archestra-dev-backend", 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 archestra-ai/archestra --skill archestra-dev-backend -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install archestra-ai/archestra archestra-dev-backend --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/archestra-ai/archestra.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/archestra-dev-backend .opencode/skills/archestra-dev-backend && 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 "archestra-dev-backend" agent skill from https://github.com/archestra-ai/archestra/tree/main/.agents/skills/archestra-dev-backend into .opencode/skills/archestra-dev-backend/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "archestra-dev-backend", 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
archestra-dev-backend- GitHub stars
- 4.4k
- Token cost
- ~1.5k tokens
- SKILL.md length
- 606 words
- Files
- 1
- Skills in repo
- 23
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
A skill your agent uses when adding or changing Archestra backend routes, models, services, API request/response schemas, endpoint permissions, or OpenAPI/codegen for the generated API client.
- Works in 5 steps: Add a RouteId entry in… → Add the route handler (see Route layout… → Add the endpoint to… → …
- Changing Archestra backend routes
- SKILL.md covers Adding or changing an API…, Route layout, The 403 footgun (deny by… and Route conventions, plus 6 more sections
- Calls pnpm
What it does
Archestra Dev Backend is an agent skill from archestra-ai/archestra. Use when adding or changing Archestra backend routes, models, services, API request/response schemas, endpoint permissions, or OpenAPI/codegen for the generated API client.
Its SKILL.md is about 1.5k 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 Backend & APIs, covering Project scaffolding, MCP servers and OpenAPI specifications. It works with OpenAPI. The repository describes itself as: Enterprise AI Platform with guardrails, MCP registry, gateway & orchestrator.
When your agent uses it
- Changing Archestra backend routes
- API request/response schemas
- Endpoint permissions
- OpenAPI/codegen for the generated API client
Example prompts
- “/archestra-dev-backend”
Workflow steps
5 steps, taken from the first numbered list in SKILL.md.
- Add a RouteId entry in platform/shared/routes.ts and set it as the route schema's operationId.
- Add the route handler (see Route layout and Route conventions below).
- Add the endpoint to requiredEndpointPermissionsMap in platform/shared/access-control.ts (see The 403 footgun).
- Check the MCP-tool mirror (see below).
- Run codegen, then validation (see Codegen and Validation).
What it can do on your machine
Read from SKILL.md and the folder at commit 268f421. 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
Shell commands in SKILL.md call:
pnpm
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.
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
Archestra Dev Backend loads about 1.5k tokens when it runs. Until then it costs about 49 tokens; SKILL.md has 606 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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 606 words (~1,537 tokens).
“Use this skill before changing files under platform/backend/ (except unit tests — see archestra-dev-testing/references/backend-tests.md). Run all commands from platform/.”
- name
- archestra-dev-backend
Files
Just SKILL.md in .agents/skills/archestra-dev-backend of archestra-ai/archestra.
Open the folder on GitHubat commit 268f421
Compare with similar skills
Archestra Dev Backend 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 |
|---|---|---|---|---|---|---|
| Archestra Dev Backend this skillarchestra-ai/archestra | 4.4k | — | ~1.5k | Automated safety check: Pass | Custom licence | |
| SpikardGoldziher/spikard | 123 | — | ~799 | Automated safety check: Pass | MIT | |
| MCP Server Builderalirezarezvani/claude-skills | 28k | — | ~985 | Automated safety check: Pass | MIT | |
| Flutter MCP Boundary AuditArenukvern/mcp_flutter | 386 | — | ~3k | Automated safety check: Pass | MIT | |
| ToolJet Marketplace Plugin BuilderToolJet/ToolJet | 41k | — | ~2.1k | Automated safety check: Pass | AGPL-3.0 | |
| OpenAPI to MCP Servermcp-use/mcp-use | 11k | — | ~5.2k | Automated safety check: Pass | Apache-2.0 |
Similar skills
MCP Server Builder
alirezarezvani/claude-skills
Design and ship production-ready MCP (Model Context Protocol) servers from OpenAPI contracts instead of hand-written tool wrappers.
Flutter MCP Boundary Audit
Arenukvern/mcp_flutter
Generic contract/schema boundary audit across authoring, discovery, validation, and execute—detecting split-brain between listings and invoke paths, gateway divergence, and permissive placeholders.
ToolJet Marketplace Plugin Builder
ToolJet/ToolJet
Turns an API description, such as an OpenAPI file or a Postman collection, into a connector plugin for ToolJet's marketplace and checks it with the repo's validator.
OpenAPI to MCP Server
mcp-use/mcp-use
Turns an OpenAPI or Swagger spec into an MCP server with the mcp-use TypeScript SDK, mapping each operation to a tool, wiring auth, testing and deploying.
API Endpoint Contract
trycompai/comp
The contract every new or modified API endpoint must follow so it is correct for the public OpenAPI spec, the MCP server (npm @trycompai/mcp-server), the ValidationPipe, and the docs.
More from archestra-ai/archestra
All 23 skills in this repoMigrate To Archestra
archestra-ai/archestra
Migrate an existing agentic PoC/pilot (Claude Code project files, MCP configs, hooks, local tools, openclaw config, or similar hand-rolled setup artifacts) into an Archestra instance.
Archestra Dev Testing
archestra-ai/archestra
A skill your agent uses for test selection and quality across backend, frontend, and e2e; load its backend reference for Vitest projects, mocking, DB fixtures, and performance.
Archestra Dev E2E
archestra-ai/archestra
A skill your agent uses when writing, debugging, or running Archestra Playwright e2e tests, API/UI fixtures, WireMock-backed tests, local/CI e2e setup, or test selectors.
Archestra Dev Frontend
archestra-ai/archestra
A skill your agent uses when modifying Archestra frontend Next.js/React code, UI components, forms, TanStack Query hooks, generated API client usage, frontend copy, or documentation links.
Archestra Dev LLM Providers
archestra-ai/archestra
A skill your agent uses when adding an LLM provider, changing proxy adapters or provider routes, fixing streaming/tool-call translation bugs, editing model fetchers or model handling, or touching…
Archestra Dev Migrations
archestra-ai/archestra
A skill your agent uses when changing Drizzle schemas, generating migrations, editing migration SQL, creating data-only migrations, diagnosing drizzle-kit check failures, or resolving…
Related
Works with
Categories
Questions about Archestra Dev Backend
What does Archestra Dev Backend do?
A skill your agent uses when adding or changing Archestra backend routes, models, services, API request/response schemas, endpoint permissions, or OpenAPI/codegen for the generated API client. Archestra Dev Backend is an agent skill from archestra-ai/archestra. Use when adding or changing Archestra backend routes, models, services, API request/response schemas, endpoint permissions, or OpenAPI/codegen for the generated API client.
When should I use Archestra Dev Backend?
Archestra Dev Backend fits situations like: changing Archestra backend routes; API request/response schemas; endpoint permissions; openAPI/codegen for the generated API client.
How do I install Archestra Dev Backend in Claude Code?
Run `npx skills add archestra-ai/archestra --skill archestra-dev-backend -a claude-code`. Or copy the skill folder (.agents/skills/archestra-dev-backend in archestra-ai/archestra) into .claude/skills/archestra-dev-backend in your project. Claude Code loads it when a task matches its description.
How do I install Archestra Dev Backend in Codex?
Run `npx skills add archestra-ai/archestra --skill archestra-dev-backend -a codex`. Or copy the skill folder (.agents/skills/archestra-dev-backend in archestra-ai/archestra) into .agents/skills/archestra-dev-backend in your project. Codex loads it when a task matches its description.
Can I use Archestra Dev Backend 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 archestra-ai/archestra --skill archestra-dev-backend -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/archestra-dev-backend, .gemini/skills/archestra-dev-backend, .github/skills/archestra-dev-backend and .opencode/skills/archestra-dev-backend in your project.
What does Archestra Dev Backend need to run?
Going by SKILL.md and its folder, Archestra Dev Backend needs the command-line tools its instructions call (pnpm).
Does Archestra Dev Backend 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 Archestra Dev Backend 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 Archestra Dev Backend use?
Archestra Dev Backend has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Archestra Dev Backend use?
About 1.5k tokens (SKILL.md is roughly 6.1k 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 Archestra Dev Backend?
Skills that share tags, products or a category with Archestra Dev Backend: Spikard (Goldziher/spikard, 123 stars), MCP Server Builder (alirezarezvani/claude-skills, 28k stars), Flutter MCP Boundary Audit (Arenukvern/mcp_flutter, 386 stars) and ToolJet Marketplace Plugin Builder (ToolJet/ToolJet, 41k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Archestra Dev Backend?
archestra-ai (a GitHub organization) maintains it in archestra-ai/archestra, which has 4,354 GitHub stars. The repository holds 23 skills in this directory. The repository was last updated on October 8, 2026.
Source: archestra-ai/archestra on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.