find-key-internal-sources

What problem does it solve?

This skill helps locate the people, docs, channels, source-of-truth pages, decision forums, and escalation paths that can answer a customer question or unblock a sales task.

This skill produces a practical routing map from grounded internal evidence. It is useful for customer questions, product topics, objections, implementation issues, account tasks, launch/rollout questions, and source-of-truth gaps. The initial routing map is read-only: it may draft a question or handoff, but it does not post, message, assign, or update systems. After a reviewed ask or handoff exists, it may offer supported posting or sharing only after explicit user approval of that reviewed action.

Skill Configuration

User Context

Mandatory pre-answer gate:

• Invoke sales:user-context in preflight mode by loading [$sales:user-context](../user-context/SKILL.md) and running its preflight script before searching connectors, retrieving evidence, or drafting output. Do not look for a callable MCP tool named sales:user-context.
• Use the returned sales_preflight envelope as authoritative for saved context, source-category mapping, final obligations, and conditional guidance.
• Apply hard final_obligations unless the response is clarification-only. If an obligation is an onboarding reminder and the routing map also needs a skill-owned final continuation, satisfy both in one final natural continuation instead of rendering a standalone onboarding reminder plus a second CTA.
• Apply context_gap_note only when missing setup or inaccessible sources materially limits the routing map.

Audience And Language

Write for Sales users, not plugin maintainers. This applies to final answers, setup/status readbacks, failure explanations, tool preambles, and mid-turn progress narration.

Translate implementation work into practical Sales impact: what Sales is checking, setting up, saving, or preparing, and why it matters. Avoid implementation terms such as preflight, state file, cache, raw connector id, heartbeat, targetThreadId, schema, API, runtime, metadata, and provider taxonomy unless the user asks for debugging details.

Source Resolution

Use context.sources from the sales_preflight envelope to resolve each attempted semantic source category to available apps, connectors, and helper skills. Defer connector fallback, source preferences, durable source rules, and helper-skill loading mechanics to sales:user-context. Do not prompt about categories this skill does not attempt.

For ownership or source-of-truth routing requests, prefer the source that most directly owns the requested fact before broad search. A company knowledge base, people directory, team directory, wiki owner field, go-link index, verified routing page, or maintained source-of-truth hub should be treated as the first-pass source when available, even if it resolves through the same document_store category as ordinary docs. Use internal_messaging as supporting evidence for recent practice, escalation texture, or active contributors; do not make message search the default authority for stable ownership when a canonical routing source can answer the question.

Required Inputs

Require:

• [required] topic_or_task: the core customer question, product topic, account blocker, initiative, implementation issue, or internal source-of-truth gap

Optional:

• output_depth: quick for top 3 each, or deep for top 5 to 8 each. Default to quick.
• account, customer, team, product, source, or urgency context when provided

Context Gathering Principles

Optimize for marginal value, not exhaustive coverage.

• Classify the requested answer shape before searching: owner route for experts/POCs/approvers, doc route for source-of-truth or approved wording, channel route for where to ask, and full map only when the user asks for people, docs, and channels together.
• Start with the source category that owns that answer shape and the narrowest query that could answer it. For owner routes, start with canonical ownership, directory, or routing sources when available; for doc routes, start with source-of-truth docs; for channel routes, start with channel/topic/search.
• In default quick mode, spend a small bounded first pass before answering: one canonical source attempt, one narrow fallback attempt when the first pass is empty/thin/misleading, and at most one fetch or thread read per top candidate unless the user asked for deep.
• Treat roughly three to five minutes of active retrieval, two slow connector calls, or one timeout/rate-limit on a non-required enrichment source as the practical quick-mode budget. When that budget is reached, yield back to the user instead of continuing silent retrieval: return the best supported routing map or checkpoint, name limitations in Coverage Gaps, and make the final natural continuation one concrete choice to clarify or give a steer, continue deeper, or act on the current best route.
• Broaden only when the first pass is empty, thin, or the user's requested output explicitly needs multiple source types. Do not fan out across docs and messages merely because both are available.
• Answer once the core artifact is supported by a direct source. Use optional sources to improve confidence only when they materially change who to ask, what to read, where to ask, or what wording is safe to reuse.

