-
-
Notifications
You must be signed in to change notification settings - Fork 692
feat(skill): add owlclaw-for-openclaw package #556
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,25 @@ | ||
| # owlclaw-for-openclaw | ||
|
|
||
| `owlclaw-for-openclaw` is a Skill package that connects OpenClaw to OwlClaw MCP tools. | ||
|
|
||
| ## Quick start | ||
|
|
||
| 1. Install `owlclaw-for-openclaw` from ClawHub. | ||
| 2. Configure endpoint: | ||
| - `OWLCLAW_MCP_ENDPOINT=http://127.0.0.1:8080/mcp` | ||
| 3. Ask your OpenClaw agent: | ||
| - "Check my AI budget." | ||
| - "Create a background task for nightly sync." | ||
|
|
||
| ## Package layout | ||
|
|
||
| - `SKILL.md`: top-level package skill. | ||
| - `skills/`: capability guides. | ||
| - `examples/`: concrete prompt examples. | ||
| - `config/owlclaw.example.json`: OpenClaw MCP config sample. | ||
|
|
||
| ## Troubleshooting | ||
|
|
||
| - If no tools appear, verify endpoint is reachable and returns `tools/list`. | ||
| - If calls fail, check OwlClaw MCP server logs and tool argument schema. | ||
|
|
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,50 @@ | ||
| --- | ||
| name: owlclaw-for-openclaw | ||
| description: Connect OpenClaw agents to OwlClaw MCP for governance and durable tasks. | ||
| metadata: | ||
| author: owlclaw | ||
| version: "0.1.0" | ||
| tags: | ||
| - openclaw | ||
| - mcp | ||
| - governance | ||
| tools: | ||
| governance_budget_status: | ||
| description: Query current budget usage for one agent. | ||
| parameters: | ||
| type: object | ||
| properties: | ||
| tenant_id: | ||
| type: string | ||
| agent_id: | ||
| type: string | ||
| required: [tenant_id, agent_id] | ||
| task_create: | ||
| description: Create one durable background task. | ||
| parameters: | ||
| type: object | ||
| properties: | ||
| workflow_name: | ||
| type: string | ||
| required: [workflow_name] | ||
| owlclaw: | ||
|
Comment on lines
+6
to
+30
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Undeclared tools referenced in skill guides The
Consumers relying on the Prompt To Fix With AIThis is a comment left during a code review.
Path: skills/owlclaw-for-openclaw/SKILL.md
Line: 6-30
Comment:
**Undeclared tools referenced in skill guides**
The `SKILL.md` frontmatter only declares two tools — `governance_budget_status` and `task_create` — but the accompanying skill guides and examples reference several additional tools that are never declared:
- `skills/governance.md` references `governance_audit_query` and `governance_rate_limit_status`
- `skills/persistent-tasks.md` references `task_status` and `task_cancel`
- `examples/background-task.md` references `task_status`
Consumers relying on the `SKILL.md` manifest to discover available tools will not find these, leading to confusion. Either add the missing tool definitions to the frontmatter or remove references to undeclared tools from the guides.
How can I resolve this? If you propose a fix, please make it concise. |
||
| binding: | ||
| type: mcp | ||
| endpoint: ${OWLCLAW_MCP_ENDPOINT} | ||
| --- | ||
|
|
||
| # OwlClaw for OpenClaw | ||
|
|
||
| Use this package to add OwlClaw governance and durable task capabilities into OpenClaw. | ||
|
|
||
| ## Installation | ||
|
|
||
| 1. Install the package in ClawHub. | ||
| 2. Set `OWLCLAW_MCP_ENDPOINT` to your OwlClaw MCP endpoint. | ||
| 3. Start your OpenClaw agent and call tools. | ||
|
|
||
| ## Included capabilities | ||
|
|
||
| - Governance: budget, audit, and rate-limit visibility. | ||
| - Persistent tasks: create, query, and cancel durable jobs. | ||
| - Business connectivity: generated MCP tools from OpenAPI via `owlclaw migrate`. | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,9 @@ | ||
| { | ||
| "mcpServers": { | ||
| "owlclaw": { | ||
| "transport": "http", | ||
| "url": "${OWLCLAW_MCP_ENDPOINT}", | ||
| "agentCardUrl": "http://127.0.0.1:8080/.well-known/agent.json" | ||
| } | ||
| } | ||
| } |
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| # Background Task Example | ||
|
|
||
| Prompt: | ||
|
|
||
| Create a background task for nightly reconciliation and report status. | ||
|
|
||
| Expected outcome: | ||
|
|
||
| OpenClaw calls `task_create` first, then `task_status` until task becomes `completed`. | ||
|
|
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| # Budget Control Example | ||
|
|
||
| Prompt: | ||
|
|
||
| Show budget status for tenant `t-1` and agent `openclaw-agent`. | ||
|
|
||
| Expected outcome: | ||
|
|
||
| OpenClaw calls `governance_budget_status` and returns current usage and remaining quota. | ||
|
|
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| # Database Connect Example | ||
|
|
||
| Prompt: | ||
|
|
||
| Create an order via business MCP tool with `order_id=ord-2026-001`. | ||
|
|
||
| Expected outcome: | ||
|
|
||
| OpenClaw discovers generated tool and executes it through OwlClaw MCP server. | ||
|
|
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,10 @@ | ||
| # Business Connect Skills | ||
|
|
||
| Use generated MCP tools from `owlclaw migrate --output-mode mcp`. | ||
|
|
||
| ## Typical flow | ||
|
|
||
| 1. Generate MCP tool definitions from OpenAPI. | ||
| 2. Register generated tools in OwlClaw MCP server. | ||
| 3. Call business tools from OpenClaw agent prompts. | ||
|
|
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,12 @@ | ||
| # Governance Skills | ||
|
|
||
| Use these tools to keep AI execution under control: | ||
|
|
||
| - `governance_budget_status` | ||
| - `governance_audit_query` | ||
| - `governance_rate_limit_status` | ||
|
|
||
| ## Example prompt | ||
|
|
||
| Check budget usage for tenant `t-1`, agent `ops-agent`. | ||
|
|
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,12 @@ | ||
| # Persistent Task Skills | ||
|
|
||
| Use durable task MCP tools: | ||
|
|
||
| - `task_create` | ||
| - `task_status` | ||
| - `task_cancel` | ||
|
|
||
| ## Example prompt | ||
|
|
||
| Create a task named `nightly_sync` and return the task id. | ||
|
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This change violates the repository policy in
AGENTS.md, which states: "Reject PRs that add skills into source code/repo content directly ... Skills must be uploaded/published via CLI." Since this commit introduces a full skill package underskills/owlclaw-for-openclaw/, it should be rejected and handled via the CLI publish flow instead of storing these distributable skill assets in the repo.Useful? React with 👍 / 👎.