Skip to content

feat(skill): add owlclaw-for-openclaw package#556

Open
yeemio wants to merge 1 commit intoopenclaw:mainfrom
yeemio:feat/owlclaw-for-openclaw-skill-pack
Open

feat(skill): add owlclaw-for-openclaw package#556
yeemio wants to merge 1 commit intoopenclaw:mainfrom
yeemio:feat/owlclaw-for-openclaw-skill-pack

Conversation

@yeemio
Copy link

@yeemio yeemio commented Feb 28, 2026

Summary\n- add \skills/owlclaw-for-openclaw\ package for OpenClaw users\n- include SKILL metadata, usage guides, examples, and MCP config sample\n\n## Why\n- provides a ready-to-install skill pack that connects OpenClaw to OwlClaw MCP governance and durable task tools\n\n## Validation\n- package assets validated in OwlClaw repo tests before copy\n

@vercel
Copy link
Contributor

vercel bot commented Feb 28, 2026

@yeemio is attempting to deploy a commit to the Amantus Machina Team on Vercel.

A member of the Team first needs to authorize it.

Copy link

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6377e4bb19

ℹ️ About Codex in GitHub

Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".

@@ -0,0 +1,50 @@
---

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Remove in-repo skill package additions

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 under skills/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 👍 / 👎.

@greptile-apps
Copy link
Contributor

greptile-apps bot commented Feb 28, 2026

Greptile Summary

This PR adds a new skills/owlclaw-for-openclaw skill package (README, SKILL manifest, config sample, examples, and skill guides) intended to connect OpenClaw agents to OwlClaw MCP governance and durable task tooling.

However, this PR violates a repository policy defined in AGENTS.md:

"Reject PRs that add skills into source code/repo content directly (for example under skills/ or seed-only additions intended as published skills). Skills must be uploaded/published via CLI."

All nine files added by this PR live directly under skills/owlclaw-for-openclaw/ in the source tree, which is exactly the pattern the policy prohibits. The skill content should instead be published to ClawHub via the CLI tooling rather than committed to the repository.

Additional issues found:

  • The SKILL.md frontmatter declares only governance_budget_status and task_create, but the skill guides (skills/governance.md, skills/persistent-tasks.md) and examples (examples/background-task.md) reference four additional tools (governance_audit_query, governance_rate_limit_status, task_status, task_cancel) that are absent from the manifest.

Confidence Score: 0/5

  • This PR should not be merged — it directly violates the repository's stated policy against committing skills as source files.
  • AGENTS.md explicitly states that PRs adding skills directly under skills/ must be rejected and that skills must be published via CLI instead. Every file in this PR falls squarely under that prohibition.
  • All nine files under skills/owlclaw-for-openclaw/ violate the policy; none should be merged as-is.

Last reviewed commit: 6377e4b

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

9 files reviewed, 1 comment

Edit Code Review Agent Settings | Greptile

Comment on lines +6 to +30
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:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Prompt To Fix With AI
This 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant