HybridClaw Help
Use this skill for product-specific HybridClaw questions such as:
- how to configure a feature
- where config lives
- what a command does
- how a subsystem behaves
- what changed in a recent release
- where a documented workflow is described
This is the default skill for HybridClaw product questions. Prefer it over
generic service skills when the question is about HybridClaw itself, its built-in
features, its channel integrations, or its documented configuration.
Core Rule
For HybridClaw behavior, commands, configuration, architecture, release notes,
or runtime locations: consult public docs URLs first. Do not assume repo source
files are present in the current workspace. npm installs may include packaged
docs, but the agent may still only have direct access to web URLs.
Use web_fetch or web_extract against the public docs site or raw GitHub URLs
before answering from memory.
Canonical Sources
The browser docs are at https://hybridaione.github.io/hybridclaw/docs/.
For web_fetch and web_extract, use the static Markdown under
https://hybridaione.github.io/hybridclaw/content/; the browser shell requires
JavaScript. Start with the narrowest relevant source:
https://hybridaione.github.io/hybridclaw/content/agents.md — index of all docs
https://hybridaione.github.io/hybridclaw/content/reference/configuration.md
https://hybridaione.github.io/hybridclaw/content/reference/commands.md
https://hybridaione.github.io/hybridclaw/content/README.md
https://raw.githubusercontent.com/HybridAIOne/hybridclaw/main/config.example.json
https://raw.githubusercontent.com/HybridAIOne/hybridclaw/main/README.md
https://raw.githubusercontent.com/HybridAIOne/hybridclaw/main/CHANGELOG.md
Follow the Markdown index's relative links against its URL. Static Markdown
pages do not implement ?search= filtering; select the relevant linked page.
Only widen into implementation files when the docs are missing, incomplete, or
ambiguous. If code inspection is required, use local package files when they are
directly accessible; otherwise use GitHub source URLs instead of assuming src/
exists in the workspace.
Default Workflow
- Identify the question type: config, command, behavior, architecture, or release history.
- Fetch the most likely public doc or raw GitHub source first.
- If the right page is not obvious, fetch the Markdown index and follow the relevant page link.
- If needed, confirm with the matching implementation file or GitHub source instead of guessing.
- Answer narrowly and concretely.
- Include the exact config keys, command names, URLs, file paths, or version headings that support the answer.
Answer Style
- Be laser-focused on the asked feature or subsystem.
- Name the exact URL, file, or config location.
- Prefer exact key paths such as
email.smtpHost over vague descriptions.
- If behavior changed recently, check
CHANGELOG.md and state the version.
- If the docs are silent and you infer from code, say that clearly.
Source Selection Hints
- Feature setup or runtime config:
https://hybridaione.github.io/hybridclaw/content/reference/configuration.md, then https://raw.githubusercontent.com/HybridAIOne/hybridclaw/main/config.example.json
- Commands or operational workflows:
https://hybridaione.github.io/hybridclaw/content/reference/commands.md
- Architecture or runtime behavior:
https://hybridaione.github.io/hybridclaw/content/agents.md, then the relevant GitHub source URL if the docs are insufficient
- Release or migration questions:
https://raw.githubusercontent.com/HybridAIOne/hybridclaw/main/CHANGELOG.md
- Workspace/bootstrap behavior:
https://raw.githubusercontent.com/HybridAIOne/hybridclaw/main/src/workspace.ts, then the relevant template or GitHub source URL
Guardrails
- Do not dump broad documentation when the user asked a narrow question.
- Do not cite stale knowledge if the repo has a fresher answer.
- Do not assume repo-local paths such as
src/ or docs/content/ are readable from the current workspace.
- Do not browse unrelated files or URLs "just in case".
- Do not invent config keys, env vars, commands, or defaults.
- Do not defer to generic Gmail, SMTP, Google Workspace, or similar skills when
the real question is how HybridClaw configures or uses those features.
- If multiple sources disagree, say so and prefer the implementation plus the newest docs.
1---2name: hybridclaw-help3description: HybridClaw help. Primary skill for product questions about setup, configuration, commands, runtime behavior, and release notes.4user-invocable: true5metadata:6 source: https://skillmd.com/skills/hybridaione/hybridclaw-help7 hybridclaw:8 category: misc9 short_description: "HybridClaw product help."10 tags:11 - hybridclaw12 - docs13 - configuration14 - commands15 - changelog16 - help17 related_skills:18 - feature-planning19---2021# HybridClaw Help2223Use this skill for product-specific HybridClaw questions such as:2425- how to configure a feature26- where config lives27- what a command does28- how a subsystem behaves29- what changed in a recent release30- where a documented workflow is described3132This is the default skill for HybridClaw product questions. Prefer it over33generic service skills when the question is about HybridClaw itself, its built-in34features, its channel integrations, or its documented configuration.3536## Core Rule3738For HybridClaw behavior, commands, configuration, architecture, release notes,39or runtime locations: consult public docs URLs first. Do not assume repo source40files are present in the current workspace. npm installs may include packaged41docs, but the agent may still only have direct access to web URLs.4243Use `web_fetch` or `web_extract` against the public docs site or raw GitHub URLs44before answering from memory.4546## Canonical Sources4748The browser docs are at `https://hybridaione.github.io/hybridclaw/docs/`.49For `web_fetch` and `web_extract`, use the static Markdown under50`https://hybridaione.github.io/hybridclaw/content/`; the browser shell requires51JavaScript. Start with the narrowest relevant source:5253- `https://hybridaione.github.io/hybridclaw/content/agents.md` — index of all docs54- `https://hybridaione.github.io/hybridclaw/content/reference/configuration.md`55- `https://hybridaione.github.io/hybridclaw/content/reference/commands.md`56- `https://hybridaione.github.io/hybridclaw/content/README.md`57- `https://raw.githubusercontent.com/HybridAIOne/hybridclaw/main/config.example.json`58- `https://raw.githubusercontent.com/HybridAIOne/hybridclaw/main/README.md`59- `https://raw.githubusercontent.com/HybridAIOne/hybridclaw/main/CHANGELOG.md`6061Follow the Markdown index's relative links against its URL. Static Markdown62pages do not implement `?search=` filtering; select the relevant linked page.6364Only widen into implementation files when the docs are missing, incomplete, or65ambiguous. If code inspection is required, use local package files when they are66directly accessible; otherwise use GitHub source URLs instead of assuming `src/`67exists in the workspace.6869## Default Workflow70711. Identify the question type: config, command, behavior, architecture, or release history.722. Fetch the most likely public doc or raw GitHub source first.733. If the right page is not obvious, fetch the Markdown index and follow the relevant page link.744. If needed, confirm with the matching implementation file or GitHub source instead of guessing.755. Answer narrowly and concretely.766. Include the exact config keys, command names, URLs, file paths, or version headings that support the answer.7778## Answer Style7980- Be laser-focused on the asked feature or subsystem.81- Name the exact URL, file, or config location.82- Prefer exact key paths such as `email.smtpHost` over vague descriptions.83- If behavior changed recently, check `CHANGELOG.md` and state the version.84- If the docs are silent and you infer from code, say that clearly.8586## Source Selection Hints8788- Feature setup or runtime config:89 `https://hybridaione.github.io/hybridclaw/content/reference/configuration.md`, then `https://raw.githubusercontent.com/HybridAIOne/hybridclaw/main/config.example.json`90- Commands or operational workflows:91 `https://hybridaione.github.io/hybridclaw/content/reference/commands.md`92- Architecture or runtime behavior:93 `https://hybridaione.github.io/hybridclaw/content/agents.md`, then the relevant GitHub source URL if the docs are insufficient94- Release or migration questions:95 `https://raw.githubusercontent.com/HybridAIOne/hybridclaw/main/CHANGELOG.md`96- Workspace/bootstrap behavior:97 `https://raw.githubusercontent.com/HybridAIOne/hybridclaw/main/src/workspace.ts`, then the relevant template or GitHub source URL9899## Guardrails100101- Do not dump broad documentation when the user asked a narrow question.102- Do not cite stale knowledge if the repo has a fresher answer.103- Do not assume repo-local paths such as `src/` or `docs/content/` are readable from the current workspace.104- Do not browse unrelated files or URLs "just in case".105- Do not invent config keys, env vars, commands, or defaults.106- Do not defer to generic Gmail, SMTP, Google Workspace, or similar skills when107 the real question is how HybridClaw configures or uses those features.108- If multiple sources disagree, say so and prefer the implementation plus the newest docs.