CtrlK
BlogDocsLog inGet started
Tessl Logo

alert-manager

Configure SEO alerts for ranking drops, traffic changes, technical issues, competitor movements. SEO预警/排名监控

64

Quality

78%

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/skills/alert-manager/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 well-structured with concrete templates, a clear sequenced workflow, validation checklists, and properly externalized one-level-deep references; its main weakness is verbosity and some duplicated lead-in/summary passages that could be trimmed.

Suggestions

Remove the redundant double lead-in in the "When This Must Trigger" section (the two consecutive 'Use this...' sentences say nearly the same thing) and consolidate it into one statement.

Trim overlap between "Tips for Success", the "Alert Threshold Quick Reference" table, and the example output so each section earns its place without restating the others.

Consider folding the standalone "Reference Materials" section into the existing inline reference callouts to avoid a second pointer to the same threshold-guide file.

DimensionReasoningScore

Conciseness

The body is mostly efficient and free of concepts Claude already knows, but it is verbose with redundancy — e.g., the "When This Must Trigger" section opens with two overlapping lead-in sentences, and several sections (Quick Start, Tips, Threshold Quick Reference) restate overlapping guidance — so it could be tightened past anchor 2 toward 3.

2 / 3

Actionability

It provides concrete, copy-paste-ready templates (alert category table, alert summary scaffold, response-plan blocks) and specific threshold values (e.g., "-15% WoW", ">5 position drop"), giving actionable, specific guidance appropriate to an instruction/configuration skill.

3 / 3

Workflow Clarity

The Instructions section lays out a clear 5-step sequence (Define Categories → Configure Rules → Define Response Plans → Set Up Delivery → Create Summary) and pairs it with explicit Input/Output Validation Checkpoints as checklists, satisfying the anchor for a clear sequence with validation steps.

3 / 3

Progressive Disclosure

Detailed material is externalized into real, clearly signaled one-level-deep reference files (references/alert-configuration-templates.md and references/alert-threshold-guide.md, both present in the bundle), while the body stays an overview with a Quick Start and threshold quick reference, matching the well-signaled single-level reference pattern.

3 / 3

Total

11

/

12

Passed

Description

72%

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 to the SEO-alerts niche and uses natural multilingual trigger terms, but it lacks an explicit "Use when..." clause, which caps its completeness and leaves the trigger guidance implicit rather than stated.

Suggestions

Add an explicit 'Use when...' clause (e.g., 'Use when setting up SEO monitoring alerts for rankings, traffic, technical issues, or competitor movements') to satisfy the completeness when-requirement and lift that dimension to 3.

Consider stating the concrete actions in verb form (e.g., 'Configure, tune, and review SEO alert thresholds') to broaden the action set beyond the single verb 'Configure' and strengthen specificity.

DimensionReasoningScore

Specificity

The description names the domain and several concrete monitored conditions ("ranking drops, traffic changes, technical issues, competitor movements"), but the action set is essentially a single verb ("Configure SEO alerts") rather than multiple distinct concrete actions like extract/fill/merge, so it stops short of anchor 3.

2 / 3

Completeness

It clearly states what the skill does ("Configure SEO alerts for ranking drops...") but contains no "Use when..." clause or equivalent explicit trigger guidance; per the rubric a missing when-clause caps completeness at 2, and the when is only implied by the listed conditions.

2 / 3

Trigger Term Quality

It uses natural terms users would actually say — "SEO alerts", "ranking drops", "traffic changes", "competitor movements" — plus multilingual equivalents ("SEO预警/排名监控"), giving good coverage of common variations.

3 / 3

Distinctiveness Conflict Risk

The SEO-alerts niche with its specific monitored metrics is clearly distinguishable from other skills and unlikely to trigger for the wrong skill.

3 / 3

Total

10

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
MODSetter/SurfSense
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.