recall-extlisted
Install: claude install-skill samzong/Recall
# Recall Ext
## First Read
Read `docs/extensions.md` before changing extension code, extension docs, or
official extension release wiring. Treat it as the design source. Treat code as
runtime truth if the doc and implementation disagree.
## Boundaries
- Keep Recall core as the data plane and stable CLI JSON/JSONL protocol.
- Build extensions as external binaries named `recall-<name>`.
- Use `recall extension ...` and `recall ext ...` for host commands.
- Manage only official extensions from the official catalog unless the product
explicitly adds third-party distribution later.
- Do not expose Rust internals, add a `recall-core` crate, or depend on SQLite
schema from an extension.
- Do not add permissions/capabilities fields for native binaries; Recall cannot
enforce them.
- Do not add an open registry unless real third-party distribution demand
exists. Official catalog first.
## Develop An Official Extension
Use `extensions/recall-probe/` as the minimal template.
1. Create `extensions/recall-<name>/` as a workspace binary package.
2. Name the Cargo package and binary `recall-<name>`.
3. Keep the package version independent from Recall core.
4. Add the package to the root workspace members, keeping `default-members = ["."]`.
5. Implement `--recall-extension-manifest` with JSON stdout:
```json
{
"name": "<name>",
"version": "0.1.0",
"protocol": 1,
"min_recall": "0.2.10",
"commands": ["<name>"]
}
```
6. Consume Recall through stable CLI commands such a