Loading...
Loading...
Found 10,137 Skills
Generate exactly one high-quality Conventional Commit message from the current Git diff. Use when Codex needs to inspect staged changes, summarize the dominant intent, and return only the final commit message with no analysis or extra text.
Submit a kid-facing English content PR to the football-english repo (zxkane/football-english). Use this whenever the user asks to "submit this week's quiz", "publish a weekly quiz", "submit a daily reading", "add today's reading", "publish a daily article", "open a daily PR", "open a quiz PR", or hands over essay paragraphs (with optional KET/PET points, vocabulary, audio, image, questions) and expects them to land in the kid-facing site. The repo publishes two kinds of content — weekly quizzes (essay + 3-20 graded questions, one per ISO week) and daily readings (essay + TTS audio + image + structured KET/PET points + optional 0-3 small questions, irregular cadence). This skill picks the right shape, writes the JSON, validates it, and opens the PR end-to-end. Trigger this skill even if the user doesn't use the words "quiz", "daily", or "PR" — any handover of essay paragraphs intended for this repo qualifies.
Use this skill when the task is specifically about operating Resend from an AI agent, terminal session, or CI job via the official resend CLI: installing/authenticating the CLI, sending/listing/updating/cancelling emails, batch sends, domains and DNS, webhooks and local listeners, inbound receiving, contacts, topics, segments, broadcasts, templates, API keys, profiles, or debugging Resend CLI/API failures. Trigger on mentions of Resend CLI, `resend`, `resend doctor`, `resend emails send`, `resend domains`, `resend webhooks listen`, `resend emails receiving`, or agent-friendly terminal automation.
Query APIs, files, and live sources using Coral SQL. Use when the user asks about data from GitHub, Slack, Linear, Datadog, Sentry, or other connected sources.
Buy and return items on Amazon using browser automation. Use for purchasing, reordering, checking order history, and processing returns.
Create or include a Liquid template in a ***plain spec file using {% include %} syntax. Use when the same spec content needs to be reused across multiple .plain files with different parameters.
This skill should be used when the user asks for efficient communication, task reports, file-operation summaries, research discussion, study-note synthesis, planning, writing feedback, or responses that need conclusion-first structure, concrete evidence, risk disclosure, and useful next steps.
Produces a compact briefing document for an AFK agent taking on a specific slice. Use after create-prd or create-issues, immediately before handing work to a coding agent. Do NOT interview the user — synthesise from the current context.
Use when the user asks to create, generate, or scaffold a SeeFlow flow from a natural-language prompt — "create a flow", "show how X works", "diagram our checkout system", "add a flow to this repo". Orchestrates four sub-agents and bun scripts to write a registered, validated flow under <project>/.seeflow/<slug>/.
Use when thinking through ideas, investigating problems, or clarifying requirements — before or during a Beat change
Use when an agent is asked to perform GitHub work in a repository that should follow using-github conventions
Generate FEATURES.md at the repo root by reading CONTEXT.md and docs/adr/, then enumerating the user-facing features the domain implies. Use after /grill-with-docs has settled the domain language and before /to-prd writes per-feature specs. Bridges the product→engineering gap between domain understanding and feature specification — the missing step that mattpocock's chain doesn't cover natively.