Marketplace for trusted AI agent skills

Skill Detail

Install OrchestKit skills, agents, and hooks for Claude Code

Install OrchestKit when a Claude Code operator wants a maintained workflow pack of skills, specialist agents, hooks, setup automation, verification, PR review, commits, and persistent project memory.

Templates & WorkflowsClaude Code
Templates & Workflows Claude Code Security Reviewed
⭐ 278 GitHub stars ⬇ 7/wk npm
COPY SKILL INSTRUCTIONS (OPTIONAL)
npx skills add agentskillexchange/skills --skill install-orchestkit-skills-agents-and-hooks-for-claude-code Copy
Uses the third-party skills CLI, not an ASE-owned installer. Check your agent’s compatibility. This copies instructions; complete the upstream tool setup below separately.
View source Documentation
At a glance
Tools required
Claude Code 2.1.251+ for full plugin support; optional Cursor, Codex, pi, Devin, or Antigravity support paths; recommended MCP servers such as Context7
Install & setup
In Claude Code, run /plugin marketplace add yonatangross/orchestkit, then /plugin install ork, then /ork:setup. For skill-only hosts, use the upstream npx skills add yonatangross/orchestkit instructions.
Author
Yonatan Gross / OrchestKit contributors
Publisher
Open Source
Last updated
Sep 19, 2026
Quick brief

Use OrchestKit when an operator wants a maintained workflow pack for Claude Code sessions instead of repeatedly explaining project conventions. The workflow is to install the plugin, run the setup wizard, let it recommend skills and MCP configuration, then invoke focused commands such as setup, implement, verify, review-pr, commit, expect, explore, and remember.

How it works

What this skill actually does

When to use it

Invoke this skill when a repository needs repeatable Claude Code workflows for implementation, review, browser testing, commits, stack-specific patterns, and project memory. It is strongest when the operator wants the Claude Code plugin experience with bundled skills, specialist agents, and hooks, while still using compatible skill subsets in Cursor, Codex, pi, Devin, or Antigravity where upstream supports them.

Scope boundary

This is not a generic collection of prompts. Keep the workflow bounded to installing and operating OrchestKit’s documented skills, agents, hooks, commands, and recommended MCP configuration. Do not treat it as a substitute for choosing project requirements, reviewing generated changes, or blindly installing every bundled skill into every runtime.

Operator checklist

  • Add the OrchestKit marketplace and install the ork plugin in Claude Code.
  • Run /ork:setup so the wizard scans the repository and recommends skills and MCP servers.
  • Use focused commands such as /ork:implement, /ork:verify, /ork:review-pr, /ork:commit, and /ork:remember.
  • Add required MCP servers such as Context7 where recommended by upstream documentation.
  • Review hooks, installed skills, and generated changes before relying on them in production repositories.