process-optimizer
Optimize skill development processes through bottleneck identification, efficiency analysis, automation discovery, and workflow improvement. Task-based operations for process analysis, bottleneck elimination, automation opportunities, and workflow streamlining. Use when optimizing development processes, reducing cycle times, improving efficiency, or streamlining workflows based on system-reviewer findings.
下記のコマンドをコピーしてターミナル(Mac/Linux)または PowerShell(Windows)に貼り付けてください。 ダウンロード → 解凍 → 配置まで全自動。
mkdir -p ~/.claude/skills && cd ~/.claude/skills && curl -L -o process-optimizer.zip https://jpskill.com/download/9465.zip && unzip -o process-optimizer.zip && rm process-optimizer.zip
$d = "$env:USERPROFILE\.claude\skills"; ni -Force -ItemType Directory $d | Out-Null; iwr https://jpskill.com/download/9465.zip -OutFile "$d\process-optimizer.zip"; Expand-Archive "$d\process-optimizer.zip" -DestinationPath $d -Force; ri "$d\process-optimizer.zip"
完了後、Claude Code を再起動 → 普通に「動画プロンプト作って」のように話しかけるだけで自動発動します。
💾 手動でダウンロードしたい(コマンドが難しい人向け)
- 1. 下の青いボタンを押して
process-optimizer.zipをダウンロード - 2. ZIPファイルをダブルクリックで解凍 →
process-optimizerフォルダができる - 3. そのフォルダを
C:\Users\あなたの名前\.claude\skills\(Win)または~/.claude/skills/(Mac)へ移動 - 4. Claude Code を再起動
⚠️ ダウンロード・利用は自己責任でお願いします。当サイトは内容・動作・安全性について責任を負いません。
🎯 このSkillでできること
下記の説明文を読むと、このSkillがあなたに何をしてくれるかが分かります。Claudeにこの分野の依頼をすると、自動で発動します。
📦 インストール方法 (3ステップ)
- 1. 上の「ダウンロード」ボタンを押して .skill ファイルを取得
- 2. ファイル名の拡張子を .skill から .zip に変えて展開(macは自動展開可)
- 3. 展開してできたフォルダを、ホームフォルダの
.claude/skills/に置く- · macOS / Linux:
~/.claude/skills/ - · Windows:
%USERPROFILE%\.claude\skills\
- · macOS / Linux:
Claude Code を再起動すれば完了。「このSkillを使って…」と話しかけなくても、関連する依頼で自動的に呼び出されます。
詳しい使い方ガイドを見る →- 最終更新
- 2026-05-18
- 取得日時
- 2026-05-18
- 同梱ファイル
- 1
📖 Claude が読む原文 SKILL.md(中身を展開)
この本文は AI(Claude)が読むための原文(英語または中国語)です。日本語訳は順次追加中。
Process Optimizer
Overview
process-optimizer improves skill development processes by identifying and eliminating inefficiencies, bottlenecks, and waste.
Purpose: Make skill development processes faster and more efficient
The 4 Optimization Operations:
- Identify Bottlenecks - Find process slowdowns and constraints
- Discover Automation - Identify automation opportunities
- Streamline Workflows - Simplify and optimize workflows
- Implement Improvements - Apply process optimizations
Integration: Uses findings from system-reviewer Operation 3 (Process Efficiency Review)
When to Use
- Development processes feel slow or inefficient
- After system-reviewer identifies process issues
- When looking to reduce cycle times
- Before scaling to many skills (optimize early)
- Continuous process improvement
Operations
Operation 1: Identify Bottlenecks
Purpose: Find steps that slow down development
Process:
- Map current process (what are the steps?)
- Measure duration (how long each step?)
- Identify slowest steps (bottlenecks)
- Analyze causes (why is it slow?)
- Prioritize by impact (which to fix first?)
Output: Bottleneck analysis with prioritized fixes
Time: 45-90 minutes
Operation 2: Discover Automation
Purpose: Identify manual work that could be automated
Process:
- List manual steps in process
- Identify repetitive/mechanical work
- Assess automation feasibility (easy/hard/impossible?)
- Estimate ROI (time to automate vs time saved)
- Prioritize automation opportunities
Output: Automation opportunities prioritized by ROI
Time: 45-90 minutes
Operation 3: Streamline Workflows
Purpose: Simplify processes, eliminate unnecessary steps
Process:
- Review each workflow step (is it necessary?)
- Identify redundant work (done twice?)
- Find unnecessary complexity (simpler approach?)
- Combine or eliminate steps
- Design streamlined workflow
Output: Streamlined process with steps eliminated/combined
Time: 60-120 minutes
Operation 4: Implement Improvements
Purpose: Apply process optimizations discovered
Process:
- Select high-priority improvement
- Design implementation (how to apply?)
- Implement (update workflows, tools, guidelines)
- Test (does it actually help?)
- Measure impact (time saved, efficiency gained)
Output: Implemented improvement with measured impact
Time: 1-4 hours (varies by improvement)
Example Process Optimizations
Optimization 1: Automated structure validation
- Before: Manual YAML checking, 30-45 min
- After: validate-structure.py script, 5-10 min automated
- Impact: 75% time reduction, 95% accuracy improvement
Optimization 2: development-workflow
- Before: Ad-hoc skill building, 17-29 hours/skill
- After: Systematic workflow, 12-18 hours/skill
- Impact: 35-40% time reduction, higher quality
Optimization 3: Fast-track approach for simple skills
- Before: Full workflow even for simple skills
- After: Skip task-development, use prompt-first approach
- Impact: 10-15% additional time savings on simple skills
Quick Reference
| Operation | Focus | Time | Output |
|---|---|---|---|
| Identify Bottlenecks | Find slowdowns | 45-90m | Bottleneck analysis |
| Discover Automation | Find automation opportunities | 45-90m | Automation prioritization |
| Streamline Workflows | Simplify processes | 60-120m | Streamlined workflows |
| Implement Improvements | Apply optimizations | 1-4h | Measured improvements |
Integration: system-reviewer (identifies issues) → process-optimizer (fixes them)
process-optimizer makes skill development faster and more efficient through systematic process improvement.