Skip to content

Add WorkBuddy and Kimi adapters for skill scanning and lifecycle - #12

Open
xtysing wants to merge 1 commit into
GrubbyLee:mainfrom
xtysing:feat-workbuddy-kimi-adapters
Open

Add WorkBuddy and Kimi adapters for skill scanning and lifecycle#12
xtysing wants to merge 1 commit into
GrubbyLee:mainfrom
xtysing:feat-workbuddy-kimi-adapters

Conversation

@xtysing

@xtysing xtysing commented Aug 9, 2026

Copy link
Copy Markdown

What

Add first-party adapters for two more AI clients so skm can scan, recommend, deduplicate, audit, and manage their skills and MCP servers.

Platform Skill locations (scanned) MCP config
WorkBuddy ~/.workbuddy/skills (user), <cwd>/.workbuddy/skills (project), plugin cache ~/.workbuddy/plugins/cache/{marketplace}/{plugin}/{version}/skills + ~/.workbuddy/plugins/marketplaces/{marketplace}/plugins/{plugin}/skills (plugin) ~/.workbuddy/mcp.json
Kimi Kimi CLI ~/.kimi/skills, Kimi Code $KIMI_CODE_HOME/skills (default ~/.kimi-code/skills), Kimi Desktop daimon-share/daimon/skills (cross-platform candidates: %APPDATA% / ~/Library/Application Support / ~/.config), plus project-level .kimi/skills and .kimi-code/skills $KIMI_CODE_HOME/mcp.json

Changes

  • src/adapters/workbuddy.js (new) — conservative read-only scan: user/project/plugin skill dirs + ~/.workbuddy/mcp.json mcpServers. Never reads sensitive fields (e.g. env).
  • src/adapters/kimi.js (new) — scans Kimi CLI / Kimi Code / Kimi Desktop brand dirs only; deliberately does not fall back to ~/.claude/skills / ~/.codex/skills / ~/.agents/skills to avoid double-counting skills already covered by other adapters or shared ownership.
  • src/paths.js — adds WorkBuddy / Kimi path constants. Kimi Desktop uses a cross-platform candidate array (same pattern as existing CURSOR_SKILLS_DIRS); non-existent dirs are skipped silently.
  • src/commands/scan.js — wires both adapters into scan, summary table, and archived counters.
  • src/commands/lifecycle.jstargetRoots() now maps workbuddy~/.workbuddy/skills and kimi → Kimi Desktop dir, enabling skm install/update/rollback --tool workbuddy|kimi. Update/rollback/disable/enable work out of the box since they operate on catalog skill paths.
  • bin/skm.js / src/i18n.js / src/commands/web.js--tool whitelist, help texts, dashboard tool list and filter values updated.

Verification (Windows 11)

skm scan  → WorkBuddy 293 skills (32 user / 261 plugin) + 2 MCP; Kimi 34 skills
skm list --tool workbuddy / --tool kimi        ✓
skm search <term> --tool kimi                  ✓
skm install <dir> --tool workbuddy --dry-run   ✓ (plans to ~/.workbuddy/skills)
skm install <dir> --tool kimi --dry-run        ✓ (plans to Kimi Desktop skills)

All new paths are optional: on machines without WorkBuddy or Kimi installed the scan is a no-op for those tools.

Notes

  • Kimi Desktop path layout is the community-observed convention {platform-data-dir}/kimi-desktop/daimon-share/daimon/skills (verified on Windows; macOS/Linux candidates included for future coverage).
  • state command remains Claude Code-only (native skillOverrides mechanism is not present in other clients).
  • Lifecycle targetRoots keeps the original safe default: without --tool, only claude/codex are targeted.

- New workbuddy adapter: scans ~/.workbuddy/skills, project-level .workbuddy/skills, plugin cache skills, and ~/.workbuddy/mcp.json
- New kimi adapter: scans Kimi CLI (~/.kimi/skills), Kimi Code ($KIMI_CODE_HOME/skills), and Kimi Desktop (cross-platform path candidates)
- Wire adapters into scan overview, web dashboard, and lifecycle commands (install/update/rollback)
- Add workbuddy/kimi to CLI --tool whitelist and help texts
@GrubbyLee

GrubbyLee commented Aug 10, 2026

Copy link
Copy Markdown
Owner

Thanks for taking the time to push this forward. The direction is good, and this definitely moves us closer to broader client coverage.

I’m going to hold this PR for now, because there are two issues we need to tighten up before merging:

  1. The lifecycle path for --tool kimi is not quite right yet. On non-Windows platforms it can point to the wrong directory, so install/update/rollback would land in the wrong place.
  2. The English help and the existing tests are not fully aligned with the new tool list. Right now the branch introduces a regression in the help/test path.

These are implementation issues, not direction issues. We do want to keep going along this line, and we’ll fix it properly on our side so the Kimi/WorkBuddy support lands in a stable way. Thanks again for the contribution.

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.

2 participants