setup-workspace
Skill5 starsChanged 24 days agoMITView on GitHub
The one entry point for setting up this uni workspace from scratch or finishing a half-done setup. Chains the other skills in order (setup-obsidian, then setup-year, then the optional extras such as tasks and HOME, flashcards, study timetable, weekly review, careers), invoking each one as a skill and skipping whatever is already done. Use when the student says "set up", "set up everything", "get started", "set up the workspace", "finish setting up", or opens a fresh clone where projects/PROFILE.md doesn't exist yet.
7 other projects use a version of this.
Adopted by
Most recently taken up by
- probabl-ai/skillstheir own version, first seen Nov 9, 2026
- Richicinschi/studio-ostheir own version, first seen Nov 8, 2026
- The-AI-Thinker/claude-code-pm-startertheir own version, first seen Oct 15, 2026
- probabl-ai/skore-skillstheir own version, first seen Oct 15, 2026
- Flop19/legal-workspace-startertheir own version, first seen Oct 8, 2026
- timscheuerai/gtm-architecture-templatetheir own version, first seen Sep 14, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- probabl-ai/skills★ 145same name
- probabl-ai/skore-skills★ 145same name
- The-AI-Thinker/claude-code-pm-starter★ 13same name
- Flop19/legal-workspace-starter★ 8same name
- timscheuerai/gtm-architecture-template★ 2same name
- hunterbohm/solo-staff★ 0same name
- Richicinschi/studio-os★ 0same 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 repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-moduleSkill
- create-flashcardsSkill
- create-study-timetableSkill
- employer-insightsSkill
- exam-practiceSkill
- find-rolesSkill
- prep-applicationSkill
- setup-careersSkill
- setup-obsidianSkill
- setup-yearSkill
- sync-moodleSkill
- weekly-reviewSkill
- whats-dueSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 4 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
Every step checks whether it's already done, so running "set up" again after a break carries on where it stopped.
- Distinctive: line 16
Check, and tell the student in one short list what's done and what's next:
- Very specific: line 25
If .obsidian/ doesn't exist, ask them to open Obsidian → Open folder as vault → this folder, and wait until they say it's open.
- Very specific: line 32
If dashboard.css isn't installed yet, invoke the setup-obsidian skill and let it finish (plugins, theme, styling, reload).
- Very specific: line 36
If projects/PROFILE.md doesn't exist, invoke the setup-year skill and let it finish (profile, Moodle login by the student, modules, …
- Distinctive: line 41
Ask once which of these they want now.
- Distinctive: line 51
Do them one at a time, in the order they chose.
“Common” is measured: kept by at least 6 in 10 of the 7 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
Set up the workspace
This is the front door. It doesn't do the work itself: it invokes the other setup skills in order, using the skill tool, so each runs exactly as written. Never read another skill's SKILL.md and improvise from it. If a skill isn't available in this session, stop and ask the student to start a new session in this folder (skills load when a session starts here), then say "set up" again.
Every step checks whether it's already done, so running "set up" again after a break carries on where it stopped.
0. Where are we?
Check, and tell the student in one short list what's done and what's next:
- This session is in the workspace folder (it has
CLAUDE.mdand.claude/skills/). If not, stop: tell them to open a new Code session in theuni-workspacefolder and say "set up" there. - Obsidian:
.obsidian/exists (the folder has been opened as a vault) and.obsidian/snippets/dashboard.cssexists (setup-obsidian has run). - Year:
projects/PROFILE.mdexists and at least one module folder (setup-year has run). - Extras:
HOME.md,tasks/TASKS.md,timetable/, anyflashcards/,careers/BRIEF.md.
1. Open the vault in Obsidian
If .obsidian/ doesn't exist, ask them to open Obsidian → Open folder as vault → this folder, and wait until they
say it's open. (Obsidian creates .obsidian/ then.) Don't hunt for the app or install it yourself (no Homebrew,
winget or downloads): if they don't have it, give them https://obsidian.md/download and wait. That's the student's
install, like the plugins. A fresh clone has no plugins yet, so Obsidian won't ask about trusting it; don't mention
that prompt.
2. Obsidian setup
If dashboard.css isn't installed yet, invoke the setup-obsidian skill and let it finish (plugins, theme,
styling, reload). Skip if it's done.
3. The year
If projects/PROFILE.md doesn't exist, invoke the setup-year skill and let it finish (profile, Moodle login by
the student, modules, assessments, DEADLINES). Skip if it's done, but if they say modules are missing, invoke
add-module for each.
4. Extras (one question)
Ask once which of these they want now. Each can also be added later by asking, and none is required:
| Extra | How |
| Home dashboard + tasks (recommended) | Copy projects/_template/HOME.md to the root and tasks/_template/TASKS.md into tasks/. Remove HOME cards and header pills (HOME and TASKS) for anything not set up yet, e.g. Timetable, Careers, Review, Moodle before the first sync. Remove the template note |
| Study timetable | Invoke create-study-timetable (it needs their lecture timetable; an .ics export is best) |
| Flashcards for exam-heavy modules | Invoke create-flashcards once per module they pick |
| Weekly review on Sunday evenings | Invoke weekly-review and follow its "Schedule it" section |
| Careers (grad roles, internships, placements) | Invoke setup-careers |
Do them one at a time, in the order they chose. After each, re-add the matching HOME card or pill if HOME exists.
5. Finish
- Offer a first "refresh Moodle" (invoke
sync-moodle) so the baseline exists andprojects/updates/MOODLE.mdis created. - Reply with: what's set up, a table of modules (credits, semester, assessment), the next three deadlines, anything
_tbc_, and what to say next: "what's due?", "refresh Moodle" (weekly), "quiz me on<module>", "weekly review". - Next time they open the folder (in Claude and Obsidian), there's nothing to set up. They just talk.
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.