AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Specx Add Delivery Controller

skill-maksimzayats-specx-specx-add-delivery-controller · by maksimzayats

Add delivery controllers for specx services, especially FastAPI HTTP routes. Use when creating top-level `delivery/` request/response schemas, one controller per scoped use-case set, route registration, FastAPI lifecycle managers, HTTP error translation, delivery-only auth/rate-limit/request services, or integration tests that exercise the delivery edge.

No reviews yet
0 installs
15 views
0.0% view→install

Install

$ agentstack add skill-maksimzayats-specx-specx-add-delivery-controller

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-maksimzayats-specx-specx-add-delivery-controller)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
22d ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Specx Add Delivery Controller? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

specx Add Delivery Controller

Use this skill at the framework boundary. Read references/controller.md before adding controller code.

Workflow

  1. Put controllers under delivery/fastapi/controllers/.py.
  2. Put request and response schemas under delivery/fastapi/schemas/.
  3. Use one controller per scoped set of use cases, for example

TasksController for create/get/list task routes.

  1. Put controller-only helpers such as auth dependencies, rate limiters, and

request-context readers under delivery/fastapi/services/.

  1. Make controllers inherit BaseController, schemas inherit

BaseFastAPISchema, delivery helpers inherit BaseDeliveryService, and FastAPI lifespan managers inherit BaseLifecycle[FastAPI].

  1. Add docstrings with scope and a concrete Example: to controllers, schemas,

and delivery services.

  1. Inject use cases or delivery services with Injected[...]. A simple

delivery-owned /healthz response needs no core workflow; inject core/health use cases when readiness checks a required external dependency or probe policy is reused across deliveries.

  1. Map request schema/path data into the use case's same-file Command or

Query input.

  1. Call the use case.
  2. Map the result into a response schema.
  3. Declare the success status explicitly when it is not 200, such as 201

for a resource-creating POST or 204 for a response with no body.

  1. Translate known application exceptions into stable, non-sensitive HTTP

responses. Do not expose raw exception messages.

  1. Register full public business route paths such as /api/v1/users. Do not

split API prefixes across routers and route fragments. Operational probes are the only unversioned exception: /healthz and /readyz.

  1. For FastAPI apps with long-lived resources, inject FastAPILifecycle into

the app factory and pass it to FastAPI(lifespan=...).

  1. Add integration tests at the HTTP boundary, including the declared success

code and each translated application error.

Code Style

Use blank lines as logical separators in all code. Keep related statements together, but separate independent setup, action, assertion, response, branch, and transformation groups so long blocks stay readable.

References

  • references/controller.md - FastAPI controller class pattern, app factory

registration, schemas, and tests.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.