docs(website): explain what the skill unlocks, and document config.toml
The agent-native copy described what the skill contains rather than what it buys you. A new home-page section shows the shape of the request that becomes possible — describe the outcome, let the agent write the pipeline — and names the specific knowledge --help cannot carry: which JSON keys a record has, that exit 4 means widen the query, that a remote path goes back byte-identical, that --follow never returns. The install page gains a reference for all nine config.toml settings with their defaults and an example file, next to the paths that were already there. The list is the one `config set` accepts, checked against FileConfig::KEYS.
This commit is contained in:
@@ -203,9 +203,16 @@ export const Docs = () => {
|
||||
<p>
|
||||
<Code>soulseek-rs skills install</Code> writes a <Code>SKILL.md</Code> into
|
||||
every coding agent on the machine — Claude Code and opencode today,{' '}
|
||||
<Code>--dir</Code> for anything else. It carries what <Code>--help</Code>{' '}
|
||||
cannot: the JSON keys of every record, what each exit code means, and the
|
||||
idioms worth reaching for. Run it again after an upgrade to update it, and{' '}
|
||||
<Code>--dir</Code> for anything else. After it lands you describe the
|
||||
outcome instead of the pipeline: “mirror that peer’s FLAC
|
||||
folder”, “watch this room for an hour and save anything
|
||||
mentioning the label”.
|
||||
</p>
|
||||
<p>
|
||||
It carries what <Code>--help</Code> cannot: the JSON keys of every record,
|
||||
that exit 4 means widen the query rather than retry it, that remote paths go
|
||||
back byte-identical, and that <Code>--follow</Code> never returns so an agent
|
||||
passes <Code>--duration</Code>. Run it again after an upgrade to update it;{' '}
|
||||
<Code>skills uninstall</Code> takes it back out.
|
||||
</p>
|
||||
</Callout>
|
||||
|
||||
Reference in New Issue
Block a user