Knowledge Note Segmenter turns an input note into a segmented record, updates a local knowledge index, and optionally delivers the result to a configured target.
The fastest way to install a skill directly from the registry.
npx clawhub@latest install knowledge-section-index-complete
Copy the skill folder to one of these locations
~/.openclaw/skills/ <project>/skills/ Priority: Workspace > Local > Bundled
Copy this prompt to OpenClaw to install it automatically.
Help me install knowledge-section-index-complete using Clawhub. If Clawhub is not installed, install it first (npm i -g clawhub).
Get the raw skill files in a ZIP archive.
Knowledge Note Segmenter is an executable workflow for processing a knowledge_note into a segmented_note, then using that result to compute an index_update and create or update a local business artifact. It combines identification and downstream index maintenance in one run, making it useful for repeatable knowledge-indexing tasks.
By default, the skill writes its result beneath the supplied output directory and contacts no external service. If configured with SMTP or an HTTP delivery endpoint, it performs the declared delivery action and returns a receipt indicating whether the outcome was sent, delivered, failed, or unconfigured. Openclaw Skills users can run the full process through the bundled Python runner.
knowledge_note input from the JSON request.segmented_note.index_update.--output-dir.Run the bundled workflow with Python and provide an input request plus an output directory:
python scripts/run.py --input examples/request.json --output-dir ./workspace
To enable optional delivery, provide a configuration file:
python scripts/run.py --input examples/request.json --output-dir ./workspace --delivery-config delivery.json
Alternatively, configure delivery through environment variables. For SMTP, set CLAWHUB_SMTP_HOST; optional settings include CLAWHUB_SMTP_PORT, CLAWHUB_MAIL_FROM, CLAWHUB_SMTP_USERNAME, and CLAWHUB_SMTP_PASSWORD. For HTTP registration or submission, set CLAWHUB_DELIVERY_ENDPOINT and optionally CLAWHUB_DELIVERY_API_KEY. The delivery target, credentials, and recipient must come from the runtime environment or explicit configuration. Without delivery settings, the workflow runs locally only. Use examples/request.json as the bundled input and examples/expected.json as a reference for the output structure.
The workflow processes a two-stage result:
| Stage | Input or output | Purpose |
|---|---|---|
| Identify | knowledge_note → segmented_note |
Reads and segments the upstream note. |
| Downstream operation | segmented_note → index_update |
Computes the business result for the knowledge index. |
| Local artifact | Output beneath --output-dir |
Creates or updates the local index-update record. |
| Optional delivery | delivery receipt |
Reports the real delivery outcome when a target is configured. |
Key files:
examples/request.json — bundled upstream input.examples/expected.json — reference output shape; runtime paths and receipt identifiers are excluded.scripts/upstream/ — identify-stage implementation: operation.py, validation.py, and config.json.scripts/downstream/ — downstream delivery implementation, including deliver_effect.scripts/run.py — complete workflow runner.source-map.json — provenance for both extracted stages.The delivery receipt outcome is reported as sent, delivered, failed, or unconfigured, according to the actual workflow result.
Loading
Support Intake Digest transforms a support request snippet into a case comment, saves the business record locally, and optionally delivers it through configured SMTP or HTTP.

Calendar Handoff Reader turns an event handoff into a normalized calendar record and can optionally deliver the resulting business action.

Customer Record Field Prep transforms an input record note into a prepared field and reporting export artifact, with optional configured delivery.

Turn referral form JSON into a validated handoff digest and business packet, with optional configured delivery and a receipt.

Convert a project intake note into a delivery ledger entry, save the business record locally, and optionally perform a configured real-world delivery action.

Release Configuration Brief transforms a configuration note into a stakeholder report, saving it locally and optionally delivering it through SMTP or HTTP.








































