CtrlK
BlogDocsLog inGet started
Tessl Logo

retro

Analyze sprint retrospectives for patterns and action item tracking. Usage: /retro analyze <retro_data.json>

61

Quality

71%

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 ./.gemini/skills/retro/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 a tight, well-organized, single-action skill with concrete commands and a clear input schema. Its main weakness is that the script and SKILL references point to external paths that are not part of this skill's own bundle, slightly weakening navigation.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned with no over-explanation of concepts Claude knows; minor trim opportunities exist in the duplicated command between 'Usage' and 'Examples' and the cross-skill reference pointer.

4 / 5

Actionability

Provides concrete commands, a copy-paste-ready input JSON schema, examples, and a script path with args; the minor gap is that no sample output or interpretation of the analysis is shown.

4 / 5

Workflow Clarity

This is a single-purpose, under-50-line read-only analysis skill whose single action ('/retro analyze <retro_data.json>') is unambiguous and well-specified, qualifying for the simple-skill exception.

5 / 5

Progressive Disclosure

Content is cleanly split into signaled one-level-deep sections (Usage, Input Format, Examples, Scripts, Skill Reference), but the referenced paths point outside this skill's bundle to 'project-management/skills/scrum-master/...' with no local bundle files present.

4 / 5

Total

17

/

20

Passed

Description

61%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 clearly states what the skill does and uses natural trigger terms, but it omits an explicit 'Use when...' clause, leaving the activation context only weakly implied. It is reasonably specific and distinct, though the action list is not comprehensive.

Suggestions

Add an explicit 'Use when...' trigger clause, e.g. 'Use when the user mentions sprint retrospectives, retro meetings, action item follow-up, or wants to analyze retrospective data.'

Expand the action list beyond 'patterns' and 'action item tracking' to concrete capabilities like 'sentiment trends' and 'action item effectiveness' that already appear in the body.

Include common synonyms such as 'retro meeting' or 'team retrospective' to broaden natural trigger coverage.

DimensionReasoningScore

Specificity

Names the domain ('sprint retrospectives') and two concrete actions ('patterns' and 'action item tracking'), matching the anchor for 1-2 concrete actions without comprehensive coverage.

3 / 5

Completeness

Has a clear 'what' ('Analyze sprint retrospectives for patterns and action item tracking') but only a 'Usage:' command, not an explicit 'Use when...' trigger, which caps completeness at 3 per the guidelines.

3 / 5

Trigger Term Quality

Includes natural terms a user would say ('sprint retrospectives', 'action item', 'retro') with good coverage; not a 5 because synonyms like 'retro meeting' or file extensions are absent.

4 / 5

Distinctiveness Conflict Risk

'Analyze sprint retrospectives' carves a specific niche with distinct triggers, though it has minor overlap risk with broader scrum/agile project-management 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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
alirezarezvani/claude-skills
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.