feat: improve-skills now leverages skill-creator skill

**Enhancement**: /improve-skills uses skill-creator for better quality

## What Changed

Updated /improve-skills command to use the skill-creator skill throughout the improvement process.

### Before v4.7.1

improve-skills did everything manually:
- Manual analysis of skills
- Manual rewriting of descriptions
- No templates or guidance
- Inconsistent results

### After v4.7.1

improve-skills leverages skill-creator:
- ✅ Uses skill-creator's templates
- ✅ Follows skill-creator's structure guidance
- ✅ Applies skill-creator's best practices
- ✅ Consistent quality across all improvements

## Implementation

**Added references to skill-creator at key steps**:

1. **Step 2 (Analyze)**:
   - Now uses skill-creator to analyze skills
   - Follows skill-creator's structure templates

2. **Step 3 (Rewrite)**:
   - Uses skill-creator's patterns for descriptions
   - Applies skill-creator's best practices

3. **Step 4 (Format)**:
   - Uses skill-creator's structure template
   - Follows activation criteria guidelines

4. **Step 5 (Final message)**:
   - Informs user skill-creator was used
   - Points to skill-creator for reference

## Benefits

**For Users**:
- ✅ Higher quality skill improvements
- ✅ Consistent structure across all skills
- ✅ Leverages existing expertise
- ✅ Better activation criteria

**For Ecosystem**:
- ✅ Commands use skills (dogfooding)
- ✅ Consistent patterns across tools
- ✅ Better integration of features

## Files Modified

- droid_cli/default/commands/improve-skills.md
- claude/default/commands/improve-skills.md

---

Closes #improve-skills-quality

Author: korallis

CHANGELOG.md

@@ -147,6 +147,26 @@ Without this, Factory CLI ignores the skill file completely.
 - `claude/default/skills/*/SKILL.md` (49 files updated, 1 already correct)
 - `droid_cli/default/skills/*/SKILL.md` (49 files updated, 1 already correct)
 
+## [4.7.1] - 2024-11-24
+
+### Enhanced
+- **improve-skills now uses skill-creator skill**: Command leverages skill-creator for better quality
+  - skill-creator provides templates, structure guidance, and best practices
+  - Automatically activated when improving skills
+  - Ensures consistent skill format across all improvements
+  - Better activation criteria and examples
+
+### Changed
+- `/improve-skills` command now references skill-creator throughout the process
+- Added guidance to use skill-creator's templates and patterns
+- Updated final message to mention skill-creator was used
+
+### Impact
+- ✅ Higher quality skill improvements
+- ✅ Consistent skill structure
+- ✅ Leverages existing skill-creator skill
+- ✅ Better use of Droidz ecosystem
+
 ## [4.7.0] - 2024-11-24
 
 ### Changed

droidz_installer/payloads/claude/default/commands/improve-skills.md

@@ -1,35 +1,51 @@
-I want you to help me improve the files that make up my Claude Code Skills by rewriting their descriptions so that they can be more readily discovered and used by Claude Code when it works on coding tasks.
+I want you to help me improve the files that make up your Skills by rewriting their descriptions so that they can be more readily discovered and used when working on coding tasks.
 
-You can refer to the Claude Code documentation on the Skills feature here: https://docs.claude.com/en/docs/claude-code/skills
+You can refer to the skills documentation here: https://docs.claude.com/en/docs/claude-code/skills
 
-All of the Skills in our project are located in `.claude/skills/`. Each Skill has its own folder and inside each Skill folder is a file called `SKILL.md`.
+All of the Skills in our project are located in `.factory/skills/`. Each Skill has its own folder and inside each Skill folder is a file called `SKILL.md`.
+
+## Using the skill-creator Skill
+
+**IMPORTANT**: Use the `skill-creator` skill to improve each SKILL.md file. The skill-creator provides templates, best practices, and patterns for creating high-quality skills.
+
+To activate: The skill-creator skill will automatically activate when you start working on skill improvement tasks.
 
 LOOP through each `SKILL.md` file and FOR EACH use the following process to revise its content and improve it:
 
-## Claude Code Skill Improvement Process
+## Skill Improvement Process
 
 ### Step 1: Confirm which skills to improve
 
