serp-analysis

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

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

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

Quality

Content

70%

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 a clear sequenced workflow, explicit validation checklists, and clean one-level-deep references to real bundle files. Its weaknesses are mild verbosity from duplicated/boilerplate sections and non-executable placeholder notation for optional tool integrations.

Suggestions

Remove the duplicated trigger lead-ins and merge 'What This Skill Does' into the 'Instructions' to cut redundant tokens and lift conciseness.

Replace the '~~SEO tool / ~~search console / ~~AI monitor' placeholders with concrete, named integration patterns (or a single explicit 'manual data only' path) to make the data-source guidance executable.

Trim the library banner and Skill-Contract/System-Mode boilerplate at the top, or move it to a referenced file, to tighten the opening.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining basics Claude knows, but includes redundant boilerplate — two near-identical 'Use this when...' lead-ins, a 'What This Skill Does' list that duplicates the 'Instructions' steps, and library/Skill-Contract banner text — that could be tightened.	2 / 3
Actionability	The Instructions give detailed, specific checklists (exact fields to capture per top-10 result, a 1–100 difficulty scale, defined output sections), but the tool-integration mechanics use non-executable '~~SEO tool' placeholders rather than concrete commands or APIs, leaving it short of fully copy-paste-ready.	2 / 3
Workflow Clarity	Presents a clear 8-step sequence (Understand Query → Map Composition → Analyze Pages → Identify Patterns → Analyze Features → Determine Intent → Calculate Difficulty → Generate Recommendations) backed by explicit input and output validation checklists, matching the anchor-3 'clear sequence with explicit validation steps'.	3 / 3
Progressive Disclosure	SKILL.md is a concise overview that points to three real, one-level-deep bundle files (analysis-templates.md, serp-feature-taxonomy.md, example-report.md), each clearly signaled with a one-line description in the Reference Materials section, matching the anchor-3 example.	3 / 3
	Total	10 / 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 its SERP niche with good natural trigger terms and low conflict risk, but it relies on a single action verb and omits an explicit 'Use when' clause within the description field itself, leaving completeness and action breadth at the mid level.

Suggestions

Add an explicit 'Use when...' clause to the description field (e.g., 'Use when analyzing search results pages, featured snippets, People Also Ask, or AI overviews for a query') to reach completeness level 3.

Vary the verbs beyond a single 'Analyze' to name distinct concrete actions (e.g., 'Map SERP features, identify ranking factors, assess difficulty') to lift specificity to 3.

Add the very common natural term 'People Also Ask' / 'PAA' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the SERP domain and enumerates concrete analysis targets ('ranking factors, features, intent patterns, AI overviews, featured snippets'), but uses a single verb ('Analyze') rather than listing multiple distinct actions, so it sits at anchor 2 rather than 3.	2 / 3
Completeness	Clearly answers 'what' (analyze SERPs for the listed facets) but the description field itself lacks an explicit 'Use when...' trigger clause, capping completeness at 2 per the judging guideline.	2 / 3
Trigger Term Quality	Includes several natural terms users would actually say — 'SERPs', 'featured snippets', 'AI overviews', 'ranking factors' — plus CJK variants, giving good coverage comparable to the anchor-3 example.	3 / 3
Distinctiveness Conflict Risk	Carves a clear niche (SERP/search-results analysis with featured-snippet/AI-overview triggers) that is unlikely to fire for unrelated skills, matching the anchor-3 'clear niche with distinct triggers'.	3 / 3
	Total	10 / 12 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/serp-analysis/SKILL.md
Commit: 3b319ce

Reviewed: about 14 hours 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.