Common foundation
Organising your skills into hats (roles)
One orchestrator per role that routes to specialised building blocks: your know-how becomes reusable, by you and by others.
The problem
Every time you explain to Claude how to review a thesis or build a slide in your template, you start from scratch. And once you have several dozen sets of instructions, nobody knows which one to trigger.
Figure. The orchestrator routes to the domains and their building blocks.
Step-by-step method
-
Write a skill as soon as a piece of know-how repeats three times: an instruction file with its trigger phrases (“review this thesis”, “build this case”), its steps, its deliverable and its safeguards.
-
Group them into hats (roles): one orchestrator per hat (academic, department, data-driven research…). It qualifies the request and routes to a building block, never doing the detailed work itself.
-
Declare the boundaries: what each hat excludes, and which other skill it hands over to.
-
Create one Claude Project per domain to keep conversation context (Academic, Department, Research).
-
Keep a skills map (an artifact): which skill, which trigger, which mission, which status.
-
Have changes proposed as “cards to approve”, in small batches, rather than letting the AI rewrite its own skills.
-
Package what is stable as a plugin, to reinstall it on a new computer or share it with a colleague.
-
A weekly learning loop: each week, Claude rereads the corrections you made and proposes a bundle of skill updates, which you install yourself after reading them.
-
One “hat” page per role: a hierarchy tab (orchestrator, domains, building blocks), one tab per domain with the status of its files, a skills and scheduled tasks tab, and the list of what remains outside.
-
Tidy up the collection: an alias or a duplicate is archived (never deleted); a building block shared between two hats is declared as such; a variant distributed to others never overwrites your personal version; format skills (Word, PowerPoint, Excel, PDF) remain cross-cutting.
Figure. The agents and their skills: see the Agents page.
Deliverable
A skills library organised by role, a readable map, one project per domain.
Starter prompt
Analyse my conversations from the last two months, group them by theme, and for each theme propose: create a project, create a skill, or nothing. Present it in a table for me to approve, without changing anything.