API Patterns
dilolabs/nosia
Builds REST APIs using respondto blocks with Jbuilder templates following the 37signals same-controllers-different-formats philosophy.
Implement, build, create, or add any feature, endpoint, page, component, or functionality.
$ npx skills add avibebuilder/claude-prime --skill cook -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install avibebuilder/claude-prime cook --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/avibebuilder/claude-prime.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/cook .claude/skills/cook && 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 "cook" agent skill from https://github.com/avibebuilder/claude-prime/tree/main/.claude/skills/cook into .claude/skills/cook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cook", 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/avibebuilder/claude-prime/tree/main/.claude/skills/cookType 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 avibebuilder/claude-prime --skill cook -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install avibebuilder/claude-prime cook --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avibebuilder/claude-prime.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/cook .agents/skills/cook && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "cook" agent skill from https://github.com/avibebuilder/claude-prime/tree/main/.claude/skills/cook into .agents/skills/cook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cook", 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 avibebuilder/claude-prime --skill cook -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install avibebuilder/claude-prime cook --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avibebuilder/claude-prime.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/cook .cursor/skills/cook && 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 "cook" agent skill from https://github.com/avibebuilder/claude-prime/tree/main/.claude/skills/cook into .cursor/skills/cook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cook", 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/avibebuilder/claude-prime.git --path .claude/skills/cook--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 avibebuilder/claude-prime --skill cook -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install avibebuilder/claude-prime cook --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avibebuilder/claude-prime.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/cook .gemini/skills/cook && 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 "cook" agent skill from https://github.com/avibebuilder/claude-prime/tree/main/.claude/skills/cook into .gemini/skills/cook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cook", 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 avibebuilder/claude-prime cookInstalls 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 avibebuilder/claude-prime --skill cook -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/avibebuilder/claude-prime.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/cook .github/skills/cook && 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 "cook" agent skill from https://github.com/avibebuilder/claude-prime/tree/main/.claude/skills/cook into .github/skills/cook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cook", 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 avibebuilder/claude-prime --skill cook -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install avibebuilder/claude-prime cook --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/avibebuilder/claude-prime.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/cook .opencode/skills/cook && 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 "cook" agent skill from https://github.com/avibebuilder/claude-prime/tree/main/.claude/skills/cook into .opencode/skills/cook/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "cook", 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.
cookImplement, build, create, or add any feature, endpoint, page, component, or functionality.
Cook is an agent skill from avibebuilder/claude-prime. Implement, build, create, or add any feature, endpoint, page, component, or functionality. Use this skill whenever the user asks you to write new code or make code changes — whether it's adding an API endpoint, building a UI page, creating an export feature, wiring up a webhook, implementing a search/filter, or any other hands-on coding task. This is the default skill for all 'build this', 'add this', 'create this', 'wire up', 'implement' requests. Covers the full cycle: clarify requirements, plan if needed…
Its SKILL.md is about 970 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 Requirements gathering, REST APIs and Webhooks. The repository describes itself as: You've heard Claude Code can do amazing things. Skills, hooks, agents, memory systems — but who has time to figure all that out? Claude Prime sets it up for you in one command. The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit 80bcfa4. 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.
Cook loads about 970 tokens when it runs. Until then it costs about 168 tokens; SKILL.md has 421 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 avibebuilder/claude-prime at commit 80bcfa4, republished under its MIT licence (© avibebuilder). 421 words, ~970 tokens.
.claude/skills/cook/SKILL.md (or your agent's skills folder).ultrathink.
Cook is an incremental loop: break work into tasks, implement one, verify it works, move to the next. The key discipline is that nothing is "done" until there's evidence it works — but how you verify adapts to the situation.
If the request is clear, start. If it's ambiguous or multi-faceted, ask clarifying questions. If the work is large or multi-path, plan first (/give-plan). Otherwise, just start.
For a small single-concern request, just implement, verify, and continue.
For multi-step work or collaboration, use .claude/scripts/tasks.py to track concrete outcomes. Task files persist in .tasks/, so a fresh context can pick up where the last one left off.
Every task requires three fields: title, desc, expected. Read the authoring rubric before writing tasks — bad tasks are worse than no tasks:
.claude/scripts/tasks.py --help for the short-form rubric and examples.claude/scripts/tasks-authoring.md for the full guide.claude/scripts/tasks.py --task-file <slug> add "<title>" "<desc>" "<expected>"
.claude/scripts/tasks.py --task-file <slug> list
.claude/scripts/tasks.py --task-file <slug> verify <id> "<evidence>"
.claude/scripts/tasks.py --task-file <slug> done <id>Pick the next unblocked task, make the change, then hand off to a tester and (for risky work) a reviewer — isolated teammates that judge the change independently. See .claude/skills/test/teammate.md and .claude/skills/review-code/teammate.md for how to spawn them.
/cook owns implementation. The tester owns verification. Give the tester:
You can still add durable tests, fixtures, or stable selectors when they belong to the product change itself. Do not stuff temporary verification tactics into /cook just to get through one run.
Before invoking verification, confirm the edits actually landed on disk. If the change you expect is missing from the diff, fix that first; a passing check against unchanged code is worthless evidence.
Do not mark a task done on confidence alone. The tester proves the behavior. The reviewer checks that the implementation is correct, scoped, and aligned with the repo. For risky or non-trivial work, spawn a reviewer before marking the task complete.
Update task status as you go so the execution trail stays trustworthy.
After the task list is complete, review the combined diff before declaring success. Cross-task issues often appear only in the final aggregate: mismatched assumptions, naming drift, incomplete ripple updates, or verification that was too narrow. Spawn a reviewer for this final pass.
When done, summarize:
<request>$ARGUMENTS</request>
© avibebuilder, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/cook of avibebuilder/claude-prime.
Open the folder on GitHubat commit 80bcfa4
Cook 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 |
|---|---|---|---|---|---|---|
| Cook this skillavibebuilder/claude-prime | 120 | — | ~970 | Automated safety check: Pass | MIT | |
| API Patternsdilolabs/nosia | 213 | 1 repos | ~2.5k | Automated safety check: Pass | MIT | |
| Loops APIopeninary/openinary | 412 | — | ~1.1k | Automated safety check: Pass | AGPL-3.0 | |
| Verifygregluffy/HomeLabInfo | 102 | — | ~424 | Automated safety check: Pass | GPL-3.0 | |
| Frappe Core APIImpertio-Studio/Frappe_Claude_Skill_Package | 187 | 1 repos | ~3.2k | Automated safety check: Pass | MIT | |
| Lemon Squeezy Integrationpockethost/pockethost | 1.4k | — | ~1.1k | Automated safety check: Pass | MIT |
dilolabs/nosia
Builds REST APIs using respondto blocks with Jbuilder templates following the 37signals same-controllers-different-formats philosophy.
openinary/openinary
A skill your agent uses whenever the user wants to integrate Loops from application code, backend services, webhook handlers, or server-side automation.
gregluffy/HomeLabInfo
Build, run, and drive the HomeLabInfo backend to verify changes at its real surfaces (REST API, UDP DHCP listener, outgoing webhooks).
Impertio-Studio/Frappe_Claude_Skill_Package
A skill your agent uses when building ERPNext/Frappe API integrations (v14/v15/v16) including REST API, RPC API, authentication, webhooks, and rate limiting.
pockethost/pockethost
Full Lemon Squeezy integration — REST API, @lemonsqueezy/lemonsqueezy.js server SDK, Lemon.js checkout overlays, webhooks, customdata, and subscriptions.
qdhenry/Claude-Command-Suite
BigCommerce API expert for building integrations, apps, headless storefronts, and automations.
avibebuilder/claude-prime
Investigate unexpected behavior and mysterious bugs. An agent skill from avibebuilder/claude-prime.
avibebuilder/claude-prime
Builds distinctive, production-grade UIs that avoid generic AI aesthetics.
avibebuilder/claude-prime
Specialized visual and multimedia processing tools. An agent skill from avibebuilder/claude-prime.
avibebuilder/claude-prime
A skill your agent uses when the user wants to work on a Claude Code skill file (SKILL.md): writing one from scratch, testing whether an existing one works well, running evals or benchmarks…
avibebuilder/claude-prime
The single config quality skill. An agent skill from avibebuilder/claude-prime.
avibebuilder/claude-prime
Syncs Claude config between prime repo and target projects. An agent skill from avibebuilder/claude-prime.
Categories
Implement, build, create, or add any feature, endpoint, page, component, or functionality. Cook is an agent skill from avibebuilder/claude-prime. Implement, build, create, or add any feature, endpoint, page, component, or functionality.
Cook fits situations like: the user asks you to write new code; make code changes — whether its adding an API endpoint; building a UI page; creating an export feature.
Run `npx skills add avibebuilder/claude-prime --skill cook -a claude-code`. Or copy the skill folder (.claude/skills/cook in avibebuilder/claude-prime) into .claude/skills/cook in your project. Claude Code loads it when a task matches its description.
Run `npx skills add avibebuilder/claude-prime --skill cook -a codex`. Or copy the skill folder (.claude/skills/cook in avibebuilder/claude-prime) into .agents/skills/cook 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 avibebuilder/claude-prime --skill cook -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/cook, .gemini/skills/cook, .github/skills/cook and .opencode/skills/cook in your project.
SKILL.md names no scripts, command-line tools or credentials: Cook 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.
Cook is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 970 tokens (SKILL.md is roughly 3.9k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Cook: API Patterns (dilolabs/nosia, 213 stars), Loops API (openinary/openinary, 412 stars), Verify (gregluffy/HomeLabInfo, 102 stars) and Frappe Core API (Impertio-Studio/Frappe_Claude_Skill_Package, 187 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
avibebuilder (a GitHub organization) maintains it in avibebuilder/claude-prime, which has 120 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on May 16, 2026.
Source: avibebuilder/claude-prime on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.