What Context Needed
Ask your agent to list must-see, should-see, and uncertain files before it answers a codebase question.
Overview
What Context Needed is a journey-wide agent skill that lists which repository files an assistant must read—usable whenever a solo builder needs accurate answers before committing to a change.
Install
npx skills add https://github.com/github/awesome-copilot --skill what-context-neededWhat is this skill?
- Structured output: Must See, Should See, Already Have, and Uncertainties sections
- Requires the agent to explain why each file path matters
- Explicitly accounts for files already visible in the conversation
- Two-step flow: list context first, then re-ask the question after files are provided
- Markdown output format ready to paste into follow-up prompts
Adoption & trust: 8.6k installs on skills.sh; 34.6k GitHub stars; 3/3 security scanners passed (skills.sh audits).
What problem does it solve?
You asked the agent a repo-specific question but it may answer without the files that actually control behavior.
Who is it for?
Large or unfamiliar repos where you want the agent to self-audit missing context before debugging, reviewing, or planning.
Skip if: Purely conceptual questions with no codebase dependency or when you already attached the full relevant tree.
When should I use this skill?
Before answering a repository-dependent question, tell the agent to list files it must examine.
What do I get? / Deliverables
You receive a prioritized file list with rationales and gaps, then re-ask your question with the right context attached.
- Markdown context plan with Must See / Should See / Already Have / Uncertainties
Recommended Skills
Journey fit
Useful at every journey phase - explore requirements and options before committing to a direction.
Where it fits
Before fixing auth, get a Must See list for middleware, session store, and env config.
Ask what files define the prototype boundary before estimating scope.
Enumerate handlers and policy files before answering a secrets-exposure question.
List logging and retry modules before diagnosing a production stack trace.
Identify event schema and tracking helpers before changing funnel metrics.
How it compares
Context-gathering ritual before Q&A—not a code search tool or automatic @-mention indexer.
Common Questions / FAQ
Who is what-context-needed for?
Solo builders using Copilot, Claude Code, Cursor, or similar agents who want fewer wrong answers on repository-specific questions.
When should I use what-context-needed?
Before debugging in Build, scoping integrations in Validate, reviewing launch configs in Ship, triaging errors in Operate, or researching unfamiliar modules in Idea—anytime the answer depends on files you have not shared.
Is what-context-needed safe to install?
It only shapes prompt behavior and does not call tools by itself; check the Security Audits panel on this Prism page for the packaged skill files.
SKILL.md
READMESKILL.md - What Context Needed
# What Context Do You Need? Before answering my question, tell me what files you need to see. ## My Question {{question}} ## Instructions 1. Based on my question, list the files you would need to examine 2. Explain why each file is relevant 3. Note any files you've already seen in this conversation 4. Identify what you're uncertain about ## Output Format ```markdown ## Files I Need ### Must See (required for accurate answer) - `path/to/file.ts` — [why needed] ### Should See (helpful for complete answer) - `path/to/file.ts` — [why helpful] ### Already Have - `path/to/file.ts` — [from earlier in conversation] ### Uncertainties - [What I'm not sure about without seeing the code] ``` After I provide these files, I'll ask my question again.