Agent skill

Apiker

by hodgef in hodgef/apiker

Develop, review, and extend the Apiker library — a framework for building serverless REST APIs on Cloudflare Workers + Durable Objects.

MITAuto-check passedBackend & APIs

Install Apiker

skills CLI
$ npx skills add hodgef/apiker --skill apiker -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install hodgef/apiker apiker --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/hodgef/apiker.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/apiker .claude/skills/apiker && rm -rf skills-src

Use ~/.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/

Facts

Skill name
apiker
GitHub stars
127
Token cost
~1.4k tokens
SKILL.md length
544 words
Files
5 (incl. references)
Skills in repo
11
Repo updated
First seen
Licence
MIT

At a glance

Develop, review, and extend the Apiker library — a framework for building serverless REST APIs on Cloudflare Workers + Durable Objects.

  • Works in 6 steps: Workers runtime only in… → No new dependencies (CONTRIBUTING.md).… → Preserve the public contract. Don't… → …
  • Tasks that involve Serverless
  • SKILL.md covers Mental model (how a request…, Where to make changes, Rules that bite if ignored and Working process, plus 1 more section
  • Calls npm

What it does

Apiker is an agent skill from hodgef/apiker. Develop, review, and extend the Apiker library — a framework for building serverless REST APIs on Cloudflare Workers + Durable Objects. Load when writing or changing code under src/components/, adding routes/handlers/controllers, working with Durable Object state, auth (JWT/bcrypt/GitHub OAuth), middleware, rate limiting, bans, firewall, logging, email, the admin panel, or the CLI scaffolder. Covers architecture, conventions, testing, and TSDoc documentation. Use this for Apiker-specific work; use the generic…

Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 5 other files, including reference files (for example `references/architecture.md`, `references/documentation.md` and `references/patterns.md`).

It sits in Backend & APIs, covering Serverless, Authentication and REST APIs. It works with Cloudflare Workers, Cloudflare Durable Objects, Cloudflare and GitHub. The repository describes itself as: 🔼 Create Serverless APIs with Cloudflare Workers, Durable Objects & Wrangler. The licence is MIT.

When your agent uses it

  • Tasks that involve Serverless
  • Tasks that involve Authentication
  • Tasks that involve REST APIs

Example prompts

  • “/apiker”

Workflow steps

6 steps, taken from the first numbered list in SKILL.md.

  1. Workers runtime only in src/components/** — no Node built-ins (fs, path,
  2. No new dependencies (CONTRIBUTING.md). Reach for Web/Workers APIs or existing deps
  3. Preserve the public contract. Don't rename exports, change res* signatures, or alter
  4. Every new public export needs TSDoc and a components/index.ts re-export path.
  5. Async everywhere for state. Never forget to await a state().get/put/....
  6. Add a test under /tests/ and run npm test before finishing.

What it can do on your machine

Read from SKILL.md and the folder at commit 444ace2. 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:

    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, 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

Apiker loads about 1.4k tokens when it runs, and up to ~6.6k if it reads all its reference files. Until then it costs about 141 tokens; SKILL.md has 544 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~141
When it runs · the whole SKILL.md, loaded when a task matches
~1.4k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~6.6k

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 hodgef/apiker at commit 444ace2, republished under its MIT licence (© hodgef). 544 words, ~1,383 tokens.

Download SKILL.mdSave it as .claude/skills/apiker/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
apiker
description
Develop, review, and extend the Apiker library — a framework for building serverless REST APIs on Cloudflare Workers + Durable Objects. Load when writing or changing code under src/components/**, adding routes/handlers/controllers, working with Durable Object state, auth (JWT/bcrypt/GitHub OAuth), middleware, rate limiting, bans, firewall, logging, email, the admin panel, or the CLI scaffolder. Covers architecture, conventions, testing, and TSDoc documentation. Use this for Apiker-specific work; use the generic Cloudflare skills for platform questions.

Apiker development

Apiker is a library that lets developers build serverless APIs on Cloudflare Workers + Durable Objects with minimal boilerplate. This skill is for working on the library itself (this repo), not on a consumer app.

Read .agents/AGENTS.md first if you haven't — it has the repo map, commands, and hard rules.

Mental model (how a request flows)

mermaid
flowchart LR
  A[Worker fetch] --> B[handleEntryRequest]
  B --> C[parse body + match route via path-to-regexp]
  C --> D[build params: request, body, headers, matches, state]
  D --> E[middleware chain]
  E --> F[firewallMiddleware?]
  F --> G[bansMiddleware]
  G --> H[handler fn]
  H --> I[Response]

Key facts an agent must internalize:

  • Single global instance. apiker is a singleton (src/components/Apiker/Apiker.ts). apiker.init(options) wires routes, exports Durable Object classes, and installs the fetch/scheduled handlers onto the consumer's exports object.
  • Routes map a path-to-regexp pattern → either a handler function (params) => Response or a "ControllerClass.method" string resolved against apiker.controllers.
  • params passed to every handler: { request, body, headers, matches, state } (see RequestParams in src/components/Request/interfaces.ts). matches.params holds route params like :id.
  • Middleware is a simple array run in order by forwardToMiddleware; the first middleware to return a truthy Response wins. Order: firewall (if enabled) → bans → handler.
  • State = Durable Objects. state(objectName?, objectId?, isCloudflareId?) returns { get, put, delete, deleteAll, list }. These proxy over fetch() to the ObjectBase Durable Object, which persists via state.storage. All methods are async.
  • objectStateMapping decides which DO instance an object name resolves to (signedIp, clientId, ip, a route-param name, or a literal). Defaults live in Apiker.init.
  • Responses are always built via the res* helpers (src/components/Response), never raw new Response in handlers (except resRaw for HTML).

For the full breakdown read references/architecture.md.

Where to make changes

I want to…Go to
Add/modify built-in routesthe domain's index.ts (e.g. Auth/Auth.ts getApikerAuthRoutes)
Add a response helper / statussrc/components/Response/Response.ts + constants.ts
Change request parsing/routingsrc/components/Request/Request.ts
Add a middlewarecreate middleware.ts in the domain, push it in Request.ts
Change DO storage behaviorsrc/components/State/State.ts + ObjectBase/ObjectBase.ts
Add init optionsOptions in Apiker/interfaces.ts + handle in Apiker.init
Add a new feature domainnew folder under components/, export from components/index.ts
Change the scaffolderscripts/create.js (Node context, not Workers)
Show full SKILL.md (240 more words)Show less

Rules that bite if ignored

  1. Workers runtime only in src/components/** — no Node built-ins (fs, path, process, Buffer). Node APIs are allowed only in scripts/ and bin/.
  2. No new dependencies (CONTRIBUTING.md). Reach for Web/Workers APIs or existing deps (path-to-regexp, cookie, cfw-bcrypt, cfw-crypto).
  3. Preserve the public contract. Don't rename exports, change res* signatures, or alter the handler params shape without maintainer sign-off. Downstream APIs depend on them.
  4. Every new public export needs TSDoc and a components/index.ts re-export path.
  5. Async everywhere for state. Never forget to await a state().get/put/....
  6. Add a test under <Domain>/tests/ and run npm test before finishing.

Working process

  1. Locate the domain folder; read its index.ts, interfaces.ts, and implementation.
  2. Follow the existing pattern in that folder — Apiker is highly consistent.
  3. Implement the smallest change that satisfies the request.
  4. Document new/changed public APIs with TSDoc (references/documentation.md).
  5. Test: add/adjust a Jest test, then npm test.
  6. Verify types: the build uses TypeScript; keep it type-clean.
  7. Record learnings if you hit a non-obvious gotcha (.agents/skills/apiker-self-improve/SKILL.md).

Reference files

  • references/architecture.md — deep dive: init, routing, middleware, Durable Object state, object-state mapping, scheduled handlers, response pipeline.
  • references/patterns.md — copy-ready recipes: add a route, a controller, a middleware, a response helper, a state-backed feature, a new component domain.
  • references/testing.md — Jest setup, the global exports mock, how to test handlers and state, running/focusing tests.
  • references/documentation.md — doc-comment style for developer IntelliSense (user docs live at hodgef.com/apiker, maintained in PRSS).

© hodgef, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in .agents/skills/apiker of hodgef/apiker.

  • SKILL.md
  • references/architecture.md
  • references/documentation.md
  • references/patterns.md
  • references/testing.md

Open the folder on GitHubat commit 444ace2

Compare with similar skills

Apiker 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.

Apiker compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Apiker this skillhodgef/apiker127—~1.4kAutomated safety check: PassMIT
Cloudflare Worker Devcuriositech/some_claude_skills243—~3.4kAutomated safety check: NotesMIT
Cloudflare WorkersEpicenterHQ/epicenter4.8k—~576Automated safety check: PassCustom licence
Cloudflareericrisco/rsc-harness174—~2.6kAutomated safety check: PassMIT
Durable Objectscloudflare/skills3k2 repos~1.5kAutomated safety check: PassApache-2.0
API Auditbriiirussell/cybersecurity-skills413—~2.8kAutomated safety check: NotesMIT

Similar skills

  • Cloudflare Worker Dev

    curiositech/some_claude_skills

    Cloudflare Workers, KV, Durable Objects, and edge computing development.

    243 GitHub stars~3.4k tokensUpdated 1 mo ago
    Backend & APIsAuto-check: notes
  • Cloudflare Workers

    EpicenterHQ/epicenter

    Cloudflare Workers patterns for Worker runtime APIs, Durable Objects, KV, R2, D1, Queues, WebSockets, streaming responses, bindings, wrangler configuration, and deployment limits.

    4.8k GitHub stars~576 tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Cloudflare

    ericrisco/rsc-harness

    A skill your agent uses when working on Cloudflare's edge platform — wrangler.jsonc bindings, choosing between D1/KV/R2/Durable Objects/Queues, deploying a Worker or SPA via Static Assets, or…

    174 GitHub stars~2.6k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Durable Objects

    cloudflare/skills

    Official

    Build, debug, or review Cloudflare Durable Objects code for persistent state and coordination.

    3k GitHub starsUsed in 2 repos~1.5k tokens
    Backend & APIsAuto-check passed
  • API Audit

    briiirussell/cybersecurity-skills

    Audit REST, GraphQL, and RPC APIs against the OWASP API Security Top 10 (2023).

    413 GitHub stars~2.8k tokensUpdated 4 mo ago
    Backend & APIsAuto-check: notes
  • Domain Web

    fjrevoredo/mini-diarium

    A skill your agent uses when building web services. An agent skill from fjrevoredo/mini-diarium.

    308 GitHub starsUsed in 1 repo~1k tokens
    Backend & APIsAuto-check passed

More from hodgef/apiker

All 11 skills in this repo
  • Cloudflare

    hodgef/apiker

    Comprehensive Cloudflare platform skill covering Workers, Pages, storage (KV, D1, R2), AI (Workers AI, Vectorize, Agents SDK), feature flags (Flagship), networking (Tunnel, Spectrum), security (WAF…

    127 GitHub starsUsed in 7 repos~2.2k tokens
    Auto-check passed
  • Durable Objects

    hodgef/apiker

    Create and review Cloudflare Durable Objects. An agent skill from hodgef/apiker.

    127 GitHub starsUsed in 4 repos~1.5k tokens
    Auto-check passed
  • Send and receive transactional emails with Cloudflare Email Service (Email Sending + Email Routing).

    127 GitHub starsUsed in 2 repos~2k tokens
    Auto-check passed
  • Web Perf

    hodgef/apiker

    Analyzes web performance using Chrome DevTools MCP. An agent skill from hodgef/apiker.

    127 GitHub starsUsed in 5 repos~2k tokens
    Auto-check passed
  • Reviews and authors Cloudflare Workers code against production best practices.

    127 GitHub starsUsed in 6 repos~1.8k tokens
    Auto-check passed
  • Agents SDK

    hodgef/apiker

    Build AI agents on Cloudflare Workers using the Agents SDK. An agent skill from hodgef/apiker.

    127 GitHub starsUsed in 3 repos~3k tokens
    Auto-check passed

Categories

Questions about Apiker

What does Apiker do?

Develop, review, and extend the Apiker library — a framework for building serverless REST APIs on Cloudflare Workers + Durable Objects. Apiker is an agent skill from hodgef/apiker. Develop, review, and extend the Apiker library — a framework for building serverless REST APIs on Cloudflare Workers + Durable Objects.

When should I use Apiker?

Apiker fits situations like: tasks that involve Serverless; tasks that involve Authentication; tasks that involve REST APIs.

How do I install Apiker in Claude Code?

Run `npx skills add hodgef/apiker --skill apiker -a claude-code`. Or copy the skill folder (.agents/skills/apiker in hodgef/apiker) into .claude/skills/apiker in your project. Claude Code loads it when a task matches its description.

How do I install Apiker in Codex?

Run `npx skills add hodgef/apiker --skill apiker -a codex`. Or copy the skill folder (.agents/skills/apiker in hodgef/apiker) into .agents/skills/apiker in your project. Codex loads it when a task matches its description.

Can I use Apiker 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 hodgef/apiker --skill apiker -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/apiker, .gemini/skills/apiker, .github/skills/apiker and .opencode/skills/apiker in your project.

What does Apiker need to run?

Going by SKILL.md and its folder, Apiker needs the command-line tools its instructions call (npm).

Does Apiker access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Apiker 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 Apiker use?

Apiker is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Apiker use?

About 1.4k tokens (SKILL.md is roughly 5.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 5.2k tokens, read only when the agent opens those files.

What are the alternatives to Apiker?

Skills that share tags, products or a category with Apiker: Cloudflare Worker Dev (curiositech/some_claude_skills, 243 stars), Cloudflare Workers (EpicenterHQ/epicenter, 4.8k stars), Cloudflare (ericrisco/rsc-harness, 174 stars) and Durable Objects (cloudflare/skills, 3k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Apiker?

hodgef (a GitHub user) maintains it in hodgef/apiker, which has 127 GitHub stars. The repository holds 11 skills in this directory. The repository was last updated on August 20, 2026.

Source: hodgef/apiker on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.