Run any Skill in Manus with one click

env-doctor

Stars1

Forks0

UpdatedApril 20, 2026 at 16:39

Guided recovery for environment.json drift. Use when the researcher runs /carrel-fix, mentions environment drift, broken setup state, or wants help repairing conflicting settings.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

linxule

linxule/carrel

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Network and Computer Systems AdministratorsComputer and Mathematical Occupations·SOC 15-1244

File Explorer

2 files

SKILL.md

readonly

name	env-doctor
description	Guided recovery for environment.json drift. Use when the researcher runs /carrel-fix, mentions environment drift, broken setup state, or wants help repairing conflicting settings.

env-doctor

Diagnoses .carrel/environment.json, offers safe repairs with approval, and walks the researcher through ambiguous drift without hiding the tradeoffs.

Mode Detection

Always work in order:

Layer 1: Validate Run carrel env validate --vault . --format json. If status is valid, say so plainly and stop.
Layer 2: Safe fix preview Run carrel env fix --safe --dry-run --vault . --format json. Group the safe fixes into a short plain-language summary and ask whether to apply them. Only run carrel env fix --safe --vault . after explicit approval.
Layer 3: Interactive doctoring If validation or the dry-run reports deferred items, shift into guided recovery. Explain the ambiguity in ordinary language, present 2-3 options, and ask the researcher to choose.

Interaction Rules

Use plain language. Avoid "ValidationError", "enum", or other implementation terms unless the researcher asks.
Group related fixes. Do not dump every field unless the researcher wants the raw detail.
If the ambiguity is about sensitivity or cloud consent, explain the practical consequence: "This setting decides whether cloud tools are okay by default."
If CLAUDE.md and environment.json disagree, say explicitly that environment.json is the structured source of truth, but ask which one reflects the researcher's current intent before changing either.
Re-run carrel env validate --vault . --format json after any applied fix to confirm the vault is clean.

Questions for Ambiguous Drift

Use short, concrete questions. Examples:

"Your sensitivity setting uses an older label. Should I treat this as medium sensitivity, which keeps cloud tools off by default?"
"CLAUDE.md says cloud tools are okay, but environment.json says no. Which one is current?"
"This tool is marked configured in your profile, but it is not installed on this machine. Should I mark it unavailable here?"

Logging

After every applied change, append an entry to _meta/capability-log.md that includes:

Timestamp
What changed
Why it changed
How to revert it

Use a compact format, for example:

- 2026-04-20 14:03 UTC — Updated `.carrel/environment.json` sensitivity from `cautious` to `medium`; revert by restoring `.carrel/environment.json.bak`.

References

references/fix-catalog.md for the safe-fix rules supported by Layer 2
/carrel-fix for the slash-command wrapper

More from this repository

same repository

carrel

linxule/carrel

Portable AI-assisted research vault operations for setup, document ingestion, transcription, web capture, environment repair, trust and sensitivity routing, reflection, collaborator handoff, and feedback export. This is the standalone engine for hosts without the Carrel Claude Code plugin, such as Cowork, Codex, Kimi Code, Gemini CLI, OpenCode, and Claude.ai skill uploads. Do not use when the Carrel Claude Code plugin or the installed carrel CLI is available; that plugin drives the typed CLI as its runtime, not this pack.

2026-07-101

automation

linxule/carrel

This skill should be used when a researcher wants to configure, understand, or adjust unattended vault maintenance. Triggers on 'schedule', 'automate', 'overnight', 'background processing', 'morning brief', 'unattended', 'what did Carrel do', 'review automation settings', 'trust level', or '/carrel-automate'.

2026-07-101

transcribe

linxule/carrel

This skill should be used when a researcher has audio or video files to transcribe, or a YouTube URL to get a transcript from. Triggers on 'transcribe', 'convert this recording', 'audio to text', 'get the transcript', or when an audio/video file or YouTube URL is provided.

2026-07-101

collaborator-onboarding

linxule/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.

2026-07-101

environment-setup

linxule/carrel

This skill should be used when a researcher wants to set up their AI research environment, mentions 'setup', 'get started', 'configure', 'onboard', or when opening a project folder with no .carrel/ directory. Also triggers on 'what tools do I have', 'check my setup', 'add a new tool'.

2026-07-101

knowledge-wiki

linxule/carrel

This skill should be used when a researcher wants to build, query, or maintain a synthesized knowledge base across their sources. Triggers on 'field map', 'knowledge map', 'what do my sources say about', 'synthesize across papers', 'literature review', 'systematic review', 'wiki', 'track contradictions', 'knowledge base', 'I keep losing track', 'lint wiki', 'wiki health', or when the agent observes repeated cross-source questions in a vault with 15+ papers.

2026-07-101

name	env-doctor
description	Guided recovery for environment.json drift. Use when the researcher runs /carrel-fix, mentions environment drift, broken setup state, or wants help repairing conflicting settings.

env-doctor

Diagnoses .carrel/environment.json, offers safe repairs with approval, and walks the researcher through ambiguous drift without hiding the tradeoffs.

Mode Detection

Always work in order:

Layer 1: Validate Run carrel env validate --vault . --format json. If status is valid, say so plainly and stop.
Layer 2: Safe fix preview Run carrel env fix --safe --dry-run --vault . --format json. Group the safe fixes into a short plain-language summary and ask whether to apply them. Only run carrel env fix --safe --vault . after explicit approval.
Layer 3: Interactive doctoring If validation or the dry-run reports deferred items, shift into guided recovery. Explain the ambiguity in ordinary language, present 2-3 options, and ask the researcher to choose.

Interaction Rules

Use plain language. Avoid "ValidationError", "enum", or other implementation terms unless the researcher asks.
Group related fixes. Do not dump every field unless the researcher wants the raw detail.
If the ambiguity is about sensitivity or cloud consent, explain the practical consequence: "This setting decides whether cloud tools are okay by default."
If CLAUDE.md and environment.json disagree, say explicitly that environment.json is the structured source of truth, but ask which one reflects the researcher's current intent before changing either.
Re-run carrel env validate --vault . --format json after any applied fix to confirm the vault is clean.

Questions for Ambiguous Drift

Use short, concrete questions. Examples:

"Your sensitivity setting uses an older label. Should I treat this as medium sensitivity, which keeps cloud tools off by default?"
"CLAUDE.md says cloud tools are okay, but environment.json says no. Which one is current?"
"This tool is marked configured in your profile, but it is not installed on this machine. Should I mark it unavailable here?"

Logging

After every applied change, append an entry to _meta/capability-log.md that includes:

Timestamp
What changed
Why it changed
How to revert it

Use a compact format, for example:

- 2026-04-20 14:03 UTC — Updated `.carrel/environment.json` sensitivity from `cautious` to `medium`; revert by restoring `.carrel/environment.json.bak`.

References

references/fix-catalog.md for the safe-fix rules supported by Layer 2
/carrel-fix for the slash-command wrapper