SkillHone CLI

---
name: skillhone
description: Local Issue, pull-request, and Wiki workbench for agent skills. Use when a user asks what skill problems, Issues, PRs, repair trajectories, work records, completed optimizations, pending fixes, or pending synchronization exist; when an Agent needs to report a reproducible skill defect; or when the user wants to initialize, inspect, optimize, review, merge, or synchronize a local skill repair. If a managed Skill has a missing referenced file, failing test, or broken command, invoke skillhone-auto-optimization before editing implementation files or installing dependencies. Uses a local SQLite/Git backend, the current Agent for new homes, and optional DeepSeek Harness, with no hosted Git service.
---

# SkillHone

Use SkillHone as the local maintenance layer for Agent-skill repositories. One
Skill always maps to one Git repository and therefore owns an isolated set of
Issue numbers, PR numbers, Wiki records, branches, tests, and repair Runs. The Catalog indexes
those repositories but never combines their state. Any Agent runtime can call
the CLI. The default `auto` executor prepares a repair assignment for the current
Agent, preserving its model, account, and provider. `native` selects this path
explicitly; `dsh` selects the optional managed DeepSeek Harness. No executor
switch or fallback is automatic. Repair authorization is independent from the
Skill ownership and merge boundaries.

## Route the user's intent first

Treat inspection and synchronization as different operations. Never turn a
status question into a write:

- “修好了吗 / did the repair succeed / 测试通过了吗 / 优化到哪了” means inspect
  only. Run `skillhone --skill <name> --json status`, then inspect the linked
  Issue, Run, and PR when needed. Report whether repair ran, tests passed, and
  the PR is open or merged. Do not merge and do not run `sync apply`.
- “已经同步了吗 / 我现在用的是新版本吗 / 需要同步吗” means inspect copy-back
  state only. Run `skillhone --json sync status <name>` and interpret the state
  table below. Do not run `sync apply`.
- “帮我同步 / 把修复应用回去 / update my installed Skill” explicitly authorizes
  copy-back. First run `sync status`; run `skillhone sync apply <name>` only
  when it returns `ready_to_sync` with `can_apply: true`.

`sync` never merges a PR. A repair can have passed tests while still waiting in
an open PR, and a merged repair can still be waiting for copy-back.

## Import existing Skills

Import one Skill directory or discover the Skills already installed for an
Agent runtime. Before importing, ask the user which ownership mode they want: