CtrlK
BlogDocsLog inGet started
Tessl Logo

serp-analysis

Use when the user asks to "analyze the SERP" or "SERP分析"; maps SERP features, layout, ranking factors, search intent, AI Overviews, and snippet opportunities for a query. Not for keyword demand discovery — use keyword-research. SERP分析/搜索结果

64

Quality

80%

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 ./seo-geo/survey/serp-analysis/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

80%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.

A well-structured, mostly lean skill that gives executable connector commands and clear step sequencing with explicit completion criteria, and properly offloads detail to real reference files. The main improvements are trimming a few repeated framing passages and adding an explicit verification feedback loop in the workflow.

Suggestions

Add an explicit validation checkpoint (e.g., 'confirm every difficulty/intent claim cites a specific feature or top result; if not, re-examine the SERP before finalizing') to give the workflow a validate->fix->retry loop.

Remove the duplicated True Difficulty weighting (stated in both the Instructions and the template reference) and tighten the Measured/User-provided/Estimated preamble to improve conciseness.

Inline one fully copy-paste-ready example command invocation for the firecrawl+Tavily corroboration flow rather than describing the two calls separately.

DimensionReasoningScore

Conciseness

Largely efficient and assumes Claude's knowledge of SERP concepts; minor instances of over-explanation (e.g., restating the 25/20/20/20/15 weighting twice and the Measured/User-provided/Estimated labeling preamble).

4 / 5

Actionability

Provides concrete executable commands (the firecrawl.py and tavily.py invocations with flags) and clear templates, but the core 8-step workflow is mostly descriptive with detailed steps deferred to references rather than fully copy-paste ready.

4 / 5

Workflow Clarity

The 8-step process is clearly numbered and sequenced with explicit Done-when criteria and a Quality bar checkpoint, but it lacks an explicit validate->fix->retry feedback loop and the destructive/batch-operations cap does not apply here.

4 / 5

Progressive Disclosure

SKILL.md is a lean overview with well-signaled one-level-deep references (analysis-templates.md, serp-feature-taxonomy.md, example-report.md) that all exist as real files, and bulk detail is appropriately split into those references.

5 / 5

Total

17

/

20

Passed

Description

80%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.

A strong description that names concrete capabilities, provides natural trigger terms in both English and Chinese, and clearly disambiguates from the related keyword-research skill. The main gap is slightly thinner coverage of common trigger variations and a few specificity gaps around competitor/local analysis.

Suggestions

Add a few more natural trigger phrases users would say, e.g. 'why am I not ranking for [keyword]' or 'what does it take to rank for [keyword]', to broaden trigger_term_quality.

Tighten the 'what' list to be more comprehensive (e.g., add competitor identification and local-pack analysis) to lift specificity from 4 to 5.

DimensionReasoningScore

Specificity

Lists several concrete actions ('maps SERP features, layout, ranking factors, search intent, AI Overviews, and snippet opportunities') with only minor coverage gaps (e.g., no mention of competitors/local-pack detail).

4 / 5

Completeness

Explicitly answers both 'what' (maps SERP features/intent/difficulty) and 'when' ('Use when the user asks to analyze the SERP...'), but the 'when' clause could name more concrete trigger phrases such as 'why am I not ranking'.

4 / 5

Trigger Term Quality

Includes natural terms users say ('analyze the SERP', 'SERP分析', 'keyword', 'search intent') plus a clear boundary phrase ('Not for keyword demand discovery'), though some common variations like 'rank for' or 'SERP results' are only weakly present.

4 / 5

Distinctiveness Conflict Risk

Has a clear niche (SERP composition/intent/difficulty analysis) with an explicit carve-out directing keyword-demand work to keyword-research, minimizing conflict risk.

5 / 5

Total

17

/

20

Passed

Validation

75%

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

Validation12 / 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

relative_links

Relative link issues: 9 suspicious

Warning

referenced_paths_exist

Referenced path issues: 2 missing, 2 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository
aaron-he-zhu/aaron-marketing-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.