Scaffold the dsh-slopo bundle and port slopo's three agent skills
The three SKILL.md files are ports of the configs slopo 0.8.0 ships for
Claude Code, not new prose. What changed is the mechanics:
* name + description frontmatter, both required by dsh
* disable-model-invocation: true kept verbatim -- dsh has the same key,
and slopo makes that choice for a reason (every one of these commands
can spend minutes embedding)
* allowed-tools / argument-hint / arguments dropped, not dsh keys
* the !`slopo ...` shell-injection directive replaced with an
instruction to call the slopo tool plus an explicit failure check,
because dsh skill bodies do not execute commands
The guidance prose is quoted from slopo; NOTICE.md records the mapping and
the licence obligation that follows from it (AGPL-3.0-or-later, matching
upstream and the LICENSE file fetched from it).
This commit is contained in:
commit
3490e5aba0
8 files changed
+923
No files matched your search
@@ -0,0 +1,22 @@
|
||||
# The layer this bundle contributes to a dsh profile that lists it.
|
||||
#
|
||||
# One row: the dsh-slopo host plugin. It contributes three things —
|
||||
# * three skills on `ctx.skills`, all user-invocable and NOT model-invocable
|
||||
# (slopo's own agent configs make the same choice, because every one of
|
||||
# these commands can spend minutes embedding);
|
||||
# * a configuration namespace on `ctx.settings`, so the embedding backend is
|
||||
# editable at runtime rather than baked into this file;
|
||||
# * one `slopo` tool that resolves the CLI, runs it, and streams progress.
|
||||
#
|
||||
# The row references the package by NAME rather than a relative path, so Node
|
||||
# resolution finds the installed copy — see the dsh publish docs.
|
||||
#
|
||||
# There is deliberately NO `config:` block here. Every value the plugin needs is
|
||||
# either discovered at runtime (the slopo binary), set by the user through the
|
||||
# settings namespace, or genuinely optional. Shipping defaults would mean baking
|
||||
# one machine's paths into a layer that other machines also apply, and the
|
||||
# plugin's own schema already carries the defaults it can honestly claim.
|
||||
|
||||
- insert:
|
||||
- id: dsh-slopo
|
||||
name: dsh-slopo
|
||||
Reference in new issue
Block a user