Journey
- 834 installs
- 1 repo stars
- Updated April 1, 2026
- journeykits/skill
journey is a Claude Code skill that searches the Journey registry and installs pre-built agent workflow kits for developers who need reusable automation workflows without hand-authoring every step.
About
journey is a Claude Code skill for discovering and installing reusable agent workflows called kits from the Journey registry at journeykits.ai. The skill queries the live Journey API (GET https://www.journeykits.ai/api/kits/journey) for up-to-date kit metadata, then guides installation when a developer mentions Journey, asks for a kit, or needs a workflow template. Each kit is a documented multi-step agent workflow packaged for coding agents. Developers reach for journey when bootstrapping agent automation, onboarding teams to shared workflow patterns, or avoiding one-off skill authoring for common tasks.
- Searches the Journey registry using natural language queries
- Supports 9 distinct agent targets including claude-code, cursor, codex, cline, windsurf, jules, aider, openclaw and gene
- Returns structured install instructions tailored to your chosen agent platform
- Fetches real-time kit details and full workflow documentation on demand
- Works completely offline using the compact summary when the network is unavailable
Journey by the numbers
- 834 all-time installs (skills.sh)
- +2 installs in the week ending Aug 2, 2026 (Skillselion tracking)
- Ranked #1,294 of 16,546 AI & Agent Building skills by installs in the Skillselion catalog
- Security screen: MEDIUM risk (skills.sh audit)
- Data as of Aug 2, 2026 (Skillselion catalog sync)
npx skills add https://github.com/journeykits/skill --skill journeyAdd your badge
Show developers this skill is listed on Skillselion. Paste this into your README.
| Installs | 834 |
|---|---|
| repo stars | ★ 1 |
| Security audit | 1 / 3 scanners passed |
| Last updated | April 1, 2026 |
| Repository | journeykits/skill ↗ |
How do you find and install pre-built agent workflows?
Instantly discover and install pre-built agent workflows from the Journey registry when they mention needing a kit or workflow.
Who is it for?
Developers standardizing Claude Code or Cursor agents with shared, registry-hosted workflow kits.
Skip if: Developers building fully custom agent logic who do not want third-party workflow templates from an external registry.
When should I use this skill?
The user mentions Journey, journeykits.ai, wants to find a kit, or asks to install a pre-built agent workflow.
What you get
Installed Journey kit workflows, registry metadata, and configured agent skill files.
- Installed Journey kit workflow
- Registry kit metadata
Files
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
selfContainedisfalse, read the kit's Setup and Constraints before proceeding. - Install dependency kits first if
dependencyKitsis 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 skills
Setup Matt Pocock SkillsScaffold the per-repo configuration that Matt Pocock’s engineering agent skills rely on so they understand the issue tracker, triage labels, and domain documentation la495k196k
Lark AppsConnect Claude, Cursor or custom agents directly to Lark (Feishu) for messaging, document automation, approval workflows and enterprise data access.402k
CavemanSlash token usage by roughly 75% while keeping every technical detail intact when working with Claude Code, Cursor or similar agents.391k94.7k
Lark Skill MakerQuickly turn any Lark/Feishu OpenAPI call or multi-step workflow into a reusable agent skill with its own SKILL.md.386k16k
Running Claude Code Via Litellm CopilotRun Claude Code at a fraction of the cost by routing requests through LiteLLM to the GitHub Copilot Chat API.270k72
Codex PetGenerate a complete Codex Pet spritesheet and metadata from one reference image without needing an OpenAI key or Codex Pro.246k10How it compares
Pick journey when you want registry-hosted, installable workflow kits; write custom skills when workflows must be fully bespoke and not depend on an external catalog.
FAQ
What is a Journey kit?
A Journey kit is a documented, reusable agent workflow published in the Journey registry at journeykits.ai. The journey skill searches that registry and installs kits as agent-ready workflow packages for coding assistants.
How does journey stay up to date?
The journey skill prefers fetching live metadata from GET https://www.journeykits.ai/api/kits/journey before complex installs. The bundled SKILL.md is an offline-friendly summary when network access is limited.
Is Journey safe to install?
skills.sh reports 1 of 3 security scanners passed. Review the Security Audits panel on this page before installing in production.