setup-context
Skill1 starsChanged 3 days agoMITView on GitHub
Set up everything this conversation needs before the work starts - read the current repository (tree, docs, rules files, build, code, git state), search the earlier and archived sessions on this computer (Claude Code transcripts and memory, claude-cluster sessions and their trash, Codex / Qwen / opencode, handover files) for what was asked, done, left and decided, then load the skills that fit the project (style, language, build, tests, docs, git) and check the MCP servers / tools it would use (configured, connected, missing), and hold it all as the working context; the questions only at the end. Use whenever the user says "setup le contexte", "prépare-toi", "charge tout ce qu'il faut", "lis le repo et les anciennes sessions", "setup les skills / mcp utiles", or summons /setup-context before a task.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- getnao/naotheir own version, first seen Oct 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- getnao/nao★ 2ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository70 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- ask-at-endSkill
- clarifySkill
- continue-workSkill
- exportSkill
- full-permissionSkill
- ideationSkill
- interactive-questionsSkill
- onboardSkill
- pauseSkill
- presentationSkill
- rtkSkill
- write-like-meSkill
- audit-bugsSkill
- audit-depsSkill
- audit-qualitySkill
- audit-securitySkill
- benchmarkSkill
- cmake-styleSkill
- cpp-classSkill
- cpp-commentsSkill
- cpp-projectSkill
- cpp-styleSkill
- better-explain-docSkill
- better-html-docSkill
- better-html-styleSkill
- better-protocol-docSkill
- docs-updateSkill
- explain-docSkill
- html-docSkill
- html-styleSkill
- protocol-docSkill
- readme-styleSkill
- reportSkill
- wiki-styleSkill
- ci-cdSkill
- git-commitSkill
- git-conventionsSkill
- pre-commitSkill
- legal-checkSkill
- legal-setupSkill
- licenseSkill
- libutils-exceptionSkill
- libutils-installSkill
- libutils-setupSkill
- libutilsSkill
- python-classSkill
- python-commentsSkill
- python-projectSkill
- python-styleSkill
- auditSkill
- cppSkill
- devSkill
- docSkill
- gitSkill
- legalSkill
- pythonSkill
- setup-projectSkill
- styleSkill
- setup-studioSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Read what the project is and what was already done, then equip the session: the skills loaded, the MCP servers / tools checked.
- Distinctive: line 26
Search by the absolute path of the project (its parents, subfolders, worktrees too), newest first:
- Distinctive: line 39
Every claim checked against the code and git: "done" in a transcript but absent from the code is not done.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Setup context: the project, its history, the right skills and tools
Read what the project is and what was already done, then equip the session: the skills loaded, the MCP servers / tools checked. Read-only on the project: nothing built, changed, committed, stopped or resumed.
Scope given with the skill: the folder / task after /setup-context if any, else the cwd and the latest request.
1. The project and its history
- The
onboardskill installed: follow its steps 0-4 (the project, its git history, the earlier sessions, merged and checked). Else do the same by hand:- Tree (
git ls-files, sizes, languages), docs read entirely (README*, CLAUDE.md / AGENTS.md and the other rules files: rules to follow from now on, CHANGELOG,docs/, TODO / NOTES /.info/ PASSATION.md), build and CI (CMakeLists, package files, workflows, hooks), code (entry points, module layout, tests, TODO / FIXME). - Git: log (recent
--stat), branches and worktrees, tags,git status/ diff of the pending work, unpushed commits, stashes (listed, never popped).
- Tree (
- Secrets: their existence and place only, never their content.
2. Earlier and archived sessions
Search by the absolute path of the project (its parents, subfolders, worktrees too), newest first:
- Claude Code:
~/.claude/projects/<path with every / and . turned into ->/*.jsonl(worktrees:<repo>--claude-worktrees-<name>), itsmemory/(MEMORY.md and its files),~/.claude/jobs/*/state.json(background jobs: their state, what they wait for). - claude-cluster:
claude-cluster list --rtkandclaude-cluster external --rtk; every instance (~/.local/share/claude-cluster/instances/*); the archived sessions too (the trash of each instance, kept 7 days by default) and their transcripts (logs/), the tasks, schedules and todo lists of the project. A running session is only read, never sent anything. - Other agents: Codex
~/.codex/sessions, Qwen Code~/.qwen/projects, opencodeopencode session list, Gemini~/.gemini(grep the project path); handover files (PASSATION.md, HANDOFF.md, NOTES.md) in the project or its parent. - From each one: the user's requests (their words for the important ones), what was done, left or failed, the decisions,
refusals and rules. A long transcript is never dumped: extract the user messages, the last assistant messages and the
errors (
jq/ a short python script), read what matters. - Every claim checked against the code and git: "done" in a transcript but absent from the code is not done.
3. The skills that fit
- List the installed skills (the listing of this session) and pick the ones the project and the task call for: its
languages' style skills (
cpp-style,python-style,coding-style,cmake-style, the comments skills), its build / tests / docs / git skills,libutilswhen it uses libutils, the routers when the work spans several (dev,audit). - Load them now (Skill tool), the most central first; never more than the task needs (each costs context). Say in one line which ones are loaded and why.
- The rules files of the project win over a skill when they disagree: say so.
4. MCP servers and tools
- The MCP servers configured (
claude mcp list, the project's.mcp.json,~/.claude.json), connected or failing, and the deferred tools of this session (ToolSearch): which ones the task would use (GitHub, a browser, docs, a database, the claude-cluster MCP...). - The CLI tools the project needs (compilers,
cmake,gh,xstyle, package managers, linters): present (command -v) and their version, missing ones noted - never installed or configured without asking. - A useful server or tool missing: noted with its exact setup command, proposed at the end (never added silently).
5. Report, then the questions
- Terse (
rtk): the project in two lines, its state (branch, last commit, pending work), what earlier sessions did and left (dated), the rules to follow, the skills loaded, the tools ready / missing, the possible next steps. - Every question only at the end, through
interactive-questions(a popup, never a list in the text): which next step, a contradiction found, a missing tool / MCP to install, an old session to resume. Nothing unclear left: no popup. - A fact that must last (a rule, a convention) goes to memory / CLAUDE.md only when the user wants it.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

