auth quickstart

DevOps Community

Skill notes

When to Use This vs authfastapiskill

Situation · Use No code exists yet · This skill Existing service needs auth added · auth_fastapi_skill Need to understand permission design in depth · auth_fastapi_skill Need scenario walkthroughs by industry · auth_service_ab0t

Step 1: Gather Requirements

Ask the user for: Service name — human-readable (e.g., "Invoice Service") Service slug — lowercase identifier (e.g., invoices). Used in permissions, audience, file names. Domain resources — the nouns (e.g., invoices, payments, customers) Actions per resource — the verbs (e.g., read, write, create, delete, send, approve)

Step 2: Copy and Customize Template

The template lives in assets/template/. Copy the entire directory to the user's target path, then replace all placeholders: Placeholder · Replace with __SERVICE_NAME__ · Human-readable name __SERVICE_SLUG__ · Lowercase slug __SERVICE_DESCRIPTION__ · One-line description

Step 3: Verify Structure

After customization, the project should have:

Step 4: Run Locally

Verify: GET /health returns {"status": "ok"} (no auth) GET /items/ returns data with bypass user (auth bypassed) Routes return proper 401/403 JSON when bypass is off and no token is provided

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
DevOps
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@tomevault-io · no license declared
Token usage
Lean
Setup complexity
Manual integration
External API key
Not required
Operating systems
Docker
Runtime requirements
Python · Docker
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
  • Env read
Network behavior
External requests
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
Step 1: Gather Requirements

Ask the user for: Service name — human-readable (e.g., "Invoice Service") Service slug — lowercase identifier (e.g., `invoices`). Used in permissions, audience, file names. Domain resources — the nouns (e.g., invoices, payments, customers) Actions per resource — the verbs (e.g., read, write, create, delete, send, approve)

02
Step 2: Copy and Customize Template

The template lives in `assets/template/`. Copy the entire directory to the user's target path, then replace all placeholders: Placeholder · Replace with `__SERVICE_NAME__` · Human-readable name `__SERVICE_SLUG__` · Lowercase slug `__SERVICE_DESCRIPTION__` · One-line description

03
Step 3: Verify Structure

After customization, the project should have:

04
Step 4: Run Locally

Verify: `GET /health` returns `{"status": "ok"}` (no auth) `GET /items/` returns data with bypass user (auth bypassed) Routes return proper 401/403 JSON when bypass is off and no token is provided

05
Step 5: Guide Next Steps

After the scaffold is running, point the user to references/next-steps.md for: Adding more permissions and type aliases Adding check callbacks (suspension, quota) Wiring up Phase 2 ownership verification with a real database Registering with the auth service

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.