pub struct Skill {
pub name: String,
pub enabled: bool,
pub files: Vec<SkillFile>,
}Expand description
A skill bundle: a manifest plus whatever it references.
The whole folder round-trips. Storing only SKILL.md breaks every skill
that carries references, scripts or data — and breaks it at run time, long
after the client thought it had configured the harness.
Fields§
§name: StringBundle name, which is how it is addressed.
enabled: boolWhether the harness may use it.
files: Vec<SkillFile>Every file in the bundle.
Implementations§
Source§impl Skill
impl Skill
Sourcepub fn has_manifest(&self) -> bool
pub fn has_manifest(&self) -> bool
Whether this bundle carries its manifest.
A bundle without one would be stored and then silently ignored at run time, which is the hardest kind of failure for a user to diagnose — so it is refused at config time instead.
Sourcepub fn has_plain_name(&self) -> bool
pub fn has_plain_name(&self) -> bool
Whether the bundle’s name is one plain path segment.
The name becomes the folder the bundle is written to when a task runs,
so a name carrying a separator or a .. would place it elsewhere.