-First, ask the user to confirm whether they want ALL of their Claude Code skills to be improved, only select Skills.  Assume the answer will be "all" but ask the user to confirm by displaying the following message, then WAIT for the user's response before proceeding to Step 2:
+First, ask the user to confirm whether they want ALL of their skills to be improved, or only select Skills.  Assume the answer will be "all" but ask the user to confirm by displaying the following message, then WAIT for the user's response before proceeding to Step 2:
 
 ```
-Before I proceed with improving your Claude Code Skills, can you confirm that you want me to revise and improve ALL Skills in your .claude/skills/ folder?
+Before I proceed with improving your Skills, can you confirm that you want me to revise and improve ALL Skills in your .factory/skills/ folder?
 
 If not, then please specify which Skills I should include or exclude.
 ```
 
 ### Step 2: Analyze what this Skill does
 
-Analyze and read the skill file to understand what it is, what it should be used for, and when it should be used. The specific best practices are described and linked within it. Look to these places to read and understand each skill:
+**Use the skill-creator skill** to analyze and understand each skill file.
+
+Analyze and read the skill file to understand what it is, what it should be used for, and when it should be used. The skill-creator skill provides guidance on:
+- Proper skill structure and format
+- Clear activation criteria
+- Effective examples and patterns
+- Resource links and documentation
 
+Look to these places to read and understand each skill:
 - The Skill's name and file name.
 - The Skill.md contains a link that points to `droidz/standards/...` — Follow that link and read its contents.
+- Use skill-creator's templates to guide improvements
 
 ### Step 3: Rewrite the Skill description
 
-The most important element of a skill.md file that impacts its discoverability and trigger-ability by Claude Code is the content we write in the `description` in the skill.md frontmatter.
+**Use the skill-creator skill** to rewrite the description following best practices.
 
-Rewrite this description using the following guidelines:
+The most important element of a skill.md file that impacts its discoverability and trigger-ability is the content we write in the `description` in the skill.md frontmatter.
+
+The skill-creator provides templates and patterns for effective descriptions. Rewrite this description using the following guidelines:
 
 - The first sentence should clearly describe what this skill is. For example: "Write Tailwind CSS code and structure front-end UIs using Tailwind CSS utility classes."
 - The second sentence and subsequent sentences should clearly and directly describe multiple examples where and when this skill should be used.
@@ -40,9 +56,11 @@ Rewrite this description using the following guidelines:
 
 ### Step 4: Insert a section for 'When to use this skill'
 
+**Use the skill-creator skill's structure template** to format this section properly.
+
 At the top of the content of skill.md, below the frontmatter, insert an H2 heading, "When to use this skill" followed by a list of use case examples.
 
-The use case examples can repeat the same one(s) listed in the description and/or expand on them.
+The skill-creator provides guidance on writing clear activation criteria. The use case examples can repeat the same one(s) listed in the description and/or expand on them.
 
 Example:
 ```markdown
@@ -56,19 +74,22 @@ Example:
 
 ### Step 5: Advise the user on improving their skills further
 
-After revising ALL Skill.md files located in the project's `.claude/skills/` folder, display the following message to the user to advise them on how to improve their Claude Code Skills further:
+After revising ALL Skill.md files located in the project's `.factory/skills/` folder, display the following message to the user to advise them on how to improve their Skills further:
 
 ```
-All Claude Code Skills have been analyzed and revised!
+All Skills have been analyzed and revised using the skill-creator skill! ✅
 
 RECOMMENDATION 👉 Review and revise them further using these tips:
 
 - Make Skills as descriptive as possible
-- Use their 'description' frontmatter to tell Claude Code when it should proactively use this skill.
+- Use their 'description' frontmatter to describe when this skill should proactively be used.
 - Include all relevant instructions, details and directives within the content of the Skill.
 - You can link to other files (like your Droidz standards files) using markdown links.
-- You can consolidate multiple similar skills into single skills where it makes sense for Claude to find and use them together.
+- You can consolidate multiple similar skills into single skills where it makes sense to find and use them together.
+
+💡 The skill-creator skill was used to ensure proper structure, clear activation criteria, and effective patterns.
 
