worker-marketplace-api Package Skill

Package: @epicdm/worker-marketplace-api Repository: flowstate-platform Path: packages/worker-marketplace-api Version: 1.0.0

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

Primary Package Workflow

Marketplace Developer And Cron

Status: Active Purpose: Guide changes to marketplace account lifecycle and scheduled maintenance. Scope: packages/worker-marketplace-api Trigger: Developer enrollment/account/signing-key, webhook, admin, federation, purchase, or cron work. Input: Target route or scheduled job behavior. Output: Route, middleware, query, and scheduled tests that keep marketplace state consistent.

Workflow

1. Start at src/index.ts to locate route mounting, middleware, and scheduled cron expressions.
2. For developer routes, pair src/routes/developer-*.ts with matching schemas and DB query helpers.
3. For protected routes, preserve middleware placement: developer auth in route modules, webhook HMAC under /webhooks/*, cron auth under /cron/*, and admin middleware under /admin.
4. For scheduled work, keep failures isolated. Existing cron code uses ctx.waitUntil and catches federation cache cleanup errors so one job does not block others.
5. Update tests near the changed surface: route tests under test/routes, DB helper tests under test/db, and test/scheduled.test.ts for cron behavior.

Cron Map

Verification

• yarn test test/routes/<route>.test.ts
• yarn test test/db/<helper>.test.ts
• yarn test test/scheduled.test.ts
• yarn typecheck

Composition

• Use flowstate-marketplace-publish-pipeline for archive upload and version publication.

Package Skill Inventory

worker-marketplace-api Skill Inventory

Package: @epicdm/worker-marketplace-api Purpose: Marketplace listings, publishing, developer enrollment, reviews, purchases, VSX compatibility, webhooks, and cron maintenance.

Composition

• Compose with flowstate-payment-x402-provisioning when marketplace purchases depend on payment records or course purchase behavior.
• Compose with flowstate-mcp-tool-registry if marketplace operations are exposed through MCP later.

Exclusions

• Do not create separate skills for every public list route; route shape is straightforward and well covered by tests.
• Do not update .flowstate/dojo in this pass.

Review Gate

worker-marketplace-api Skill Review

Reviewed: 2026-06-30 Result: Pass for local agent use.

Checks

• Skills focus on real operational workflows: publish pipeline and developer/cron lifecycle.
• Source paths include route callers, DB schema, middleware, library helpers, and tests.
• Skills avoid generated feature inventory copying.

Follow-up

• Add a focused skill if future federation logic grows beyond admin/cron maintenance.

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-marketplace-api/package.json. Do not treat generated feature lists as lessons; use workflow evidence from CODE-REVIEW.md, SKILL-INVENTORY.md, and REVIEW.md.