All agent skills

Leading Deeper with AI / 02

Build reusable context

Put answers, sources and open questions in one starting point the next person or agent can reuse.

AI connects existing documents, code and conversations into a sourced draft. A person checks sources and gaps before accepting guidance.SourcesAI mapYour review
AI generation or assessmentHuman input or judgment

Fictional example / AI draft

Team digest starting point · draft

System overview
Ready queue items → digest job → email to the subscribed team. Operations owns investigations. This is the flow described by the supplied README, not a verified account of a live run. [K1]
See the full example
When does it run?
The current repository excerpt configures weekdays at 09:00 UTC [K2]. Older onboarding notes say 10:00 UTC [K3]. Treat this as a source conflict: the actual deployed schedule has not been established.
Where do I start with a missing email?
Inspect the relevant dated run record and its delivery result. Do not equate a successful run with recipient receipt. [K2] No run or delivery records were supplied, so this draft cannot diagnose a specific missing email. [K3]
Gaps and proposed entry point
First resolve the deployed schedule before a colleague relies on a send time. Then add links to the run records and delivery evidence. Proposed documentation outline: purpose and owner; verified schedule; missing-email investigation; source versions and open questions. No shared source has been updated.
Give your agent this context

All examples use invented sources and results. They are illustrations, not reports from Jasmine’s workplace or measured outcomes.

[K1] Digest README · revision 4
The team digest collects items marked ready in the queue and sends one email to the subscribed team. Ask: when is the digest scheduled, and where should I begin if someone reports a missing email? The operations team owns investigations.
[K2] Supplied config and runbook excerpt · current repository snapshot
digest.schedule: weekdays at 09:00 UTC. Runbook: for a missing email, inspect the run record for the relevant date and its delivery result. A successful job run alone does not establish that a recipient received the email.
[K3] Onboarding notes · revision 1
The digest goes out at 10:00 UTC on weekdays. The deployment schedule and recipient delivery records are not included in this source pack.
How this example works
  1. 01 / You

    Choose the reader's questions

    Supply the three excerpts and ask for an entry point covering scheduling and missing-email investigations. Keep the source labels and versions attached.

  2. 02 / AI

    Build a referenced map

    Explain the supported flow, answer each question with references, and expose the schedule conflict and missing deployment evidence. Do not fill the gaps with assumed behavior.

  3. 03 / You

    Resolve the consequential gap

    An operations reviewer checks the deployed schedule and the referenced runbook before deciding what should become shared documentation.

You check before using the result

  • Can the reviewer follow every reference and verify which schedule is deployed?
  • Could a new colleague find the next investigation step without reading an unsupported diagnosis?

Use the AI tool approved for your work with supplied material. Wording and layout will vary by model; look for the evidence, uncertainty and review decisions shown here. Connections and recurring runs depend on your setup.

What the output should include across models
  • System overview
  • When does it run?
  • Where do I start with a missing email?
  • Gaps and proposed entry point
Use this agent skill ↑
Connect your sources (optional)
01

Start here

Bring your context.

What you’ll need

  • System or workflow to understand
  • Authorized code, documentation, tickets and discussion excerpts
  • Questions the next person needs to answer
  • Available source identifiers, dates or versions

MCP & tool setup

The agent needs the source material, not a particular MCP. Add conversation access only if live team discussions are part of the agreed scope.

Read current knowledge and source artifactsPossible toolsFilesDocsGitHubGitLab

Needed when: When the knowledge starting point relies on repository or documentation sources that were not supplied directly.

MCP or tool examples
Local file or repository tools · An approved documentation/search connector or MCP · GitHub or GitLab MCP for remote repository material
Tools must support
Read the authorized documentation, code and referenced artifacts; Search relevant content; Capture stable source identifiers, dates and versions
Access needed
Read access to the selected sources only. Drafting these outputs does not require publishing or editing the source of truth.
Without that connection
Provide an approved local snapshot or excerpts with source identifiers and relevant versions.
Read team conversationsPossible toolsSlackTeams

Needed when: Only when the scope includes live Slack or Teams conversations rather than supplied excerpts.

MCP or tool examples
Slack’s official MCP server · An organization-approved Teams-capable MCP, such as Work IQ where available
Tools must support
Search approved channels within the reporting period; Read relevant messages and complete threads; Retain message links, dates and thread context
Access needed
Read access to the channels and threads included in the task. Verify the installed server exposes the needed search and read tools; Teams availability varies by tenant, licensing and administrator policy. Sending messages and administration are not needed.
Without that connection
Provide approved thread exports or excerpts with dates, source links and enough surrounding context to interpret them.

No live connection? Supply approved code/document snapshots and conversation excerpts with dates and source identifiers. The draft can be produced entirely from those files.

Use the full prompt instead
02

Copy. Adapt. Try.

Make it your own.

01Gather the sources

Bring the approved code, documents and discussion context.

02AIConnect the pieces

Ask the agent for a concise map with source references.

03AIHumanExpose the gaps

AI flags possible gaps. A knowledgeable person checks the sources and uncertainty.

Replace the bracketed inputs. Use context you’re authorized to share.

Download .txt

Copy the template or select the text directly.

Using an agent? Other formats

Adaptable template based on the talk; not the original internal prompt.

Review checks
03

Keep your judgment in the loop

Review the result.

01

Can a knowledgeable person verify the claims from the references?

02

Are assumptions and stale or conflicting sources clearly visible?

03

Can the next person answer a real question using this draft?

What evidence should you look for?
  • Try a small, repeatable set of real questions and record supported answers and remaining gaps.
  • Keep source coverage and reviewer corrections visible; a document's existence does not prove completeness.
How this connects to the talk

A pattern practiced in both settings

From practice to work.

Softball IQ

Curated questions and project instructions made Softball IQ context reusable, including corrections that should inform the next attempt.

At work

The team used existing code, documentation and conversations to build shared knowledge for colleagues, support and agents.

Your judgmentA knowledgeable person verifies claims, resolves conflicts and decides what belongs in the shared source.

Value to checkTest whether people can answer real questions from the material, then track corrections, remaining gaps and repeated requests for context.