fix(docs): standardize terminology and CLI formatting
This commit is contained in:
@@ -325,7 +325,7 @@ The `text_to_speech` tool generates audio that the gateway delivers as native vo
|
||||
|
||||
Voice and provider are configured by the user in `~/.hermes/config.yaml` under the `tts:` key. The model only sends text; it does not choose the voice.
|
||||
|
||||
The tool returns a `MEDIA:<path>` tag that the gateway send pipeline intercepts and delivers as a native audio message. If `[[audio_as_voice]]` is present (Opus format available), Telegram sends it as a voice bubble instead of an audio file.
|
||||
The tool returns a `MEDIA:<path>` tag that the gateway sending pipeline intercepts and delivers as a native audio message. If `[[audio_as_voice]]` is present (Opus format available), Telegram sends it as a voice bubble instead of an audio file.
|
||||
|
||||
**Telegram voice bubbles & ffmpeg:**
|
||||
|
||||
|
||||
@@ -791,7 +791,7 @@ This is probably a PR to vercel-labs/skills — they already support 35+ agents
|
||||
|
||||
### 7. Marketplace.json for Hermes Skills
|
||||
|
||||
Create a `.claude-plugin/marketplace.json` in the Hermes-Agent repo so Hermes's built-in skills (axolotl, vllm, etc.) are installable by Claude Code users too:
|
||||
Create a `.claude-plugin/marketplace.json` in the Hermes Agent repo so Hermes's built-in skills (axolotl, vllm, etc.) are installable by Claude Code users too:
|
||||
|
||||
```json
|
||||
{
|
||||
|
||||
@@ -369,7 +369,7 @@ The `skill_manage` tool lets the agent create, update, and delete its own skills
|
||||
| `write_file` | Add/overwrite a supporting file | `name`, `file_path`, `file_content` |
|
||||
| `remove_file` | Remove a supporting file | `name`, `file_path` |
|
||||
|
||||
### patch vs edit
|
||||
### Patch vs Edit
|
||||
|
||||
`patch` and `edit` both modify skill files, but serve different purposes:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user