dig
Explore, analyze, plan, or spec features for the Apify MCP server. Adapts to what the user asks — from quick code exploration to full GitHub issue specs. Use when the user asks to explore code, understand behavior, plan a change, design a feature, or create an issue spec.
Install
git clone https://github.com/apify/apify-mcp-server /tmp/apify-mcp-server && ln -s /tmp/apify-mcp-server/.claude/skills/dig ~/.claude/skills/digFrom README
Dig Flexible skill for exploring, planning, and speccing work on the Apify MCP server. Do NOT edit source files — this skill is for understanding and planning only. Step 0: Parse arguments and determine intent $ARGUMENTS contains the user's request and optional repo path overrides. Flags (optional): | Flag | Default | Purpose | |----------------|----------------------------------|--------------------------------| | --sdk | ../typescript-sdk | MCP SDK source repo path | | --ext-apps | ../ext-apps | MCP Apps SDK source repo path | | --internal | ../apify-mcp-server-internal | Internal server repo path | Everything not matching a flag is the user's request. Resolution order for source repos: flag path → default sibling path → nodemodules/ (compiled types only) → GitHub URL (last resort). Always verify the path exists before using it. Determine the intent Infer the intent from the user's natural language.