init
Frictionless setup. Detects missing daemon, installs it, configures local memory, and verifies the full plugin → MCP → daemon round-trip. Run after `/plugin install origin@7xuanlu`, or any time the user says "set up origin", "is origin working", "fix origin".
What this skill does
# /init Self-healing setup. Goal: 30 seconds, two user actions max (install plugin, type /init). Default backend is local memory — no local model, no API key, no prompts. Local model and Anthropic key are opt-in upgrades documented in `/help`. ## Steps Run in order. Stop and report at the first failure that needs human attention. Otherwise, push through automatically. ### 1. Daemon health probe ``` Bash: curl -fsS -m 1 http://127.0.0.1:7878/api/health ``` - 200 OK → skip to step 4. - Anything else → step 2. ### 2. Bootstrap (auto-install if missing) Detect whether the `origin` CLI is on PATH: ``` Bash: command -v origin >/dev/null 2>&1 && echo present || echo absent ``` If `absent`, run the installer (no human prompts): ``` Bash: curl -fsSL https://raw.githubusercontent.com/7xuanlu/origin/v0.6.1/install.sh | bash ``` Then add it to PATH for the current session and configure local memory non-interactively: ``` Bash: export PATH="$HOME/.origin/bin:$PATH" && origin setup --basic && origin install ``` If `present` (CLI exists, daemon down), just install + start: ``` Bash: origin setup --basic 2>/dev/null || true; origin install ``` `origin setup --basic` is idempotent — safe to re-run. `origin install` writes the launchd plist and starts the daemon. ### 3. Re-probe daemon health ``` Bash: for i in 1 2 3 4 5; do curl -fsS -m 1 http://127.0.0.1:7878/api/health && break; sleep 1; done ``` If the daemon still isn't reachable after ~5s, surface the error and stop. Likely cause: launchd plist load failure, port 7878 occupied by another process, or macOS Tahoe Metal init issue (daemon degrades but still binds — check `lsof -ti :7878`). ### 4. Doctor (verify backend) Call the `origin` MCP server's `doctor` tool: ``` doctor() ``` Expected: local memory configured (no model, no key). Capture the mode string for the final report. ### 5. MCP round-trip ``` context() ``` Pass → continue. Fail → MCP not wired. Tell user: "origin-mcp didn't respond. Restart Claude Code so the plugin's `.mcp.json` re-spawns the server." ### 6. Ready report Print: ``` Origin ready. Daemon: up on 127.0.0.1:7878 Mode: <mode from doctor()> MCP: connected Data: ~/.origin/ (pages, sessions, db symlink) Try: /brief, /capture <thing>, /recall <query>, /help ``` If this was the first /init invocation in the session, dispatch `/help` once so the user sees the verb cheat-sheet without asking. ## Optional upgrades (don't auto-run) Mention these in the ready report only if the user explicitly asks for "richer features" or asks about model-backed extraction: - `origin model install` — local Qwen for distill cycles. - `origin key set anthropic` — Anthropic for stronger synthesis. Default flow ignores both. Storage, search, recall, and MCP memory all work in local memory mode. ## When to use - Right after `/plugin install origin@7xuanlu`. - Hook printed "daemon down — run /origin:init". - User says "set up origin", "is it working", "reinstall origin". ## When NOT to use - Daemon already verified this session → `/brief` instead. - Editing one config field → `origin doctor` or settings file directly.
Related in AI Agents
skill-development
IncludedComprehensive meta-skill for creating, managing, validating, auditing, and distributing Claude Code skills and slash commands (unified in v2.1.3+). Provides skill templates, creation workflows, validation patterns, audit checklists, naming conventions, YAML frontmatter guidance, progressive disclosure examples, and best practices lookup. Use when creating new skills, validating existing skills, auditing skill quality, understanding skill architecture, needing skill templates, learning about YAML frontmatter requirements, progressive disclosure patterns, tool restrictions (allowed-tools), skill composition, skill naming conventions, troubleshooting skill activation issues, creating custom slash commands, configuring command frontmatter, using command arguments ($ARGUMENTS, $1, $2), bash execution in commands, file references in commands, command namespacing, plugin commands, MCP slash commands, Skill tool configuration, or deciding between skills vs slash commands. Delegates to docs-management skill for official documentation.
reprompter
IncludedTransform messy prompts into well-structured, effective prompts — single or multi-agent. Use when: "reprompt", "reprompt this", "clean up this prompt", "structure my prompt", rough text needing XML tags and best practices, "reprompter teams", "repromptception", "run with quality", "smart run", "smart agents", multi-agent tasks, audits, parallel work, anything going to agent teams. Don't use when: simple Q&A, pure chat, immediate execution-only tasks. See "Don't Use When" section for details. Outputs: Structured XML/Markdown prompt, quality score (before/after), optional team brief + per-agent sub-prompts, agent team output files. Success criteria: Single mode quality score ≥ 7/10; Repromptception per-agent prompt quality score 8+/10; all required sections present, actionable and specific.
adaptive-compaction
IncludedAdaptive add-on policy and recovery layer that decides WHEN to compact, prune, snapshot, or fork -- replacing fixed-percent auto-compaction across Claude Code, Codex, and MCP-capable hosts. Trigger on auto-compact timing or damage: "when should I compact", "is it safe to compact now or start a fresh session", "auto-compact fires too early/mid-task", "switching to an unrelated task but the window still has space", "context rot", "answers get worse the longer the session runs", "the agent forgot the plan or my decisions after it summarized", "add a layer on top that manages context without changing the agent", raising autoCompactWindow to give the policy room, or installing/tuning a cross-tool compaction policy or PreCompact hook -- even when "compaction" is never said but the problem is context-window pressure or post-summarization memory loss. Do NOT use to summarize a conversation, build RAG, write a summarization prompt (decides WHEN not HOW), or answer max-context-length trivia.
agent-skill-creator
IncludedCreate cross-platform agent skills from workflow descriptions. Activates when users ask to create an agent, automate a repetitive workflow, create a custom skill, or need advanced agent creation. Triggers on phrases like create agent for, automate workflow, create skill for, every day I have to, daily I need to, turn process into agent, need to automate, create a cross-platform skill, validate this skill, export this skill, migrate this skill. Supports single skills, multi-agent suites, transcript processing, template-based creation, interactive configuration, cross-platform export, and spec validation.
llm-wiki
IncludedUse when building or maintaining a persistent personal knowledge base (second brain) in Obsidian where an LLM incrementally ingests sources, updates entity/concept pages, maintains cross-references, and keeps a synthesis current. Triggers include "second brain", "Obsidian wiki", "personal knowledge management", "ingest this paper/article/book", "build a research wiki", "compound knowledge", "Memex", or whenever the user wants knowledge to accumulate across sessions instead of being re-derived by RAG on every query.
skill-master
IncludedAgent Skills authoring, evaluation, and optimization. Create, edit, validate, benchmark, and improve skills following the agentskills.io specification. Use when designing SKILL.md files, structuring skill folders (references, scripts, assets), ingesting external documentation into skills, running trigger evals, benchmarking skill quality, optimizing descriptions, or performing blind A/B comparisons. Keywords: agentskills.io, SKILL.md, skill authoring, eval, benchmark, trigger optimization.