orient
Skill1 starsChanged 36 days agoMITView on GitHub
Use at the start of a new session when the user says "orient", "/orient", or asks to get up to speed on the workspace. Produces a briefing of active state, in-flight work, staleness flags, and a recommended next action.
27 other projects use a version of this.
Adopted by
Most recently taken up by
- ntholm86/principles-of-earned-autonomy-skills-suitetheir own version, first seen Nov 11, 2026
- nguyenvanphituoc/shapeup-sdlc-plugintheir own version, first seen Nov 9, 2026
- blinkboxhq/Blinkboxtheir own version, first seen Nov 8, 2026
- emergent-wisdom/understanding-graphtheir own version, first seen Nov 1, 2026
- Braydenh563/Tessellatetheir own version, first seen Nov 1, 2026
- AN0099/toothpaste-kittheir own version, first seen Oct 24, 2026
Used with
Projects with it also use retro, ui-ux-pro-max and 1 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
AWSSkillretro
Conduct a retrospective on a coding session.
Also in 3 projects that use this
StrayDragonSkillui-ux-pro-max
UI/UX design intelligence. 50 styles, 21 palettes, 50 font pairings, 20 charts, 8 stacks (React, Next.js, Vue, Svelte, SwiftUI, React Native, Flutter, Tailwind). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app, .html, .tsx, .vue, .svelte. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
Also in 3 projects that use this
AWSSkillship
Finalize dev work on an issue branch — update docs, push, and open a PR.
Also in 3 projects that use this
Other versions27 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 27
- seandavi/lifeos-template★ 46same name
- wrg32786/aigent-os★ 26same name
- jcottam/agent-resources★ 25same name
- sergeeey/Claude-cod-top-2026★ 9same name
- ramboz/jig★ 7same name
- blinkboxhq/Blinkbox★ 4same name
- Braydenh563/MemoryMap-AI★ 4same name
- Braydenh563/Tessellate★ 4same name
- david-vrba/claude-power-skills★ 4same name
- ntholm86/principles-of-earned-autonomy-skills-suite★ 4same name
17 more not listed
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.
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 5 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 25 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Read the fixed file set below. Do not wander: If a file listed here doesn't exist, note it and move on — don't improvise replacements.
- Distinctive: line 43
Do NOT read project source code or docs beyond the file set above.
- Distinctive: line 44
Do NOT fire subagents during orient — the file set is small and bounded.
- Distinctive: line 45
Do NOT write to any file during orient — this is read-only.
- Very specific: line 46
Do NOT include the ## Completed historical tables in what you summarize.
- Distinctive: line 47
If a listed file is missing, note it in the briefing as a structural flag — don't skip silently.
“Common” is measured: kept by at least 6 in 10 of the 25 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Purpose
Bring Claude up to speed on this workspace quickly and deterministically at session start, without burning context on speculative exploration. Output is a concise briefing the user can redirect.
Iron Law
Read the fixed file set below. Do not wander. If a file listed here doesn't exist, note it and move on — don't improvise replacements.
Procedure
1. Read (in parallel)
CLAUDE.md— workspace working context (includes the Command shortcuts table)tasks/todo.md— current implementation plantasks/lessons.md— self-improvement rules to apply this sessiontasks/notes.md— master task list (scan active sections; skip the## Completedtable)
2. Freshness scan
Glob for */CONTEXT.md and */PLAN.md across project folders and check mtime. Flag any older than 30 days as potentially stale. Do NOT read the files — just check mtime.
3. Produce the briefing
Output under 300 words, structured as:
Active state — one line on where the workspace is right now.
In-flight work — anything with an open plan or checklist that isn't closed. Cite file paths.
Staleness flags — any CONTEXT.md / PLAN.md older than 30 days.
Lessons active this session — one-line summary per entry in lessons.md.
Recommended next action — one task with a one-sentence tradeoff. Present as "I'd pick X because Y; alternatives are Z" — something the user can redirect, not a decided plan.
Rules
- Do NOT read project source code or docs beyond the file set above. The user can ask for depth on a specific project after orienting.
- Do NOT fire subagents during orient — the file set is small and bounded.
- Do NOT write to any file during orient — this is read-only.
- Do NOT include the
## Completedhistorical tables in what you summarize. - If a listed file is missing, note it in the briefing as a structural flag — don't skip silently.
- End with one question offering direction: "Want depth on any of these, or start on the recommended next action?"
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.