-For more best practices, refer to the official Claude Code documentation on Skills:
-https://docs.claude.com/en/docs/claude-code/skills
+For more best practices, refer to:
+- Skills documentation: https://docs.claude.com/en/docs/claude-code/skills
+- The skill-creator skill in your skills directory for templates and examples
 ```

droidz_installer/payloads/droid_cli/default/commands/improve-skills.md

@@ -4,6 +4,12 @@ You can refer to the skills documentation here: https://docs.claude.com/en/docs/
 
 All of the Skills in our project are located in `.factory/skills/`. Each Skill has its own folder and inside each Skill folder is a file called `SKILL.md`.
 
+## Using the skill-creator Skill
+
+**IMPORTANT**: Use the `skill-creator` skill to improve each SKILL.md file. The skill-creator provides templates, best practices, and patterns for creating high-quality skills.
+
+To activate: The skill-creator skill will automatically activate when you start working on skill improvement tasks.
+
 LOOP through each `SKILL.md` file and FOR EACH use the following process to revise its content and improve it:
 
 ## Skill Improvement Process
@@ -20,16 +26,26 @@ If not, then please specify which Skills I should include or exclude.
 
 ### Step 2: Analyze what this Skill does
 
-Analyze and read the skill file to understand what it is, what it should be used for, and when it should be used. The specific best practices are described and linked within it. Look to these places to read and understand each skill:
+**Use the skill-creator skill** to analyze and understand each skill file.
+
+Analyze and read the skill file to understand what it is, what it should be used for, and when it should be used. The skill-creator skill provides guidance on:
+- Proper skill structure and format
+- Clear activation criteria
+- Effective examples and patterns
+- Resource links and documentation
 
+Look to these places to read and understand each skill:
 - The Skill's name and file name.
 - The Skill.md contains a link that points to `droidz/standards/...` — Follow that link and read its contents.
+- Use skill-creator's templates to guide improvements
 
 ### Step 3: Rewrite the Skill description
 
-The most important element of a skill.md file that impacts its discoverability and trigger-ability by Claude Code is the content we write in the `description` in the skill.md frontmatter.
+**Use the skill-creator skill** to rewrite the description following best practices.
 
-Rewrite this description using the following guidelines:
+The most important element of a skill.md file that impacts its discoverability and trigger-ability is the content we write in the `description` in the skill.md frontmatter.
+
+The skill-creator provides templates and patterns for effective descriptions. Rewrite this description using the following guidelines:
 
 - The first sentence should clearly describe what this skill is. For example: "Write Tailwind CSS code and structure front-end UIs using Tailwind CSS utility classes."
 - The second sentence and subsequent sentences should clearly and directly describe multiple examples where and when this skill should be used.
@@ -40,9 +56,11 @@ Rewrite this description using the following guidelines:
 
 ### Step 4: Insert a section for 'When to use this skill'
 
+**Use the skill-creator skill's structure template** to format this section properly.
+
 At the top of the content of skill.md, below the frontmatter, insert an H2 heading, "When to use this skill" followed by a list of use case examples.
 
-The use case examples can repeat the same one(s) listed in the description and/or expand on them.
+The skill-creator provides guidance on writing clear activation criteria. The use case examples can repeat the same one(s) listed in the description and/or expand on them.
 
 Example:
 ```markdown
@@ -59,7 +77,7 @@ Example:
 After revising ALL Skill.md files located in the project's `.factory/skills/` folder, display the following message to the user to advise them on how to improve their Skills further:
 
 ```
-All Skills have been analyzed and revised!
+All Skills have been analyzed and revised using the skill-creator skill! ✅
 
 RECOMMENDATION 👉 Review and revise them further using these tips:
 
@@ -69,6 +87,9 @@ RECOMMENDATION 👉 Review and revise them further using these tips:
 - You can link to other files (like your Droidz standards files) using markdown links.
 - You can consolidate multiple similar skills into single skills where it makes sense to find and use them together.
 
-For more best practices, refer to the skills documentation:
-https://docs.claude.com/en/docs/claude-code/skills
+💡 The skill-creator skill was used to ensure proper structure, clear activation criteria, and effective patterns.
+
+For more best practices, refer to:
+- Skills documentation: https://docs.claude.com/en/docs/claude-code/skills
+- The skill-creator skill in your skills directory for templates and examples
 ```

install.sh

@@ -31,7 +31,7 @@ safe_read() {
   fi
 }
 
-VERSION="4.7.0"
+VERSION="4.7.1"
 REPO_URL="https://github.com/korallis/Droidz"
 BRANCH="${DROIDZ_BRANCH:-main}"
 GITHUB_RAW="https://raw.githubusercontent.com/korallis/Droidz/${BRANCH}"