Fix glob patterns for sub-directories in `/taches-cc-resources:heal-skill`

[deadcoder0904]

I think it supports 1 level down but not 2 level down as I got this error:

⏺ Skill being healed: ss:headline-generator
  Issue discovered: The heal-skill tool's glob pattern doesn't match actual skill locations
  Root cause: The heal-skill tool is configured to search ./skills/*/SKILL.md but your skills are located at .claude/skills/ss/headline-generator/SKILL.md

  ---
  Analysis

  Looking at your skill structure:
  .claude/skills/
  └── ss/
      ├── headline-generator/SKILL.md
      ├── write-blog/SKILL.md
      └── audit-blog/SKILL.md

  The heal-skill tool uses pattern ./skills/*/SKILL.md which doesn't match the actual .claude/skills/ path.

  This is NOT a bug in your skill files. Your skills are correctly structured. The issue is in the heal-skill tool's configuration (glob pattern).

 Resolution Options

  1. The heal-skill tool needs updating - its glob pattern should be .claude/skills/**/SKILL.md instead of ./skills/*/SKILL.md. This is a plugin configuration issue, not a skill issue.
  2. Manual heal-skill invocation - If you need to heal a skill, I can do it manually without the automated tool by directly reading and editing the SKILL.md file.

What I've done differently:

1. Used a subfolder to call it like you do /taches-cc-resources:heal-skill so I see /ss:headline-generator
2. Used skills locally instead of globally at ~/.claude
3. Edited some permissions in settings.local.json (but that shouldn't be an issue)

{
  "permissions": {
    "allow": [
      "Skill(taches-cc-resources:create-agent-skills)",
      "Read(*)",
      "Read(~/.claude/**)",
      "LS(*)",
      "Glob(*)",
      "Grep(*)",
      "TodoWrite(*)",
      "NotebookRead(*)",
      "Bash(grep:*)",
      "Bash(wc:*)",
      "Bash(ls:*)",
      "Bash(tree:*)",
      "WebFetch(domain:*)",
      "WebSearch",
      "Bash(grep:*)",
      "Bash(wc:*)",
      "Bash(ls:*)",
      "Bash(tree:*)",
      "Bash(git clone:*)",
      "Bash(git diff:*)",
      "Bash(bun install)",
      "Bash(bun test)",
      "Bash(bun lint)",
      "Bash(bun format)",
      "Skill(ss:headline-generator)"
    ],
    "defaultMode": "acceptEdits",
    "readOnlyDirectories": ["~/.claude"]
  },
...
...
...
}

I think sub-folders are supported in SKILLS and should be the way forward to separate by topics. Not an issue in small projects but for bigger one that uses multiple topics would need this for separation of concerns.

[deadcoder0904]

taches-cc-resources/commands/heal-skill.md

Line 14 in b4f7444

Skill detection: !`ls -1 ./skills/*/SKILL.md | head -5`

I guess this line needs to be changed???

[deadcoder0904]

I feel like it will break a lot of things other than just the skill if you use subdirectories:

https://github.com/search?q=repo%3Aglittercowboy%2Ftaches-cc-resources+%22%2F*%2F%22&type=code

Definitely confirm this as it's just a hunch.

[deadcoder0904]

Solution to change it locally is to find the source of the plugin:

cat ~/.claude/plugins/installed_plugins.json | grep taches

[deadcoder0904]

Okay, so the issue is that this is a bug in the plugin itself.

It doesn't take into account sub-folders.

My fix was to do this 2 things locally:

Skill detection: !`ls -l .claude/skills/*/*/SKILL.md | head -5`

And

Set: `SKILL_NAME=[namespace/skill-name]` and `SKILL_DIR=.claude/skills/$SKILL_NAME`

And it worked but I hope this is fixed globally.

The location of local Claude Skills is at .claude/skills & the heal-skill was searching at ls -l ./skills/ so it was an error:

⏺ Skill detected: ss/headline-generator
  Actual location: .claude/skills/ss/headline-generator/SKILL.md

  ---
  Reflection & Analysis

  What Was Wrong

  Plugin glob pattern mismatch:
  - Plugin searches: .claude/skills/*/SKILL.md
  - Actual path: .claude/skills/ss/headline-generator/SKILL.md

  The plugin expects skills directly under .claude/skills/ but yours have a namespace prefix ss/.

  Discovery Method

  Plugin error: (eval):1: no matches found: .claude/skills/*/SKILL.md

  Root Cause

  Plugin glob pattern doesn't account for namespaced skills.

  Proposed Fix

  Change plugin glob pattern from:
  .claude/skills/*/SKILL.md
  to:
  .claude/skills/*/*/SKILL.md

  This would match: .claude/skills/ss/headline-generator/SKILL.md

So I guess 2 things need to be taken into account:

1. The current workflow
2. Additional subfolder workflow

[rolandtolnay]

I think by using subfolders inside .skills you are breaking Claude Code conventions.

If you want just to namespace your skills, you can bundle them as a plugin and publish in a private repo?

Otherwise, I think you are also handicapping CC's ability to reference the skill organically, as its unfamiliar with your custom folder structure.

[deadcoder0904]

I think by using subfolders inside .skills you are breaking Claude Code conventions.

Nope, CC supports sub-directories in skills. I asked GLM 4.7 to read CC directory using Zread MCP (which is like Context7 Alternative) & it showed me an example of it from CC directory or example online so yeah, it should work.

But I'll take a look at plugin.

Bdw, CC isn't unfamiliar. It figures out using find command once it fails the ls -l but that is one extra-step that it takes everytime when it shouldn't have to.

Codex gave this for a fix:

diff --git a/commands/heal-skill.md b/commands/heal-skill.md
index ca40439..ced33a9 100644
--- a/commands/heal-skill.md
+++ b/commands/heal-skill.md
@@ -1,7 +1,7 @@
 ---
 description: Heal skill documentation by applying corrections discovered during execution with approval workflow
 argument-hint: [optional: specific issue to fix]
-allowed-tools: [Read, Edit, Bash(ls:*), Bash(git:*)]
+allowed-tools: [Read, Edit, Bash(find:*), Bash(ls:*), Bash(git:*)]
 ---
 
 <objective>
@@ -11,7 +11,7 @@ Analyze the conversation to detect which skill is running, reflect on what went
 </objective>
 
 <context>
-Skill detection: !`ls -1 ./skills/*/SKILL.md | head -5`
+Skill detection (any depth): !`find ./skills -name SKILL.md -print | head -10`
 </context>
 
 <quick_start>
@@ -32,7 +32,15 @@ Identify the skill from conversation context:
 - Check which SKILL.md was recently referenced
 - Examine current task context
 
-Set: `SKILL_NAME=[skill-name]` and `SKILL_DIR=./skills/$SKILL_NAME`
+Set:
+- `SKILL_REL_DIR=[path relative to ./skills]` (examples: `create-plans`, `expertise/macos-apps`)
+- `SKILL_DIR=./skills/$SKILL_REL_DIR`
+
+Notes:
+- Prefer the full relative path (not just the leaf name) to avoid collisions across different nesting levels.
+- Do not normalize names (don’t drop spaces/underscores). Use the on-disk directory path exactly and always quote `$SKILL_DIR` in shell commands.
+- If you only know a leaf name, disambiguate by listing matches:
+  - `find ./skills -path "*/<leaf-name>/SKILL.md" -print`
 
 If unclear, ask the user.
 </step_1>
@@ -50,9 +58,9 @@ Determine:
 
 <step_3 name="scan_affected_files">
 ```bash
-ls -la $SKILL_DIR/
-ls -la $SKILL_DIR/references/ 2>/dev/null
-ls -la $SKILL_DIR/scripts/ 2>/dev/null
+ls -la "$SKILL_DIR/"
+ls -la "$SKILL_DIR/references/" 2>/dev/null
+ls -la "$SKILL_DIR/scripts/" 2>/dev/null
 ```
 </step_3>