Sync Skill to Jay

Treat jay-skills/skills/<skill-name> as the sole publishable source of truth. ~/.agents/skills/<skill-name> is an installation artifact managed by npx skills add, not a source to copy back over the repository.

Authorization boundary

After a Skill is created or updated, ask once whether the user wants to synchronize, publish, and reinstall it. The confirmation must identify the repository, Skill name, publish branch, Git push, and global installation. One affirmative answer authorizes the complete workflow below, including the bounded one-time SSH fallback described under "Commit and push". Ask again only when a conflict, unexpected dirty worktree, identity mismatch, new credentials, validation failure, or scope expansion requires a new decision.

Do not infer permission to publish another Skill, rewrite Git history, force-push, alter remotes, or expose a private Skill.

Source resolution

1. Locate the local jay-skills checkout and verify that its remote represents nangongwentian-fe/jay-skills.
2. Resolve the exact target as skills/<skill-name> and prove it stays inside the repository's skills/ directory.
3. For an existing Skill, edit and validate the repository target directly.
4. For a new Skill created elsewhere, import its complete directory only when the repository target does not yet exist.
5. If an external or installed copy differs from an existing repository target, never copy it over the target. Show the relevant diff and port only the intended changes into the repository source.

Never move, delete, or rewrite an explicit project source or an installed copy merely because publication succeeds.