agent-readiness

$npx mdskill add JKHeadley/instar/agent-readiness

Score a task or workflow on its coordination-vs-judgment ratio for agent-readiness

  • Identify tasks/workflows suitable for automation based on their balance of coordination and judgment.
  • Depends on EXO 3.0 task-decomposition matrix as input data.
  • Decides readiness by analyzing the nature of each step in a workflow, prioritizing coordination over judgment.
  • Provides score and recommendation to users or agents about whether a task is agent-ready.

SKILL.md

.github/skills/agent-readinessView on GitHub ↗
---
name: agent-readiness
description: Score a task or workflow on its coordination-vs-judgment ratio to tell whether it's a good agent candidate (EXO 3.0 task-decomposition matrix).
metadata:
  user_invocable: "true"
---

# /agent-readiness

Salim Ismail's EXO 3.0 diagnostic, made runnable: score a piece of work on its
**coordination-vs-judgment ratio**. Coordination work — routing information,
approvals, scheduling, status tracking, prescriptive/standardized steps — is what
AI agents do best, so it's *agent-ready*. Judgment work — resolving ambiguity,
handling exceptions, navigating relationships, making a call with no playbook —
should stay with (or escalate to) humans.

## When to use

- Before delegating a task/workflow to an agent — is it actually a good candidate?
- When deciding whether a process should be fully automated, agent-with-oversight,
  hybrid, or kept human-led.
- When mapping which of your workflows a small team + agents could rebuild first
  (Salim: "every task that scores high on coordination has agent readiness").

## How

Score a task:
```bash
curl -X POST -H "Authorization: Bearer $AUTH" -H 'Content-Type: application/json' \
  -d '{"task":{"name":"Invoice intake","description":"Route invoices, schedule approvals, track status, compile a weekly report, notify owners."}}' \
  http://localhost:${INSTAR_PORT:-4042}/agent-readiness/score
```

Score a workflow (by its steps):
```bash
curl -X POST -H "Authorization: Bearer $AUTH" -H 'Content-Type: application/json' \
  -d '{"workflow":{"steps":["Fetch the record","Assign accounts","Schedule orientation","Update the tracker"]}}' \
  http://localhost:${INSTAR_PORT:-4042}/agent-readiness/score
```

Returns:
```json
{
  "coordinationSignals": 5, "judgmentSignals": 0,
  "coordinationRatio": 1.0, "overallReadiness": 100,
  "recommendation": "deploy-agent",
  "reason": "...",
  "matched": { "coordination": ["route","schedule",...], "judgment": [] }
}
```

`recommendation` is one of: `deploy-agent` (75+), `agent-with-oversight` (55–74),
`hybrid` (40–54), `human-led` (<40). Deterministic + advisory — it answers a
question; it never blocks. Pair it with the MTP Protocol (`/intent/org/test-action`)
to check both "is this agent-ready?" and "does our purpose endorse it?"

More from JKHeadley/instar

SkillDescription
agent-passportView this agent's digital passport (identity + trust + allowed/forbidden actions) and verify a peer's passport against a proposed action (EXO 3.0).
autonomousEnter autonomous development mode with STRUCTURAL enforcement. Uses a stop hook to prevent premature exit. Generates stop conditions and confirms with user before starting. Work independently for a specified duration with progress reporting.
command-guardSet up a PreToolUse hook in .claude/settings.json that blocks dangerous commands — rm -rf, force push, database drops, and others — before they execute. Teaches the pattern of safety hooks for any Claude Code project. Trigger words: safety, guard, block dangerous, protect, prevent destructive, safe mode, dangerous commands, risky operations.
credential-leak-detectorPostToolUse hook that scans Bash tool output for leaked credentials — API keys, tokens, private keys, and secrets — before they reach the conversation. Blocks critical leaks, redacts high-severity matches, and warns on suspicious patterns. 14 detection patterns covering OpenAI, Anthropic, AWS, GitHub, Stripe, Google, Slack, SendGrid, Twilio, PEM keys, bearer tokens, and generic secrets. No external dependencies. Trigger words: security, credential leak, secret exposure, key detection, token scan, API key leaked, credential guard, secret scanner, prevent credential leak.
instar-devInstar-specific development skill used by the instar-developing agent (Echo, or any agent assigned instar-dev responsibilities). Wraps /build with mandatory side-effects review, signal-vs-authority principle check, and artifact generation. Structural enforcement via pre-commit/pre-push hooks — the instar repo refuses commits and pushes that didn't come through this skill. NOT a user-facing skill — end users should never invoke it.
instar-feedbackSubmit structured feedback about instar bugs, feature requests, improvements, or innovations worth sharing. Use when something isn't working, when a feature is missing, when you've built something that could benefit all agents, or when the user mentions a problem with instar. Also use proactively after building significant features — ask yourself if other agents would benefit. Feedback is relayed agent-to-agent to instar maintainers. Trigger words: bug report, feedback, issue, something's wrong, feature request, this isn't working, improvement, suggest, built something useful, other agents could use this.
instar-identityEstablish and recover persistent agent identity that survives context compaction, session restarts, and autonomous operation. Use when an agent needs to know who it is, recover after context compression, orient at session start, or understand the identity infrastructure. Trigger words: who am I, remember, identity, after restart, compaction, context loss, who am I working with, my principles.
instar-projectRegister, inspect, and drive multi-spec projects via the instar /projects API. Twelve subcommands cover the full Phase 1 surface — create / status / next / advance / drift / run-round / halt / ack / resume / abandon / accept-partial / claim-ownership.
instar-schedulerSchedule recurring agent tasks using cron expressions. Use when the user asks to run something on a schedule, check something periodically, automate a recurring task, set up a cron job, or wants work to happen while they're away. Trigger words: schedule, recurring, cron, every hour, every day, run daily, periodic, automated.
instar-sessionSpawn, monitor, and communicate with persistent Claude Code sessions running in the background. Use when a task needs to run without blocking the current session, when the user asks to do something in the background, or when a long-running task needs its own context window. Trigger words: background task, spawn session, persistent, run in background, parallel, separate session, async task.