CtrlK
BlogDocsLog inGet started
Tessl Logo

semrush

SEMrush integration. Manage Projects, Keywords, Domains, Competitors. Use when the user wants to interact with SEMrush data.

64

Quality

76%

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 ./skills/semrush/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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 body is highly actionable with copy-paste CLI commands and a well-structured connection workflow including validation checkpoints. Its main weaknesses are an unnecessary introductory explanation of what Semrush is and broken step cross-references (Step 2 / 1a).

Suggestions

Remove or trim the intro paragraph explaining what Semrush is and editorial asides like "so you can focus on the integration logic rather than auth plumbing" — Claude already knows the product.

Fix the broken cross-references: label an explicit 'Step 1'/'Step 2' sequence (or rename the '1b' heading) so 'skip to Step 2' resolves to a real section.

De-duplicate the action-discovery command, which appears in both 'Searching for actions' and 'Popular actions'.

DimensionReasoningScore

Conciseness

Mostly efficient command-focused content, but the intro paragraph explains what Semrush is (a concept Claude already knows), adds editorializing like "so you can focus on the integration logic rather than auth plumbing", and repeats the action-list command across two sections.

3 / 5

Actionability

Fully executable, copy-paste ready commands cover the common cases — install, login, connection ensure, action list/run with JSON input, and proxy requests with a complete flags table.

5 / 5

Workflow Clarity

The connection sequence has explicit state checkpoints (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR) and a poll-again feedback loop, but cross-references are broken — "skip to Step 2" with no labeled Step 2 and a "1b" heading with no "1a".

4 / 5

Progressive Disclosure

No bundle files exist and the 146-line body is a single file with well-organized sections and no nested references; content is appropriately placed with only minor opportunities to split detail (e.g. clientAction state handling) into references.

4 / 5

Total

16

/

20

Passed

Description

78%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 cleanly names the tool and several concrete capabilities and includes an explicit 'Use when' trigger, but the trigger clause is generic and lacks common synonyms like SEO/rankings. Distinctiveness is strong thanks to the named-tool niche.

DimensionReasoningScore

Specificity

"Manage Projects, Keywords, Domains, Competitors" names the domain plus several concrete capability objects, though the single shared verb 'Manage' is less varied than the score-5 anchor's multiple distinct verbs.

4 / 5

Completeness

Both 'what' (SEMrush integration; manage Projects/Keywords/Domains/Competitors) and 'when' ("Use when the user wants to interact with SEMrush data") are present, but the 'when' clause is generic rather than concrete trigger phrases.

4 / 5

Trigger Term Quality

"SEMrush", "Keywords", "Domains", and "Competitors" are natural user terms, but common synonyms like "SEO", "rankings", and "keyword research" are missing.

4 / 5

Distinctiveness Conflict Risk

"SEMrush integration" targets a clear named-tool niche with distinct triggers and minimal conflict risk with other skills.

5 / 5

Total

17

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
membranedev/application-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.