journey
Search and install Journey kits — real agent workflows from the Journey registry. Use when the user mentions Journey, wants to find a kit, or needs to install agent workflows.
What this skill does
# Journey — search and install kits **Journey base URL:** `https://www.journeykits.ai` For the full, up-to-date workflow (doc version, extra endpoints, publishing, org flows), fetch: `GET https://www.journeykits.ai/api/kits/journey` This file is a compact offline-friendly summary. When online, prefer refreshing from that endpoint before complex installs. ## What Journey is Journey is a registry of reusable agent workflows called **kits**. Each kit is a documented workflow (usually `kit.md` plus optional `skills/`, `tools/`, `src/`, etc.). You discover kits via search, then install with a **target** so the API returns structured install instructions for your specific agent platform. ## Key API endpoints | Action | Request | |--------|---------| | Search kits | `GET https://www.journeykits.ai/api/kits/search?q=<url-encoded-query>` | | Kit detail | `GET https://www.journeykits.ai/api/kits/<owner>/<slug>` | | Install a kit | `GET https://www.journeykits.ai/api/kits/<owner>/<slug>/install?target=<target>&ref=latest` | | Full guide | `GET https://www.journeykits.ai/api/kits/journey` | **Always include `?target=`** on install. Available targets: `claude-code`, `cursor`, `codex`, `cline`, `windsurf`, `jules`, `aider`, `openclaw`, `generic`. Without `target`, you get a raw bundle only; with it, you get `files`, `preflightChecks`, `nextSteps`, `dependencyKits`, `compatibilityNotes`, `verification`, and `instructions`. **Detect your target** from context: Claude Code → `claude-code`, Cursor → `cursor`, Codex → `codex`, Cline → `cline`, Windsurf → `windsurf`, Jules → `jules`, Aider → `aider`. If unsure, use `generic`. ## Workflow 1. **Search** — `GET .../api/kits/search?q=...` and pick a result (`kitRef` is `owner/slug`). 2. **Inspect** — optional `GET .../api/kits/<owner>/<slug>` before installing. 3. **Install** — `GET .../api/kits/<owner>/<slug>/install?target=<target>&ref=latest`. 4. **Process the install response in order:** - If `selfContained` is `false`, read the kit's Setup and Constraints before proceeding. - Install **dependency kits** first if `dependencyKits` is non-empty. - Run **preflightChecks** (shell commands); stop if a required check fails. - Write every entry in **files** under `suggestedRootDir`, preserving paths. Respect **`writeMode: "append"`** — append to existing config files, do not overwrite. - Follow **nextSteps**, review **compatibilityNotes**, run **verification** if present. - Read **`kit.md`** in the written tree as the primary workflow guide. ## Related reads (when online) - Kit format: `GET https://www.journeykits.ai/api/docs/kit-md` - Capabilities: `GET https://www.journeykits.ai/.well-known/agent-kit.json` - OpenAPI: `GET https://www.journeykits.ai/api/openapi.json` ## Authentication Public search and most kit pages work without a key. Private kits, org flows, and publishing need an agent API key (`Authorization: Bearer <token>`). Do not bootstrap new agent identities as part of casual install flows unless the user explicitly asks.
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.