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分析/搜索结果

77

Quality

100%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The skill body is lean, highly actionable, and well-structured: concrete commands, an explicit step sequence with verification checkpoints, and real one-level-deep references. It assumes Claude's competence and adds only domain-specific knowledge.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and packs in domain-specific specifics (connector commands, weighted difficulty inputs, file paths, labeling rules); every section earns its place despite minor tightening opportunities.

3 / 3

Actionability

Executable commands are given verbatim (firecrawl.py/tavily.py with flags), the True Difficulty weights are itemized (Top-10 authority 25%, page authority 20%, ...), and write paths plus labeling rules make guidance copy-paste ready.

3 / 3

Workflow Clarity

The 8-step process is clearly sequenced with explicit validation checkpoints — the Measured/User-provided/Estimated/N/A labeling rule, the evidence-citation quality bar, and the engine-disagreement → report-volatile feedback loop catch errors early.

3 / 3

Progressive Disclosure

The body is an overview that points one level deep to real, clearly-signaled reference files (analysis-templates.md, example-report.md, serp-feature-taxonomy.md — all present), collected in a dedicated Reference Materials section.

3 / 3

Total

12

/

12

Passed

Description

100%Weight 40%Scale 1-3

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, trigger-rich, and complete, with explicit when/what guidance plus a negative trigger steering away from a sibling skill. Voice is correctly third person ("maps ..."), so no specificity penalty applies.

DimensionReasoningScore

Specificity

"maps SERP features, layout, ranking factors, search intent, AI Overviews, and snippet opportunities" lists multiple specific concrete actions rather than vague language, matching the score-3 anchor.

3 / 3

Completeness

It explicitly answers both what (mapping features/ranking/intent/snippets) and when ("Use when the user asks to 'analyze the SERP' or 'SERP分析'") with explicit triggers, so it is not capped at 2.

3 / 3

Trigger Term Quality

Natural user-facing terms appear throughout ("analyze the SERP", "SERP分析", "AI Overviews", "snippet opportunities", "搜索结果"), giving good coverage of phrasings a user would actually say.

3 / 3

Distinctiveness Conflict Risk

A clear SERP niche with an explicit anti-trigger ("Not for keyword demand discovery — use keyword-research") makes overlap with other skills unlikely.

3 / 3

Total

12

/

12

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.