CtrlK
BlogDocsLog inGet started
Tessl Logo

analyze-dashboard

Deeply analyze Amplitude dashboards by analyzing key charts, surfacing top areas for concern and takeaways, identify anomalies, then explain changes using customer feedback trends.

68

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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 tight, highly actionable workflow with concrete Amplitude tool calls, chart-type-specific analysis rules, and a clear sequenced procedure with decision checkpoints. It assumes Claude's competence and stays within a single well-organized file with no unnecessary reference indirection.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it never explains what Amplitude or a dashboard is, and every line is actionable domain guidance (chart-type signals, tool calls, output structure) that earns its place.

3 / 3

Actionability

Gives concrete, executable tool calls with parameters (Amplitude:get_dashboard, query_charts, get_feedback_insights with projectId/dateStart/dateEnd, get_feedback_mentions) plus specific per-chart-type analysis rules and a defined output structure — copy-paste ready guidance.

3 / 3

Workflow Clarity

A clear Step 0–5 sequence with explicit decision checkpoints (chart prioritization, 'Skip this step if...' conditions, 'if a relevant insight is found'); this is a read-only analysis workflow so the destructive/batch validation cap does not apply.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the single SKILL.md is well-organized into When to Use, sequenced Instructions, and Best Practices sections with no nested references, satisfying the self-contained well-organized-sections allowance.

3 / 3

Total

12

/

12

Passed

Description

67%

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 specific and well-differentiated, naming several concrete analysis actions tied to a clear Amplitude-dashboard niche. Its weakness is the missing explicit 'Use when...' trigger clause in the description field itself, which caps completeness and leaves natural trigger-term coverage partial.

Suggestions

Add an explicit 'Use when...' clause to the description naming natural user phrasings (e.g. 'Use when the user asks to review or walk through an Amplitude dashboard, prep for a meeting, or explain why a metric moved').

Include common natural trigger terms directly in the description ('dashboard review', 'walk me through this dashboard', 'why did this metric change') rather than only in suggest_when.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'analyzing key charts, surfacing top areas for concern and takeaways, identify anomalies, then explain changes using customer feedback trends' — matching the multi-action anchor.

3 / 3

Completeness

It clearly answers 'what' (analyze dashboards, surface concerns, explain changes via feedback) but lacks any explicit 'Use when...' trigger clause in the description; the when guidance lives only in suggest_when, capping completeness at 2 per the missing-trigger guideline.

2 / 3

Trigger Term Quality

Domain terms like 'Amplitude dashboards', 'charts', and 'anomalies' are present, but common natural phrasings a user would say (e.g. 'walk me through this dashboard', 'review a dashboard') only appear in suggest_when, not the description, so coverage of natural variations is partial.

2 / 3

Distinctiveness Conflict Risk

The 'Amplitude dashboards' niche with feedback-correlation framing is a clear, distinct trigger set unlikely to fire for unrelated skills.

3 / 3

Total

10

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
amplitude/builder-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.