feat(skills): add registry doctor diagnostics and docs
This commit is contained in:
@@ -69,6 +69,18 @@ Skills without `permissions` still load, but:
|
||||
- If a skill is activated (via routing) and it has no `permissions` block, **it has no tool access**.
|
||||
- This is deliberate: skills should be auditable capability packages.
|
||||
|
||||
## Registry Trust Model (ClawHub / Community Catalogs)
|
||||
|
||||
Registry catalogs are discovery metadata, not trusted code.
|
||||
|
||||
- Flynn supports registry discovery and install-by-id via `flynn skills registry *` and `flynn skills install --registry-id`.
|
||||
- Registry metadata fields such as `publisher`, `homepage`, and `sha256` are treated as **declared/unverified**.
|
||||
- Non-local registry sources require explicit operator confirmation (`--confirm`) during install.
|
||||
- Resolved sources (local/git/archive) are still routed through the same skill scanner and installer safety gates.
|
||||
- Registry-driven installs emit dedicated audit events (`skills.registry_install`) including registry id/source and outcome.
|
||||
|
||||
Operationally: treat a registry as a candidate index. Trust is established by your own review and scanner outcomes, not by catalog claims alone.
|
||||
|
||||
## Runtime Enforcement
|
||||
|
||||
Enforcement happens in two places:
|
||||
|
||||
Reference in New Issue
Block a user