# Sutra

> Orchestrator for the claude-skills-pack. Use when the user wants the pack's members to cooperate — a commit that also journals and captures a lesson, a review that recalls prior risks, a verify that feeds the memory loop. Sutra owns the unified /sutra:* command surface, the capability registry, the artifact interchange schema, cross-plugin recall, and the verify→lesson→recall feedback loop. It dr…

- **Type:** Skill
- **Install:** `agentstack add skill-prajwalmahajan101-claude-skills-pack-sutra`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [prajwalmahajan101](https://agentstack.voostack.com/s/prajwalmahajan101)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [prajwalmahajan101](https://github.com/prajwalmahajan101)
- **Source:** https://github.com/prajwalmahajan101/claude-skills-pack/tree/main/skills/sutra

## Install

```sh
agentstack add skill-prajwalmahajan101-claude-skills-pack-sutra
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Sutra — the pack orchestrator

Sutra is the composition root of `claude-skills-pack`. It owns everything *between* the members;
each member (code_assist, sb, unabridged) owns only itself and never references the others. Remove
sutra and every member still works in isolation. Install sutra and the pack becomes one cooperating
system with a single canonical command surface.

**Iron rule: sutra never re-implements a member's logic.** It resolves the member, drives that
member's own router/runner, and layers the cross-plugin bridge steps around it.

## Step 1 — resolve the pack (always first)

```
node ~/.claude/skills/sutra/bin/sutra-tools.js registry
```

This reports each member's `present` / `version` / `capabilities`. Every bridge step below is a
**no-op when its member is absent** — a missing member is never a reason to stop.

## Step 2 — route the request to a /sutra:* command

The command surface mirrors the members' capabilities under one namespace. Two tiers (see
`commands/_manifest.json`):

| Tier | Commands | What sutra adds |
|---|---|---|
| **Composed (Tier-1)** | `do recall sync capture review commit verify` | hand-tuned composed flows: pre-`recall` context, `graph` impact, post artifact→vault `sync`, `loop-emit`, offer `lesson`, unabridged discipline on full-output steps (`do` is the catch-all agent) |
| **Pass-through** | every other member command (`journal plan debug adr incident release onboard flow structure* refactor test format github graph notify scan track secure* kanban tasks topic search connect distill emerge health decision …`) | reachable via `/sutra:do` (the agent composes bridges automatically) or the member's own `/:` namespace |

`/sutra:*` is the **canonical, recommended** surface when the full pack is installed. It does not hide
the members' own `/code_assist:*` and `/sb:*` namespaces — those remain for standalone use.

**The catch-all: `/sutra:do `** dispatches any request to the **`sutra-agent`** subagent,
which knows the entire ecosystem and composes members automatically. The Tier-1 commands
(`/sutra:review`, `/sutra:commit`, `/sutra:verify`, `/sutra:recall`, `/sutra:sync`, `/sutra:capture`)
are the same composition pre-wired for common flows. Every other member capability is reached via
`/sutra:do` or the member's own namespace — see `commands/_manifest.json`.

## Step 3 — execute the wrapper

Each command file in `commands/` is a thin delegator described by `commands/_manifest.json`:
`{ member, router|runner, pre[], post[] }`. To run one:

1. Resolve the target member via the registry (Step 1). If absent, run the pass-through fallback or
   report that the capability needs its member installed.
2. Run any `pre` hooks (e.g. `recall --context ""` to reason WITH prior knowledge).
3. Drive the member's own router/runner — the member's files are the single source of truth for its
   logic. Do NOT duplicate it here.
4. Run any `post` hooks (`sync-artifacts` → vault, `loop-emit` → feedback log, offer `/sutra:capture`).

## What sutra owns (and the members do not)

- **Registry** (`registry/members.json` + `sutra-tools.js registry`) — the only place member presence
  and capabilities are declared. Members never detect each other.
- **Interchange schema** (`schema/*.spec.md` + `sutra-tools.js schema-check`) — the canonical shapes of
  `.journal/`, `docs/adr/`, `.code_review/`. code_assist writes its own format; sutra's conformance
  check catches drift. This lives in sutra so code_assist stays standalone.
- **Bridges** (`bridge/ROUTER.md`) — artifact→vault sync and recall-fusion, described in registry terms.
- **Feedback loop** (`loop/ROUTER.md`) — verify/plan/incident outcomes → `sb` lessons (some tagged
  `risk`) → surfaced again by the next `recall`. Writing out feeds the pull-back.

## The CLI

`bin/sutra-tools.js` is the deterministic backbone (zero-dep, JSON out):
`registry`, `selfcheck`, `bridge status`, `recall --context`, `sync-artifacts `,
`schema-check `, `loop-emit --event --note`, `version`. Every command is safe when a member is
absent.

## Rules

- Bridges are additive. If a member is missing, say nothing about it and proceed.
- Never re-implement a member's family logic — drive its router/runner.
- External writes inherited from members (track/notify/github) stay dry-run + confirm.
- Honor the members' own discipline (code_assist's Iron Laws, unabridged's no-truncation).

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [prajwalmahajan101](https://github.com/prajwalmahajan101)
- **Source:** [prajwalmahajan101/claude-skills-pack](https://github.com/prajwalmahajan101/claude-skills-pack)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-prajwalmahajan101-claude-skills-pack-sutra
- Seller: https://agentstack.voostack.com/s/prajwalmahajan101
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.