Skill Claude CodeCodex
Declare new API resource(s) in an existing API service. Use whenever the app needs to call an endpoint that has no service:name resource yet.
Front-end application for Blockscout chain explorer
Skill Claude CodeCodex
Declare new API resource(s) in an existing API service. Use whenever the app needs to call an endpoint that has no service:name resource yet.
Skill Claude CodeCodex
Step-by-step checklist for adding a new NEXTPUBLIC environment variable. Use when introducing any new runtime env var.
Skill Claude CodeCodex
Scaffold a new page (index / detail / general) and optionally wire it to API data. Use when adding any new route to the app, or when wiring API data into an already-scaffolded page (one with TODO (api-data): markers).
Skill Claude CodeCodex
Ensure GitHub CLI (gh) is installed and authenticated before running gh commands; guide the user to configure it if not.
Skill Claude CodeCodex
Create a GitHub issue from the available context. Use when the user asks to file an issue from a source they name (Slack thread, notes, document) or from this conversation.
Skill Claude CodeCodex
Create or finalize a pull request — three modes: placeholder draft PR at spec time, finalize a draft into ready-for-review, or a regular PR right away for work done outside the task workflow.
Skill Claude Code
Create a GitHub deployment for the current branch using the deploy-review workflow.
Skill Claude CodeCodex
Checklist for deprecating a NEXTPUBLIC environment variable — immediate removal, or a grace period before a later removal. Use when removing, renaming, or replacing a runtime env var.
Skill Claude Code
Land a finished product task — prune the working files (keep spec.md), then finalize the draft PR into ready-for-review.
Skill Claude Code
Grill a product task (GitHub issue) into implementable work.
Skill Claude CodeCodex
Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.
Skill Claude Code
Execute one ticket of a product-task spec.
Skill Claude Code
Prepare the next release of the application (tag, docs, release notes), then publish the pre-release and request a staging roll-up.
Skill Claude CodeCodex
Publish a beta version of a @blockscout/-types npm package and pin it here. Use when a needed response type isn't in any published package version yet.
Skill Claude CodeCodex
Resolve the real request URL of an API resource on a live Blockscout instance (service:name + instance → full URL). Use whenever a request must be made to, or a sample response fetched from, a deployed instance's API.
Skill Claude Code
Turn a Slack request into the exact env vars to set on a live instance, and hand them to DevOps.
Skill Claude Code
Close out review findings on a PR — adjudicate each one, fix what deserves fixing, then reply and resolve the threads.
Skill Claude Code
Review a change on three axes — spec compliance, repo standards, correctness — each in a fresh subagent context, then post the findings as inline PR comments (or report them in chat when there is no PR).
Skill Claude CodeCodex
Download Slack attachments by file ID, or upload local files into a Slack thread. Use when a Slack message lists Files: whose contents matter, or when posting a file to Slack; the MCP connector reports metadata only. Guides Keychain token setup if missing.
Skill Claude CodeCodex
Watch Slack threads (DMs and channels) for new replies over a Socket Mode WebSocket, printing one line per genuinely-new reply. Use to be notified inside a live local Claude Code or Cursor session (not a cloud agent).
Skill Claude Code
Turn the current conversation into a product-task spec and publish it as a draft PR: no interview, just synthesis of what you've already discussed.
Skill Claude Code
Break a product-task spec into a set of tracer-bullet tickets, each declaring its blocking edges.
Skill Claude CodeCodex
Add a new term, update an existing definition, or remove an outdated entry in .agents/GLOSSARY.md. Use whenever the user wants to write something into the project glossary, or asks "should this be in the glossary?". Enforces the file's principle — disambiguation and etymology only, no paths/env vars/UI-location…
At most 3 mods per repository are shown here, and a mod shipped inside a plugin is left to that plugin's page — the rest are on their repository pages: