HomerandClaude Opus 5.5
539896494f
The CLI's facts in memory, notes_search, note_manage, skills_list, skill_view and skill_manage are `variables` now, filled with the CLI's own values (src/tool/spec-vars.ts): every description and parameter list the CLI sends is word for word what 1.1.0 said, except note and document ids, which are strings on both sides (a number is still taken). Descriptions are filled by the prompt texts' rules, parameter descriptions too. `narrow` says what a project offers of a shared tool's parameters. Memory's changes are one pure function (applyOps). Conformance: fill, narrow, memory. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
42 lines
1.0 KiB
JSON
42 lines
1.0 KiB
JSON
{
|
|
"name": "skill_view",
|
|
"scope": "shared",
|
|
"risk": "read",
|
|
"exclusive": false,
|
|
"block": "read",
|
|
"purpose": false,
|
|
"aliases": {
|
|
"cli": [],
|
|
"llembas": [
|
|
"skill_get"
|
|
]
|
|
},
|
|
"variables": {
|
|
"files": "what else a skill carries and how to read it (\", and the list of its supporting files (references, templates, scripts, assets). To read one of those, call again with file_path.\"), or \".\""
|
|
},
|
|
"description": "Load a skill: its full instructions{{files}}",
|
|
"parameters": {
|
|
"type": "object",
|
|
"properties": {
|
|
"name": {
|
|
"type": "string",
|
|
"description": "The skill's name (the skills list in your instructions, or skills_list)"
|
|
},
|
|
"file_path": {
|
|
"description": "A supporting file, relative to the skill: references/api.md, templates/config.yaml… Omit for SKILL.md.",
|
|
"type": "string"
|
|
}
|
|
},
|
|
"required": [
|
|
"name"
|
|
]
|
|
},
|
|
"narrow": {
|
|
"llembas": {
|
|
"drop": [
|
|
"file_path"
|
|
]
|
|
}
|
|
}
|
|
}
|