@atlashub/smartstack-cli 3.39.0 → 3.41.0

package/templates/skills/cc-skill/steps/step-04-validate.md

@@ -1,124 +1,124 @@
----
-name: step-04-validate
-description: Validate generated skill structure and display final summary
----
-
-# Step 4: Validate Skill
-
-## MANDATORY EXECUTION RULES:
-- Validate ALL generated files
-- Check frontmatter completeness
-- Verify step chaining (if progressive)
-- Display actionable report if issues found
-
-## YOUR TASK:
-Validate the generated skill against official Claude Code conventions and display a final summary.
-
----
-
-## EXECUTION SEQUENCE:
-
-### 1. Read Generated Files
-
-```
-Read: "{target_dir}/SKILL.md"
-
-If progressive:
-  Glob: "{target_dir}/steps/step-*.md"
-  Read each step file
-```
-
-### 2. Validate SKILL.md
-
-**Frontmatter checks:**
-- [ ] `name` exists, lowercase, max 64 chars
-- [ ] `description` exists, non-empty
-- [ ] `argument-hint` present (if skill accepts args)
-- [ ] `disable-model-invocation` set for side-effect skills
-- [ ] `model` is valid (inherit/haiku/sonnet/opus) or absent
-
-**Content checks:**
-- [ ] Has `<objective>` section
-- [ ] Has `<quick_start>` with examples
-- [ ] Line count < 500
-- [ ] No unreplaced placeholders (e.g., `{placeholder}`)
-
-**Progressive-specific checks:**
-- [ ] Has `<entry_point>` pointing to first step
-- [ ] Has `<step_files>` listing all steps
-- [ ] Has `<state_variables>` documenting persistent state
-- [ ] Has `<workflow>` describing high-level flow
-
-### 3. Validate Step Files (if progressive)
-
-For each step file:
-- [ ] Has YAML frontmatter with `name` and `description`
-- [ ] Has `next_step` (except last step)
-- [ ] `next_step` path resolves to existing file
-- [ ] Has sections: YOUR TASK, EXECUTION SEQUENCE, SUCCESS METRICS
-- [ ] Last step has completion message (no next_step)
-
-**Chain validation:**
-```
-step-00 → step-01 → step-02 → ... → step-N (final)
-Verify: each next_step file exists
-Verify: no circular references
-Verify: no orphan steps (steps not in chain)
-```
-
-### 4. Validate File References
-
-Check all file paths referenced in SKILL.md and step files:
-- Templates referenced exist in `templates/`
-- References referenced exist in `references/`
-- Scripts referenced exist in `scripts/`
-
-### 5. Display Validation Report
-
-```
-Skill Validation Report:
-
-| Check | Status |
-|-------|--------|
-| Frontmatter complete | PASS/FAIL |
-| Content sections | PASS/FAIL |
-| Line count ({N} lines) | PASS/WARN |
-| Step chaining | PASS/FAIL/N/A |
-| File references | PASS/FAIL |
-
-{If any FAIL: show specific issues and recommendations}
-```
-
-### 6. Display Final Summary
-
-```
-Skill Created Successfully!
-
-| Property | Value |
-|----------|-------|
-| Name | {skill_name} |
-| Type | {skill_type} |
-| Location | {target_dir} |
-| Invocation | /cc-skill {skill_name} |
-| Files | {file_count} |
-
-Files created:
-  {target_dir}/SKILL.md
-  {target_dir}/steps/step-00-init.md (if progressive)
-  {target_dir}/steps/step-01-*.md (if progressive)
-  ...
-
-Next steps:
-- Test the skill: /{skill_name}
-- Add references: {target_dir}/references/
-- Add templates: {target_dir}/templates/
-- Run audit: /cc-audit
-```
-
----
-
-## SUCCESS METRICS:
-- All validations pass (or issues clearly reported)
-- Final summary displayed with file list
-- Next steps provided to the user
-- Skill is ready to use
+---
+name: step-04-validate
+description: Validate generated skill structure and display final summary
+---
+
+# Step 4: Validate Skill
+
+## MANDATORY EXECUTION RULES:
+- Validate ALL generated files
+- Check frontmatter completeness
+- Verify step chaining (if progressive)
+- Display actionable report if issues found
+
+## YOUR TASK:
+Validate the generated skill against official Claude Code conventions and display a final summary.
+
+---
+
+## EXECUTION SEQUENCE:
+
+### 1. Read Generated Files
+
+```
+Read: "{target_dir}/SKILL.md"
+
+If progressive:
+  Glob: "{target_dir}/steps/step-*.md"
+  Read each step file
+```
+
+### 2. Validate SKILL.md
+
+**Frontmatter checks:**
+- [ ] `name` exists, lowercase, max 64 chars
+- [ ] `description` exists, non-empty
+- [ ] `argument-hint` present (if skill accepts args)
+- [ ] `disable-model-invocation` set for side-effect skills
+- [ ] `model` is valid (inherit/haiku/sonnet/opus) or absent
+
+**Content checks:**
+- [ ] Has `<objective>` section
+- [ ] Has `<quick_start>` with examples
+- [ ] Line count < 500
+- [ ] No unreplaced placeholders (e.g., `{placeholder}`)
+
+**Progressive-specific checks:**
+- [ ] Has `<entry_point>` pointing to first step
+- [ ] Has `<step_files>` listing all steps
+- [ ] Has `<state_variables>` documenting persistent state
+- [ ] Has `<workflow>` describing high-level flow
+
+### 3. Validate Step Files (if progressive)
+
+For each step file:
+- [ ] Has YAML frontmatter with `name` and `description`
+- [ ] Has `next_step` (except last step)
+- [ ] `next_step` path resolves to existing file
+- [ ] Has sections: YOUR TASK, EXECUTION SEQUENCE, SUCCESS METRICS
+- [ ] Last step has completion message (no next_step)
+
+**Chain validation:**
+```
+step-00 → step-01 → step-02 → ... → step-N (final)
+Verify: each next_step file exists
+Verify: no circular references
+Verify: no orphan steps (steps not in chain)
+```
+
+### 4. Validate File References
+
+Check all file paths referenced in SKILL.md and step files:
+- Templates referenced exist in `templates/`
+- References referenced exist in `references/`
+- Scripts referenced exist in `scripts/`
+
+### 5. Display Validation Report
+
+```
+Skill Validation Report:
+
+| Check | Status |
+|-------|--------|
+| Frontmatter complete | PASS/FAIL |
+| Content sections | PASS/FAIL |
+| Line count ({N} lines) | PASS/WARN |
+| Step chaining | PASS/FAIL/N/A |
+| File references | PASS/FAIL |
+
+{If any FAIL: show specific issues and recommendations}
+```
+
+### 6. Display Final Summary
+
+```
+Skill Created Successfully!
+
+| Property | Value |
+|----------|-------|
+| Name | {skill_name} |
+| Type | {skill_type} |
+| Location | {target_dir} |
+| Invocation | /cc-skill {skill_name} |
+| Files | {file_count} |
+
+Files created:
+  {target_dir}/SKILL.md
+  {target_dir}/steps/step-00-init.md (if progressive)
+  {target_dir}/steps/step-01-*.md (if progressive)
+  ...
+
+Next steps:
+- Test the skill: /{skill_name}
+- Add references: {target_dir}/references/
+- Add templates: {target_dir}/templates/
+- Run audit: /cc-audit
+```
+
+---
+
+## SUCCESS METRICS:
+- All validations pass (or issues clearly reported)
+- Final summary displayed with file list
+- Next steps provided to the user
+- Skill is ready to use