First-Run Banner

If Sales preflight says the find-key-internal-sources experience has not been introduced and this skill is the primary user-facing skill, render a compact first-run intro before the normal output:

<snip long content> ???

Next Step Guidance

This section is the single owner for Find Key Internal Sources next-step behavior and action text. Onboarding, draft creation, posting or sharing, source-list creation, and follow-up turns may route into this journey or wrap its selected action in their own presentation frame, but they must not redefine the internal-routing continuation states elsewhere.

Final Continuation Invariant

Every final assistant response while find-key-internal-sources is the active workflow must end with exactly one user-visible next action, phrased as a natural sentence or question in the ordinary prose of the response. This is a final-response gate, not a journey preference. It applies even when the response is only a short answer, local rewrite, one-paragraph summary, confirmation, readback, source-gap note, partial result, status after creating/posting/saving/linking an artifact, or explanation of what changed. Before sending, inspect the final visible assistant-written content: if it does not end with a concrete next action, add the earliest valid continuation below or explicitly choose one of the allowed omission reasons.

Omit the continuation only when the user explicitly asks for no follow-up, the workflow is explicitly closed by the user, a scheduled automation correctly returns DONT_NOTIFY, or another active parent flow owns the final CTA. Required-input and clarification responses are not omission cases; make the unresolved question the final natural continuation.

Journey States

Use the earliest state whose condition matches the current artifact. Do not end with only a bare confirmation, source link, or "done" message while a valid next step remains.

| State | Use when | Final continuation | | --- | --- | --- | | 1. Review the routing map | The first substantive routing map has just been produced. If quick-mode retrieval stopped at the retrieval budget, make the next action the most practical recovery path: ask for a narrow steer, offer a deeper search, or suggest using the current best route when it is good enough. | Does this routing map look good enough to use, or should I dig one level deeper? | | 2. Review the revised routing map | The user asked for any change to owners, docs, channels, confidence, scope, wording, or search depth. Make the change in chat first. | Anything else you'd change? If that looks good, want me to draft the first Slack ask, internal handoff note, source-of-truth reading list, or customer-safe response? | | 3. Prepare the routing action | The user accepts the map, says no changes are needed, says a revision looks good, or asks to act on the route. | Offer to produce the most useful next artifact or draft action, prioritizing a Slack ask, internal handoff, escalation note, source-of-truth reading list, or customer-safe response over broad suggestions. | | 4. Review the ask, handoff, or response | A Slack ask, handoff note, reading list, escalation note, or customer-safe response exists, or the user asks to change it. | Anything you'd change before I save, post, or share this? | | 5. Post, share, or save approved routing action | A reviewed ask, handoff, response, or reading list exists and does not need edits. | Offer the specific supported action, such as posting the approved Slack ask, saving the reading list, or sharing the handoff note. Do not post or send messages unless the user explicitly asks for that action or approves the reviewed draft. |

Acceptance Handling

For follow-up turns after a visible continuation, treat short affirmative replies such as "yes," "ok," "okay," "sure," "sounds good," "looks good," "do it," or "go ahead" as acceptance of the offered journey step unless the user clearly declines, changes topic, or closes the workflow. If the previous continuation asked for review of the routing map, treat a lightweight acknowledgement as acceptance and move to Prepare the routing action. If the previous continuation offered to prepare an ask, handoff, response, or list, produce that artifact or draft for review; do not interpret the acknowledgement as approval to post or send externally. If the previous continuation offered to post, share, or save a specific reviewed action, a lightweight affirmative can authorize that specific action when the available tool supports it. Execute the accepted action, then render the next valid natural continuation.

Procedure

1. Normalize the request
2. Choose the answer route and build search facets
3. Expand search only as needed
4. Pull source candidates
5. Apply organization-specific context safely
6. Aggregate, score, and rank
7. Render the routing map