Agents · sub-agents · skills
4 agents, one per role, 18 domain sub-agents and 47 skills. The agent receives the request, the sub-agent chains the steps, the skill does the work. You keep the decision.
Install the agents in Claude: connectors, plugins, skills →
The augmented secretariat, shared by all three roles: what comes in, where it is filed, what is coming.
↓ Download the agentConnectorFree sign-up · 5 downloads
Daily roadmap, projects, deadlines to anticipate, documents retrieved.
dashboardP1dashboard-writeP2campus-dashboard-agentTriage of emails by action, date capture, contacts.
mail-triageP1calendar-captureP2directoryP2campus-mail-agentAvailability, conflicts, requests to decide on.
calendarP1requestsP3campus-calendar-agentRoot folder, typology, filing, inventory.
filingP1file-typologyP2inventoryP3campus-archivist-agentForms, professional identity, career file.
identityP3cvP2activity-historyP3activity-reportP3campus-administrative-agentFrom the scientific question to publication and op-ed.
↓ Download the agentConnectorFree sign-up · 5 downloads
Search, sort, read, synthesise, keep watch.
bibliographyP1literature-watchP2evidence-synthesisP2campus-bibliography-agentReview, arbitrate, follow through to submission; peer reviews for journals.
manuscript-reviewP1manuscript-portfolioP2peer-reviewP3campus-manuscript-agentResearch database, cohorts, studies.
research-databaseP3database-queryP3studiesP3campus-data-agentTalks, slides, online materials, travel.
congress-talkP1slide-bankP2slideP1pdf-figureP2online-slidesP3congress-travelP2campus-congress-agentFaculty, diplomas, supervision, continuing education.
↓ Download the agentConnectorFree sign-up · 5 downloads
Lectures, MCQs, OSCEs, assessment design, exam boards, delegated duties.
facultyP2delegated-dutiesP3campus-faculty-agentUniversity diploma: start of year, lists, calendar, exams.
university-diplomaP3campus-diploma-agentTheses, dissertations, defences.
thesis-defenceP2supervisionP3campus-supervision-agentClinical cases and imaging for teaching.
clinical-caseP2echo-imagingP3mri-imagingP3campus-visual-teaching-agentWatch on continuing-education platforms.
↓ All skills of this sub-agentcampus-training-agentThe department: organisation, staff meetings, rota, care pathways, projects.
↓ Download the agentConnectorFree sign-up · 5 downloads
Staff-meeting programme, talks, topics never covered.
staff-talkP2staff-programmeP3campus-staff-meetings-agentRota tool, absences, stand-ins, publication.
rotaP2absences-stand-insP3campus-rota-agentDepartment projects, reports, strategy.
department-projectP3unit-reportP3campus-head-of-department-agentProcedures, consult requests, care pathways, events.
protocolsP3consults-pathwaysP3eventP3campus-unit-head-agentThe Organiser, Researcher and Teacher agents are shared. Only the clinical agent changes.
Medication circuit, pharmaceutical validation, preparations and devices, clinical trials, vigilance.
Clinical sessions, technical platform, clinical supervision of students.
Care organisation, placement supervision, protocols and pathways.
They do nothing themselves: they read a plan and call the agents at set times.
Every day, early
Organiser Agent: health check, mail, daily plan.
One hour later
Resumes the morning run if incomplete.
Every evening
Archivist Agent.
Every evening
Mail, projects, pending decisions.
Friday
Researcher, Teacher, Clinician agents: deadlines, watches, rota.
The 1st
Administrative Agent: CV, history; index, backup.
| Level | What it is | Example |
|---|---|---|
| Agent | A role. It receives the request and chooses the right domain; it never does the detail. | Researcher agent |
| Sub-agent | A domain of that role. It chains the skills in the right order. | Conference agent |
| Skill | A building block that does one precise job, with its deliverable and its safeguards. | slide, pdf-figure |
| Routine | A scheduled task that calls the agents at a fixed time. | Weekly, on Fridays |
Agents and sub-agents are technically “orchestrator” skills: their only job is routing. This is what lets you add a building block without rewriting everything.
A skill is an instruction file that Claude loads when the request matches. It fits on one page:
name: review
description: Review a thesis, dissertation or article on three levels,
with tracked changes under my name, and follow the manuscript through to submission.
trigger on: "review this thesis", "do the next version", "blocking issues before submission"
steps:
1. Read the whole document and the instructions
2. Substance, structure, form; references checked in PubMed
3. Save a new suffixed version, never overwrite
deliverable: the reviewed .docx + a note of the blocking issues
safeguards: common foundation (never overwrite, never send, human validation)
hands off to: directory (co-authors), calendar (deadlines)An artifact is an interactive page published from Claude: dashboard, validation page, map. Three rules:
A link between two elements is not magic: it is always one of these three things, written down in black and white.
| Type of link | Where it is written | Example |
|---|---|---|
| A hand-off | In the skill (“hands off to”) | email triage sends a received manuscript to the review skill |
| A routine step | In the routine’s plan file | the evening run updates the dashboard’s ongoing projects |
| A database write | In the skill or the plan, with the target collection | the literature watch writes its references to the watch tab |
If a link is not written anywhere, it does not exist: this is the first thing the cross-inventory checks.
Reference
Here is the actual content of the skills of an academic hat, anonymized: role, trigger phrases, steps, absolute rules and mistakes already made. Use it as a model for writing your own. Order: orchestrators, congress and slide chain, imaging, staff meetings and teaching, career.
Role: the single hat for university activity. It qualifies, routes and logs; it never itself produces a talk, a review or a bibliography.
Triggers: “my university activity”, “where am I with my articles”, “what do I have to prepare”, any university request with no named building block.
Explicitly excludes: consulting for industry, protocol review, invoicing, accounting, personal life. Rule: assignment follows the payer, not the tool.
Step 1 — qualify with one question
| Domain | Content |
|---|---|
| A · Research and publications | manuscript, thesis, dissertation, review, bibliography, cohort |
| B · Congresses and presentations | talk, workshop, clinical case, slide, session, travel |
| C · Department and staff meetings | staff meeting, schedule, laboratory, reading protocol |
| D · Career and outreach | CV, history, supervision, learned societies |
| E · Teaching and training | lectures, MCQs, semiology, tutoring, OSCE, exam-question review (docimology), diploma, training watch |
Step 2 — route
Rules inherited by all building blocks
Traces: an academic cockpit (deadlines, manuscripts, congresses, staff meetings, reviews), the anticipation board, a reference document for the hat. D-30 rule: any congress presentation triggers a preparation alert.
Role: router, never executor. It owns the entry-point question, scoping, final assembly, review and the shared slide basket.
Triggers: “make a presentation, a talk, congress slides”, “prepare my communication”, “state of the art”, “symposium”.
Architecture: a single tabbed HTML workshop, tabs always accessible even when empty: bibliography; online congress materials; bank of past presentations; imaging; analysis and annotation of a submitted deck (quality score, never automatic correction); storyboard and generation.
Step 0 — always asked first: start from scratch, from the bank, from updating a specific presentation, from a scientific question (delegated to the synthesis skill), or resume a recent presentation (all its slides loaded into the basket).
Absolute rules
Technical points: the reference script lives on the user’s side (to be checked at the start of the session); a table of journals with their impact factor kept up to date by hand; the result always opened in the browser; a shared database never opened directly (working copy, then copied back and verified by checksum).
Status: separate from the personal skill, which remains unchanged; designed for any physician, with no machine-specific paths. Starting point for a distributable offering.
Triggers: only on explicit request for the “online” version.
Structure: scoping (new presentation, update, merge), bibliography, past presentations (local folder), media bank (local folder), analysis and annotation, storyboard with timed rehearsal mode.
Excluded: subscription congress materials (copyright) and patient imaging (health-data hosting not covered).
Technical constraint: local HTML workshop, no server; each action produces a line to copy into the conversation.
Quality: one figure per slide, figures always cited, fidelity of reused slides, four bullets at most, slide-by-slide review before delivery.
Role: index past presentations as thumbnails, display them in a gallery, and copy the chosen slides exactly as they are, never reinterpreted.
Triggers: only “reuse, recycle, pick from” one’s old slides.
A single canonical index, always reused and refreshed incrementally (file date and size), never recreated elsewhere.
| Item | Rule |
|---|---|
| Language | English on the slides |
| Format | 16:9, never 4:3 |
| Volume | about one slide per minute |
| Citations | “Author et al., Journal Year”, never a DOI on the slide |
| Fidelity | reused slide strictly identical to the source |
| Harmonization | at the very end, on explicit request |
| Final assembly | always with explicit approval |
Scope before producing: topic and angle, congress and format, audience, three take-home messages written before the slides, available material.
Status: normative source of the template, applicable to the whole chain.
Step 0 — always ask for the mode
| Mode | Content |
|---|---|
| 0 · Verification | no layout touched; citation and summary in the notes |
| 1 · Layout | reformat to the template with the images present |
| 2 · Rebuild | start entirely from the source publication |
| 3 · Update | add a second or third reference |
| 4 · Variant | layout specified by the user |
Three absolute rules: no slide outside the template; no slide without the original figure extracted from the PDF (otherwise a flagged box and a list of PDFs to download); never large decorative numbers.
Template: white background, text on the left, figure on the right; bold title at the top with a colored rule; four to six short bullets, never full sentences; two figures stacked, never side by side; discreet citation at bottom right.
Mistakes already made, turned into rules: text too small, bullets as full sentences, too many numbers, invented subtitle, misplaced citation, “rebuild” mode that rephrases instead of starting from the source, style imported from a generic design skill. Never let a generic skill decide the style.
Automation: as soon as a source PDF is located, the figure is extracted and inserted, and the PDF is delivered alongside the slide.
Role: replace screenshots with programmatic extraction, at constant resolution, from the actual PDF.
Steps: 1) local copy of the PDF, never a screenshot; 2) render the page at high resolution; 3) locate the rectangle to extract, and if it is ambiguous, present the options rather than guess; 4) crop and insert into the right column, stacked below an existing figure, citation added only if missing.
Boundaries: the bibliography has its own mechanism for open-access articles; this skill is for a non-open-access article or a specific figure.
Strict scope: only the congresses covered by your subscription.
Real incident: an unfiltered search returned a majority of results outside the subscription. Fix: systematic filtering by event type, including retroactively.
Constraint: materials are served in a secure viewer; manual download, never bulk download by script. The skill automates everything that comes after.
Steps: filtered search → selection page ranked by number of slides → 16:9 presentation from the selected pages, full morphology.
Full cycle: PubMed search → interactive selection → download → filing → Word and PowerPoint deliverables, one slide per reference even without a PDF.
Mandatory attribution: source and DOI link for any data presented.
Folders: an active cumulative bank, never emptied; a read-only PDF archive, always checked before re-downloading, never written to.
Eight steps: scope (topic and bibliography name); exhaustive search; enrichment of metadata and impact factor; checkbox table (year and impact sliders, access badge); retrieval of the selection; download (open access first, a single batch per session); filing; Word and PowerPoint generation.
Paywalled articles: legal access tools, then the university’s institutional access. Never bypass a paywall or a captcha.
Difference from the bibliography: a permanent feed that never empties, versus a one-off review. Founding rule: never have to go back to an article to make a slide from it; the slide is produced right away.
Construction: one feed per major theme, plus a cross-cutting feed (methods, guidelines, AI). Measure the annual volume of each feed before setting an alert, and aim for a few references per week after deduplication.
Query rules: no impact-factor filter (PubMed does not allow it); quality comes from a whitelist of journals; no isolated ambiguous acronym; a systematic exclusion block (comment, editorial, erratum, retraction); tighten a feed that is too large.
Absolute rule: nothing is deleted; a discarded reference moves to the “discarded” status and stays archived.
Role: reasoning layer between the bibliography and the presentation: a question becomes an evidence table, compared against the slide bank to spot what is missing or outdated.
Steps: scope the question (population, intervention, comparator, outcome, never a raw keyword); multi-source search; check of the existing bank; filtering; structured extraction (never an invented number); evidence table: stopping point, validation mandatory; gap identification; output in the presentation format.
Boundary: never replaces the presentation orchestrator; it is one of its entry points.
Output: a single file that grows case by case, regenerated by a script from data files, never rewritten by hand.
Block of four slides: divider (number, title, sex, age, context, never a name); initial presentation; additional tests; course and follow-up.
Layout: text on the left, figures on the right, font size adapted to the volume, telegraphic style; a fixed palette.
Anonymization: no surname, first name or date of birth on the slides; the internal identifier goes in the notes.
Principle: export → series classification → black-background presentation, four animated loops per slide, never still images by default.
Series classification by their technical markers (localizers, cine, T1 mapping, flow, late gadolinium enhancement, console captures).
Standard deck: title, long-axis cine, short-axis cine, T1 mapping, late gadolinium enhancement. Excluded by default: localizers, flow, secondary captures (except numerical quantification).
Principle: a hierarchical bank (workshop → case → exam), a persistent cache and scripts (never in a temporary folder), a processing pipeline in stages (metadata, thumbnails, classification, photos and videos, themes).
Classification in mandatory order: strain, spectral Doppler, 3D, color Doppler, 2D, other.
Output: four videos per slide, black background, no visible text, technical information in the notes, looped playback; integration into the presentation workshop.
Watch out: check the identifier of each exam before any grouping; two folders with similar names may be the same exam, or two different patients.
Difference: native lossless video (GIF degrades color Doppler).
Standard five-slide deck: parasternal views; apical views; diastole; right ventricle; strain.
View identification: always read the label burned in by the machine, never guess from anatomical appearance. Option: comparison between visits.
Principle: always start from the history of past staff meetings before producing anything.
Step 0: index of staff meetings (theme, volume, families covered, themes never addressed), the files themselves, the slide bank.
| Mode | Chain |
|---|---|
| 0 · History only | stops after step 0 |
| 1 · Reuse | bank, then slide to re-source |
| 2 · Literature review | synthesis, then bibliography |
| 3 · Specific opinion | synthesis, then targeted bibliography |
| 4 · Clinical case | clinical case and imaging |
| 5 · Scheduling | calendar only |
Format: short, about fifteen slides; beyond forty, it is no longer a staff meeting. End a review with a “what this changes for us” slide.
Excludes the university diploma, which has its own skill.
The chain, always in this order: lecture to prepare → lecture delivered and uploaded → questions → exam-question review (docimology) → exam → deliberation.
Missions delegated to assistant professors: exam-question review (docimology), semiology, ECG tutoring, OSCE, each with its own content, pace and lead.
Anticipation: D-30 before a lecture (materials and questions ready), D-15 before an exam-question review (docimology) session.
Typical rhythm: several seminars per year (in person and by video), exam, official results report.
Five modes: calendar for the year; mailing list (cross-checking results reports and email archives); in-person day; exam and results report (fixed format); daily watch of the dedicated mailbox.
Privacy: student names and grades stay in the local files, never copied into a published page.
Role: pure watch, produces no content: collects, sorts, then hands off (diploma, faculty, presentation, clinical case).
Rules: access through an already logged-in browser, never entering credentials or signing up without validation; six items at most on the dashboard; a log so an item already seen is never flagged again.
Difference from the review: the review is written; this skill prepares what will be said orally.
Automatic trigger: the weekly routine spots defenses at D-14 and produces the sheet at D-7.
| Role | Sheet |
|---|---|
| Chair | full sheet; welcome remarks and closing remarks; synthesis questions |
| Examiner | short sheet, two or three remarks |
| Supervisor | background and supervision, lighter criticism |
Golden rule: any item not found in a source is marked [TO BE CONFIRMED]; three reliable lines are better than ten plausible ones.
Two moments: the review (Word tracked changes and comments attributed to your name, never to “Claude”); lifecycle follow-up (co-author feedback, arbitration, versions up to submission).
Naming: each deliverable starts with the manuscript’s short name. One folder per manuscript: the untouched original, dated reviews, co-author feedback.
Scope: by default the scientific part in English, not the introductory chapters of a thesis.
Three levels: form and English (tracked changes); methodology (reasoned comment); reasoning (consistency of title, abstract, discussion), often the most useful.
Three flaws to check systematically: an outcome whose definition changes from one section to another; reference numbering that no longer matches the list; units that differ between text and tables (never decide alone).
Sources: a central data sheet, identity, and PubMed for recent publications only.
Principle: never invent; missing data is marked [MISSING INFORMATION]; when sources contradict each other, present both and have the user decide. A decision already made is not asked again: write it into the skill.
Commands: generate, in English, update (with changes flagged), full version with identity and history.
Difference from the CV: cumulative and detailed, enriched with each reported event, without waiting for a regeneration.
Strict attribution rule: collective work (for example a unit’s activity report) remains attributed to the collective, never merged with a personal achievement.
Absolute rule: the final document is always the previous year’s, duplicated then completed; the official template is never reformatted or reworded.
Log: one line per detected event (date, category, detail, source, status “to validate”, “kept”, “discarded”). Nothing enters the document without explicit validation, via checkboxes.
Strict exclusion: any consulting activity for industry, even if the email goes through an academic mailbox.
Deadline: set a D-30 alert before the submission date.
Updated 27 Sept 2026
Each sub-agent on this site maps to skills actually in use, with their key rule.
| Agent | Sub-agent | Skills | Key rule |
|---|---|---|---|
| Organiser | Dashboard | reacteurreacteur-ecrire | Single hub: roadmap 7-9 days, work in progress, documents, mail decisions, horizons. |
gestion-mailcapture-agenda | Three-column triage (reply / do-calendar / file); + aliases; nothing is ever written into the mailbox. | ||
| Calendar | agenda | Propose, then write only after « accept »; tentative events prefixed « ? », free, grey, no reminder. | |
| Archivist | classementfichier | Profile first, then file; never overwrite, never delete (archive instead). | |
| Administrative | identitecvhistoriquebilan-activite | Forms and identity, CV from a data sheet + PubMed, activity history, annual statutory reports. | |
| Researcher | Bibliography | biblioveilleresearch | PubMed search → impact-factor whitelist → PDFs → Word + slide deck; permanent watch; research layer turns a question into an evidence table and gaps in the slide bank. |
| Manuscript | article | Native Word tracked changes attributed to the author; three review levels; co-author feedback arbitrated point by point until submission. | |
| Data | megabase-cardiomegabase-cmhmegabase-pvmmegabase-requete | One orchestrator, one sub-skill per cohort, one query skill (« how many patients with… ») behind a live artifact. | |
| Congress | presentation-congrespresentationesc365-toposlidepdf-figure-vers-diapocongres-organisation | Seven-tab workshop, indexed slide bank (never filtered by the AI), congress-platform slides, single-slide template, PDF figure → slide, door-to-door travel plan. | |
| Teacher | Faculty | fac | Lecture → MCQ → docimology → exam → deliberation chain, with D-30 and D-15 rules. |
| Diploma | diu-echo | Multi-site mailing list, calendar options, results minutes, a dedicated mailbox watched weekly. | |
| Supervision | soutenance-thesearticle | Speaking notes for a defense (chair or member) in one file; the written review is the manuscript skill. | |
| Visual teaching | cas-cliniqueechoechopacirm-cardiaque | Four-slide anonymised case blocks; DICOM → four looping clips per black slide, patient banner cropped. | |
| Training | formation | Watch only (no purchase, no enrolment), hands over to the producing skills. | |
| Clinician | Staff meetings | staff | Starts from the index of every staff deck since 2012; never repeats a topic unknowingly. |
| Rota | planning | Read-only for routines; edits only in a supervised session with triple test before publishing. | |
| Common | Orchestrator | academique | Level 1: qualifies (domain A–E), routes, never executes. Excludes consulting and accounting. |
The morning brief, the anticipation cockpit and the mail decision board were merged into a single Reactor: tabs for daily roadmap, work in progress, documents, mail decisions, weekly / monthly / semester horizons, presentations (D-30 rule), teaching, training watch, literature watch. Every routine writes there; the person only decides.
Forwarding a message to your own address with a « + » tag turns it into an instruction the routines can act on: +agenda proposes a calendar event, +slide builds one slide from a paper, +claude runs a written instruction. Only messages you send yourself trigger anything; incoming mail never does.
Every file is profiled on six axes (family, profile, origin, version, sensitivity, location) before it is moved. Doubt is a first-class outcome: the file stays where it is and a question is posted for the person. Ninety-six profiles, learned from each correction.
Routines, mail chain, disk, index and surfaces each have a light (ok / warn / crit) updated by the routines themselves at the start of every run. The sentinel reads the lights, never the platform's run timers, and alerts only when an action is expected.
A weekly retrospective reads the week's journals and drafts lessons per skill and per project. Nothing is applied without an explicit « accept »; the lesson registry shows what is active, what was proposed and what was declined.
Each scheduled routine reads two files first (common rules, then its own plan) which take precedence over its prompt. Changing behaviour means editing a file, versioned and never overwritten, not recreating a task.