Name: yoast-seo
Rating: 54.400000000000006 (1 reviews)
Author: membranedev

yoast-seo

Yoast SEO integration. Manage data, records, and automate workflows. Use when the user wants to interact with Yoast SEO data.

Quality

61%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/yoast-seo/SKILL.md

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 content is highly actionable, with concrete executable commands and a useful connection-state feedback loop, and it is reasonably well-structured. Its main weakness is conciseness: an unnecessary introductory explanation of what Yoast SEO is and redundant action-discovery sections.

Suggestions

Remove or drastically shorten the opening paragraph explaining what Yoast SEO is; Claude already knows this, and it competes with context tokens.

Merge 'Searching for actions' and 'Popular actions' into a single section, since both demonstrate `membrane action list --intent=...` and the duplication adds length without new guidance.

Fix the step numbering in the connection flow (label Step 1 and reconcile the stray '1b') so the sequence reads as a coherent numbered workflow.

Dimension	Reasoning	Score
Conciseness	The body is mostly operational with concrete commands, but it opens by explaining what Yoast SEO is ('a popular WordPress plugin that helps users optimize their website content...') and repeats the action-list command across 'Searching for actions' and 'Popular actions', adding padding Claude doesn't need.	3 / 5
Actionability	Commands are copy-paste ready with real flags and placeholders (CONNECTION_ID, QUERY), and the proxy section includes a complete flag table covering methods, headers, body, query, and path params.	5 / 5
Workflow Clarity	There is a clear install -> authenticate -> connect -> poll-for-ready -> search -> run sequence with an explicit connection-state feedback loop (READY/BUILDING/CLIENT_ACTION_REQUIRED/CONFIGURATION_ERROR), but step numbering is inconsistent ('Step 2' is referenced while Step 1 isn't labeled, and '1b' appears abruptly).	4 / 5
Progressive Disclosure	The single self-contained file is organized into clear, well-signaled sections (Overview, Working with Yoast SEO, Install, Auth, Connecting, Searching, Popular actions, Best practices) with no nested references, though the 'Searching for actions' and 'Popular actions' sections overlap and could be consolidated.	4 / 5
	Total	16 / 20 Passed

Description

48%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 includes an explicit Use-when trigger and a clearly named domain, but the capabilities section relies on generic verbs ('manage data, records, automate workflows') that don't convey what Yoast SEO actually does. Specificity and trigger-term coverage are the weakest points.

Suggestions

Replace the generic 'Manage data, records, and automate workflows' with concrete Yoast SEO actions, e.g. 'Retrieve and update SEO configuration for posts, pages, and taxonomies, run keyword and readability analysis, and send direct API requests through Membrane'.

Add natural trigger terms users would say, such as 'Use when the user wants to check or change Yoast SEO settings, meta descriptions, focus keywords, or SEO scores for posts and pages'.

Avoid the boilerplate 'automate workflows' phrasing, which is vague and adds conflict risk with other integration skills.

Dimension	Reasoning	Score
Specificity	The phrase 'Manage data, records, and automate workflows' names the Yoast SEO domain but the actions are generic and could apply to almost any app, with no concrete SEO-specific operations.	2 / 5
Completeness	Both a 'what' ('Manage data, records, and automate workflows') and a 'when' ('Use when the user wants to interact with Yoast SEO data') are present, but the 'what' is too vague to clearly answer what the skill does.	3 / 5
Trigger Term Quality	'Yoast SEO' and 'interact with Yoast SEO data' provide a relevant natural keyword and a Use-when trigger, but common variations like 'SEO configuration', 'meta descriptions', or 'keyword analysis' are missing.	3 / 5
Distinctiveness Conflict Risk	The Yoast SEO domain name gives it a clear niche with a distinct trigger, though the generic 'manage data, records, and workflows' phrasing leaves minor overlap risk with other integration skills.	4 / 5
	Total	12 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: membranedev/application-skills
Path: skills/yoast-seo/SKILL.md
Commit: f484c82

Reviewed: 3 days 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.