create-tutorial

A workflow for creating runnable Membrane API Gateway tutorials. Membrane is software that sits between clients and APIs to route and manage requests; each tutorial combines a lesson, working configuration, support files, and usually an integration test.

In plain words
What is it for?
Use it to add numbered YAML or Markdown tutorial steps, category startup files, README links, and matching tests for Membrane Gateway examples.
Why use it?
It keeps tutorial instructions, startup files, and tests together, so examples can be run by readers and checked for breakage in continuous integration, automated checks that run when code changes.

Skill for Claude CodeCodex

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

agentmods
npx agentmods add skills/membrane/api-gateway/create-tutorial
Any agent
npx skills add membrane/api-gateway --skill create-tutorial
Clone the repo
git clone --depth 1 https://github.com/membrane/api-gateway

Made for: Claude Code, Codex.

Per session 97 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 2,436 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 1 finding. Scan, not verified.
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5 $0.00097 $0.02436
Opus 5 $0.00048 $0.01218
Sonnet 5 $0.00019 $0.00487
Haiku 4.5 $0.00010 $0.00244

Measured 2d ago against content hash 860c09fc35b4, method: parsed. Prices are Anthropic first-party input rates as of 2026-08-30, from the pricing page.

Security

Grade A, and why

create-tutorial scanned grade A with 1 finding against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 2d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Makes network callslowCapability

Not a fault in itself. Listed so you know the mod talks to something, and to what.

Membrane config (e.g. a curl-only walkthrough against a hosted API). A `.md` step gets no
.claude/skills/create-tutorial/SKILL.md · 215 lines

How it starts

The opening of the file, as written. The whole thing — 215 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Create a Tutorial

In this repo a tutorial is usually a runnable, self-teaching YAML config. The leading comment block of the file is the lesson; the config below it is the working example the reader runs. A complete tutorial therefore has three parts, and they must stay in sync:

  1. The numbered YAML in distribution/tutorials/<category>/ — the lesson plus the config.
  2. Category support filesmembrane.sh, membrane.cmd, a README.md (and run-docker.* where the category offers Docker), so the reader can actually start it.
  3. An integration test under distribution/src/test/java/com/predic8/membrane/tutorials/… so the tutorial can't silently rot. These tests unzip the built distribution and start Membrane against the tutorial's YAML, so a broken example fails CI.

A tutorial step can also be a plain .md file — use this when the step needs no local Membrane config (e.g. a curl-only walkthrough against a hosted API). A .md step gets no integration test; it just lives alongside the numbered YAMLs and is linked from the README.

Work through the steps below in order. The reader of a tutorial follows the file top-to-bottom with no other docs open, so the single most important thing is that the YAML teaches itself.

Step 1 — Choose the category and filename

Categories live under distribution/tutorials/: getting-started, json, xml, advanced, transformation, security, soap, orchestration, misc, ai/.... Pick the one that fits; only create a new category if nothing fits (see "New category" at the end).

Files are numbered NN-Title.yaml (e.g. 10-PathParameters.yaml). The number sets reading order. List the directory and pick the next gap — convention leaves room between numbers (10, 20, 30…) so steps can be inserted later. Match the existing PascalCase-with-hyphens title style.

Step 2 — Write the YAML (the lesson lives here)

Open a sibling file in the same category and mirror its shape. Every tutorial YAML has the same skeleton:

Read the full file on GitHub · 215 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 2d ago First seen · 215 lines · 97 tokens per session scan A 860c09fc35b4

Subscribe to this mod's changes

create-tutorial is a skill published in the GitHub repository membrane/api-gateway (638 stars, last pushed 2d ago), licensed Apache-2.0. It adds 97 tokens to every session and 2,436 once invoked, about $0.0005 per session on Opus 5. A static security scan graded it A with 1 finding (makes network calls). No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Related

Other skills, from other repositories

api-design-patterns

Design robust APIs with RESTful patterns, GraphQL schemas, versioning strategies, and error handling conventions. Supports OpenAPI/Swagger documentation and SDK generation patterns. Triggers on API design, schema definition, endpoint architecture, or developer experience requests.

organvm-iv-taxis/a-i--skills · 54 tokens

api-designer

Designs production-grade APIs — REST, GraphQL, gRPC, and AsyncAPI patterns including pagination, versioning, error handling, rate limiting, and API governance. Use when the user asks to design APIs, create endpoints, build an API layer, write OpenAPI specs, or needs help with REST/GraphQL/gRPC service design.

buiphucminhtam/forgewright · 73 tokens

api-design

Design and implement RESTful APIs with proper routing, validation, error handling, and documentation. Use when building new API endpoints, designing API architecture, or improving existing APIs.

asgarovf/locusai · 37 tokens

api-design-first

Design-first API development skill. Generates OpenAPI 3.1 specifications, enforces REST design best practices, validates endpoints, handles versioning, pagination, error formatting, authentication patterns, rate limiting, and idempotency. Activates when users say "design an API", "create OpenAPI spec", "API endpoint"…

JPeetz/agent-skills · 117 tokens

lap

LAP CLI -- compile, search, and manage API specs for AI agents. Use when working with API specifications (OpenAPI, GraphQL, AsyncAPI, Protobuf, Postman), compiling specs to LAP format, searching the LAP registry, generating skills from API specs, or publishing APIs. Commands: init, compile, search, get, skill…

Lap-Platform/LAP · 89 tokens

lap

LAP CLI -- compile, search, and manage API specs for AI agents. Use when working with API specifications (OpenAPI, GraphQL, AsyncAPI, Protobuf, Postman), compiling specs to LAP format, searching the LAP registry, generating skills from API specs, or publishing APIs. Commands: init, compile, search, get, skill…

Lap-Platform/LAP · 89 tokens