Initial commit: OpenClaw Skill Collection

6 custom skills (assign-task, dispatch-webhook, daily-briefing,
task-capture, qmd-brain, tts-voice) with technical documentation.
Compatible with Claude Code, OpenClaw, Codex CLI, and OpenCode.

openclaw-knowhow-skill/docs/infrastructure/plugins/index.md

@@ -0,0 +1,47 @@
+# OpenClaw Plugins Documentation
+
+## Overview
+
+Plugins extend OpenClaw with additional capabilities. A plugin is just a small code module that extends OpenClaw with extra features.
+
+## Key Capabilities
+
+Plugins can register:
+- Gateway RPC methods
+- Gateway HTTP handlers
+- Agent tools
+- CLI commands
+- Background services
+- Skills (via directories in the plugin manifest)
+- Auto-reply commands
+
+## Installation & Management
+
+Basic commands for plugin operations:
+
+```bash
+openclaw plugins list
+openclaw plugins install @openclaw/voice-call
+openclaw plugins enable <id>
+openclaw plugins disable <id>
+```
+
+The system loads plugins from multiple locations: config paths, workspace extensions, global extensions, and bundled extensions.
+
+## Official Plugins Available
+
+Notable built-in options include voice calling, memory search (Core and LanceDB variants), and messaging channels like Microsoft Teams, Matrix, Nostr, and Zalo.
+
+## Configuration
+
+Plugins use a declarative config model with JSON Schema validation. Plugin config is validated using the JSON Schema embedded in `openclaw.plugin.json`.
+
+Plugin slots enable exclusive categories—only one active simultaneously. For example, memory plugins use the `memory` slot.
+
+## Security Consideration
+
+Plugins run in-process with the Gateway, so treat them as trusted code. Users should only install plugins from reliable sources.
+
+## Development
+
+Plugins export either a function or an object with registration logic. The manifest requires an `openclaw.plugin.json` file with metadata, schema, and UI hints for the Control UI.

openclaw-knowhow-skill/docs/infrastructure/plugins/voice-call.md

@@ -0,0 +1,28 @@
+# Voice Call Plugin Documentation
+
+## Overview
+
+The Voice Call plugin enables OpenClaw to make outbound notifications and support multi-turn conversations with inbound call policies. It currently supports four providers: Twilio, Telnyx, Plivo, and a mock provider for development.
+
+## Installation
+
+Users can install via npm with `openclaw plugins install @openclaw/voice-call` or from a local folder for development purposes. The Gateway must be restarted after installation to load the plugin.
+
+## Key Configuration Areas
+
+**Provider Setup**: The plugin requires selecting a provider and configuring provider-specific credentials (account SID for Twilio, auth ID for Plivo, etc.).
+
+**Webhook Configuration**: Twilio/Telnyx require a publicly reachable webhook URL. The plugin serves webhooks on a configurable port and path, with security options for handling proxies and tunnels.
+
+**TTS Integration**: The plugin uses the core `messages.tts` configuration, with the ability to override it specifically for voice calls. Edge TTS is excluded from telephony due to audio format requirements.
+
+## Inbound Calls
+
+Inbound functionality is disabled by default but can be enabled through an allowlist policy with optional greeting and response tuning parameters.
+
+## Access Methods
+
+The plugin is accessible via:
+- CLI commands (`openclaw voicecall call`, `continue`, `speak`, etc.)
+- Agent tool named `voice_call`
+- Gateway RPC endpoints

openclaw-knowhow-skill/docs/infrastructure/plugins/zalouser.md

@@ -0,0 +1,16 @@
+# Zalo Personal Plugin Documentation
+
+## Overview
+The Zalo Personal plugin enables OpenClaw to automate personal Zalo user accounts through the `zca-cli` tool. This integration operates within the Gateway process and uses the channel identifier `zalouser` to distinguish it from potential official Zalo API integrations.
+
+## Key Warnings
+Users should be aware that unofficial automation may lead to account suspension/ban. This represents a significant risk factor when implementing this plugin.
+
+## Installation Requirements
+The plugin can be installed via npm or from a local development folder. Regardless of installation method, the Gateway must be restarted afterward. Additionally, the `zca-cli` tool must be available on the system PATH where the Gateway runs.
+
+## Configuration
+Settings are defined under `channels.zalouser` in the configuration file, with options for enabling the channel and setting the DM policy to "pairing."
+
+## Functionality
+The plugin supports several CLI operations including login/logout, status checks, and message sending. Through the agent tool interface, users can perform actions like sending messages, sharing images and links, and accessing friend/group information.