linxule

Examine philosophical assumptions and check for methodological coherence. Use when users question their philosophical stance, their language contradicts their declared epistemology, they are moving between stages and want to verify coherence, or something feels 'off' about their analytical approach. Checks language coherence, method-epistemology alignment, and AI relationship consistency.

Shared infrastructure for Interpretive Orchestration. Provides state management, configuration I/O, batched file operations, and enforcement utilities for qualitative research projects. Use when working with .interpretive-orchestration/config.json, checking stage completion, updating progress, or validating project setup.

Dialogical coding for qualitative research. Acts as thinking partner in Stage 1 (never suggests codes, only asks questions) and reflexive coding partner in Stage 2 (4-stage visible reasoning). Use when coding interview transcripts, field notes, or other qualitative data.

Initialize a new qualitative research project with Socratic onboarding. Guides researchers through philosophical foundation establishment via interactive dialogue. Use when starting a new project, setting up epistemic stance, or configuring methodological preferences.

Deep reasoning and paradox navigation via MCP tools. Integrates Sequential Thinking for systematic analysis and Lotus Wisdom for navigating contradictions. Use when planning complex analysis, working through theoretical tensions, or making methodological decisions.

Progress dashboard and navigation for Interpretive Orchestration. Shows current stage, progress indicators, next steps, and atelier status. Use when checking progress, navigating between stages, or planning next steps.

This skill should be used when users need to convert PDFs (especially with tables or figures), mentions 'convert', 'PDF', 'document processing', has complex academic papers to import, or asks about document conversion options.

This skill should be used when users have audio interview recordings to transcribe, need to convert PDF documents, mentions 'import data', 'transcribe', 'convert', or is starting data preparation for Stage 1 or Stage 2.

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.

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'.

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.

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.

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'.

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.

This skill should be used when a researcher wants to think through ideas, discuss a paper, get feedback on arguments, explore connections, brainstorm, or needs intellectual engagement. Also covers research self-portrait synthesis — surfacing patterns across a researcher's own recent work ('show me my research patterns', 'what have I been working on', 'give me a mirror', '/carrel-mirror'). Triggers on 'help me think', 'what do you think', 'push back', 'what am I missing', 'I'm stuck', 'explore connections', 'mirror', 'self-portrait'.

This skill should be used when evaluating an external skill, MCP, or tool for absorption into Carrel ('should we absorb this', 'evaluate for absorption', 'does this overlap'), when Claude has just created a custom artifact for a researcher and needs to log it and update their environment dashboard, when promoting a recurring custom solution to a template ('promote this to a template', 'make this official'), when walking a researcher through a plugin version upgrade ('check for updates', 'what changed', '/carrel-migrate'), or during quarterly upstream review ('review upstream sources', 'what capabilities have we added', 'check registry').

Ask Kimi a read-only free-form question about the current repository. Use for prose explanations, flow tracing, module comparisons, or conceptual reasoning where Codex should delegate the answer to local kimi-code rather than perform implementation.

Run a read-only adversarial Kimi challenge review that questions assumptions, design choices, and tradeoffs. Use when the user wants pushback on whether the approach is right, not a defect-only review.

Run an independent read-only Kimi review over the current working tree or a branch diff. Use when the user wants a second reviewer for defects, regressions, or implementation risks, not edits.

Verify local Kimi companion readiness and manage the kimi-code PreToolUse hook plus optional review gate state. Use when explicitly requested to install, check, enable, disable, or uninstall the integration. Codex and Claude Code share one ~/.kimi-code/config.toml but each own a host-scoped block, so $kimi-setup here does not disturb Claude Code's /kimi:setup (and vice-versa).

Run a read-only parallel Kimi review fan-out across many independent targets. Use only for explicit broad fan-out requests where one subagent per target is the point.

Run a write-capable Kimi swarm that edits many disjoint targets in a throwaway worktree and returns a reviewable patch. Use only for explicit parallel edit fan-out requests; the plugin never applies or commits the patch.

Cancel an active plugin-managed Kimi job for the current repository. Use only when the user explicitly asks to cancel a Kimi run.

Run Kimi's autonomous goal mode for an explicitly requested hands-off multi-turn objective. This is write-capable and budget-bounded; use only when the user explicitly asks Kimi to pursue an objective autonomously.

Safely consolidate drifted/duplicate project folders in the memex vault — cwd-fragment folders (e.g. `Apps-arena`, `GitHub-loom`), duplicate/split projects (one project's content scattered across two folders), and name-mismatch folders. Trigger on "consolidate project folders", "merge duplicate projects", "fix project detection drift", "deduplicate Apps-* folders", "clean up fragment folders", or after `memex check --folders` reports drift. Preserves observations + embeddings via `memex obs reassign` (never naive `git mv` + rebuild, which cascade-deletes obs).

Tend the knowledge garden — diagnose vault health, condense project memos into `_project.md` overviews, create/merge cross-project topics, fix broken links, archive superseded notes, extend trails. Trigger on "tend the garden", "condense", "update project overview", "check vault health", "where are we with X?", "what does this project know?", "extend a trail", or when a `_project.md` is empty/stale, a project has 5+ unprocessed memos, or a concept appears in 2+ projects. For autonomous tending with judgment, prefer curator-practice.

Operating philosophy for autonomous memex curator tending — orientation protocol, signal triage, bounded work units, initiative thresholds, logging conventions. Trigger on cron-launched runs with no user prompt, "use your judgment", "tend without instructions", "do a pass on the vault", "I'll be away — do what needs doing", or "what should I work on next?" in vault context. For procedural how-to on specific operations (condense, link, archive, crystallize), defer to garden-tending. Do NOT trigger when the user gives an explicit task ("update X project overview", "fix broken links in topics/Y", "condense Z's memos") — those go straight to garden-tending without the judgment layer.

How to write effective session memos — format, frontmatter schema, observation extraction, topic-signal append. Trigger on `/memex:save`, "save this for later", "remember this", "save what we discussed", "document this session", "create a memo", or when the `[memex]` activity nudge appears in context. Do NOT trigger for general note-taking, scratchpads, technical specs, design docs, READMEs, or code comments — memos are session-reflection artifacts that capture what happened (decisions, tensions, surprises, open threads), not project documentation.

Retrieve session memory across 4 modes — TEMPORAL (date browsing), KEYWORD (FTS lookup), DEEP (cross-session synthesis), LOAD (specific file). Trigger on "what did I do yesterday/last week", "why did we...", "remind me...", "find the memo about...", "last time we...", "patterns across projects", "load the X topic". Do NOT trigger for future-oriented questions ("how should we..."), general knowledge, current-session-answerable questions, or vault maintenance (use garden-tending).

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.

Navigate Xule Lin's public research site, machine-readable indexes, markdown pages, and attribution boundaries.