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.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/process-optimizer/SKILL.md

Quality

Content

67%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured and reasonably concise with clear sequenced workflows for each operation. Its primary gap is actionability: the methodology is described at a high level without concrete tools, commands, or specific techniques that would let Claude execute the steps directly.

Suggestions

Add concrete tools or techniques for each operation step (e.g., specific scripts, measurement templates, or named analysis methods) instead of guiding questions like 'how long each step?'.

Provide an executable example or template for at least one operation (e.g., a bottleneck-measurement table format or an automation-ROI calculation formula).

Remove the Quick Reference table or fold it into the operation sections to eliminate the minor redundancy and tighten conciseness.

Dimension	Reasoning	Score
Conciseness	The body is largely lean — short operation descriptions and a before/after/impact table — with only minor redundancy, namely the Quick Reference table restating the per-operation time/output already given above.	4 / 5
Actionability	Each operation gives a numbered process with guiding questions, but the steps are abstract ('Map current process (what are the steps?)', 'Estimate ROI') with no specific tools, scripts, or concrete methods to execute them, leaving key execution details missing.	3 / 5
Workflow Clarity	Every operation has a clearly numbered 5-step sequence, and Operation 4 includes test/measure checkpoints; the analysis operations (1-3) lack explicit validation, but they are non-destructive so the workflow-clarity cap does not apply.	4 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well organized into Overview, When to Use, Operations, Examples, and Quick Reference sections; content is appropriately self-contained, with only minor opportunity to externalize the examples or reference table.	4 / 5
	Total	15 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description clearly states both capabilities and trigger conditions with concrete action verbs and natural trigger phrases. Its main weakness is that some actions lean generic and it lacks synonym/extension coverage that would maximize trigger-term and distinctiveness scores.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — 'bottleneck identification, efficiency analysis, automation discovery, and workflow improvement' — but 'efficiency analysis' and 'workflow improvement' remain somewhat generic, so it stops short of the fully comprehensive anchor at 5.	4 / 5
Completeness	Explicitly answers both what ('Optimize skill development processes through bottleneck identification...') and when ('Use when optimizing development processes, reducing cycle times...') with concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Includes natural phrases a user would say ('optimizing development processes, reducing cycle times, improving efficiency, or streamlining workflows'), but lacks synonyms or domain-specific file/term variations that would push it to 5.	4 / 5
Distinctiveness Conflict Risk	The tie to 'system-reviewer findings' and the skill-development niche gives it a clear, distinct trigger, but the broad efficiency/streamlining language creates minor overlap risk with general productivity skills.	4 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: fernandezbaptiste/Skrillz
Path: skills/process-optimizer/SKILL.md
Commit: 93ed392

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.