Add Overview header to meta skill templates and improve job descriptions

- Add "## Overview" section header in both Claude and Gemini meta skill templates
  to better structure the job description content
- Rewrite job.yml descriptions for commit, add_platform, and update jobs to be
  more narrative and avoid duplicating step information that's already shown
  in the Available Steps section
- Regenerate all skill files via deepwork sync to reflect the template changes

This makes the SKILL.md files clearer and more readable by providing context
in the Overview section without redundant step lists.

Author: claude

.claude/skills/add_platform.add_capabilities/SKILL.md

@@ -176,14 +176,11 @@ When you find a new hook type, consider whether it maps to an existing pattern o
 
 A workflow for adding support for a new AI platform (like Cursor, Windsurf, etc.) to DeepWork.
 
-This job guides you through four phases:
-1. **Research**: Capture the platform's CLI configuration and hooks system documentation
-2. **Add Capabilities**: Update the job schema and adapters with any new hook events
-3. **Implement**: Create the platform adapter, templates, tests (100% coverage), and README updates
-4. **Verify**: Ensure installation works correctly and produces expected files
-
 The workflow ensures consistency across all supported platforms and maintains
-comprehensive test coverage for new functionality.
+comprehensive test coverage for new functionality. It starts with research to
+capture the platform's configuration and hooks documentation, then adds any new
+hook capabilities to the schema and existing adapters, implements the full adapter
+with templates and tests, and finally verifies installation works correctly.
 
 **Important Notes**:
 - Only hooks available on slash command definitions should be captured

.claude/skills/add_platform.implement/SKILL.md

@@ -272,14 +272,11 @@ The templates use Jinja2 and should produce files that match exactly what the pl
 
 A workflow for adding support for a new AI platform (like Cursor, Windsurf, etc.) to DeepWork.
 
-This job guides you through four phases:
-1. **Research**: Capture the platform's CLI configuration and hooks system documentation
-2. **Add Capabilities**: Update the job schema and adapters with any new hook events
-3. **Implement**: Create the platform adapter, templates, tests (100% coverage), and README updates
-4. **Verify**: Ensure installation works correctly and produces expected files
-
 The workflow ensures consistency across all supported platforms and maintains
-comprehensive test coverage for new functionality.
+comprehensive test coverage for new functionality. It starts with research to
+capture the platform's configuration and hooks documentation, then adds any new
+hook capabilities to the schema and existing adapters, implements the full adapter
+with templates and tests, and finally verifies installation works correctly.
 
 **Important Notes**:
 - Only hooks available on slash command definitions should be captured

.claude/skills/add_platform.research/SKILL.md

@@ -226,14 +226,11 @@ Take time to be thorough - incomplete documentation will slow down subsequent st
 
 A workflow for adding support for a new AI platform (like Cursor, Windsurf, etc.) to DeepWork.
 
-This job guides you through four phases:
-1. **Research**: Capture the platform's CLI configuration and hooks system documentation
-2. **Add Capabilities**: Update the job schema and adapters with any new hook events
-3. **Implement**: Create the platform adapter, templates, tests (100% coverage), and README updates
-4. **Verify**: Ensure installation works correctly and produces expected files
-
 The workflow ensures consistency across all supported platforms and maintains
-comprehensive test coverage for new functionality.
+comprehensive test coverage for new functionality. It starts with research to
+capture the platform's configuration and hooks documentation, then adds any new
+hook capabilities to the schema and existing adapters, implements the full adapter
+with templates and tests, and finally verifies installation works correctly.
 
 **Important Notes**:
 - Only hooks available on slash command definitions should be captured

.claude/skills/add_platform.verify/SKILL.md

@@ -151,14 +151,11 @@ Take time to verify each aspect - finding issues now is much better than having
 
 A workflow for adding support for a new AI platform (like Cursor, Windsurf, etc.) to DeepWork.
 
-This job guides you through four phases:
-1. **Research**: Capture the platform's CLI configuration and hooks system documentation
-2. **Add Capabilities**: Update the job schema and adapters with any new hook events
-3. **Implement**: Create the platform adapter, templates, tests (100% coverage), and README updates
-4. **Verify**: Ensure installation works correctly and produces expected files
-
 The workflow ensures consistency across all supported platforms and maintains
-comprehensive test coverage for new functionality.
+comprehensive test coverage for new functionality. It starts with research to
+capture the platform's configuration and hooks documentation, then adds any new
+hook capabilities to the schema and existing adapters, implements the full adapter
+with templates and tests, and finally verifies installation works correctly.
 
 **Important Notes**:
 - Only hooks available on slash command definitions should be captured

.claude/skills/add_platform/SKILL.md

@@ -9,16 +9,15 @@ description: "Add a new AI platform to DeepWork with adapter, templates, and tes
 
 > **CRITICAL**: Always invoke steps using the Skill tool. Never copy/paste step instructions directly.
 
