Individual skill

spk-integrate-orchestrator-api

Use Spec Kitty orchestrator-api from external systems, respecting host boundaries, state contracts, and workflow commands.

src/charter/offering/skills/spk-integrate-orchestrator-api/SKILL.md

Read pinned source

Source commit 25b7cd4fbc8f42ec71219408e2b5d76e7dae38b4

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: No
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Not checked yet
Last checked: Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,717
Repository last updated: Nov 7, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

claude-code Repository topic
gemini-cli Repository topic
spec-driven-development Repository topic
cursor-agent Repository topic
github-copilot Repository topic
windsurf Repository topic
ai-coding-workflow Repository topic
ai-development-dashboard Repository topic
ai-progress-tracking Repository topic
coding-agent-orchestration Repository topic
operations Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

SKILL.mdcore · 869 bytes

Read excerpt


# spk-integrate-orchestrator-api

Use this skill when an agent, script, CI job, or external service needs to drive
Spec Kitty through orchestrator-api.

## Flow

1. Identify the external caller and allowed host boundary.
2. Use documented API contracts rather than scraping local artifacts.
3. Preserve state-machine invariants: no implicit success, no skipped gates.
4. Route mission advancement through runtime decisions.
5. A `PREFLIGHT_FAILED` without a `teardown_error_code` is raised before any lane/target mutation; a refusal leaves refs untouched.

## Legacy Alias