feat(skills): discover Claude Code skills from .claude/skills - #43
Conversation
Import skills from ~/.claude/skills and .claude/skills when compat.importClaudeSkills is enabled (default on). Native .klaatai/skills entries win on name collisions. /skill list shows scope and source directory. Fixes KlaatAI#38
|
🤖 KlaatAI Review Bot (powered by Klaatu, advisory only — a maintainer makes the real call) Issue match Test coverage Correctness concerns Verdict This is an automated review to help triage faster, not a gate. Nothing here blocks merging. |
|
@syf2211 Really appreciate you taking the time to improve KlaatCode. Your contribution helps make the project better for everyone. If you haven't already, we'd love it if you could ⭐ star the repository and follow https://github.com/KlaatAI on GitHub to stay updated with new features and releases. Feel free to keep using KlaatAI for your projects, and don't hesitate to open more issues, suggest ideas, or submit future PRs—we're always happy to have contributors like you in the community. Looking forward to seeing your next contribution. Meantime please follow KlaatAI socials and if ok you can join discord too for suggestions on project, thanks Happy coding! 🚀 |
Summary
Add compatibility discovery for Claude Code skills stored under
~/.claude/skillsand.claude/skills/<name>/SKILL.md, gated bycompat.importClaudeSkills(default on). Native.klaatai/skillsentries continue to win on name collisions.Motivation
Many developers already maintain Claude Code skill libraries. KlaatCode should discover those skills without manual migration so users can invoke them via
/skillor/<name>.Fixes #38
Changes
src/skills/loader.tswith shared frontmatter parsingcompat.importClaudeSkillsconfig flag (opt-out)/skill list(e.g.project · .claude/skills)Tests
bun run typecheck— passbun test— pass (159 tests, including 6 new loader tests)Notes