Replies: 1 comment
-
|
Update: I noticed the Instead, I'd like to reframe this as a question: Should these skills be coupled to a third-party registry (OpenClaw/ClawHub)? If OpenClaw integration is intentional and staying, it would help to:
|
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Problem
The SKILL.md files in
/skills/includeopenclawmetadata in their YAML frontmatter:This appears across all skills (gws-calendar, gws-gmail, gws-drive, etc.).
Why this is problematic
Vendor lock-in on an open format — Agent skills are just markdown files with YAML frontmatter. Introducing a third-party registry standard (
openclaw) as metadata creates an unnecessary dependency on an external specification that doesn't govern how skills are consumed.Skills should be tool-agnostic — The
name,version, anddescriptionfields in the frontmatter are sufficient. Categorization and binary requirements can be expressed without adopting an external standard.Confusion for contributors — Developers looking at these skills may assume
openclawis a required part of the skill format, when it has no effect on how Claude Code (or any other AI coding agent) processes the skill.Suggestion
Remove the
openclawblock from the frontmatter and keep the existing standard fields (name,version,description). If categorization or requirements metadata is needed, use flat keys that don't reference an external standard:Beta Was this translation helpful? Give feedback.
All reactions