[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78ENPFXFNQPTPB3S1R1D1Q5":3,"skill-same:01M78ENPFXFNQPTPB3S1R1D1Q5":51},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":6,"ownerDescription":29,"updatedAt":30,"install":31,"resources":44},"01M78ENPFXFNQPTPB3S1R1D1Q5","skill-sync-manager",null,"Inspect, configure, safely edit, recover, link, and synchronize user-authored Agent Skills managed by Skill Sync. Use before modifying any Skill path that may be managed, when setting up Skill Sync with a private data repository, when exposing Skills to Codex, WorkBuddy, Kimi Code, or Claude Code, and when diagnosing conflicts, stale or tampered deployments, edit sessions, or synchronization failures.","lirt1231\u002Fskill-sync","lirt1231","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F46098996?v=4","01M78ENM89SGSJ3QSQQ9WK7GVX","Haotian Li 李昊天","01M78ENM8YVGTP6ZJHWSQFQ1RR",0,"MIT","https:\u002F\u002Fgithub.com\u002Flirt1231\u002Fskill-sync\u002Fblob\u002Fmain\u002Fskills\u002Fskill-sync-manager\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: skill-sync-manager\ndescription: Inspect, configure, safely edit, recover, link, and synchronize user-authored Agent Skills managed by Skill Sync. Use before modifying any Skill path that may be managed, when setting up Skill Sync with a private data repository, when exposing Skills to Codex, WorkBuddy, Kimi Code, or Claude Code, and when diagnosing conflicts, stale or tampered deployments, edit sessions, or synchronization failures.\n---\n\n# Skill Sync Manager\n\nUse the `skill-sync` executable as the control plane for managed Skills. Treat\nAgent Skill paths and rendered deployments as read-only outputs. Modify a\nmanaged Skill only through the isolated workspace returned by `skill-sync edit\nbegin`.\n\n## Establish the environment\n\n1. Check that the CLI exists and is current enough:\n\n   ```bash\n   skill-sync version\n   skill-sync managed check --help\n   skill-sync edit begin --help\n   ```\n\n   This workflow requires Skill Sync 0.1.0 or later. If a command is missing,\n   stop and ask the user to install or upgrade the public tool repository. Do\n   not replace a missing command with direct filesystem edits.\n2. Run `skill-sync preview --json`. This is a cached, local inspection and does\n   not fetch the network.\n3. If Skill Sync is not initialized, ask for the user's private Skill data\n   repository URL before running:\n\n   ```bash\n   skill-sync init --repo \u003Cprivate-skill-data-repository>\n   ```\n\n   Never use `https:\u002F\u002Fgithub.com\u002Flirt1231\u002Fskill-sync` as the data repository.\n   That public repository distributes the tool and this manager Skill; the\n   user's authored Skills belong in a separate repository that should normally\n   be private.\n4. Run `skill-sync doctor --json` before the first mutation and after setup.\n\nThe default canonical root is `~\u002F.agents\u002Fskills`. Per-machine configuration is\nstored under `~\u002F.config\u002Fskill-sync\u002Fconfig.json`; rendered deployments, edit\nsessions, backups, and receipts stay in the platform-specific local data root.\nDo not copy those machine-local files into the user's Skill data repository.\n\n## Mandatory pre-edit gate\n\nBefore writing, deleting, renaming, or generating files in any existing Skill:\n\n1. Identify the exact path and concrete client ID. Supported client IDs are\n   `codex`, `workbuddy`, `kimi-code`, and `claude-code`.\n2. Run the read-only ownership check:\n\n   ```bash\n   skill-sync managed check \u003Cexact-path-or-skill-name> --client \u003Cclient-id> --json\n   ```\n\n   Omit `--client` only for an unambiguous canonical path or logical Skill name.\n3. Read command data from `.result` in the JSON envelope and enforce it:\n   - `managed=false`: Skill Sync does not control the path. Continue with the\n     normal local workflow, but never import or globalize it implicitly.\n   - `managed=true, healthy=true`: do not edit the checked path, deployment, or\n     canonical source directly. Use a managed edit session.\n   - `managed=true, healthy=false`: stop and diagnose or recover first.\n   - Ambiguous output, a safety error, or exit code `4`: fail closed. Report the\n     details and never guess ownership.\n\nInclude this ownership check in every execution plan that can modify an\nexisting Skill. A writable path is not evidence that direct editing is safe.\n\n## Choose the authored scope\n\nUse the smallest scope matching the request:\n\n- `--base`: shared content that should reach every configured client.\n- `--family \u003Cid>`: content shared by a registered Agent family. The `kimi`\n  family currently contains only `kimi-code`.\n- `--client \u003Cid>`: content intended for one concrete client only.\n\nNever widen Client to Family or Base for convenience. Ask the user when two\npossible scopes have different effects.\n\n## Run a managed edit\n\n1. Create exactly one session:\n\n   ```bash\n   skill-sync edit begin \u003Cskill> --base --actor \u003Cclient-id> --json\n   skill-sync edit begin \u003Cskill> --family \u003Cfamily-id> --actor \u003Cclient-id> --json\n   skill-sync edit begin \u003Cskill> --client \u003Cclient-id> --actor \u003Cclient-id> --json\n   ```\n\n2. Read `.result.session_id` and `.result.workspace_path`. Edit only that exact\n   workspace. Never edit its parent session directory, baseline snapshot,\n   canonical source, rendered deployment, or Agent link.\n3. Inspect in order:\n\n   ```bash\n   skill-sync edit diff \u003Csession-id> --json\n   skill-sync edit validate \u003Csession-id> --json\n   skill-sync edit impact \u003Csession-id> --json\n   ```\n\n   For a Family session, add `--resolved-client \u003Cclient-id>` to `edit diff` when\n   one concrete-client view needs separate inspection.\n4. Stop when validation is invalid, the authored baseline is stale, impact is\n   blocked, scope differs from the request, or any client state is unsafe.\n5. Summarize the authored diff, resolved client changes, and impact for the\n   user. Require confirmation before applying unless the user already gave\n   explicit authorization for this exact reviewed change.\n6. Apply and read back the result:\n\n   ```bash\n   skill-sync edit apply \u003Csession-id> --json\n   skill-sync doctor --json\n   ```\n\n7. Stop on `cleanup_pending` or `needs-recovery`. Preserve every reported\n   receipt, backup, quarantine, and recovery path.\n\nUse `skill-sync edit abort \u003Csession-id> --json` only to discard an active\nworkspace. Do not abort `applying` or `needs-recovery` sessions. Use\n`skill-sync edit delete \u003Csession-id> --json` only when the user explicitly asks\nto remove deletable local session history.\n\n`edit apply` never commits or pushes Git. Synchronization is a separate action\nthat requires explicit user authorization.\n\n## Recover a tampered deployment\n\nWhen inspection reports `tampered-render`, preview without mutation:\n\n```bash\nskill-sync edit recover \u003Cskill> --client \u003Cclient-id> --json\n```\n\nRequire the user to choose one action:\n\n- Preserve changes: use `--capture`, then review the new session through diff,\n  validate, impact, and apply.\n- Discard changes: use `--discard` to quarantine and rebuild from canonical.\n\nNever choose capture versus discard automatically. Layered deployment previews\noffer discard only. A single-client recovery must not attempt to repair a\nmulti-client transactional `needs-recovery` state.\n\n## Synchronize and expose Skills\n\n1. Run `skill-sync preview --json` to explain the next action without network\n   access.\n2. Run `skill-sync doctor --json` and stop on unsafe ownership, real-directory\n   conflicts, damaged deployments, or unresolved receipts.\n3. Select only Skills explicitly requested:\n\n   ```bash\n   skill-sync scan --json\n   skill-sync select \u003Cskill-name>...\n   ```\n\n4. Import existing real Agent-local Skills through the CLI instead of moving\n   them manually:\n\n   ```bash\n   skill-sync import --agent \u003Ccodex|claude|workbuddy> \u003Cskill-name>...\n   ```\n\n5. Use `skill-sync sync` for the explicit network synchronization workflow.\n   It may fetch, pull, commit, or push according to the previewed state.\n6. Expose selected Skills to detected clients with `skill-sync link`. Restrict\n   scope with repeatable `--skill` and `--agent` filters when requested.\n7. Start `skill-sync web` only when the user wants the local visual interface.\n\nStop rather than selecting a conflict winner when local and remote changes\ntouch the same synchronization unit. Do not force-push.\n\n## Install or update this manager Skill\n\nThe distributable source is\n`https:\u002F\u002Fgithub.com\u002Flirt1231\u002Fskill-sync\u002Ftree\u002Fmain\u002Fskills\u002Fskill-sync-manager`.\n\n- For a first installation, follow the public repository README and refuse to\n  overwrite an existing destination directory.\n- If the installed manager is already managed, run the mandatory ownership\n  check and update it through a Base edit session. Copy the repository version\n  only into that session's workspace, then diff, validate, impact, and request\n  confirmation before apply.\n- Never update this Skill by writing through an Agent link or by replacing its\n  canonical directory in place.\n\n## Safety rules\n\n- Never modify a managed Agent path, rendered deployment, or canonical source\n  directly.\n- Never delete or overwrite a real directory in an Agent Skill location.\n- Stop on `conflict`, `wrong-link`, `tampered-render`, ambiguous ownership,\n  stale baselines, or locally changed content.\n- Never upload bundled or third-party Skills without explicit user direction.\n- Never expose credentials, private Skill content, edit sessions, backups,\n  receipts, or machine-local absolute paths in a public repository or report.\n- Never force-push or choose a conflict winner automatically.\n","# Skill Sync Manager\n\nUse the `skill-sync` executable as the control plane for managed Skills. Treat\nAgent Skill paths and rendered deployments as read-only outputs. Modify a\nmanaged Skill only through the isolated workspace returned by `skill-sync edit\nbegin`.\n\n## Establish the environment\n\n1. Check that the CLI exists and is current enough:\n\n   ```bash\n   skill-sync version\n   skill-sync managed check --help\n   skill-sync edit begin --help\n   ```\n\n   This workflow requires Skill Sync 0.1.0 or later. If a command is missing,\n   stop and ask the user to install or upgrade the public tool repository. Do\n   not replace a missing command with direct filesystem edits.\n2. Run `skill-sync preview --json`. This is a cached, local inspection and does\n   not fetch the network.\n3. If Skill Sync is not initialized, ask for the user's private Skill data\n   repository URL before running:\n\n   ```bash\n   skill-sync init --repo \u003Cprivate-skill-data-repository>\n   ```\n\n   Never use `https:\u002F\u002Fgithub.com\u002Flirt1231\u002Fskill-sync` as the data repository.\n   That public repository distributes the tool and this manager Skill; the\n   user's authored Skills belong in a separate repository that should normally\n   be private.\n4. Run `skill-sync doctor --json` before the first mutation and after setup.\n\nThe default canonical root is `~\u002F.agents\u002Fskills`. Per-machine configuration is\nstored under `~\u002F.config\u002Fskill-sync\u002Fconfig.json`; rendered deployments, edit\nsessions, backups, and receipts stay in the platform-specific local data root.\nDo not copy those machine-local files into the user's Skill data repository.\n\n## Mandatory pre-edit gate\n\nBefore writing, deleting, renaming, or generating files in any existing Skill:\n\n1. Identify the exact path and concrete client ID. Supported client IDs are\n   `codex`, `workbuddy`, `kimi-code`, and `claude-code`.\n2. Run the read-only ownership check:\n\n   ```bash\n   skill-sync managed check \u003Cexact-path-or-skill-name> --client \u003Cclient-id> --json\n   ```\n\n   Omit `--client` only for an unambiguous canonical path or logical Skill name.\n3. Read command data from `.result` in the JSON envelope and enforce it:\n   - `managed=false`: Skill Sync does not control the path. Continue with the\n     normal local workflow, but never import or globalize it implicitly.\n   - `managed=true, healthy=true`: do not edit the checked path, deployment, or\n     canonical source directly. Use a managed edit session.\n   - `managed=true, healthy=false`: stop and diagnose or recover first.\n   - Ambiguous output, a safety error, or exit code `4`: fail closed. Report the\n     details and never guess ownership.\n\nInclude this ownership check in every execution plan that can modify an\nexisting Skill. A writable path is not evidence that direct editing is safe.\n\n## Choose the authored scope\n\nUse the smallest scope matching the request:\n\n- `--base`: shared content that should reach every configured client.\n- `--family \u003Cid>`: content shared by a registered Agent family. The `kimi`\n  family currently contains only `kimi-code`.\n- `--client \u003Cid>`: content intended for one concrete client only.\n\nNever widen Client to Family or Base for convenience. Ask the user when two\npossible scopes have different effects.\n\n## Run a managed edit\n\n1. Create exactly one session:\n\n   ```bash\n   skill-sync edit begin \u003Cskill> --base --actor \u003Cclient-id> --json\n   skill-sync edit begin \u003Cskill> --family \u003Cfamily-id> --actor \u003Cclient-id> --json\n   skill-sync edit begin \u003Cskill> --client \u003Cclient-id> --actor \u003Cclient-id> --json\n   ```\n\n2. Read `.result.session_id` and `.result.workspace_path`. Edit only that exact\n   workspace. Never edit its parent session directory, baseline snapshot,\n   canonical source, rendered deployment, or Agent link.\n3. Inspect in order:\n\n   ```bash\n   skill-sync edit diff \u003Csession-id> --json\n   skill-sync edit validate \u003Csession-id> --json\n   skill-sync edit impact \u003Csession-id> --json\n   ```\n\n   For a Family session, add `--resolved-client \u003Cclient-id>` to `edit diff` when\n   one concrete-client view needs separate inspection.\n4. Stop when validation is invalid, the authored baseline is stale, impact is\n   blocked, scope differs from the request, or any client state is unsafe.\n5. Summarize the authored diff, resolved client changes, and impact for the\n   user. Require confirmation before applying unless the user already gave\n   explicit authorization for this exact reviewed change.\n6. Apply and read back the result:\n\n   ```bash\n   skill-sync edit apply \u003Csession-id> --json\n   skill-sync doctor --json\n   ```\n\n7. Stop on `cleanup_pending` or `needs-recovery`. Preserve every reported\n   receipt, backup, quarantine, and recovery path.\n\nUse `skill-sync edit abort \u003Csession-id> --json` only to discard an active\nworkspace. Do not abort `applying` or `needs-recovery` sessions. Use\n`skill-sync edit delete \u003Csession-id> --json` only when the user explicitly asks\nto remove deletable local session history.\n\n`edit apply` never commits or pushes Git. Synchronization is a separate action\nthat requires explicit user authorization.\n\n## Recover a tampered deployment\n\nWhen inspection reports `tampered-render`, preview without mutation:\n\n```bash\nskill-sync edit recover \u003Cskill> --client \u003Cclient-id> --json\n```\n\nRequire the user to choose one action:\n\n- Preserve changes: use `--capture`, then review the new session through diff,\n  validate, impact, and apply.\n- Discard changes: use `--discard` to quarantine and rebuild from canonical.\n\nNever choose capture versus discard automatically. Layered deployment previews\noffer discard only. A single-client recovery must not attempt to repair a\nmulti-client transactional `needs-recovery` state.\n\n## Synchronize and expose Skills\n\n1. Run `skill-sync preview --json` to explain the next action without network\n   access.\n2. Run `skill-sync doctor --json` and stop on unsafe ownership, real-directory\n   conflicts, damaged deployments, or unresolved receipts.\n3. Select only Skills explicitly requested:\n\n   ```bash\n   skill-sync scan --json\n   skill-sync select \u003Cskill-name>...\n   ```\n\n4. Import existing real Agent-local Skills through the CLI instead of moving\n   them manually:\n\n   ```bash\n   skill-sync import --agent \u003Ccodex|claude|workbuddy> \u003Cskill-name>...\n   ```\n\n5. Use `skill-sync sync` for the explicit network synchronization workflow.\n   It may fetch, pull, commit, or push according to the previewed state.\n6. Expose selected Skills to detected clients with `skill-sync link`. Restrict\n   scope with repeatable `--skill` and `--agent` filters when requested.\n7. Start `skill-sync web` only when the user wants the local visual interface.\n\nStop rather than selecting a conflict winner when local and remote changes\ntouch the same synchronization unit. Do not force-push.\n\n## Install or update this manager Skill\n\nThe distributable source is\n`https:\u002F\u002Fgithub.com\u002Flirt1231\u002Fskill-sync\u002Ftree\u002Fmain\u002Fskills\u002Fskill-sync-manager`.\n\n- For a first installation, follow the public repository README and refuse to\n  overwrite an existing destination directory.\n- If the installed manager is already managed, run the mandatory ownership\n  check and update it through a Base edit session. Copy the repository version\n  only into that session's workspace, then diff, validate, impact, and request\n  confirmation before apply.\n- Never update this Skill by writing through an Agent link or by replacing its\n  canonical directory in place.\n\n## Safety rules\n\n- Never modify a managed Agent path, rendered deployment, or canonical source\n  directly.\n- Never delete or overwrite a real directory in an Agent Skill location.\n- Stop on `conflict`, `wrong-link`, `tampered-render`, ambiguous ownership,\n  stale baselines, or locally changed content.\n- Never upload bundled or third-party Skills without explicit user direction.\n- Never expose credentials, private Skill content, edit sessions, backups,\n  receipts, or machine-local absolute paths in a public repository or report.\n- Never force-push or choose a conflict winner automatically.\n",{"name":5,"description":7},"main","3d2088d256ff5fc362124b741ed50403c978688b","skills\u002Fskill-sync-manager","https:\u002F\u002Fgithub.com\u002Flirt1231\u002Fskill-sync","https:\u002F\u002Fgithub.com\u002Flirt1231","PhD candidate @ HIT, interested in self-evolving agents, LLM and Non-Parametric Bayesian.","2026-10-02 04:19:45",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add lirt1231\u002Fskill-sync --skill skill-sync-manager",{"tool":37,"command":38},"bunx","bunx skills add lirt1231\u002Fskill-sync --skill skill-sync-manager",{"tool":40,"command":41},"pnpm","pnpm dlx skills add lirt1231\u002Fskill-sync --skill skill-sync-manager","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flirt1231\u002Fskill-sync\u002Fblob\u002Fmain\u002Fskills\u002Fskill-sync-manager\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",269,"https:\u002F\u002Fgithub.com\u002Flirt1231\u002Fskill-sync\u002Fblob\u002Fmain\u002Fskills\u002Fskill-sync-manager\u002Fagents\u002Fopenai.yaml",[52,58,64,70,76,82],{"skillNo":53,"name":54,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":55,"categories":56,"keywords":57,"publishedAt":19},"01M78EP5CQJ9XFXNAJAVZ369RR","kimi","https:\u002F\u002Fgithub.com\u002Flirt1231\u002Fskill-sync\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvariant-overlay\u002Fvariants\u002Fkimi\u002FSKILL.md",[],[],{"skillNo":59,"name":60,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M78EP3BSZAA13BM4QQD4W9WF","kimi-code","https:\u002F\u002Fgithub.com\u002Flirt1231\u002Fskill-sync\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvariant-overlay\u002Fvariants\u002Fkimi-code\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M78EP1BVR75XXSQ9ZEQVQHB1","base-only","https:\u002F\u002Fgithub.com\u002Flirt1231\u002Fskill-sync\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvariant-overlay\u002Fexpected\u002Fbase-only\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M78ENZ3N5MM25RDZ5ZEX4NBE","base-family","https:\u002F\u002Fgithub.com\u002Flirt1231\u002Fskill-sync\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvariant-overlay\u002Fexpected\u002Fbase-family\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M78ENWTRQK9W90AQGWNP4GAM","base-family-client","https:\u002F\u002Fgithub.com\u002Flirt1231\u002Fskill-sync\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvariant-overlay\u002Fexpected\u002Fbase-family-client\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M78ENVS1NF4SE7VG46R0C1AM","base-client","https:\u002F\u002Fgithub.com\u002Flirt1231\u002Fskill-sync\u002Fblob\u002Fmain\u002Ftests\u002Ffixtures\u002Fvariant-overlay\u002Fexpected\u002Fbase-client\u002FSKILL.md",[],[]]