outpost
Sets up and configures Hookdeck Outpost for outbound event delivery to customer endpoints. Use when sending webhooks to customers, building webhook delivery infrastructure, managing tenants and destinations with supported types (webhooks, Hookdeck Event Gateway, AWS SQS/Kinesis/S3, Azure Service Bus, GCP Pub/Sub, RabbitMQ, Kafka), or aligning topics and publishes. EventBridge support is tracked in GitHub issues.
- Installs
- 126
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/hookdeck/agent-skills --skill outpost- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads outpost automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Hookdeck Outpost
Outbound event delivery: publish platform events to tenants’ destinations (webhooks, queues, cloud buses—see supported destinations). Open source on GitHub; managed on Hookdeck Cloud or self-hosted.
Single source of truth: Use Hookdeck Outpost documentation for concepts, API, quickstarts, and UI guidance. This skill links there and adds agent workflow notes under references/.
API base URL and credentials
The managed Outpost API is at https://api.outpost.hookdeck.com/2025-07-01 — not api.hookdeck.com. Authenticate with a Hookdeck project API key that belongs to an Outpost project (Hookdeck Dashboard → your Outpost project → Settings → Secrets), sent as a bearer token. Keep the key server-side.
export OUTPOST_API_BASE_URL="https://api.outpost.hookdeck.com/2025-07-01"
export OUTPOST_API_KEY="..." # key from an Outpost project
# Upsert a tenant: 201 if Outpost created it, 200 if it already existed
curl --request PUT "$OUTPOST_API_BASE_URL/tenants/customer_acme_001" \
--header "Authorization: Bearer $OUTPOST_API_KEY"
Hookdeck has organization API keys and project API keys. For Outpost server work, use a project API key — and the project it belongs to is what matters.
A key for a non-Outpost project authenticates against api.hookdeck.com and works with the Hookdeck CLI, so it looks correct, but returns 404 Not Found on most Outpost routes. Read that 404 as this key is for the wrong project, not "Outpost is not provisioned on this account", and ask the user for a key from an Outpost project. Do not fall back to building the task on api.hookdeck.com — that is the Event Gateway, a different product.
Documentation index for agents
llms.txt: https://hookdeck.com/docs/outpost/llms.txt — plain-text map of doc pages as.mdURLs; fetch once when you need the full tree or many pages.- Concepts: Tenants, destinations, topics, publish
- API reference: REST / OpenAPI; self-hosted spec file:
https://github.com/hookdeck/outpost/blob/main/docs/apis/openapi.yaml - SDKs: Overview — for TypeScript, Python, or Go, follow that language’s quickstart for correct signatures.
- Building your own UI: Guide — screen flow, BFF pattern, implementation checklists.
- Destinations / topics: Destination types · Topics and subscriptions
Quickstarts (smallest path first)
Use the official managed-Outpost walkthroughs before opening full-stack examples in this repo:
| curl (HTTP only) | Hookdeck Outpost curl quickstart |
| TypeScript | TypeScript quickstart |
| Python | Python quickstart |
| Go | Go quickstart |
Compact link list: references/outpost-quickstarts.md.
Test webhook destination URLs (README and docs)
When you need a throwaway HTTPS URL for a webhook destination (quickstarts, curl examples, “verify delivery”):
- Prefer Hookdeck Console — create a Source, copy its URL (e.g.
https://hkdk.events/…), and inspect or replay deliveries in one place. This is the Hookdeck-native default for agents and humans.
Fast path for agents
- Start with references/outpost-scope.md to pick Quick path vs New minimal app vs Existing app.
- If scope is ambiguous, default to the smallest quickstart-shaped artifact.
- Fetch only the language quickstart you need (curl, TypeScript, Python, Go).
- Use references/outpost-verify.md before finishing.
- Open full-stack examples only when the task clearly requires BFF/UI integration patterns.
Scope and verification (agent workflow)
Dashboard-style guidance (no {{PLACEHOLDERS}} — those stay dashboard-only):
- references/outpost-scope.md — three-path ladder, default-to-smallest, language vs architecture, topic reconciliation, SDK vs OpenAPI / BFF pointers with links to Building your own UI anchors.
- references/outpost-verify.md — trimmed “before you stop” checklist.
BFF / wire JSON: Authentication · Wire JSON, SDK responses, and your UI
Supported destination types
Available: Webhooks (HTTP), Hookdeck Event Gateway, AWS SQS, AWS Kinesis, AWS S3, Azure Service Bus, GCP Pub/Sub, RabbitMQ (AMQP), Kafka
Planned: AWS EventBridge
Deployment and API pointers
- Managed: Hookdeck Outpost docs and per-language quickstarts.
- Self-hosted quickstarts: Docker, Kubernetes, Railway, Configuration.
- API reference: Outpost REST / OpenAPI.
- Base URL and auth:
https://api.outpost.hookdeck.com/2025-07-01with a project API key for an Outpost project — see API base URL and credentials.
Full-stack reference examples (advanced)
Use only when the task needs realistic BFF + dashboard patterns—not for “smallest example” (use Quickstarts and llms.txt first).
Integration maps (read before opening trees):
- Next.js: references/nextjs-saas-integration-map.md
- FastAPI: references/fastapi-saas-integration-map.md
Treat examples as references, not copy-paste scaffolds. Prefer the user’s codebase and use maps for Outpost-specific behavior (server-only Outpost project API key, tenant mapping, BFF routes, domain publish).
| Example | Stack | Location |
|---|---|---|
| SaaS (Next.js) | App Router + @hookdeck/outpost-sdk + dashboard UI | examples/nextjs-saas/ — README |
| SaaS (FastAPI + React) | FastAPI BFF (httpx → Outpost) + template UI | examples/fastapi-saas/ — README |
Dependency and version pins live in the example manifests (package.json, pyproject.toml).
How to use the examples: Read the integration maps and README overviews first; open other files only when they match the user’s task.
Tests: npm test in nextjs-saas (Vitest); pytest test_outpost_wire.py in fastapi-saas/backend via ./scripts/test-examples.sh outpost. Next.js example uses npm.
Future skills
Destination-specific skills (outpost-webhooks, outpost-sqs, …) may be added as documentation matures.
Related skills
- hookdeck — skill router for Hookdeck products
- event-gateway — Hookdeck Event Gateway (inbound webhooks)
FAQ
What does the outpost skill do?
Sets up and configures Hookdeck Outpost for outbound event delivery to customer endpoints. Use when sending webhooks to customers, building webhook delivery infrastructure, managing tenants and destinations with supported types (webhooks, Hookdeck Event Gateway, AWS SQS/Kinesis/S3, Azure Service Bus, GCP Pub/Sub, RabbitMQ, Kafka), or aligning topics and publishes. EventBridge support is tracked in GitHub issues.
How do I install outpost?
Run npx skills add https://github.com/hookdeck/agent-skills --skill outpost in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/outpost/ (personal) or .claude/skills/outpost/ (project).
Which AI agents can use outpost?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is outpost safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains outpost?
It is published by hookdeck in hookdeck/agent-skills. It has 126 recorded installs.
More from hookdeck/agent-skills
event-gateway
hookdeck/agent-skills
Comprehensive guide to the Hookdeck Event Gateway for receiving, routing, and delivering webhooks and events. Covers setup, connections, authentication, local development, monitoring, and API automation. Use when receiving webhooks, setting up webhook endpoints, testing webhooks locally, configuring webhook relay or event queue, event routing, webhook retry, webhook monitoring, third-party routing, asynchronous APIs, or local webhook development. For provider webhooks (Stripe, Shopify, Chargebee, GitHub, etc.), use together with the matching skill from hookdeck/webhook-skills; do not only parse JSON — use provider SDK verification and event construction (e.g. Stripe constructEvent).
hookdeck
hookdeck/agent-skills
Open the skill to read its SKILL.md instructions.
Popular devops & cloud skills
microsoft-foundry
microsoft/azure-skills
Build, deploy, evaluate, optimize, fine-tune, and manage Microsoft Foundry agents, models, and resources end to end. USE FOR: foundry, azd ai agent, azd provision/deploy, hosted agent scaffold/develop/run/deploy/troubleshoot, prompt agent create, managed harness agent create, GitHub Copilot harness agent, create agent, update agent, add tool to agent, invoke agent, agent insights, evaluate agent, batch eval, continuous eval, continuous monitoring, agent CI/CD, optimize prompt, improve prompt, optimize agent instructions, Agent Optimizer scaffold, dataset curation from traces, deploy model, model fine-tuning (SFT/DPO/RFT), Foundry project, RBAC, role assignment, permissions, quota, capacity, region, deployment failure, AI Services, create Foundry resource, knowledge index, customize deployment, onboard, availability, training-data, grader, distillation, large file upload. DO NOT USE FOR: Azure Functions, App Service, general Azure deploy (use azure-deploy), general Azure prep (use azure
azure-diagnostics
microsoft/azure-skills
Debug Azure production issues on Azure using AppLens, Azure Monitor, resource health, and safe triage. WHEN: debug production issues, troubleshoot app service, app service high CPU, app service deployment failure, troubleshoot container apps, container app 503 or target port mismatch, troubleshoot functions, function telemetry missing or stopped after a config/connection-string change, troubleshoot AKS, VM RDP, Linux SSH, VM black screen, can't connect to VM, reset VM password, NSG or firewall blocking, kubectl cannot connect, kube-system/CoreDNS failures, pod pending, crashloop, node not ready, upgrade failures, analyze logs, KQL, insights, image pull failures, cold start issues, health probe failures, resource health, root cause of errors, troubleshoot event hubs, troubleshoot service bus, messaging SDK error, AMQP connection failure, message lock lost, lock renewal during long-running processing, service bus dead letter.
azure-prepare
microsoft/azure-skills
Prepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wants to use azd as the deployment tool, or the project already has an azure.yaml file. DO NOT USE FOR: non-azd deployments, Python App Service code-only deploys (use python-appservice-deploy), or cross-cloud migration (use azure-cloud-migrate). WHEN: prepare app for azd, create azure.yaml, set up azd infrastructure, modernize app for Azure with azd, deploy with azd, function app, timer trigger, service bus trigger, event-driven function, managed identity, generate Bicep, generate Terraform, create and deploy to Azure.
azure-ai
microsoft/azure-skills
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text to speech.
azure-deploy
microsoft/azure-skills
Execute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application — use azure-prepare instead. This skill runs azd up, azd deploy, terraform apply, and az deployment commands with built-in error recovery. Requires .azure/deployment-plan.md from azure-prepare and validated status from azure-validate. WHEN: "run azd up", "run azd deploy", "execute deployment", "push to production", "push to cloud", "go live", "ship it", "bicep deploy", "terraform apply", "publish to Azure", "launch on Azure". DO NOT USE WHEN: "create and deploy", "build and deploy", "create a new app", "set up infrastructure", "create and deploy to Azure using Terraform" — use azure-prepare for these.
azure-validate
microsoft/azure-skills
Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity permissions, and prerequisites before deploying. WHEN: validate my app, check deployment readiness, run preflight checks, verify configuration, check if ready to deploy, validate azure.yaml, validate Bicep, test before deploying, troubleshoot deployment errors, validate Azure Functions, validate function app, validate serverless deployment, verify RBAC roles, check role assignments, review managed identity permissions, what-if analysis, validate Container Apps deployment.