add-api-version
This workflow guides the addition or modification of Dropshot HTTP API endpoints while ensuring proper versioning.
Install
mkdir -p .claude/skills/add-api-version && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/7785" && unzip -o skill.zip -d .claude/skills/add-api-version && rm skill.zipInstalls to .claude/skills/add-api-version
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
Add a new version to a Dropshot HTTP API. Use when the user wants to make versioned changes to a Dropshot-managed HTTP API, such as adding, making changes to, or removing an API endpoint.Key capabilities
- →Fetches official versioning guides for Dropshot
- →Structures API change requests
- →Manages endpoint deprecation and additions
How it works
It pulls authoritative workflow documentation and guides the user through sequential steps to modify API definitions.
Inputs & outputs
When to use add-api-version
- →Add new API endpoint version
- →Modify existing Dropshot API
- →Remove deprecated API versions
About this skill
Add API version
Add a new version to a Dropshot API in this repository.
Instructions
Follow these steps in order. Do not skip ahead.
Step 1: Fetch the guide
Fetch the guide from the dropshot-api-manager repository:
curl -fsSL https://raw.githubusercontent.com/oxidecomputer/dropshot-api-manager/refs/heads/main/guides/new-version.md
Do not summarize the guide. Read and follow it exactly as written. Remember to fetch RFD 619 for context.
Step 2: Ascertain the scope of the request
If not already provided, ask the user:
- Which API they would like to change.
- What changes to make.
Step 3: Make the change
Follow the guide carefully and systematically to add a new version to the provided API which makes the given changes.
Follow the guide step by step; do not skip any steps.
When not to use it
- →Modifying non-Dropshot APIs
- →Quick/non-versioned API prototypes
Prerequisites
Limitations
- →Must follow guide steps exactly
- →Only for Dropshot-managed APIs
- →High dependency on external guide content
How it compares
It ensures strict compliance with Dropshot-specific versioning standards instead of ad-hoc API updates.
Compared to similar skills
add-api-version side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| add-api-version (this skill) | 1 | 6mo | Review | Advanced |
| solana-dev | 0 | 3mo | Review | Advanced |
| mcp | 0 | 7mo | Review | Advanced |
| solana-dev | 0 | 4mo | No flags | Beginner |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by oxidecomputer
View all by oxidecomputer →You might also like
solana-dev
mashharuki
Use when user asks to "build a Solana dapp", "write an Anchor program", "create a token", "debug Solana errors", "set up wallet connection", "test my Solana program", "deploy to devnet", or "explain Solana concepts" (rent, accounts, PDAs, CPIs, etc.). End-to-end Solana development playbook covering
mcp
Piebald-AI
Guide for working with Splitrail's MCP server. Use when adding tools, resources, or modifying the MCP interface.
solana-dev
solanabr
Unified skill hub for Solana development. Routes to external submodule skills (solana-foundation, sendai, solana-game, trailofbits, cloudflare, qedgen, colosseum) and local skills. Progressive disclosure — read only what you need.
azure-eventhub-rust
RJsolucoes
|
use-rest-api
torrust
Use the Torrust Tracker REST API. Covers authentication, all endpoints (stats, metrics, torrents, auth keys, whitelist), and making announce/scrape requests to verify API behaviour. Triggers on "use API", "test API", "call REST API", "query API", "API endpoint", "curl tracker", "tracker client", "an
tauri
EpicenterHQ
Tauri path handling, cross-platform file operations, and API usage. Use when working with file paths in Tauri frontend code, accessing filesystem APIs, or handling platform differences in desktop apps.