Find Key Internal Sources
Use when a seller needs to find the best internal experts, owners, approvers...
Install
npx skills add XiaomiMiMo/MiMo-Code --skill find-key-internal-sources -g -a claude-code -y- Repository
- XiaomiMiMo/MiMo-Code13.7k
- Category
- Business
- Updated
- 3d ago
- License
- MIT
- Context cost
- Mediumabout 2,605 tokens
- Runs scripts
- No, instructions only
What it does
Use when a seller needs to find the best internal experts, owners, approvers, documents, channels, source-of-truth materials, or escalation routes for a customer question, product topic, competitive objection, implementation issue, account task, or other sales-support need. Route questions such as 'who knows about this?', 'what should I read?', 'where is the source of truth?', and 'which internal channel or document should I use?' here.
Find Key Internal Sources
Find the smallest reliable internal route that helps a seller get an answer or unblock work: the right people, maintained docs, public channels, decision forums, and escalation paths. The default output is a quick, evidence-backed routing map plus a draft-ready first ask. This workflow is read-only and never posts, assigns, or updates systems.
Common Skill Instructions
MANDATORY: If not already in context, read and adhere closely to plugins/sales/skills/index/SKILL.md## Cross-Skill Best Practices.
Key Dependency Categories
Use only the categories needed for the selected route; do not fan out across every source by default.
- ~~Knowledge & Files for maintained source-of-truth pages, owner metadata, wikis, field guides, playbooks, FAQs, runbooks, launch docs, and decision records
- ~~Internal Messaging for public channels, channel topics, threads, active contributors, escalation routes, support channels, and decision forums
- ~~CRM for customer or account identity, ownership, opportunity context, and CRM-visible blockers that clarify an account-specific question
Prefer canonical ownership and source-of-truth material over chat mentions. ~~CRM can resolve account truth, but it does not by itself prove who owns the internal answer.
Reference Loading
SKILL.md owns the normal route selection, bounded search, ranking, and output map. Load references only when their extra detail matters:
- Use references/search-patterns.md when query fan-out, compound facets, source-specific search, or stopping rules need more detail.
- Use references/company-context.md only after the generic pass, when user-provided or connector-visible terminology is likely to change the route.
