CtrlK
BlogDocsLog inGet started
Tessl Logo

performance-reporter

Generate comprehensive performance reports with insights and actionable recommendations.

56

Quality

64%

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 ./apps/desktop/electron/default-skills/performance-reporter/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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 well-organized, lean instruction skill with concrete guidance and a clear sequenced workflow plus a data-quality checkpoint. Its main gaps are the absence of a worked example and a validate-retry feedback loop, which keep actionability and workflow clarity at 4 rather than 5.

DimensionReasoningScore

Conciseness

The body is lean and does not explain concepts Claude already knows, but a few stylistic flourishes ("Report like an analyst the team actually wants to hear from", "Keep tables tight and the prose tighter") are mild over-explanation that could be trimmed, fitting the efficient-with-minor-instances anchor.

4 / 5

Actionability

Guidance is concrete and specific — named metrics ("engagement, reach, growth"), explicit counts ("3-5 concrete recommendations", "3-5 sentences"), and a defined output section structure — but no worked example or sample output is provided, leaving a minor gap.

4 / 5

Workflow Clarity

The five numbered steps give a clear sequence and there is an explicit data-quality checkpoint ("Flag data quality issues... rather than reporting on top of broken inputs"), but there is no validate→fix→retry feedback loop for handling flagged bad data, so it stops short of the top anchor.

4 / 5

Progressive Disclosure

The skill is under 50 lines, single-purpose, and organized into clear sections (When to use, Reporting principles, How to approach, Output format) with a well-signaled boundary pointer to "Audience Analyst"; no external references are needed, so per the simple-skill guideline it scores 5 on organization alone.

5 / 5

Total

17

/

20

Passed

Description

50%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 states a clear purpose but is generic and buzzword-padded, with no explicit "Use when..." trigger guidance and ambiguous scope that risks overlap with other reporting skills. It answers "what" but not "when," landing at middling scores across all dimensions.

Suggestions

Add an explicit "Use when..." clause naming concrete triggers, e.g. "Use when the user asks for a performance report on social/content metrics (engagement, reach, growth) or wants to compare platforms or time periods."

Replace buzzwords ("comprehensive", "actionable") with the specific natural terms users say — metrics, analytics, engagement, reach, KPIs, platform comparison — to improve trigger-term coverage and specificity.

Disambiguate "performance" as social/content marketing performance (vs. app or financial performance) so the skill is clearly distinguishable from other analytics or reporting skills.

DimensionReasoningScore

Specificity

"Generate comprehensive performance reports with insights and actionable recommendations" names the domain plus two-to-three actions (generate reports, provide insights, provide recommendations), but "comprehensive" and "actionable" are buzzwords that pad rather than specify, matching the anchor for naming a domain with 1-2 concrete actions.

3 / 5

Completeness

It gives a clear "what" (generate performance reports with insights and recommendations) but has no "Use when..." clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

It includes relevant keywords ("performance reports", "insights", "recommendations") but omits the natural domain terms a user would actually say — metrics, analytics, engagement, KPIs — which the body itself relies on, so coverage has relevant keywords but misses common variations.

3 / 5

Distinctiveness Conflict Risk

"Performance reports" is somewhat specific but "performance" is ambiguous (app, social, financial performance) and the description does not disambiguate, so it could still overlap with other analytics or reporting skills.

3 / 5

Total

12

/

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
holaboss-ai/holaOS
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.