Update to Sales

{
  "name": "find-key-internal-sources",
  "description": "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.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 238
    },
    {
      "relative_path": "references/company-context.md",
      "size_in_bytes": 1143
    },
    {
      "relative_path": "references/search-patterns.md",
      "size_in_bytes": 5261
    }
  ],
  "skill_md_contents": "---\nname: find-key-internal-sources\ndescription: \"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.\"\n---\n\n# Find Key Internal Sources\n\nFind 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.\n\n## Common Skill Instructions\n\nMANDATORY: If they are not already in context, read and follow [the shared Sales skill instructions](../../shared_skill_instructions.md).\n\n## Key Dependency Categories\n\nUse only the categories needed for the selected route; do not fan out across every source by default.\n\n- ~~Knowledge & Files for maintained source-of-truth pages, owner metadata, wikis, field guides, playbooks, FAQs, runbooks, launch docs, and decision records\n- ~~Internal Messaging for public channels, channel topics, threads, active contributors, escalation routes, support channels, and decision forums\n- ~~CRM for customer or account identity, ownership, opportunity context, and CRM-visible blockers that clarify an account-specific question\n\nPrefer 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.\n\n## Reference Loading\n\n`SKILL.md` owns the normal route selection, bounded search, ranking, and output map. Load references only when their extra detail matters:\n\n- Use [references/search-patterns.md](references/search-patterns.md) when query fan-out, compound facets, source-specific search, or stopping rules need more detail.\n- Use [references/company-context.md](references/company-context.md) only after the generic pass, when user-provided or connector-visible terminology is likely to change the route.\n\n## Terms\n\n- **Source-of-truth page:** the maintained doc, wiki, tracker, or page that should be treated as the most authoritative answer source.\n- **DRI:** directly responsible individual, the person accountable for a topic, decision, or follow-through.\n- **SME:** subject matter expert, someone with practical depth on the topic even if they are not the accountable owner.\n- **Decision forum:** the recurring meeting, channel, doc, or group where tradeoffs and approvals are handled.\n\n## Workflow Guidance\n\n### 1. Resolve the topic and route\n\n- Require a concrete topic_or_task: customer question, product topic, objection, implementation issue, account blocker, initiative, or source-of-truth gap.\n- Infer it from the active thread or provided Sales output when clear. If still ambiguous, make a bounded candidate pass of at most three source reads, then ask one friendly question with up to three concrete candidates.\n- Treat ambiguous company-like names as possible account anchors. Use a bounded ~~CRM lookup when available before relying on internal docs or messages for account-specific routing.\n- Default to quick. Use deep only when requested or when a high-stakes question clearly needs broader corroboration.\n\nChoose the smallest answer route that satisfies the request:\n\n- owner_route — who owns, approves, knows, or should be contacted\n- doc_route — what to read, which page is maintained, or what wording is approved\n- channel_route — where to ask, discuss, escalate, or get support\n- full_map — experts, docs, and channels together when the request actually needs all three\n\n### 2. Search canonical sources first\n\n- For owner_route, start with maintained ownership, directory, routing, or source-of-truth pages; use messages to confirm current practice or fill gaps.\n- For doc_route, discover maintained docs through metadata only and preserve user-supplied result limits, document-type, title, and privacy filters on every query, including retries. Before reading content, require a topic-matched maintained authoritative source; reject generated follow-up packages, pre-reads, meeting summaries, one-off deliverables, and review or evaluation artifacts. If no trustworthy source remains, report the evidence gap instead of opening a generated document.\n- For channel_route, start with public channel names, topics, purposes, and documented escalation routes; inspect recent public threads only when they change confidence.\n- Use ~~CRM first for account identity and deal context when the route is customer-specific, then use ~~Knowledge & Files or ~~Internal Messaging for internal ownership.\n- In quick, make one canonical source attempt, one narrow fallback when the first pass is empty, thin, or misleading, and at most one fetch or thread read per top candidate.\n- Broaden only when the first pass is weak, the topic spans distinct surfaces, or the user asked for deep. Stop when a supported route is good enough, results stabilize, or additional searching produces low-confidence duplicates.\n\n### 3. Build useful search facets\n\n- Start with exact topic terms, then add aliases, abbreviations, legacy/current names, product/team names, and task-shape terms such as owner, approval, policy, runbook, playbook, FAQ, support, or escalation.\n- For a compound question, keep separate tracks for the product/account surface and the control/process surface. Do not let a strong policy hit replace product routing, or a launch page replace approval ownership.\n- Use [references/search-patterns.md](references/search-patterns.md) when query fan-out, source-specific search, or stopping rules need more detail.\n- Use company-specific terminology only when it comes from the user or connector-visible source truth. Do not invent internal names, channel patterns, URLs, or ownership conventions.\n- Apply organization-specific expansions only after generic candidate retrieval, keep base scoring primary, and cap the total context-based boost per candidate at `+0.25`.\n\n### 4. Pull, score, and rank candidates\n\nNormalize candidates by type, title or name, URL, source, evidence, ownership signal, and freshness. Deduplicate near-identical entries.\n\nRank by:\n\n1. direct relevance to the requested answer route\n2. authority and maintenance signal\n3. freshness\n4. cross-source confirmation\n5. practical usefulness for the seller's next action\n\n- Prefer direct evidence links over profile-only or mention-only matches.\n- Prefer maintained source-of-truth pages, field guides, FAQs, and playbooks over one-off notes.\n- Prefer channels whose topic, purpose, linked guide, or recent threads show an ownership path over channels that merely mention the topic.\n- For people inferred mainly from ~~Internal Messaging, require a recent ownership or expertise signal, defaulting to the last 90 days; omit or down-rank stale candidates.\n- Exclude deactivated or inactive users. Default to public channels only; include private channels, group DMs, direct messages, or externally shared channels only when the user explicitly asks and access is appropriate.\n- Keep distinct routes when a topic spans product/GTM guidance and policy, security, implementation, pricing, or approval ownership.\n\n### 5. Render the routing map\n\n- Return only the depth the request needs. For a single route, keep the other required sections compact with Not searched in quick pass or No high-confidence candidate found.\n- Explain each candidate's answer-path type: DRI, approver, SME, maintainer, accountable team, decision forum, launch owner, escalation channel, support channel, or feedback channel.\n- Include a one-line rationale, direct link when available, evidence signal, and freshness or confidence when it affects trust.\n- If the user's wording conflates two surfaces, add a short framing note explaining the split and continue with both routes unless the distinction changes which sources are safe to use.\n- Recommended First Ask must be a concrete draft the seller can send to the best owner or public channel. Draft it in chat; do not post it.\n- Coverage Gaps must name unavailable or weak categories, the effect on confidence, and the smallest useful next step.\n\n### Next Step Options\n\nAfter the first output, offer the most relevant follow-up from the options below. Offer one clear transition, not a menu. Suggest ONLY these unless you are very confident another option is more useful:\n- Draft the first ask to the recommended owner, expert, or public channel.\n- Open and synthesize the strongest source-of-truth document for the seller's question.\n- Prepare a concise escalation note when the supported route requires escalation.\n- Create a reusable routing note with the verified people, docs, channels, and caveats.\n- Find the smallest missing source that would resolve an ownership or approval gap.\n\nNext steps to avoid:\n- Posting, assigning, escalating, or updating ownership automatically.\n\n## Modes\n\n- quick — default; up to three candidates each for experts, docs, and channels, with bounded retrieval\n- deep — five to eight candidates each when evidence quality supports them\n- owner_route, doc_route, channel_route, full_map — answer-shape routes; combine with quick or deep\n\n## Output Format\n\n```md\n# Internal Routing Map: [Topic]\n\n[Optional framing note when the topic spans distinct ownership surfaces.]\n\n## Experts\n- **[Name / team]** — [DRI / approver / SME / other type]; [why this route]. [Evidence link] · [confidence/freshness]\n\n## Docs\n- **[Doc]** — [source-of-truth / field guide / FAQ / other type]; [why it matters]. [Link] · [confidence/freshness]\n\n## Channels\n- **[#channel]** — [support / escalation / decision forum / other type]; [why ask here]. [Link] · [confidence/freshness]\n\n## Recommended First Ask\n> [Draft-ready question or handoff, addressed to the best owner or public channel.]\n\n## Coverage Gaps\n- [Missing or weak source, confidence impact, and smallest useful next step]\n\n---\n\n{Follow the instructions and output format/conditions in [Limitations and Improvements](../../shared_skill_instructions.md#limitations-and-improvements)}\n\n{Follow the instructions and output format/conditions in [Next Steps](../../shared_skill_instructions.md#4-offer-one-next-step)}\n```\n\n## Example Prompts\n\n- `Find the key internal sources for a customer question.`\n- `Find who owns the Enterprise SSO rollout path for ExampleCorp.`\n- `Find the docs and channels for answering a customer's security review question.`\n- `Route this implementation blocker to the right internal people and source of truth.`\n\n## Rules\n\n- Do not fabricate owners, experts, channels, documents, source-of-truth paths, links, or ownership certainty.\n- Keep facts and inference separate; label uncertain ownership Likely or Possible.\n- Keep the routing-map phase read-only. Do not post, send, assign, or update anything.\n- Prefer fewer high-confidence routes over long noisy lists.\n- Always cite sources with hyperlinks when useful links are available; say (no useful link available) when the absence matters.\n"
}