context7-local-rules

To minimize external API lookups in an MCP workflow, default to local Markdown rules for knowledge retrieval and gate external Context7 calls with a one-time confirmation prompt. This local-first approach reduces unnecessary context switching by relying on your internal knowledge base unless explicitly required.

A local-first fallback mechanism for MCP rules prioritizes your local Markdown knowledge base during workflows and implements a 3-layer decision logic. It safely falls back to local data when Context7 is unavailable, issuing a concise risk note if you choose to skip the external lookup.

Configure Context7 gating by activating the skill to reference local docs/rules.md for decision logic. The system prompts you for a one-time confirmation before executing any Context7 calls, ensuring external lookups are intentional rather than automatic.

Your MCP workflow triggers unnecessary context switching because it defaults to external lookups instead of local data. Applying a hybrid MCP-first approach with local Markdown rules and a 3-layer operation logic prevents this by keeping context local until an explicit override is confirmed.

Yes, you need a SKILL.md file to satisfy repository scoping requirements for MCP workflows. This file must include the skill name and description, and you can optionally include directories for scripts, references, and assets to support the local-first rules.