control-flow

Linearize complex control flow with early returns, guard clauses, nested ifs, and natural-language conditions. Use when flattening nested conditions, linearizing try/catch logic, or separating mixed throw-and-return handlers, not for a broad "simplify this" pass over a diff or package, which belongs to collapse-pass.

Quality

90%

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

Quality

Content

82%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.

A strong, example-driven body: nearly all content is executable before/after TypeScript demonstrating the pattern, with a coherent core workflow. The weaknesses are modest — a sentence or two of over-explanation, no behavior-preservation validation step, and everything inlined in one file rather than split out.

Suggestions

Trim the sentence explaining what a try-catch structure is and consolidate the restated pattern steps from the try/catch section into the Core Pattern to remove redundancy (conciseness).

Add a brief verification checkpoint to the workflow, e.g. 'after linearizing, confirm each early return maps to a branch of the original code and tests still pass' (workflow_clarity).

Consider moving the longer before/after examples into a references file (e.g. references/examples.md) so SKILL.md stays a lean overview of the core pattern (progressive_disclosure).

Dimension	Reasoning	Score
Conciseness	Sections are lean and code-first, but "try-catch blocks create a nested, two-branch structure: the try body and the catch body" explains a basic concept Claude already knows, and the human-reasoning pattern is restated twice (Core Pattern and the try/catch recap). This sits above the 3-anchor's 'unnecessary explanation' but short of the 5-anchor's every-token-earns-its-place.	4 / 5
Actionability	Five concrete TypeScript examples drawn from real code cover the common cases (early returns, natural-language booleans, cleanup checks, try/catch linearization with full before/after, sequential guards); the only elision is an incidental `// ... toast content`, not the pattern itself.	5 / 5
Workflow Clarity	The Core Pattern gives a clear numbered sequence (ask, assess, act, name, avoid) and each example shows a consistent guard shape, but there is no checkpoint for verifying behavior is preserved after restructuring — a real validation gap for a control-flow refactoring skill, placing it at the 4-anchor rather than 5.	4 / 5
Progressive Disclosure	Well-organized single-file skill with clear section headers and a clearly signaled related-skill pointer (`refactoring`), but at 163 lines with all examples inlined it does not meet the 5-anchor's overview-plus-one-level-deep-references split; structure is good with only minor organization gaps.	4 / 5
	Total	17 / 20 Passed

Description

92%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.

An excellent description: concrete capabilities, explicit natural-language triggers for both what and when, and an explicit negative boundary that disambiguates it from a sibling skill. Only minor synonym coverage is missing in the trigger terms.

Dimension	Reasoning	Score
Specificity	"Linearize complex control flow with early returns, guard clauses, nested ifs, and natural-language conditions" lists multiple concrete techniques that comprehensively cover the control-flow refactoring domain; no meaningful coverage gap remains for the 4-anchor to apply.	5 / 5
Completeness	The first sentence explicitly states what the skill does and "Use when flattening nested conditions, linearizing try/catch logic, or separating mixed throw-and-return handlers" gives concrete trigger phrases, directly matching the anchor-5 example structure.	5 / 5
Trigger Term Quality	"flattening nested conditions", "linearizing try/catch logic", and "separating mixed throw-and-return handlers" are phrases users naturally say when requesting this refactor, but common synonyms such as "simplify nested conditionals" or "deeply nested if statements" are absent.	4 / 5
Distinctiveness Conflict Risk	The description carves out a clear niche and explicitly routes overlapping requests elsewhere ("not for a broad 'simplify this' pass over a diff or package, which belongs to collapse-pass"), minimizing wrong-skill triggering.	5 / 5
	Total	19 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: EpicenterHQ/epicenter
Path: .agents/skills/control-flow/SKILL.md
Commit: f9441c8

Reviewed: 3 days 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.