From project-plugin
Analyzes Claude Code plugin skills to identify script opportunities for performance gains (fewer tokens, faster execution, consistency), then creates scripts optionally via --analyze, --create, or --all.
How this skill is triggered — by the user, by Claude, or both
Slash command
/project-plugin:project-skill-scriptssonnetThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
Analyze plugin skills to identify opportunities where supporting scripts would improve performance (fewer tokens, faster execution, consistent results), then optionally create those scripts.
Analyze plugin skills to identify opportunities where supporting scripts would improve performance (fewer tokens, faster execution, consistent results), then optionally create those scripts.
| 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 |
git rev-parse --show-toplevelfind . -maxdepth 2 -name 'plugin.json' -type ffind . -name 'scripts/*.sh' -type fParse $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 candidatesExecute this skill script analysis and creation workflow:
Execute analyzer to get structured data on all skills:
bash "${CLAUDE_PLUGIN_ROOT}/skills/project-discovery/scripts/analyze-skills.sh" $(git rev-parse --show-toplevel 2>/dev/null || echo '.')For each candidate skill:
For approved candidates:
<plugin>/skills/<skill-name>/scripts/<script-name>.shchmod +x <path>modified: date in frontmatterPresent findings:
If scripts created:
feat(<affected-plugins>): add supporting scripts to skills
Include in body:
$ /project:skill-scripts --analyze
Skill Scripts Analysis
Current Coverage: 5/191 skills have supporting scripts
Top Candidates:
git-plugin/gh-cli-agentic score=14 type=context-gather
kubernetes-plugin/kubectl-debugging score=12 type=multi-tool
testing-plugin/playwright-testing score=10 type=workflow
$ /project:skill-scripts --create testing-plugin/playwright-testing
Analyzing testing-plugin/playwright-testing...
Found: 6 bash blocks, 3 phases, 12 commands
Creating scripts/run-tests.sh...
- Consolidates: test discovery, execution, report parsing
- Replaces: 5 individual tool calls
- Output: structured test results with file:line references
Updated SKILL.md with "Recommended" section.
| Situation | Action |
|---|---|
| Skill has no bash patterns | Skip, report "no script opportunity" |
| Script already exists | Report existing, ask to overwrite |
| SKILL.md is read-only | Report error, suggest manual update |
| Plugin not found | List available plugins |
npx claudepluginhub laurigates/claude-plugins --plugin project-pluginAnalyzes repository plugins to extract capabilities from commands, agents, skills, and scripts, then synthesizes and applies adapted patterns to the current task. Activates on 'skill adapter' requests or relevant context.
Maintains Claude Code plugins through domain analysis, structure review, behavioral testing, and quality fixes for skills, commands, agents, hooks, and reference sheets. Use when enhancing existing packs.
Refines and validates existing Claude Code skills for clarity, efficiency, and production readiness. Use for improving structure, best practices, token reduction, and production checks.