package/templates/skills/cc-skill/templates/skill-forked.md

@@ -1,85 +1,85 @@
-# Template: Forked Context Skill
-
-Use this template when creating a skill that runs in an isolated subagent context. Best for research, exploration, or tasks that need a clean context.
-
-## Generated SKILL.md format:
-
-```yaml
----
-name: {{SKILL_NAME}}
-description: |
-  {{DESCRIPTION}}
-{{#if ARGUMENT_HINT}}
-argument-hint: "{{ARGUMENT_HINT}}"
-{{/if}}
-context: fork
-agent: {{AGENT_TYPE}}
-allowed-tools: "{{ALLOWED_TOOLS}}"
-{{#if DISABLE_MODEL_INVOCATION}}
-disable-model-invocation: true
-{{/if}}
-{{#if MODEL}}
-model: {{MODEL}}
-{{/if}}
----
-
-<objective>
-{{OBJECTIVE}}
-
-**Note:** This skill runs in an isolated context. Use allowed tools directly - do NOT launch Task agents.
-</objective>
-
-<quick_start>
-
-` ` `bash
-/{{SKILL_NAME}} {{EXAMPLE_ARGS_1}}
-/{{SKILL_NAME}} {{EXAMPLE_ARGS_2}}
-` ` `
-
-</quick_start>
-
-## Task
-{{TASK_DESCRIPTION}}: $ARGUMENTS
-
-<workflow>
-
-## 1. Parse Input
-- Extract key information from the input
-- Identify scope and targets
-
-## 2. {{MAIN_PHASE}}
-{{MAIN_PHASE_INSTRUCTIONS}}
-
-## 3. Report Results
-- Provide comprehensive answer
-- Reference file paths and line numbers
-- Include relevant code examples
-
-</workflow>
-
-<execution_rules>
-- **PARALLEL SEARCH**: Run independent searches simultaneously
-- **CITE SOURCES**: Always reference file paths and line numbers
-- **STAY FOCUSED**: Only explore what is needed
-- **NO TASK AGENTS**: Use allowed tools directly (context is already forked)
-- {{RULE_1}}
-</execution_rules>
-
-<priority>
-{{PRIORITY_STATEMENT}}
-</priority>
-```
-
-## Agent Types:
-| Agent | Tools | Best for |
-|-------|-------|----------|
-| `Explore` | Read, Grep, Glob | Fast codebase search |
-| `Plan` | Read, Grep, Glob | Research and design |
-| `general-purpose` | All tools | Complex tasks |
-
-## Notes:
-- Forked skills run in isolated context (separate conversation)
-- Use `allowed-tools` to limit tool access
-- $ARGUMENTS passes user input to the forked context
-- Do NOT use progressive step loading with forked skills
-- Best for: code search, documentation lookup, research, analysis
+# Template: Forked Context Skill
+
+Use this template when creating a skill that runs in an isolated subagent context. Best for research, exploration, or tasks that need a clean context.
+
+## Generated SKILL.md format:
+
+```yaml
+---
+name: {{SKILL_NAME}}
+description: |
+  {{DESCRIPTION}}
+{{#if ARGUMENT_HINT}}
+argument-hint: "{{ARGUMENT_HINT}}"
+{{/if}}
+context: fork
+agent: {{AGENT_TYPE}}
+allowed-tools: "{{ALLOWED_TOOLS}}"
+{{#if DISABLE_MODEL_INVOCATION}}
+disable-model-invocation: true
+{{/if}}
+{{#if MODEL}}
+model: {{MODEL}}
+{{/if}}
+---
+
+<objective>
+{{OBJECTIVE}}
+
+**Note:** This skill runs in an isolated context. Use allowed tools directly - do NOT launch Task agents.
+</objective>
+
+<quick_start>
+
+` ` `bash
+/{{SKILL_NAME}} {{EXAMPLE_ARGS_1}}
+/{{SKILL_NAME}} {{EXAMPLE_ARGS_2}}
+` ` `
+
+</quick_start>
+
+## Task
+{{TASK_DESCRIPTION}}: $ARGUMENTS
+
+<workflow>
+
+## 1. Parse Input
+- Extract key information from the input
+- Identify scope and targets
+
+## 2. {{MAIN_PHASE}}
+{{MAIN_PHASE_INSTRUCTIONS}}
+
+## 3. Report Results
+- Provide comprehensive answer
+- Reference file paths and line numbers
+- Include relevant code examples
+
+</workflow>
+
+<execution_rules>
+- **PARALLEL SEARCH**: Run independent searches simultaneously
+- **CITE SOURCES**: Always reference file paths and line numbers
+- **STAY FOCUSED**: Only explore what is needed
+- **NO TASK AGENTS**: Use allowed tools directly (context is already forked)
+- {{RULE_1}}
+</execution_rules>
+
+<priority>
+{{PRIORITY_STATEMENT}}
+</priority>
+```
+
+## Agent Types:
+| Agent | Tools | Best for |
+|-------|-------|----------|
+| `Explore` | Read, Grep, Glob | Fast codebase search |
+| `Plan` | Read, Grep, Glob | Research and design |
+| `general-purpose` | All tools | Complex tasks |
+
+## Notes:
+- Forked skills run in isolated context (separate conversation)
+- Use `allowed-tools` to limit tool access
+- $ARGUMENTS passes user input to the forked context
+- Do NOT use progressive step loading with forked skills
+- Best for: code search, documentation lookup, research, analysis

