project-skill-scripts

name	project-skill-scripts
description	Find and create supporting scripts for plugin skills. Use when auditing skills for script opportunities, improving token efficiency, or extracting bash blocks from SKILL.md.
args	[--analyze] [--create <plugin/skill>] [--all]
allowed-tools	Bash(chmod *), Bash(mkdir *), Read, Write, Edit, Glob, Grep, TodoWrite
argument-hint	--analyze | --create git-plugin/git-commit-workflow | --all
created	"2026-01-24T00:00:00.000Z"
modified	"2026-05-09T00:00:00.000Z"
reviewed	"2026-02-14T00:00:00.000Z"

/project:skill-scripts

Analyze plugin skills to identify opportunities where supporting scripts would improve performance (fewer tokens, faster execution, consistent results), then optionally create those scripts.

When to Use This Skill

Use this skill when...	Use alternative when...
Analyzing skill improvement opportunities	Need to create a single script for a skill
Bulk script creation across plugins	One-off script for one specific need
Measuring coverage of scripts across portfolio	Script generation is already done

Context

• Plugin root: !git rev-parse --show-toplevel
• Total plugins: !find . -maxdepth 2 -name 'plugin.json' -type f
• Skills with scripts: !find . -name 'scripts/*.sh' -type f

Parameters

Parse $ARGUMENTS for:

• --analyze: Scan all skills, report candidates (default)
• --create <plugin/skill>: Create script for specific skill only
• --all: Analyze and create scripts for all high-scoring candidates

Execution

Execute this skill script analysis and creation workflow:

Step 1: Run analysis script

Execute analyzer to get structured data on all skills:

1. Run analyzer: bash "${CLAUDE_PLUGIN_ROOT}/skills/project-discovery/scripts/analyze-skills.sh" $(git rev-parse --show-toplevel 2>/dev/null || echo '.')
2. Parse output to identify:
   • Current coverage (skills with scripts)
   • High-scoring candidates (score >= 8)
   • Script type recommendations

Step 2: Analyze candidates (--create or --all modes)

For each candidate skill:

1. Read SKILL.md to understand the workflow
2. Identify script opportunity patterns:
   • Multiple sequential git/gh commands → context-gather script
   • Multi-phase workflow → workflow script
   • Project type detection + conditional execution → multi-tool script
   • Repeated command with different args → utility script
3. Evaluate benefit: >= 4 tool calls, consistency, error handling, reuse frequency
4. Skip if: single simple commands, interactive/creative, already well-structured