plan-export

33

blockscout

Export a detailed phased implementation plan for a GitHub issue to a file, reading all applicable rules from .cursor/rules before planning

gh-issue-bug

33

blockscout

Generate a structured bug report for GitHub issues based on conversation context about bugs, errors, or broken functionality

test-guided-tool-run

33

blockscout

Use when user asks to "run tool as function", "test directly", or "call standalone" (outside MCP server). Essential for correct mock Context setup (MagicMock + AsyncMock). Finds integration tests with real test data.

gh-issue-improvement

33

blockscout

Generate a structured improvement/enhancement proposal for GitHub issues based on conversation context

read-temp-file

33

blockscout

Reads the content of a file located in the temporary directory (temp/) which is otherwise ignored by git.

describe-changes

33

blockscout

Describe very high level changes required to implement discussed functionality (functionality, test, docs)

consult-spec

33

blockscout

TRIGGER CONDITIONS - invoke this skill when ANY of these apply: User-triggered (explicit request): - User mentions "specification", "SPEC", "SPEC.md", "spec requirements" - User asks to "verify with spec", "confirm with specification", "check requirements" - User requests "authoritative requirements" or "source of truth" Agent self-triggered (during reasoning): - Before implementing any feature or making code changes - When verifying technical requirements or constraints - When making architectural or design decisions - When you need unbiased guidance not influenced by current implementation - When encountering conflicting information and need ground truth PURPOSE: Consults SPEC.md through an isolated subagent that ONLY reads the specification, never implementation code. This ensures guidance is based on authoritative requirements, not potentially incorrect existing code.