worker-directory-api Package Skill

Package: @epicdm/worker-directory-api Repository: flowstate-platform Path: packages/worker-directory-api Version: 0.0.1

Use this published Dojo skill as the package-level entrypoint. For detailed workflows, use the package-local skills listed below.

Primary Package Workflow

Directory API Worker

Status: Active Purpose: Preserve Directory API route boundaries and schema-backed responses. Scope: packages/worker-directory-api Trigger: Agent/company route, work history, webhook, cron, schema, or app composition changes. Input: Endpoint path, public/auth requirement, Zod schema, DB query, or webhook/cron secret. Output: Correct route behavior and tests.

Workflow

1. Start at src/index.ts to confirm route mounting and public/auth boundaries.
2. Keep agent and company search/detail public unless product requirements explicitly change.
3. Apply requireAuth() only to mutation routes that need identity.
4. Use query helpers from src/db/queries and schemas from src/schemas.
5. For webhook and cron routes, keep their dedicated middleware mounted before handlers.
6. Regenerate OpenAPI when schemas or route definitions change.

Verification

• Run yarn workspace @epicdm/worker-directory-api test.
• Run yarn workspace @epicdm/worker-directory-api typecheck.

Package Skill Inventory

Skill Inventory: @epicdm/worker-directory-api

Package Role

@epicdm/worker-directory-api provides agent/company directory search, profiles, SAGA document export, registration payment flows, work history, webhooks, and cron expiry.

Skills

Composition Notes

• Compose with payment skills when x402 request generation changes.
• Compose with API-core auth patterns for JWT/internal auth.
• Keep public read routes separate from authenticated mutation routes.

Review Gate

Review Gate: @epicdm/worker-directory-api Skills

Result

Pass.

Checks

• Skills are backed by app, route, middleware, lib, schema, and test evidence.
• Public read behavior and auth/ownership ordering are explicit.
• Verification commands are package-local.

Start with this skill to understand the package purpose, then use the package-local focused skills for specific workflows. Keep this Dojo version aligned with packages/worker-directory-api/package.json. Do not treat generated feature lists as lessons; use workflow evidence from CODE-REVIEW.md, SKILL-INVENTORY.md, and REVIEW.md.