with one click
website
website contains 11 collected skills from AI-Shipping-Labs, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Foundational entrypoint for the AI Shipping Labs PRODUCTION HTTP API. Use to learn how to authenticate, where the token/config lives, how to discover the full endpoint surface via the OpenAPI spec, the safe-write protocol, and the cross-cutting surfaces — integration settings / env config, content sync, and background-task observability. For user/CRM endpoints use `ai-shipping-labs-users`; for events and workshops use `ai-shipping-labs-events`.
Run the full development loop - pick issues, implement, QA, PM review, commit, push, repeat. Works for both new features (open issues) and Playwright test implementation (needs-testing issues).
Update a member's own AI Shipping Labs sprint plan through the member Plans API. Use when a member wants to list plans, fetch one plan, download Markdown, sync a Markdown plan back to the platform, toggle progress, or edit weeks, checkpoints, deliverables, next steps, resources, and week notes through /member-api/v1 using a member-owned API key.
Use when asked to update AI Shipping Labs sprint plans from Zoom, Slack, onboarding, questionnaire, or meeting notes; add or import missing sprint plans; clean plan task formatting; or fetch/check people registered for a production event.
Use when asked to create or update an AI Shipping Labs sprint plan from a member's submitted onboarding answers, CRM/user context, or member profile; includes fetching production onboarding data, drafting a markdown plan, importing it through the production plans API, and attaching internal context to the member profile/CRM.
Create and manage AI Shipping Labs events and workshops in production. Use when asked to "create an event", "schedule a workshop", "set up an event series", "add a Zoom event", "make a recurring event", "publish a workshop", cancel/reschedule an occurrence, or bulk-create Zoom meetings for a series. Events are created via the production API; workshops are git content synced from the workshops-content repo.
Use when asked to look up a user, inspect a user's tier/subscription/bounce state, add or remove a CRM note or tag, merge duplicate accounts, add an email alias, mark a user bounced, import/export contacts, or record people in the AI Shipping Labs CRM. The user + CRM read/write surface of the production API.
Use when asked to read AI Shipping Labs Slack — get a Slack user's email, resolve a Slack handle/display name/real name to an email, look up a Slack user by ID, read a Slack thread or channel, or answer "who posted in
Use when asked to take people from a Slack thread/channel (e.g. "who's going to X", "who signed up for the course/event") and record them in the AI Shipping Labs CRM — resolve Slack users to emails, confirm platform users, add member notes + tags, and optionally hand off to plan generation. Triggered by screenshots of Slack threads or requests like "add these people to the CRM".
Use when an AI Shipping Labs sprint member is missing a production sprint plan, or when a local markdown plan from telegram-writing-assistant or zoom-calls must be imported into the production plans API.
Upload a screenshot file and get back a shareable CloudFront URL