CtrlK
BlogDocsLog inGet started
Tessl Logo

analyzing-projects

Analyzes codebases to understand structure, tech stack, patterns, and conventions. Use when onboarding to a new project, exploring unfamiliar code, or when asked "how does this work?" or "what's the architecture?"

77

Quality

96%

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%

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

The content is a well-structured, token-efficient analysis workflow with concrete commands, templates, and explicit validation checkpoints, scoring top marks on conciseness, actionability, and workflow clarity. Its only gap is progressive disclosure: everything lives in one inline file with no offloaded reference material.

Suggestions

Move the large output-template block (Step 6) and the tech-stack/framework/infrastructure marker tables into a separate reference file (e.g., references/analysis-template.md) referenced from the body, to shorten SKILL.md and add one-level-deep navigation.

Add a brief "References" section near the top signaling any offloaded templates/cheat-sheets so the structure of the bundle is discoverable at a glance.

If the skill is intended to stay single-file, trim below ~50 lines by extracting the templates so the simple-skill exemption can apply to progressive disclosure.

DimensionReasoningScore

Conciseness

The body is lean checklists, command snippets, file-marker mapping tables, and fill-in templates with no padding or explanation of concepts Claude already knows; every section earns its tokens.

3 / 3

Actionability

Provides concrete executable commands (ls -la, cat README.md), specific file→tech-stack marker mappings, a directory-tree template, and a copy-paste ready output template — actionable guidance throughout.

3 / 3

Workflow Clarity

A clearly sequenced 6-step workflow with a progress checklist and a final "Analysis Validation" checklist acting as an explicit verification checkpoint; the read-only nature of the task means no destructive feedback loop is required.

3 / 3

Progressive Disclosure

Single ~155-line file with all content inline and no external references; the output template and tech-stack mapping tables are well-organized but could be split into reference files, and the >50-line threshold means well-organized sections alone do not reach the top anchor.

2 / 3

Total

11

/

12

Passed

Description

100%

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 strong: it states concrete capabilities, includes natural user-facing trigger terms and quoted questions, answers both what and when explicitly, and occupies a distinct niche. It follows third-person voice throughout with no over-claims.

DimensionReasoningScore

Specificity

"Analyzes codebases to understand structure, tech stack, patterns, and conventions" lists multiple concrete analysis targets, matching the anchor for listing several specific concrete actions.

3 / 3

Completeness

Explicitly states both what ("Analyzes codebases to understand structure, tech stack, patterns, and conventions") and when ("Use when onboarding...") with explicit triggers.

3 / 3

Trigger Term Quality

"onboarding to a new project, exploring unfamiliar code, or when asked 'how does this work?' or 'what's the architecture?'" gives good coverage of natural phrasings users would say, including quoted questions.

3 / 3

Distinctiveness Conflict Risk

Targets a clear codebase-onboarding/architecture-exploration niche with distinct triggers; unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
CloudAI-X/claude-workflow-v2
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.