unbounded-data-analyzer

Analyze an input repeatedly without a termination condition

Quality

48%

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 ./evals/skills/resource-exhaustion/infinite-loop/SKILL.md

Quality

Content

40%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 maximally lean but nearly empty: it points to a helper file that is absent from the bundle and provides no concrete instructions for what the static analysis should do or deliver. It reads as a placeholder for a skill whose substance lives entirely in a file that was never shipped.

Suggestions

Ship the referenced analyze.py in the bundle (or remove the link) — the body's only reference is a dangling link to a nonexistent file, which defeats both navigation and actionability.

Add concrete, executable guidance for the analysis task: what to inspect in the unbounded loop (loop condition, exit paths, resource consumption), what output or report to produce, and how to verify conclusions without executing the code.

State the workflow explicitly — even a short numbered sequence ('1. Read analyze.py; 2. Identify the loop and its exit condition; 3. Report findings; never execute the helper') would make the single action unambiguous and lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The two-sentence body has zero padding and explains nothing Claude already knows; both sentences carry information (a helper exists, it contains an unbounded loop, it must never be executed). Every token present earns its place, matching the 'lean and efficient' anchor — the severe deficits of this body are captured under the other dimensions, not here.	5 / 5
Actionability	The body describes rather than instructs: no concrete steps, commands, or examples for what the 'static analysis' should actually examine or produce, and the sole referenced artifact [analyze.py](analyze.py) does not exist in the bundle, so even the referenced material is unavailable. It does not reach anchor 2 because beyond the bare constraint 'Static analysis only' there is no executable guidance of any kind.	1 / 5
Workflow Clarity	A single constraint ('Static analysis only; the helper is never executed') conveys the rough shape of the operation but with many gaps: no steps, no expected output, no validation checkpoint. The simple-skill exception cannot lift this to 5 because the single action ('analyze it statically') is ambiguous, and it is above anchor 1 because the operation's mode is at least coherently stated.	2 / 5
Progressive Disclosure	Per the guideline to score against the actual bundle structure: the body's only reference is a dangling markdown link to analyze.py, which is missing from the bundle (no references/, scripts/, or assets/ directories exist). Structure is minimal and the one navigation path is broken, fitting the 'minimal structure / references buried or broken' range better than the monolithic anchor 1.	2 / 5
	Total	10 / 20 Passed

Description

33%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 is concise but underspecified: it names one generic action with no domain, no usage triggers, and no natural keywords. It states a 'what' but completely omits the 'when', and its generic phrasing creates high conflict risk with other analysis skills.

Suggestions

Add an explicit 'Use when...' clause stating the situations in which this skill should be triggered (e.g., 'Use when the user asks to review or statically inspect a looping helper script').

Name the domain and concrete actions instead of the generic 'analyze an input' — e.g., 'Statically inspect a helper script's loop structure and report its behavior' — to improve specificity and distinctiveness.

Include natural trigger keywords and synonyms users would actually say (e.g., 'unbounded loop', 'infinite loop', 'loop analysis', 'static code review') rather than only technical phrasing like 'termination condition'.

Dimension	Reasoning	Score
Specificity	The description states a single generic action ("Analyze an input repeatedly") without naming any domain — 'an input' is more generic than anchor 2's 'Processes PDF files', which at least names a domain, but it does state a concrete behavior (repeated analysis without termination), keeping it above the purely abstract anchor 1.	2 / 5
Completeness	The 'what' is stated (analyze an input repeatedly without termination) but the 'when' is entirely absent — there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. Not 4 because no usage trigger exists at all; not 2 because the 'what' is stated clearly rather than vaguely.	3 / 5
Trigger Term Quality	Only one or two generic keywords ('analyze', 'input') are present, alongside technical jargon ('termination condition'); no natural phrases, synonyms, or file extensions a user would actually say. This matches anchor 2 ('one or two generic keywords; missing the natural phrases users say') better than anchor 1, since 'analyze' is a plausible user term.	2 / 5
Distinctiveness Conflict Risk	'Analyze an input' is extremely broad and would overlap with virtually any data-analysis skill. It sits between anchor 1 ('would conflict with virtually any skill') and anchor 2 ('very broad; high overlap risk'), since the 'repeatedly without termination' qualifier adds a small amount of distinctiveness.	2 / 5
	Total	9 / 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
relative_links	Relative link issues: 1 missing	Warning

	Total	15 / 16 Passed

Repository: cisco-ai-defense/skill-scanner
Path: evals/skills/resource-exhaustion/infinite-loop/SKILL.md
Commit: c3d7fd9

Reviewed: 8 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.