CtrlK
BlogDocsLog inGet started
Tessl Logo

analysis

Comprehensive analysis operations for code, skills, processes, data, and patterns. Task-based operations with pattern recognition, metrics calculation, trend identification, and actionable insights generation. Use when analyzing code quality, reviewing skill effectiveness, identifying process improvements, extracting patterns, or generating insights from data.

56

Quality

66%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

52%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 per operation with useful checklists and example outputs, but it is far too long, lectures on concepts Claude already knows, and ships dangling references to nonexistent bundle files. It reads as an inlined reference manual rather than a lean SKILL.md overview.

Suggestions

Trim the Best Practices and Common Mistakes sections to a few bullet points or move them into a references/ file — Claude already knows confirmation bias, correlation-vs-causation, and analysis paralysis.

Cut the 30-40 line self-referential example blocks per operation down to one compact representative snippet, or relocate full examples to references/examples.md.

Create the referenced files (references/code-analysis-guide.md, references/skill-metrics-guide.md, references/pattern-recognition-guide.md) or remove the "For More Information" links so progressive disclosure is not built on missing targets.

DimensionReasoningScore

Conciseness

The 816-line body is noticeably verbose: the Common Mistakes section lectures on confirmation bias, correlation vs. causation, and analysis paralysis, and the Operations section pads each entry with 30-40 line self-referential example outputs, all concepts Claude already knows — below a 3 because several sections are pure padding.

2 / 5

Actionability

Each operation gives a concrete numbered Process, a Validation Checklist, an Outputs list, and a full example output, so the guidance is specific and actionable; it stops short of 5 only because some steps remain high-level directives ("Calculate Metrics", "Identify Patterns") without exact methods.

4 / 5

Workflow Clarity

Every operation has a clearly sequenced 5-step process plus an explicit Validation Checklist, giving strong checkpoints; it is not a 5 because the checklists are completeness gates rather than error-recovery feedback loops, and the operations are read-only so no destructive-validation cap applies.

4 / 5

Progressive Disclosure

The file is a monolithic 816-line wall with massive inlined examples and full Best Practices / Common Mistakes sections that belong in reference files, and the three "For More Information" links point to references/*.md files that do not exist in the bundle — minimal real structure, below a 3.

2 / 5

Total

12

/

20

Passed

Description

80%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 strong description that clearly states both capability and trigger conditions with concrete "Use when" phrasing in third person. Its main weakness is breadth — "analysis" spans five domains and overlaps with several more specific review/analysis skills.

DimensionReasoningScore

Specificity

Names the domain (code, skills, processes, data, patterns) and lists several concrete operations — "pattern recognition, metrics calculation, trend identification, and actionable insights generation" — but the operations stay somewhat abstract rather than fully concrete, so it sits below a 5.

4 / 5

Completeness

It explicitly answers both what ("Comprehensive analysis operations... pattern recognition, metrics calculation, trend identification... ") and when ("Use when analyzing code quality, reviewing skill effectiveness... or generating insights from data") with concrete trigger phrases.

5 / 5

Trigger Term Quality

The "Use when" clause surfaces natural phrases users would say ("analyzing code quality", "reviewing skill effectiveness", "identifying process improvements", "extracting patterns", "generating insights from data"), but it lacks synonyms and file-extension variants that would push it to 5.

4 / 5

Distinctiveness Conflict Risk

The five enumerated operations give it some shape, but the name "analysis" and triggers like "analyzing code quality" / "reviewing skill effectiveness" overlap heavily with code-review and skill-reviewer skills, so it is not clearly distinct — above a 2 because it does carve out a recognizable niche.

3 / 5

Total

16

/

20

Passed

Validation

81%

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

Validation13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (817 lines); consider splitting into references/ and linking

Warning

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

referenced_paths_exist

Referenced path issues: 3 missing

Warning

Total

13

/

16

Passed

Repository
fernandezbaptiste/Skrillz
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.