alert-manager

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

Quality

66%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/alert-manager/SKILL.md

Quality

Content

67%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 content is well-structured and actionable with clear workflows, validation checkpoints, and properly signaled references to real bundle files. Its main weakness is moderate verbosity from inline template duplication that overlaps the referenced guides.

Suggestions

Remove the inline 'Alert Threshold Quick Reference' table and defer fully to references/alert-threshold-guide.md to cut duplication and tokens.

Trim filler checklist lines (e.g. 'Don't panic') and consolidate the two large inline markdown templates into the reference files, keeping only a compact example in SKILL.md.

Tighten the Data Sources and Skill Contract sections, which repeat concepts already implied by the Instructions and Validation Checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with clear sections, but it carries padded inline table templates, a duplicated threshold table that also lives in the referenced guide, and filler checklist lines like 'Don't panic', so it could be tightened.	3 / 5
Actionability	Concrete templates (alert category table, summary table, threshold quick reference) plus a worked example with real keyword rows and a numbered response plan give mostly executable guidance, with only minor gaps from placeholder fields like [domain] and [X].	4 / 5
Workflow Clarity	A clear five-step Instructions sequence is paired with dedicated Input/Output Validation Checkpoints and review checklists, giving most checkpoints with only minor validation gaps for a non-destructive configuration task.	4 / 5
Progressive Disclosure	The body points to two real, verified reference files (alert-configuration-templates.md, alert-threshold-guide.md) with clearly signaled one-level-deep 'Reference' callouts; the main gap is the inline threshold table duplicating the referenced guide.	4 / 5
	Total	15 / 20 Passed

Description

66%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 is specific and trigger-rich, with concrete monitoring domains and multilingual terms, but it omits an explicit 'when to use' clause from the description field itself, capping completeness. Adding a 'Use when...' trigger phrase directly in the description would raise it.

Suggestions

Append an explicit trigger clause to the description field, e.g. 'Use when setting up monitoring alerts for rankings, traffic, backlinks, or AI visibility changes.'

Add a few more natural synonyms/extensions users say (e.g. 'backlink alerts', 'indexing alerts', 'drop notifications') to broaden trigger-term coverage toward 5.

Keep the third-person voice (currently correct) but ensure the verb directly leads the 'when' clause to lock in a 5 on completeness.

Dimension	Reasoning	Score
Specificity	The description names a concrete action ('Configure SEO alerts') plus four specific monitoring domains ('ranking drops, traffic changes, technical issues, competitor movements'), listing several specific concrete items with only minor gaps in coverage.	4 / 5
Completeness	It clearly states 'what' the skill does but the description field itself contains no 'Use when...' trigger clause (that guidance lives in the separate when_to_use field), so per the missing-trigger-clause rule completeness is capped at 3.	3 / 5
Trigger Term Quality	Natural user-facing terms ('SEO alerts', 'ranking drops', 'traffic changes', 'technical issues', 'competitor movements') are present, supplemented by multilingual variants (SEO预警/排名监控), giving good keyword coverage with a few natural synonyms missing.	4 / 5
Distinctiveness Conflict Risk	The SEO-alerting niche with specific metric categories is mostly distinct from other skills, with only minor overlap risk against a generic rank-tracking or monitoring skill.	4 / 5
	Total	15 / 20 Passed

Validation

87%

Warnings & errors only

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

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: .cursor/skills/alert-manager/SKILL.md
Commit: be4a191

Reviewed: 15 days ago

Table of Contents

Discovery Implementation Validation

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.