-A workflow for adding support for a new AI platform (like Cursor, Windsurf, etc.) to DeepWork.
+## Overview
 
-This job guides you through four phases:
-1. **Research**: Capture the platform's CLI configuration and hooks system documentation
-2. **Add Capabilities**: Update the job schema and adapters with any new hook events
-3. **Implement**: Create the platform adapter, templates, tests (100% coverage), and README updates
-4. **Verify**: Ensure installation works correctly and produces expected files
+A workflow for adding support for a new AI platform (like Cursor, Windsurf, etc.) to DeepWork.
 
 The workflow ensures consistency across all supported platforms and maintains
-comprehensive test coverage for new functionality.
+comprehensive test coverage for new functionality. It starts with research to
+capture the platform's configuration and hooks documentation, then adds any new
+hook capabilities to the schema and existing adapters, implements the full adapter
+with templates and tests, and finally verifies installation works correctly.
 
 **Important Notes**:
 - Only hooks available on slash command definitions should be captured

.claude/skills/commit.commit_and_push/SKILL.md

@@ -118,14 +118,10 @@ This is the final step of the commit workflow. It ensures the user has reviewed
 
 A workflow for preparing and committing code changes with quality checks.
 
-This job runs tests until they pass, formats and lints code with ruff,
-then reviews changed files before committing and pushing. The lint step
-uses a sub-agent to reduce context usage.
-
-Steps:
-1. test - Pull latest code and run tests until they pass
-2. lint - Format and lint code with ruff (runs in sub-agent)
-3. commit_and_push - Review changes and commit/push
+This job ensures code quality before committing by running the test suite until
+all tests pass, then formatting and linting with ruff. The lint step runs in a
+sub-agent to reduce context usage. Finally, it reviews changed files with you
+before creating the commit and pushing to the remote.
 
 
 

.claude/skills/commit.lint/SKILL.md

@@ -108,14 +108,10 @@ This step ensures code quality and consistency before committing. It runs after
 
 A workflow for preparing and committing code changes with quality checks.
 
-This job runs tests until they pass, formats and lints code with ruff,
-then reviews changed files before committing and pushing. The lint step
-uses a sub-agent to reduce context usage.
-
-Steps:
-1. test - Pull latest code and run tests until they pass
-2. lint - Format and lint code with ruff (runs in sub-agent)
-3. commit_and_push - Review changes and commit/push
+This job ensures code quality before committing by running the test suite until
+all tests pass, then formatting and linting with ruff. The lint step runs in a
+sub-agent to reduce context usage. Finally, it reviews changed files with you
+before creating the commit and pushing to the remote.
 
 
 

.claude/skills/commit.test/SKILL.md

@@ -86,14 +86,10 @@ This is the first step of the commit workflow. Tests must pass before proceeding
 
 A workflow for preparing and committing code changes with quality checks.
 
-This job runs tests until they pass, formats and lints code with ruff,
-then reviews changed files before committing and pushing. The lint step
-uses a sub-agent to reduce context usage.
-
-Steps:
-1. test - Pull latest code and run tests until they pass
-2. lint - Format and lint code with ruff (runs in sub-agent)
-3. commit_and_push - Review changes and commit/push
+This job ensures code quality before committing by running the test suite until
+all tests pass, then formatting and linting with ruff. The lint step runs in a
+sub-agent to reduce context usage. Finally, it reviews changed files with you
+before creating the commit and pushing to the remote.
 
 
 ## Required Inputs

.claude/skills/commit/SKILL.md

@@ -9,16 +9,14 @@ description: "Run tests, lint, and commit code changes"
 
 > **CRITICAL**: Always invoke steps using the Skill tool. Never copy/paste step instructions directly.
 
-A workflow for preparing and committing code changes with quality checks.
+## Overview
 
-This job runs tests until they pass, formats and lints code with ruff,
-then reviews changed files before committing and pushing. The lint step
-uses a sub-agent to reduce context usage.
+A workflow for preparing and committing code changes with quality checks.
 
-Steps:
-1. test - Pull latest code and run tests until they pass
-2. lint - Format and lint code with ruff (runs in sub-agent)
-3. commit_and_push - Review changes and commit/push
+This job ensures code quality before committing by running the test suite until
+all tests pass, then formatting and linting with ruff. The lint step runs in a
+sub-agent to reduce context usage. Finally, it reviews changed files with you
+before creating the commit and pushing to the remote.
 
 
 ## Available Steps

.claude/skills/deepwork_jobs/SKILL.md

@@ -9,6 +9,8 @@ description: "DeepWork job management commands"
 
 > **CRITICAL**: Always invoke steps using the Skill tool. Never copy/paste step instructions directly.
 
+## Overview
+
 Core commands for managing DeepWork jobs. These commands help you define new multi-step
 workflows and learn from running them.