CtrlK
BlogDocsLog inGet started
Tessl Logo

weekly-review

Produce a weekly synthesis of authored commits with highlights by bugfix, tech debt, and net-new work

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 ./cursor-team-kit/skills/weekly-review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

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

The body is concise, well-organized, and clearly sequenced with a sensible guardrail checkpoint. The main gap is actionability — providing the actual git commands to collect authored commits would make the guidance copy-paste ready.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned (Trigger, Workflow, Guardrails, Output) with no concept-padding or unnecessary explanation; every line earns its place.

3 / 3

Actionability

Steps carry concrete parameters (7-10 days, exclude merge commits, 2-5 bullets, three classification categories), but no executable git commands are given and 'primary branch context' is left vague.

2 / 3

Workflow Clarity

A clear 5-step numbered sequence with an explicit checkpoint ('If git email is missing, ask the user to set it before proceeding'); for this simple single-purpose skill, the well-organized flow satisfies the top anchor.

3 / 3

Progressive Disclosure

Under 50 lines with a single task and no need for external references; the four clearly labeled sections provide appropriate organization, satisfying the simple-skill guidance.

3 / 3

Total

11

/

12

Passed

Description

57%

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 produces and carves out a distinct niche, but it lacks an explicit 'Use when...' trigger clause and broader natural-language trigger terms. Adding trigger guidance would lift completeness and trigger-term quality.

Suggestions

Add an explicit 'Use when...' clause, e.g. 'Use when the user needs a weekly recap or status update of recently shipped work for retros or planning.'

Broaden trigger terms to common user phrasings — 'weekly recap', 'weekly review', 'status update', 'standup summary', 'retro'.

Lead with more concrete verbs (e.g. 'Summarize, classify, and highlight authored commits...') to strengthen the specificity of capabilities.

DimensionReasoningScore

Specificity

Names the domain ('authored commits') and a main action ('Produce a weekly synthesis') with a categorized output structure, but it describes a single deliverable rather than multiple distinct concrete actions like the 3-anchor's 'extract, fill, merge'.

2 / 3

Completeness

The 'what' is clearly stated, but there is no explicit 'Use when...' trigger clause, so per the judging guidelines completeness is capped at 2.

2 / 3

Trigger Term Quality

Includes relevant natural terms ('weekly', 'authored commits', 'bugfix', 'tech debt', 'net-new work') but omits common variations users would actually say, such as 'weekly recap', 'weekly review', 'status update', or 'retro'.

2 / 3

Distinctiveness Conflict Risk

The niche — a weekly synthesis of authored commits categorized into bugfix/tech debt/net-new — is specific and unlikely to trigger for an unrelated skill.

3 / 3

Total

9

/

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
cursor/plugins
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.