CtrlK
BlogDocsLog inGet started
Tessl Logo

serp-analysis

Analyze SERPs: ranking factors, features, intent patterns, AI overviews, featured snippets. SERP分析/搜索结果

64

Quality

77%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.cursor/skills/serp-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

77%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 a well-structured, actionable research skill with an explicit sequenced workflow and validation checklists, supported by real, clearly-signaled reference files; its main weakness is padding and frontmatter-trigger duplication that could be trimmed.

Suggestions

Remove the 'When This Must Trigger' bullet list since it duplicates the frontmatter when_to_use and triggers, and cut the editorial line 'Understand the battlefield before creating content' to tighten conciseness.

Condense the Skill Contract and Data Sources sections to the essential 'Reads/Writes/Promotes/Next handoff' lines, dropping explanatory prose Claude can infer.

DimensionReasoningScore

Conciseness

The body is mostly efficient but carries padding — the editorial line 'Understand the battlefield before creating content', the 'When This Must Trigger' list that duplicates the frontmatter triggers, and the verbose Skill Contract/Data Sources sections restate things Claude can infer, fitting the 'mostly efficient with some unnecessary explanation' anchor.

3 / 5

Actionability

An 8-step procedure with concrete per-step fields to document (URL, domain authority, word count, H1, backlinks) plus explicit input prompts gives mostly executable guidance with only minor gaps, matching the anchor-4 example for an instruction-only skill.

4 / 5

Workflow Clarity

A clearly sequenced 8-step workflow is paired with an explicit 'Validation Checkpoints' section containing input and output checklists, matching the anchor-5 'clear sequence with explicit validation steps and checklists'; the destructive/batch cap does not apply to this research skill.

5 / 5

Progressive Disclosure

The overview points to three verified, one-level-deep bundle files (references/analysis-templates.md, example-report.md, serp-feature-taxonomy.md) each clearly signaled with its scope, matching the anchor-5 'clear overview with well-signaled one-level-deep references'.

5 / 5

Total

17

/

20

Passed

Description

77%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 distinctive with strong trigger-term coverage including multilingual synonyms, but it lacks an explicit 'when to use' clause within the description field itself, capping completeness at the midpoint.

Suggestions

Append an explicit 'Use when...' clause to the description (e.g., 'Use when analyzing search engine results pages, featured snippets, or AI overviews for a query') so trigger guidance lives in the description field, not only in when_to_use.

Rewrite the capability list as verb-led actions ('Analyze ranking factors, map SERP features, detect search intent...') to lift specificity from a colon-list to a full action list.

DimensionReasoningScore

Specificity

Lists five concrete analysis outputs ('ranking factors, features, intent patterns, AI overviews, featured snippets'), giving multiple specific capabilities, but they are framed as a colon-list rather than the verb-led action list of the anchor-5 example, leaving a minor gap.

4 / 5

Completeness

The description gives a clear 'what' but contains no 'Use when...' trigger clause; per the rubric, a missing explicit trigger guidance caps completeness at 3, even though a separate when_to_use field exists in the frontmatter.

3 / 5

Trigger Term Quality

Covers natural terms users say ('SERPs', 'ranking factors', 'AI overviews', 'featured snippets') plus multilingual synonyms ('SERP分析', '搜索结果分析'), matching the comprehensive-synonym coverage of the anchor-5 example.

5 / 5

Distinctiveness Conflict Risk

Targets a clearly distinct SERP-analysis niche with specific feature triggers, minimizing overlap with other skills, matching the anchor-5 'clear niche with distinct triggers'.

5 / 5

Total

17

/

20

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.