CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

zoom-out

Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.

66

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary prompt-style skill body: lean, concrete, and unambiguous, with a specific deliverable (map of modules and callers using domain glossary vocabulary). The only nitpick is the unstated assumption that a project domain glossary exists.

DimensionReasoningScore

Conciseness

Two lean sentences with zero padding — every token earns its place and nothing explains what Claude already knows. This matches the "lean and efficient; assumes Claude's competence" anchor exactly.

5 / 5

Actionability

The guidance is concrete for an instruction-only skill: "Go up a layer of abstraction. Give me a map of all the relevant modules and callers, using the project's domain glossary vocabulary" specifies an exact deliverable. It falls short of fully executable only because it assumes a domain glossary exists without offering a fallback.

4 / 5

Workflow Clarity

This is a simple, single-purpose skill (a single prompt with one unambiguous action), which the scoring notes say can score 5 when the action is unambiguous. No destructive or batch operations are involved, so no validation cap applies.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external references — a two-sentence prompt has nothing to split or disclose progressively, and no bundle files exist to reference. This fits the simple-skill exception for a clean top score.

5 / 5

Total

19

/

20

Passed

Description

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

A well-structured description with an explicit and natural "Use when..." trigger clause and clear what/when coverage. Its main weakness is that the capability description stays abstract — the concrete deliverables only appear in the body — and the second-person phrasing in the trigger clause violates the third-person voice convention.

Suggestions

Replace the generic capability phrase with the concrete deliverables from the body, e.g. "Produces a map of the relevant modules and callers in a codebase, framed one level of abstraction above the current code".

Rewrite the trigger clause in third person to remove "you're" (e.g. "Use when the user is unfamiliar with a section of code or asks how it fits into the bigger picture") to avoid the voice penalty.

Add a few natural synonyms to the trigger coverage — "overview", "architecture", or "how the pieces fit together" — to strengthen trigger term quality toward the top anchor.

DimensionReasoningScore

Specificity

The description names the domain (code comprehension) but the actions are generic — "zoom out and give broader context or a higher-level perspective" names no concrete deliverable (the concrete "map of modules and callers" guidance lives only in the body). The second-person clause "Use when you're unfamiliar" further costs 1 point per the voice guideline.

2 / 5

Completeness

Both parts are present: a what ("Tell the agent to zoom out and give broader context or a higher-level perspective") and an explicit "Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture" clause. The what is explicit but not fully concrete, so it sits between the 4 and 5 anchors.

4 / 5

Trigger Term Quality

Natural trigger phrases are present — "zoom out", "broader context", "higher-level perspective", "unfamiliar with a section of code", "bigger picture" — giving good keyword coverage, though a few natural synonyms ("overview", "architecture", "how does this fit together") are missing.

4 / 5

Distinctiveness Conflict Risk

"Zoom out" / "bigger picture" framing carves a reasonably distinct niche, with only minor overlap risk against closely related skills like code-explanation or architecture-review skills.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

SnowingFox/ai-skills

Path

.cursor/skills/zoom-out/SKILL.md

Reviewed

Table of Contents

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.