API Designer
Jeffallan/claude-skills
Designs REST and GraphQL APIs from resource modeling to an OpenAPI 3.1 contract, with versioning, pagination and RFC 7807 error handling.
A skill your agent uses when changing API/DTO/schema/wire-format contracts, SSE/event payloads, shared protocol packages, or producer/consumer mappings across MahoShojo-Generator runtimes.
Install API Contract Change
$ npx skills add RunoreLab/MahoShojo-Generator --skill api-contract-change -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install RunoreLab/MahoShojo-Generator api-contract-change --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/RunoreLab/MahoShojo-Generator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/api-contract-change .claude/skills/api-contract-change && 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 "api-contract-change" agent skill from https://github.com/RunoreLab/MahoShojo-Generator/tree/feature%2Fv0.2.0_Battle_Growth_MahoShojo/.agents/skills/api-contract-change into .claude/skills/api-contract-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-contract-change", 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/RunoreLab/MahoShojo-Generator/tree/feature%2Fv0.2.0_Battle_Growth_MahoShojo/.agents/skills/api-contract-changeType 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 RunoreLab/MahoShojo-Generator --skill api-contract-change -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install RunoreLab/MahoShojo-Generator api-contract-change --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RunoreLab/MahoShojo-Generator.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.agents/skills/api-contract-change .agents/skills/api-contract-change && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "api-contract-change" agent skill from https://github.com/RunoreLab/MahoShojo-Generator/tree/feature%2Fv0.2.0_Battle_Growth_MahoShojo/.agents/skills/api-contract-change into .agents/skills/api-contract-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-contract-change", 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 RunoreLab/MahoShojo-Generator --skill api-contract-change -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install RunoreLab/MahoShojo-Generator api-contract-change --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RunoreLab/MahoShojo-Generator.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.agents/skills/api-contract-change .cursor/skills/api-contract-change && 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 "api-contract-change" agent skill from https://github.com/RunoreLab/MahoShojo-Generator/tree/feature%2Fv0.2.0_Battle_Growth_MahoShojo/.agents/skills/api-contract-change into .cursor/skills/api-contract-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-contract-change", 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/RunoreLab/MahoShojo-Generator.git --path .agents/skills/api-contract-change--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 RunoreLab/MahoShojo-Generator --skill api-contract-change -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install RunoreLab/MahoShojo-Generator api-contract-change --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RunoreLab/MahoShojo-Generator.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.agents/skills/api-contract-change .gemini/skills/api-contract-change && 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 "api-contract-change" agent skill from https://github.com/RunoreLab/MahoShojo-Generator/tree/feature%2Fv0.2.0_Battle_Growth_MahoShojo/.agents/skills/api-contract-change into .gemini/skills/api-contract-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-contract-change", 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 RunoreLab/MahoShojo-Generator api-contract-changeInstalls 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 RunoreLab/MahoShojo-Generator --skill api-contract-change -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/RunoreLab/MahoShojo-Generator.git skills-src && mkdir -p .github/skills && cp -r skills-src/.agents/skills/api-contract-change .github/skills/api-contract-change && 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 "api-contract-change" agent skill from https://github.com/RunoreLab/MahoShojo-Generator/tree/feature%2Fv0.2.0_Battle_Growth_MahoShojo/.agents/skills/api-contract-change into .github/skills/api-contract-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-contract-change", 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 RunoreLab/MahoShojo-Generator --skill api-contract-change -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install RunoreLab/MahoShojo-Generator api-contract-change --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/RunoreLab/MahoShojo-Generator.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.agents/skills/api-contract-change .opencode/skills/api-contract-change && 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 "api-contract-change" agent skill from https://github.com/RunoreLab/MahoShojo-Generator/tree/feature%2Fv0.2.0_Battle_Growth_MahoShojo/.agents/skills/api-contract-change into .opencode/skills/api-contract-change/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "api-contract-change", 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
api-contract-change- GitHub stars
- 167
- Token cost
- ~362 tokens
- SKILL.md length
- 139 words
- Files
- 1
- Skills in repo
- 4
- Repo updated
- First seen
- Licence
- Apache-2.0
At a glance
A skill your agent uses when changing API/DTO/schema/wire-format contracts, SSE/event payloads, shared protocol packages, or producer/consumer mappings across MahoShojo-Generator runtimes.
- Works in 7 steps: Locate the canonical schema/contract and… → Enumerate every producer, consumer,… → Separate internal telemetry/server… → …
- Changing API/DTO/schema/wire-format contracts
- SKILL.md covers Workflow and Stop / ask
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
API Contract Change is an agent skill from RunoreLab/MahoShojo-Generator. Use when changing API/DTO/schema/wire-format contracts, SSE/event payloads, shared protocol packages, or producer/consumer mappings across MahoShojo-Generator runtimes. Do not use for implementation-only changes that preserve the existing contract.
Its SKILL.md is about 360 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 API design. The repository describes itself as: 基于 AI 结构化生成的个性化魔法少女角色生成器。 The licence is Apache-2.0.
When your agent uses it
- Changing API/DTO/schema/wire-format contracts
- SSE/event payloads
- Shared protocol packages
- Producer/consumer mappings across MahoShojo-Generator runtimes
Example prompts
- “/api-contract-change”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Locate the canonical schema/contract and applicable accepted ADR/spec from the relevant docs topic.
- Enumerate every producer, consumer, mapper/adapter, persistence/replay path, public projection and compatibility test before editing.
- Separate internal telemetry/server fields from public client contracts; do not leak server-only authority or secrets through a convenience…
- Decide compatibility behavior explicitly: additive/backward-compatible, versioned, migration required, or intentionally breaking.
- Modify the canonical contract first, then synchronize producers/consumers and regenerate derived artifacts using existing repo tools.
- Add regression coverage at the boundary that previously allowed drift, including replay/reconnect paths when the protocol supports them.
- Run targeted contract/runtime tests first; expand to workspace/global verification only when shared boundaries changed.
What it can do on your machine
Read from SKILL.md and the folder at commit e7e8d4b. 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
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.
Network
No URLs in SKILL.md.
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
API Contract Change loads about 362 tokens when it runs. Until then it costs about 67 tokens; SKILL.md has 139 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
The full file from RunoreLab/MahoShojo-Generator at commit e7e8d4b, republished under its Apache-2.0 licence (© RunoreLab). 139 words, ~362 tokens.
Download SKILL.mdSave it as
.claude/skills/api-contract-change/SKILL.md (or your agent's skills folder).- name
- api-contract-change
- description
- Use when changing API/DTO/schema/wire-format contracts, SSE/event payloads, shared protocol packages, or producer/consumer mappings across MahoShojo-Generator runtimes. Do not use for implementation-only changes that preserve the existing contract.
API Contract Change
Workflow
- Locate the canonical schema/contract and applicable accepted ADR/spec from the relevant docs topic.
- Enumerate every producer, consumer, mapper/adapter, persistence/replay path, public projection and compatibility test before editing.
- Separate internal telemetry/server fields from public client contracts; do not leak server-only authority or secrets through a convenience projection.
- Decide compatibility behavior explicitly: additive/backward-compatible, versioned, migration required, or intentionally breaking.
- Modify the canonical contract first, then synchronize producers/consumers and regenerate derived artifacts using existing repo tools.
- Add regression coverage at the boundary that previously allowed drift, including replay/reconnect paths when the protocol supports them.
- Run targeted contract/runtime tests first; expand to workspace/global verification only when shared boundaries changed.
Stop / ask
Ask only when the desired breaking/compatibility policy is genuinely unresolved by current accepted docs or when production migration/cutover authorization is required.
© RunoreLab, 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
Files
Just SKILL.md in .agents/skills/api-contract-change of RunoreLab/MahoShojo-Generator.
Open the folder on GitHubat commit e7e8d4b
Compare with similar skills
API Contract Change 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 |
|---|---|---|---|---|---|---|
| API Contract Change this skillRunoreLab/MahoShojo-Generator | 167 | — | ~362 | Automated safety check: Pass | Apache-2.0 | |
| API DesignerJeffallan/claude-skills | 12k | 2 repos | ~2k | Automated safety check: Pass | MIT | |
| Nodejs Backend Patternsever-works/ever-works | 158 | 18 repos | ~4k | Automated safety check: Pass | AGPL-3.0 | |
| Pangolin CRUD Endpointsfosrl/pangolin | 23k | — | ~461 | Automated safety check: Pass | Custom licence | |
| API Design Principlesjh941213/my-cc-harness | 126 | 20 repos | ~3.4k | Automated safety check: Pass | None | |
| Backend PatternshellangleZ/burn-in-cceverywhere-ralph | 112 | 17 repos | ~3.3k | Automated safety check: Pass | None |
Similar skills
Nodejs Backend Patterns
ever-works/ever-works
Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices.
Pangolin CRUD Endpoints
fosrl/pangolin
Use whenever asked to add, create, or scaffold a CRUD endpoint, router, or entity in this repo's server (create/list/get/update/delete handlers, new…
API Design Principles
jh941213/my-cc-harness
REST 및 GraphQL API 설계 원칙 가이드. An agent skill from jh941213/my-cc-harness.
Backend Patterns
hellangleZ/burn-in-cceverywhere-ralph
Backend architecture patterns, API design, database optimization, and server-side best practices for Node.js, Express, and Next.js API routes.
API And Interface Design
dzhalaevd/Donatello
Guides stable API and interface design. An agent skill from dzhalaevd/Donatello.
More from RunoreLab/MahoShojo-Generator
Code Review
RunoreLab/MahoShojo-Generator
A skill your agent uses when reviewing MahoShojo-Generator code, a branch, commit range, pull request, or implementation against current behavior and accepted ADR/spec requirements.
Platform Migration
RunoreLab/MahoShojo-Generator
A skill your agent uses for platform-rearchitecture, runtime migration, hosted/local routing changes, storage/session/DR migrations, or staged movement between old and new application boundaries in…
Release Readiness
RunoreLab/MahoShojo-Generator
A skill your agent uses when preparing or reviewing a MahoShojo-Generator version release, release candidate, changelog/docs readiness, deployment impact, migration notes, or final pre-release…
Related
Categories
Questions about API Contract Change
What does API Contract Change do?
A skill your agent uses when changing API/DTO/schema/wire-format contracts, SSE/event payloads, shared protocol packages, or producer/consumer mappings across MahoShojo-Generator runtimes. API Contract Change is an agent skill from RunoreLab/MahoShojo-Generator. Use when changing API/DTO/schema/wire-format contracts, SSE/event payloads, shared protocol packages, or producer/consumer mappings across MahoShojo-Generator runtimes.
When should I use API Contract Change?
API Contract Change fits situations like: changing API/DTO/schema/wire-format contracts; SSE/event payloads; shared protocol packages; producer/consumer mappings across MahoShojo-Generator runtimes.
How do I install API Contract Change in Claude Code?
Run `npx skills add RunoreLab/MahoShojo-Generator --skill api-contract-change -a claude-code`. Or copy the skill folder (.agents/skills/api-contract-change in RunoreLab/MahoShojo-Generator) into .claude/skills/api-contract-change in your project. Claude Code loads it when a task matches its description.
How do I install API Contract Change in Codex?
Run `npx skills add RunoreLab/MahoShojo-Generator --skill api-contract-change -a codex`. Or copy the skill folder (.agents/skills/api-contract-change in RunoreLab/MahoShojo-Generator) into .agents/skills/api-contract-change in your project. Codex loads it when a task matches its description.
Can I use API Contract Change 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 RunoreLab/MahoShojo-Generator --skill api-contract-change -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/api-contract-change, .gemini/skills/api-contract-change, .github/skills/api-contract-change and .opencode/skills/api-contract-change in your project.
What does API Contract Change need to run?
SKILL.md names no scripts, command-line tools or credentials: API Contract Change is instructions for the agent only.
Does API Contract Change 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 API Contract Change 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 API Contract Change use?
API Contract Change is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does API Contract Change use?
About 362 tokens (SKILL.md is roughly 1.4k 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 API Contract Change?
Skills that share tags, products or a category with API Contract Change: API Designer (Jeffallan/claude-skills, 12k stars), Nodejs Backend Patterns (ever-works/ever-works, 158 stars), Pangolin CRUD Endpoints (fosrl/pangolin, 23k stars) and API Design Principles (jh941213/my-cc-harness, 126 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains API Contract Change?
RunoreLab (a GitHub organization) maintains it in RunoreLab/MahoShojo-Generator, which has 167 GitHub stars. The repository holds 4 skills in this directory. The repository was last updated on October 8, 2026.
Source: RunoreLab/MahoShojo-Generator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.