Cross-Tool Search with Cited Answers
Get one cited answer from connected chat, email, docs, and tickets, with decision history and explicit evidence gaps.
Before & after
Same prompt, same agent — the only difference is the skill.
Let me help you find that information. You'd need to search through Slack for any API design discussions, then check your email for related threads, scan any shared documents or wikis, and check your project tracker for related tickets. I'd recommend starting with the most recent conversations and working backward. You might find the discussion spread across multiple channels and platforms. Would it help if I suggested a search strategy, or would you prefer I help you pull from one source at a time? Once you've gathered the information, I can help synthesize it for you.
SEARCH DECOMPOSED INTO: → Design decision thread → Email follow-ups with specs → Updated API documentation → Implementation tickets RESULTS WITH SOURCE ATTRIBUTION: DECISION (engineering channel, Jul 18 3:14pm): Team chose REST over GraphQL. Rationale: simpler onboarding, lower infrastructure cost for current scale. FOLLOW-UP SPEC (email from Sarah, Jul 19 10:22am): Rate limiting set at 1000 requests per minute per key. Versioning via URL path: /v1/endpoints, /v2/endpoints. DOCUMENTATION UPDATE (API design doc, last edited Jul 22): Full specification reflects REST decision. Includes authentication flow, error codes, deprecation policy. IMPLEMENTATION TICKETS (project tracker): • Migrate existing GraphQL resolvers to REST handlers (assigned to 3 engineers) • Update client libraries for v2 endpoints (in progress) • Deprecate GraphQL API with 6-month window (planned) KEY DETAILS FOUND: Endpoint count: 47 total (23 migrated, 24 pending) Estimated completion: August 15 Breaking changes: authentication schema revised, error response format standardized
About this skill
“Where did we decide this?” often means searching a chat thread, a follow-up email, a document, and a ticket that disagree. This skill turns one question into targeted searches across available connected tools, then returns a supported answer that separates current decisions from drafts and assumptions.
What it does
- Breaks a question into searchable entities, aliases, dates, and evidence needs.
- Searches available connected sources in parallel where supported, with follow-up queries driven by evidence gaps.
- Opens original threads, documents, and tickets to check context beyond search snippets.
- Reconstructs decisions across tools while distinguishing proposals, approvals, implementation, and verified operation.
- Resolves conflicting sources using ownership, explicit approval, effective dates, and supersession evidence.
- Cites material claims and reports inaccessible sources, incomplete coverage, and unresolved questions.
What you get
One concise answer with linked, dated evidence and any decision history needed to explain it. A compact coverage note shows where the search ran and what remains unknown.
Best for
Teams whose decisions and operating knowledge are scattered across chat, email, wikis, documents, and project trackers. Especially useful for finding final decisions, current policies, launch status, and the source behind a disputed claim.
SKILL.md preview
---
name: cross-tool-search-with-cited-answers
description: Synthesizes answers across available connected chat, email, documents, wikis, and work trackers using targeted parallel searches, original-source inspection, and claim-level citations. Use when the user says "what did we decide about this", "search across our tools", "where is the final spec", "Slack and the doc disagree", "I keep finding outdated answers", "who approved this change", or "find the decision and its sources".
---
# Cross-Tool Search with Cited Answers
… (sign up to view the full skill)More research & data skills
View all Research & Data skills →Source-Reconciled Research Brief
Turn supplied links into a concise brief with claim-level citations, reconciled source conflicts, and explicit evidence gaps.
Source-Traced Research Bundle
Compile many sources into one bundle where every claim is atomic, sourced, dated, tiered, and conflict-checked, in Markdown or JSON.
A/B Test Power and Validity Designer
Exact A/B sample sizes and MDE with math shown, plus the traps: unit mismatch, multiple variants, peeking, guardrail power, and SRM.
Research Routing and Cited Briefings
Route research to the right method, then produce a cited briefing with evidence gaps, disagreements, and a source audit.