Help us improve
Share bugs, ideas, or general feedback.
From carrel
This skill should be used when a researcher wants to share their Carrel vault with someone else — an RA, co-author, lab member, or advisor. Triggers on 'share with', 'onboard a collaborator', 'generate a handbook', 'lab handbook', 'help my RA get up to speed', or when the /carrel-share command is invoked. Distinct from /carrel-setup, which sets up a NEW vault for a NEW researcher; this skill assumes an existing vault with accumulated context.
npx claudepluginhub linxule/carrel --plugin carrelHow this skill is triggered — by the user, by Claude, or both
Slash command
/carrel:collaborator-onboardingThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Synthesizes the accumulated context of an existing Carrel vault into a markdown handbook that a new collaborator can read to come up to speed on **how this researcher works in this vault**. Vault-specific, not Carrel-general.
Guides technical evaluation of code review feedback: read fully, restate for understanding, verify against codebase, respond with reasoning or pushback before implementing.
Share bugs, ideas, or general feedback.
Synthesizes the accumulated context of an existing Carrel vault into a markdown handbook that a new collaborator can read to come up to speed on how this researcher works in this vault. Vault-specific, not Carrel-general.
/carrel-share command is invoked/carrel-setup. Setup is for someone creating their own new Carrel environment from scratch. This skill assumes the vault already exists and has been used./carrel-mirror. Mirror writes a self-portrait for the researcher's own awareness. This skill writes for someone else to read — different audience, different framing./team-onboarding. That command generates generic Claude Code usage tips from your local session history. This skill produces a vault-specific handbook from vault content.Read these in order. Skip any that don't exist or are empty — degrade gracefully.
| Source | Purpose |
|---|---|
.carrel/environment.json | Researcher profile, sensitivity, configured tools, automation status, wiki status, collaborators field, team_context |
CLAUDE.md (vault root) | Narrative profile, "how to work with [name]" guidance |
_meta/friction_log.md | Recurring pain points the collaborator should know about |
_meta/capability-log.md | Custom trackers, plugins, conventions added over time |
_meta/reflections/ | Recent ~5 entries — current preoccupations |
_meta/mirror/ | Most recent self-portrait — synthesized trajectory |
notes/threads/ | Active analytical threads (status: active only) |
wiki/SCHEMA.md | Wiki conventions and tag taxonomy (only if wiki active) |
wiki/index.md | List of wiki pages (only if wiki active) |
| Vault folder structure | Top-level folders that exist in this vault |
_meta/cheat_sheet.md | Existing reference card — point the collaborator at it |
The handbook must answer four questions for the collaborator:
notes/threads/, latest reflection)Use references/handbook-template.md for the markdown structure. Each section has a "skip if" rule for graceful degradation.
The skill has two operating modes — choose based on how the researcher framed the request.
A short brief exchange up front, then conversational refinement at the end. Use this when the researcher says "share with my RA" or "onboard Jane" without further detail.
Brief (one short exchange — don't make it a form):
Refinement (after synthesis): show the draft, ask one focused question: "Anything missing, or anything that shouldn't go to [name]?" Apply edits, save the final.
Canonical copy (optional): offer "Want me to also save this as _meta/lab-handbook.md — your canonical 'latest version' you can update over time?" If yes, copy the file. If no, the dated handbook stands alone.
Skip the brief, use defaults (new lab member, general access), save the dated handbook, skip the canonical copy. Use this when the researcher says "just generate one", "quick handbook", "draft something I can edit", or otherwise signals they want a starting point rather than a conversation.
Quick mode is a behavioral shortcut. The CLI does not have a separate flag for it — it surfaces as --mode quick on the generate call.
Once mode + collaborator + sensitivity are resolved, hand off to the CLI for synthesis and the file write:
carrel vault share generate \
--mode interactive|quick \
--for <collaborator-slug> \
--sensitivity low|medium|high \
[--vault PATH]
The CLI owns: source-material reads, handbook synthesis emission, sensitivity-rule application (what gets redacted at each level), idempotent dated-filename writes under _meta/handbook/, and the optional canonical-copy write. This skill owns: mode selection, the brief (interactive), the refinement loop (interactive), and the sensitivity conversation when redaction is uncertain.
Use --explain to preview what the CLI would write — including which sources it would pull from and which sections sensitivity rules would redact — without committing.
Files land at _meta/handbook/[YYYY-MM-DD]-for-[collaborator-slug].md.
[YYYY-MM-DD] = today's date[collaborator-slug] = lowercase, hyphenated. Examples: jane, new-ra, co-author-cornell. If the collaborator isn't named, use lab-member.Optionally also save as _meta/lab-handbook.md — the canonical "latest" version. Researcher chooses (interactive mode only).
The --sensitivity flag controls how the CLI applies redaction; this skill resolves it with the researcher before invoking.
Default: read the researcher's sensitivity from .carrel/environment.json and pass it through. Override only when the collaborator's access is narrower than the researcher's vault-wide setting (e.g., a HIGH-sensitivity vault but the new RA only needs the public-facing project — pass --sensitivity medium with the researcher's confirmation).
Narration during synthesis (HIGH sensitivity):
Narration during synthesis (MEDIUM sensitivity):
private- or irb-)Narration during synthesis (LOW sensitivity):
If the collaborator's role is unclear, default to the more restrictive interpretation and tell the researcher you've done so: "I treated their access as HIGH-sensitivity since you didn't specify their role — let me know if I should loosen it."
papers/" is not useful. "Mostly institutional theory, with a recent shift toward field-level change" is.The handbook is a snapshot. Refresh whenever:
lab-handbook.md)There is no automatic refresh. The researcher decides.
/carrel-share (entry point for this skill)vault-ops (vault structure conventions), automation (if vault has scheduled automation, surface that to the collaborator), knowledge-wiki (if wiki active, explain its conventions)/carrel-mirror (self-portrait — adjacent but different audience), /carrel-setup (for collaborators who need their own vault)_meta/handbook/, _meta/lab-handbook.md (optional canonical copy)