Expand description
The agent skills: the payload, the user-scope record, and the installer.
Skills land under the invoking user’s home and never into a target repository. An agent resolves a skill by name across scopes, so a second copy under one name is a second entry offering the same skill, with no way for the operator to tell which one runs. One installed binary already serves every repository, and the skills routing into it belong at the same scope.
That places every destination outside the reach of rk init, which has a
target directory to compare against and a landing to refuse. Here there is
no target and no manifest, so record stands in for one: it answers the
single question the installer cannot otherwise answer — are these bytes
ones we wrote?
Re-exports§
pub use crate::digest::Digest;
Modules§
- installer
- Install the embedded skills into the agent skill directories.
- record
- The user-scope skill record: what this tool last wrote outside a project.
Structs§
- Shared
Artifact - One shared artifact: its path under the shared root, and its bytes.
- Skill
- One embedded skill: its directory name and its
SKILL.mdtext.