-
-
Notifications
You must be signed in to change notification settings - Fork 69.1k
[Feature]: Support .agents/skills directory for cross-agent skill discovery #8822
Copy link
Copy link
Closed
Closed
Copy link
Labels
enhancementNew feature or requestNew feature or request
Description
Summary
Support the emerging .agents/skills/ directory convention for per-project skill discovery, as proposed in agentskills/agentskills#15.
Motivation
Currently each AI coding tool uses its own location for skills (.claude/skills/, .github/skills/, etc.), forcing users to maintain symlinks or duplicate files across projects.
The .agents/skills/ convention is gaining adoption across the ecosystem:
- Already supported: VS Code, Codex, Gemini CLI, Goose, Amp, VTCode, Pi, Mistral Vibe, OpenCode
- Pending: Claude Code, GitHub (internal), Cursor, Qwen Code
Proposed Behavior
- On startup/project load, check for
.agents/skills/directory in the workspace root - If present, load any valid skill definitions (SKILL.md files) from it
- Treat these as additional skills alongside the configured global skills directory
- Project-level skills could optionally override or extend global skills
Benefits
- Allows skill files to be committed per-project without vendor lock-in
- Enables portable skill directories that work across multiple AI agents
- Aligns OpenClaw with the emerging industry convention
- Users can share projects with embedded skills that "just work"
References
- Original proposal: Proposal: include a standard folder where agent skills should be agentskills/agentskills#15
- Convention discussion and adoption tracking in that issue
lobster-biscuit
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
enhancementNew feature or requestNew feature or request
Type
Fields
Give feedbackNo fields configured for issues without a type.