How do I install the Sac Retrieve skill?

Run npx skillmds@latest add spillwavesolutions/sac-retrieve in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Sac Retrieve safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Sac Retrieve?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Sac Retrieve free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Sac Retrieve?

spillwavesolutions (@spillwavesolutions) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Sac Retrieve by spillwavesolutions — Agent Skill

Name: Sac Retrieve
Author: spillwavesolutions

Sac Retrieve

Query-time retrieval of SAC architecture context without contaminating the parent. Spawn architecture-retriever for topology (Service, ApiContract, Package, Runtime, Pipeline, IdentityProvider, blast radius). Do not run sac_search or sac_pack in the parent. Consume only the retrieval card.

File contents

SAC Retrieve

Parent-facing. This is query-time retrieve, not reverse-engineering.

Do not run sac_search.py, sac_pack.py, or sac_blast_radius.py in the parent for retrieval. Hit lists and full pack markdown must stay out of the parent working context. Progressive disclosure clips the graph; it does not isolate the parent.

Spawn

Spawn the architecture-retriever agent (host Task / sub-agent).

Pass through:

query — what the parent needs (topology, contract, runtime, impact)
seed — optional concept path when already known (services/order-service.md)
bundle / repo — knowledge root the human already owns, or sample-knowledge/

The child owns search, scoring, --tiny / --hops 2 pack, optional blast-radius, and up to two deepen steps. It returns a retrieval card only.

Consume

Read only the card. Do not ask the child for full hits, mermaid, or pack bodies.

## Retrieval card
- Query: …
- Seed: `/path` (`Type`) — why chosen
- Fit: high|medium|low — one sentence
- Engine: rg|scan
- Pack: hops=N nodes=N tokens=N/budget  (or Blast: hops=N)
- Lead nodes: (5–8 bullets: title · type · path · one-line why)
- Critical edges: (up to 5 typed edges that matter) or none
- Open gaps: unverified / missing owners / orphans or none
- Next: stay|deepen-2hop|blast-radius|try-alt-seed `/other`

If Next is deepen-2hop, blast-radius, or try-alt-seed, spawn the retriever again with that instruction. Do not run the engine yourself.

Orthogonal fan-out

Architecture topology is SAC. Project-memory (Meeting, Feature, DecisionRecord, Experiment, TicketLink) is PKC. If the parent also needs that plane, fan out to PKC knowledge-retriever in a separate child. Do not merge the two engines in this parent turn.

Design-time

Skill sac-design-with should spawn this retriever (and blast-radius via the child) before proposing new services, APIs, or apps.

---name: sac-retrievedescription: Query-time retrieval of SAC architecture context without contaminating the parent. Spawn architecture-retriever for topology (Service, ApiContract, Package, Runtime, Pipeline, IdentityProvider, blast radius). Do not run sac_search or sac_pack in the parent. Consume only the retrieval card.---# SAC RetrieveParent-facing. This is **query-time retrieve**, not reverse-engineering.Do **not** run `sac_search.py`, `sac_pack.py`, or `sac_blast_radius.py` in theparent for retrieval. Hit lists and full pack markdown must stay out of theparent working context. Progressive disclosure clips the graph; it does notisolate the parent.## SpawnSpawn the **`architecture-retriever`** agent (host Task / sub-agent).Pass through:- **query** — what the parent needs (topology, contract, runtime, impact)- **seed** — optional concept path when already known (`services/order-service.md`)- **bundle** / **repo** — knowledge root the human already owns, or `sample-knowledge/`The child owns search, scoring, `--tiny` / `--hops 2` pack, optional blast-radius,and up to two deepen steps. It returns a **retrieval card only**.## ConsumeRead only the card. Do not ask the child for full hits, mermaid, or pack bodies.```markdown## Retrieval card- Query: …- Seed: `/path` (`Type`) — why chosen- Fit: high|medium|low — one sentence- Engine: rg|scan- Pack: hops=N nodes=N tokens=N/budget (or Blast: hops=N)- Lead nodes: (5–8 bullets: title · type · path · one-line why)- Critical edges: (up to 5 typed edges that matter) or none- Open gaps: unverified / missing owners / orphans or none- Next: stay|deepen-2hop|blast-radius|try-alt-seed `/other````If **Next** is `deepen-2hop`, `blast-radius`, or `try-alt-seed`, spawn theretriever again with that instruction. Do not run the engine yourself.## Orthogonal fan-outArchitecture topology is SAC. Project-memory (Meeting, Feature, DecisionRecord,Experiment, TicketLink) is PKC. If the parent also needs that plane, fan outto PKC **`knowledge-retriever`** in a separate child. Do not merge the twoengines in this parent turn.## Design-timeSkill `sac-design-with` should spawn this retriever (and blast-radius via thechild) before proposing new services, APIs, or apps.

Frequently asked questions