skills/skill-delete/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: skill-delete
-description: Remove a skill from the jsc skill set safely. List skills, let the user pick, inventory every file referencing the skill via a sub agent, fix each affected file through decision-tree questions until guideline checks pass, then delete the skill and open a PR via jsc-git pr. Use only for removal; not for renaming (use skill-update).
+description: Remove a skill from the jsc skill set safely. List skills starting from the Gitea canonical marketplace (cloning any missing domain repo), let the user pick, inventory every file referencing the skill via a sub agent, fix each affected file through decision-tree questions until guideline checks pass, then delete the skill, deep-verify each installed CLI's on-disk skill and hook storage is clean, and open a PR via jsc-git pr. Use only for removal; not for renaming (use skill-update).
 ---
 
 # skill-delete — delete a skill
@@ -9,14 +9,16 @@ Single source of guidelines: [`../../references/guidelines.md`](../../references
 
 ## Flow
 
-1. List every skill in the skill set: scan `jsc-*/skills/*/SKILL.md`.
-2. Let the user pick the skill to delete. Options state the impact scope: which skills reference it, and that its command stops working after deletion.
-3. Inventory every file related to the skill — this step MUST run as a sub agent:
+1. Query Gitea for the canonical skill set first: run `jsc-gitea/tools/gitea.sh api GET /repos/plugins/jsc/raw/.claude-plugin/marketplace.json` to get the authoritative domain list, then scan local `jsc-*/skills/*/SKILL.md` and present a "domain / name / description" list covering every domain in the marketplace. Completion condition: the list covers all marketplace domains.
+2. For any marketplace domain whose repo is missing from the working directory, clone it first (`gitea.sh clone-url plugins/{domain}`), then rescan. Completion condition: every domain repo exists locally.
+3. Let the user pick the skill to delete. Options state the impact scope: which skills reference it, and that its command stops working after deletion.
+4. Inventory every file related to the skill — this step MUST run as a sub agent:
    - `grep -r` for the skill name and `/jsc-{domain}:{name}` across all jsc-* repositories
    - References in other SKILL.md files, the domain README's 「Skills 目錄」 section, the two marketplace.json files in `plugins/jsc` plus their synced copies in every domain repo, `tools/`, and the `jsc-hooks` wiring
-4. For each affected file:
+5. For each affected file:
    1. Decide whether the file needs a fix to keep its current behavior after the deletion. If no fix is needed, **skip the rest of this loop**.
    2. Ask for fix details via the `jsc-ask:ask` decision tree (call a replacement skill? inline the flow? drop the feature too?). Every option states its impact scope.
-   3. After fixing, check the guidelines.md audit checklist. On failure, return to step 4.2.
-5. Delete the skill directory `skills/{name}/`, then sync the domain README and bump the version in all three manifests.
-6. Call `jsc-git:pr` to open a Push Request.
+   3. After fixing, check the guidelines.md audit checklist. On failure, return to step 5.2.
+6. Delete the skill directory `skills/{name}/`, then sync the domain README and bump the version in all three manifests.
+7. Deep-delete verification — this step MUST run as a sub agent: after deleting via each CLI's native plugin commands, physically inspect every installed CLI's on-disk skill and hook storage. Detect CLIs via `jsc-cli/tools/detect-clis.sh`; check Claude's `~/.claude/plugins/cache/` and hook entries in settings, plus the equivalent locations for codex / copilot / antigravity / kiro. Confirm no file or hook wiring for the deleted skill remains. Completion condition: every location checked and clean; remove any leftover by hand and recheck.
+8. Call `jsc-git:pr` to open a Push Request.

skills/skill-new/SKILL.md

@@ -14,7 +14,7 @@ Single source of guidelines: [`../../references/guidelines.md`](../../references
    - Trigger (when to use, when not to, trigger keywords)
    - Input and output (can a standard input/output flow move down to `tools/`; does it need Gitea operations — if so, make the skill use `jsc-gitea/tools/gitea.sh` + token)
    - Owning domain (list the existing `jsc-*` domains to choose from)
-2. If the domain does not exist:
+2. If the domain does not exist (if the repository exists on Gitea but not in the working directory, clone it and skip to step 3):
    1. Propose one short English word for the new domain (a single word preferred) and confirm it with the user.
    2. Ask the user to create the repository `plugins/{domain}`. Clone it, then build the content following the structure of `https://gitea.jsc.idv.tw/plugins/template`: three plugin manifests (plugin name `jsc-{domain}`, version starting at `0.0.1`), `skills/`, README.md, AGENTS.md.
    3. Add the plugin entry (URL source pointing at the new repository) to `.claude-plugin/marketplace.json` and `.agents/plugins/marketplace.json` in `plugins/jsc` (the canonical copy), then sync the two updated files to every domain repository, including the new one. Every repo carries the same marketplace files, so any repo works as the registration entry point. The sync MUST run as a sub agent.

skills/skill-update/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: skill-update
-description: Update an existing skill in the jsc skill set. List all skills, let the user pick one, ask update details via decision tree, apply the change, re-check against the guidelines checklist until it passes, then open a PR via jsc-git pr. Use for modifying a skill; not for creating (skill-new) or removing (skill-delete).
+description: Update an existing skill in the jsc skill set. List all skills starting from the Gitea canonical marketplace (plugins/jsc marketplace.json), cloning any missing domain repo, then let the user pick one, ask update details via decision tree, apply the change, re-check against the guidelines checklist until it passes, then open a PR via jsc-git pr. Use for modifying a skill; not for creating (skill-new) or removing (skill-delete).
 ---
 
 # skill-update — update a skill
@@ -9,9 +9,10 @@ Single source of guidelines: [`../../references/guidelines.md`](../../references
 
 ## Flow
 
-1. List every skill in the skill set: scan `jsc-*/skills/*/SKILL.md` and present a "domain / name / description" list.
-2. Let the user pick the skill to update.
-3. Ask for update details via the `jsc-ask:ask` decision tree (change the goal? the trigger? the flow? move rules down to a hook or a tool?). Every option states its impact scope (example: renaming breaks the existing invocation command).
-4. Update the skill — this step MUST run as a sub agent: modify SKILL.md and related files, sync the domain README's 「Skills 目錄」 section, and bump the version in all three manifests.
-5. Check every item of the guidelines.md audit checklist. On any failure, **return to step 3**: ask again and fix, until all items pass.
-6. Call `jsc-git:pr` to open a Push Request.
+1. Query Gitea for the canonical skill set first: run `jsc-gitea/tools/gitea.sh api GET /repos/plugins/jsc/raw/.claude-plugin/marketplace.json` to get the authoritative domain list, then scan local `jsc-*/skills/*/SKILL.md` and present a "domain / name / description" list covering every domain in the marketplace. Completion condition: the list covers all marketplace domains.
+2. For any marketplace domain whose repo is missing from the working directory, clone it first (`gitea.sh clone-url plugins/{domain}`), then rescan. Completion condition: every domain repo exists locally.
+3. Let the user pick the skill to update.
+4. Ask for update details via the `jsc-ask:ask` decision tree (change the goal? the trigger? the flow? move rules down to a hook or a tool?). Every option states its impact scope (example: renaming breaks the existing invocation command).
+5. Update the skill — this step MUST run as a sub agent: modify SKILL.md and related files, sync the domain README's 「Skills 目錄」 section, and bump the version in all three manifests.
+6. Check every item of the guidelines.md audit checklist. On any failure, **return to step 4**: ask again and fix, until all items pass.
+7. Call `jsc-git:pr` to open a Push Request.