clip-recap
clip-recap — Stored tacit knowledge lookup
When to call
- Before starting work on a target (
clip <target>) — retrieve identifiers like channels, projects, labels - When a specific person, team, or role name appears — check
people.<name>/team.*entries - When domain terms, abbreviations, or process names are ambiguous — check if the bundle has a definition
- When the user uses implicit references like "our team", "that channel", "the usual way"
What you get
Entry bodies stored in ~/.clip/recap/. If someone else or a previous session has saved context there, you work from the same shared assumptions.
Usage
clip recap— list all groups (Targets / Bundles)clip recap <name>— list entries in a groupclip recap <name> <key>— read entry bodyclip recap <name> <key> --json-output— JSON modeclip recap search <kw>— search across meta and body
If the group has an overview entry, start there.
More from ori-kim/cli-proxy
clip
CLI proxy gateway for CLI tools, MCP servers, OpenAPI REST, gRPC, and GraphQL APIs. Enforces ACL rules and handles OAuth. All external tool calls must go through clip. Route by use case and read the relevant reference for target types, management, safety, aliases, or profiles.
13clip-skills
Manage reusable prompt-template skills stored in the clip registry. Use to create, list, install to agents, import external skills, or compose skills into groups for batch activation. Route by use case and read the relevant reference for create, install, groups, or import.
5clip-context-mode
Use clip's context-mode extension to index large clip target outputs through the upstream context-mode MCP server, then search or purge the indexed result.
2