Agent skills

APULODI ships official Agent Skills — structured knowledge files that AI coding agents load before writing integrations. Instead of guessing endpoints from training data, an agent that has the skill installed works from verified facts: the real upload flow, the async transform contract, the webhook signature scheme, response envelopes and common mistakes to avoid.

Install

Use the skills CLI:

bash

# Umbrella skill (overview + routing to the sub-skills)
npx skills add hassiekond/apulodi-skills@apulodi

Or install individual sub-skills:

bash

npx skills add hassiekond/apulodi-skills@apulodi-file-uploads
npx skills add hassiekond/apulodi-skills@apulodi-media-transforms
npx skills add hassiekond/apulodi-skills@apulodi-webhooks
npx skills add hassiekond/apulodi-skills@apulodi-management

The skills install into your project's .agents/skills/ directory and are picked up by Claude Code, Cursor, Codex, Cline, Gemini CLI, Antigravity and 20+ other agents.

What's inside

Skill	What it teaches the agent
`apulodi`	What APULODI is, the auth model, base URL, response envelopes, SDK install, routing to sub-skills
`apulodi-file-uploads`	The 3-step direct-to-storage upload flow, multipart uploads for large files, listing and filtering, lifecycle operations (rename, copy, restore, delete), download URLs
`apulodi-media-transforms`	Image, video and audio transformations; the async pending → ready contract; signed variant URLs; transform-at-upload patterns
`apulodi-webhooks`	HMAC signature verification in TypeScript and Python, replay protection, event de-duplication, the full event catalog, drop-in receivers
`apulodi-management`	Organizations, projects, team invitations and roles, API-key administration via the dashboard APIs

Why skills instead of prompting

Every fact in the skills was cross-checked against the platform's implementation — the actual route handlers, validation schemas and SDK sources — so the examples agents produce are correct by construction:

Uploads are the real 3-step flow (initiate → direct PUT → complete), never proxied through your server.
Transforms are treated as asynchronous, so agents wait for ready instead of rendering placeholders.
Webhook receivers verify the raw body with the exact signing scheme the platform uses, including the replay window.
API keys stay server-side, and idempotency keys are used on retries.

The skills live in the public apulodi-skills repository and are MIT-licensed. They are updated alongside the API — reinstall with npx skills update to pick up changes.

Tips

Install the umbrella skill plus the sub-skills you need; the umbrella is small and tells the agent when to consult the others.
Keep skills out of version control if you prefer — the CLI writes them to .agents/skills/, which you can gitignore like other generated assets.
Pair them with this documentation site: the skills contain the operational knowledge, the API reference has the exhaustive details.

← Handling large files