package/templates/skills/cc-skill/templates/skill-progressive.md

@@ -1,102 +1,102 @@
-# Template: Progressive Step Loading Skill
-
-Use this template when creating a complex skill with multiple phases that benefit from progressive step loading.
-
-## Generated SKILL.md format:
-
-```yaml
----
-name: {{SKILL_NAME}}
-description: |
-  {{DESCRIPTION}}
-{{#if ARGUMENT_HINT}}
-argument-hint: "{{ARGUMENT_HINT}}"
-{{/if}}
-{{#if DISABLE_MODEL_INVOCATION}}
-disable-model-invocation: true
-{{/if}}
-{{#if MODEL}}
-model: {{MODEL}}
-{{/if}}
----
-
-<objective>
-{{OBJECTIVE}}
-</objective>
-
-<quick_start>
-
-` ` `bash
-/{{SKILL_NAME}} {{EXAMPLE_ARGS_1}}
-/{{SKILL_NAME}} {{EXAMPLE_ARGS_2}}
-` ` `
-
-</quick_start>
-
-<parameters>
-
-<flags>
-| Flag | Description |
-|------|-------------|
-| {{FLAG_SHORT}} | {{FLAG_DESCRIPTION}} |
-</flags>
-
-<examples>
-` ` `bash
-/{{SKILL_NAME}} {{EXAMPLE_1}}
-/{{SKILL_NAME}} {{EXAMPLE_2}}
-` ` `
-</examples>
-
-</parameters>
-
-<workflow>
-{{#each STEPS}}
-{{@index_plus_one}}. {{this.title}}
-{{/each}}
-</workflow>
-
-<state_variables>
-| Variable | Type | Description |
-|----------|------|-------------|
-{{#each STATE_VARS}}
-| `{ {{this.name}} }` | {{this.type}} | {{this.description}} |
-{{/each}}
-</state_variables>
-
-<entry_point>
-
-**FIRST ACTION:** Load `steps/step-00-init.md`
-
-</entry_point>
-
-<step_files>
-| Step | File | Purpose |
-|------|------|---------|
-{{#each STEPS}}
-| {{this.number}} | `steps/step-{{this.number}}-{{this.name}}.md` | {{this.description}} |
-{{/each}}
-</step_files>
-
-<execution_rules>
-- **Load one step at a time** - Progressive loading to minimize context
-- **Persist state variables** across all steps
-- **Follow next_step directive** at end of each step
-- {{RULE_1}}
-- {{RULE_2}}
-</execution_rules>
-
-<success_criteria>
-- {{CRITERIA_1}}
-- {{CRITERIA_2}}
-- {{CRITERIA_3}}
-</success_criteria>
-```
-
-## Notes:
-- Keep SKILL.md under 500 lines (detailed content goes in steps)
-- Each step should be self-contained
-- State variables persist across all steps
-- Always start with step-00-init for argument parsing
-- Always end with a validation/summary step
-- Best for: workflows, generators, multi-phase operations
+# Template: Progressive Step Loading Skill
+
+Use this template when creating a complex skill with multiple phases that benefit from progressive step loading.
+
+## Generated SKILL.md format:
+
+```yaml
+---
+name: {{SKILL_NAME}}
+description: |
+  {{DESCRIPTION}}
+{{#if ARGUMENT_HINT}}
+argument-hint: "{{ARGUMENT_HINT}}"
+{{/if}}
+{{#if DISABLE_MODEL_INVOCATION}}
+disable-model-invocation: true
+{{/if}}
+{{#if MODEL}}
+model: {{MODEL}}
+{{/if}}
+---
+
+<objective>
+{{OBJECTIVE}}
+</objective>
+
+<quick_start>
+
+` ` `bash
+/{{SKILL_NAME}} {{EXAMPLE_ARGS_1}}
+/{{SKILL_NAME}} {{EXAMPLE_ARGS_2}}
+` ` `
+
+</quick_start>
+
+<parameters>
+
+<flags>
+| Flag | Description |
+|------|-------------|
+| {{FLAG_SHORT}} | {{FLAG_DESCRIPTION}} |
+</flags>
+
+<examples>
+` ` `bash
+/{{SKILL_NAME}} {{EXAMPLE_1}}
+/{{SKILL_NAME}} {{EXAMPLE_2}}
+` ` `
+</examples>
+
+</parameters>
+
+<workflow>
+{{#each STEPS}}
+{{@index_plus_one}}. {{this.title}}
+{{/each}}
+</workflow>
+
+<state_variables>
+| Variable | Type | Description |
+|----------|------|-------------|
+{{#each STATE_VARS}}
+| `{ {{this.name}} }` | {{this.type}} | {{this.description}} |
+{{/each}}
+</state_variables>
+
+<entry_point>
+
+**FIRST ACTION:** Load `steps/step-00-init.md`
+
+</entry_point>
+
+<step_files>
+| Step | File | Purpose |
+|------|------|---------|
+{{#each STEPS}}
+| {{this.number}} | `steps/step-{{this.number}}-{{this.name}}.md` | {{this.description}} |
+{{/each}}
+</step_files>
+
+<execution_rules>
+- **Load one step at a time** - Progressive loading to minimize context
+- **Persist state variables** across all steps
+- **Follow next_step directive** at end of each step
+- {{RULE_1}}
+- {{RULE_2}}
+</execution_rules>
+
+<success_criteria>
+- {{CRITERIA_1}}
+- {{CRITERIA_2}}
+- {{CRITERIA_3}}
+</success_criteria>
+```
+
+## Notes:
+- Keep SKILL.md under 500 lines (detailed content goes in steps)
+- Each step should be self-contained
+- State variables persist across all steps
+- Always start with step-00-init for argument parsing
+- Always end with a validation/summary step
+- Best for: workflows, generators, multi-phase operations