what-context-needed
Ask Copilot what files it needs to see before answering a question
Profile →npx skills add github/awesome-copilot --skill what-context-needed --agent copilot
Same command for any agent — swap --agent for claude-code, codex, cursor.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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.
- My Question
- Instructions
- Output Format
What does the what-context-needed skill do?
Ask Copilot what files it needs to see before answering a question
How do I install it?
Run `npx skills add github/awesome-copilot --skill what-context-needed --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From github/awesome-copilot, a repository with 37,432 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.