forked from Selig/openclaw-skill
Selig
4c966a3ad2
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.
41 lines
1.2 KiB
Markdown
41 lines
1.2 KiB
Markdown
# Skills (macOS)
|
|
|
|
## Overview
|
|
|
|
The macOS application surfaces OpenClaw skills through a gateway rather than parsing them locally.
|
|
|
|
## Key Components
|
|
|
|
### Data Source
|
|
|
|
The system retrieves skill information via `skills.status` from the gateway, which provides all skills plus eligibility and missing requirements. Requirements come from the `metadata.openclaw.requires` field in skill markdown files.
|
|
|
|
### Installation Process
|
|
|
|
The `metadata.openclaw.install` property specifies available installation methods:
|
|
|
|
- brew
|
|
- node
|
|
- go
|
|
- uv
|
|
|
|
When users initiate installation, the app invokes `skills.install` on the gateway host. The gateway prioritizes a single installer:
|
|
|
|
1. Prefers brew when available
|
|
2. Otherwise uses the node package manager specified in `skills.install`
|
|
3. Falls back to npm as the default
|
|
|
|
### Credential Management
|
|
|
|
API keys and environment variables are stored locally at `~/.openclaw/openclaw.json` under the `skills.entries.<skillKey>` path.
|
|
|
|
Configuration updates use the `skills.update` endpoint to modify:
|
|
|
|
- Enabled status
|
|
- API keys
|
|
- Environment settings
|
|
|
|
### Remote Configuration
|
|
|
|
Installation and configuration changes occur on the gateway host rather than the local machine, maintaining centralized management of skill deployment.
|