Skills live in the useorgx/skills public repository. The wizard CLI installs them locally with one command:
In the OrgX app and cloud runtime,
skills/ is a generated, pinned cache of
useorgx/skills, not a second authoring surface. Runtime reads stay local and
network-free; CI uses pnpm skills:check-source to prove the cache still
matches useorgx/skills@<sha>. Use SKILL_PACKS_DIR only for explicit local
overrides.How Skills Work
When you install an OrgX skill pack, the wizard writes aSKILL.md file into your local Claude configuration at .claude/skills/orgx/. Claude picks this up as context for any conversation in that directory, giving it:
- The right sequence of MCP tool calls to call
- Domain-specific quality rules and artifact contracts
- Evidence proof requirements (durable links, not OrgX wrapper pages)
- Trigger patterns so skills activate on natural language cues
.cursor/rules/orgx.md with equivalent rules.
Source of Truth and Runtime Cache
Canonical authoring happens in useorgx/skills. The OrgX app vendors a generated cache atskills/ so cloud agents can load skill
instructions without fetching GitHub during an agent run.
pnpm skills:sync-sourcerefreshes the cache fromuseorgx/skillsand updatesskills/.source.lock.json.pnpm skills:check-sourcefails when any managed skill file drifts from the pinned source ref.- App-only skills remain explicit local overlays in
skills/.source.lock.json. SKILL_PACKS_DIR=/path/to/skillsis still supported for deliberate local development overrides.
Installing Skills
Default Starter Pack
morning-briefing, initiative-kickoff, bulk-create, nightly-recap.
Specific Packs
All Packs
Available Skills
Daily Operations
morning-briefing
Trigger: “morning briefing”, “daily status”, “what’s pending”, “what should I work on first?”Generates a concise daily report with value signals, pending decisions (critical first), blocked tasks grouped by initiative, and agent activity. Calls
orgx_recommend + orgx_search for decisions and blocked tasks.nightly-recap
Trigger: “nightly recap”, “daily summary”, “what happened today”, “end of day report”Summarizes the day’s OrgX activity — completed tasks, decisions made, agent work, and any errors that need attention. Good for async standup notes or end-of-day logs.
Initiative Management
initiative-kickoff
Trigger: “kickoff”, “new initiative”, “start project”, “create initiative for”, “set up [goal]”Transforms a one-line goal into a full OrgX initiative: parses the objective, checks for duplicates, creates the initiative with milestones and workstreams, assigns agent domains, and optionally launches immediately.Not for: updating existing initiatives, simple task creation.
initiative-protocol
Trigger: managing an active OrgX initiative lifecycleHandles creation, decomposition into workstreams and streams (with DAG dependencies), launch, monitoring, and completion. Reference protocol for any skill that needs to touch initiative state.
workstream-protocol
Trigger: workstream creation, management, stream coordinationCovers workstream creation, stream setup with agent domain and
auto_continue, dependency wiring, and health checks. Used internally by initiative-protocol and orchestrator-agent.milestone-protocol
Trigger: milestone creation, scheduling, gate checkingManages milestone definitions with due dates and completion gates. Coordinates with workstreams to track progress toward milestones.
task-protocol
Trigger: individual task execution within a workstreamHandles task lifecycle: start → execute → verify → complete. Emits telemetry at each phase, follows domain-specific workflows, and submits learnings on completion.
Domain Agent Skills
These skills give your MCP client the same specialized expertise as OrgX’s built-in agents. Each produces evidence-based artifacts with durable proof links.engineering-agent
engineering-agent
Domain: Technical decisions, implementation risk, code qualityArtifacts produced: RFCs, ADRs, code review summaries, incident postmortems, tech debt inventories, capacity plans, runbooks, migration playbooks, dependency audits, performance budgets, architecture docs (any C4 level), threat models, SLO definitions, build-vs-buy analysesProof rules: GitHub PR/commit/blob permalinks, public docs URLs, or absolute file paths only. No OrgX wrapper pages.
product-agent
product-agent
Domain: Problem framing, user value, prioritization, measurable outcomesArtifacts produced: PRDs, initiative plans, product canvases, user research briefs, competitive analyses, feature prioritization matrices, pivot evaluations, metric dashboard specs, launch readiness checklists
marketing-agent
marketing-agent
Domain: Campaign planning, content creation, growth, SEO/AEOArtifacts produced: Campaign briefs, landing page copy, blog posts, email sequences, social content calendars, SEO/AEO keyword plans, go-to-market playbooks, press releases, brand messaging guides
sales-agent
sales-agent
Domain: Pipeline, outreach, objection handling, competitive positioningArtifacts produced: Outreach sequences, qualification frameworks, competitive battlecards, proposal templates, win/loss analyses, ICP definitions, discovery call scripts
design-agent
design-agent
Domain: UX rationale, design decision support, UI briefsArtifacts produced: UX rationale documents, design briefs, component specs, accessibility assessments, user flow diagrams, design system contribution guidelines
operations-agent
operations-agent
Domain: Process operations, incident management, runbooksArtifacts produced: Incident reports, process playbooks, runbooks, SOC procedures, vendor evaluations, operational risk assessments, team capacity reports
orchestrator-agent
orchestrator-agent
Domain: Cross-domain execution coordinationArtifacts produced: Initiative plans, delegation messages, synthesis reports, retrospectives, dependency audits, resource allocations, risk registers, stakeholder updates, program status reportsThe orchestrator never does domain work itself — it coordinates, sequences, unblocks, and synthesizes across other agents.
Specialized Skills
design-audit
Trigger:
/design-audit <target_path_or_url> [reference_urls...]Applies cognitive psychology, Gestalt theory, and principles from Rams, Tufte, Norman, and others to audit any UI surface. Outputs a scored assessment with prioritized improvements. Minimum target: 9/10 per pass.bulk-create
Trigger: “bulk create”, “create tasks from list”, “import checklist”, “batch create”Parses markdown checklists, bullet lists, or numbered lists and creates multiple OrgX entities in batch. Detects priorities from keywords and wires up dependencies for nested items.
Proof Rules (All Skills)
Every domain skill enforces these artifact proof rules:- Durable sources only: GitHub PR/commit/blob permalinks, public URLs, or absolute file paths (
/path/to/fileorfile://...) - No OrgX wrapper pages:
/live/...,/artifacts/..., and/console/...are dashboards, not evidence preview_markdownis supporting context: it does not replace a durable proof URL
Writing Custom Skills
Skills are plain Markdown files with a YAML frontmatter header. Place them in.claude/skills/ in your project directory:
Next Steps
Wizard CLI
Full CLI reference for installing and managing skills.
Agent Quickstart
Run your first agent task with skills wired in.
Agent Recipes
Pre-built workflows combining multiple skills.
MCP Tools
Full reference for the tools skills call under the hood.
