CtrlK
BlogDocsLog inGet started
Tessl Logo

seo-content-writer

Write SEO blog posts, articles, landing pages with keyword integration, header optimization, and snippet targeting. SEO文章写作/内容优化

56

Quality

66%

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 ./.cursor/skills/seo-content-writer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 a well-structured, actionable SEO writing workflow with clear sequencing and good use of local reference files, though it is padded with skill-ecosystem boilerplate and inlines detail that belongs in references. Trimming the meta-boilerplate and moving the CORE-EEAT table to its reference would improve conciseness and progressive disclosure.

Suggestions

Remove the Skill Contract/State Model/Save Results ecosystem boilerplate and the redundant second 'When This Must Trigger' sentence to tighten conciseness.

Move the inlined 16-item CORE-EEAT table and the validation checklists into their referenced benchmark/reference files, keeping only a pointer in SKILL.md.

DimensionReasoningScore

Conciseness

The body is mostly efficient with dense actionable templates, but carries noticeable padding — redundant 'When This Must Trigger' sentences, Skill Contract/State Model ecosystem boilerplate, and a 'Save Results' memory/hot-cache section that don't aid SEO writing.

3 / 5

Actionability

Provides concrete fill-in templates and specific numeric thresholds (150-160 char meta, 50-60 char titles, 2-5 internal links, 40-60 word FAQ answers), but the in-body templates are placeholder-fill rather than fully worked examples.

4 / 5

Workflow Clarity

The 9-step Instructions sequence is clearly ordered with a final self-check, issue classification (auto-correct vs. needs-decision), and Input/Output validation checklists; validation is self-scored rather than a rigorous pass/fail re-validation gate.

4 / 5

Progressive Disclosure

Local references (seo-writing-checklist, title-formulas, content-structure-templates) are real, clearly signaled, and one level deep, but substantial detail (the CORE-EEAT 16-item table, content-type templates, validation checklists) is inlined in the body and several referenced repo files are external/non-local.

4 / 5

Total

15

/

20

Passed

Description

66%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 is specific and well-targeted to the SEO content niche with good natural keyword coverage, but it omits an explicit 'Use when...' trigger clause, which caps completeness. Adding a trigger clause and a few more natural user phrases would raise it.

Suggestions

Add an explicit 'Use when...' trigger clause to the description (e.g., 'Use when writing SEO-optimized articles, blog posts, or landing pages targeting a specific keyword') to satisfy the completeness 'when' requirement.

Include more natural user phrasings such as 'SEO content', 'content writing', and 'SEO copywriting' alongside the technical technique labels.

DimensionReasoningScore

Specificity

Lists 'keyword integration, header optimization, and snippet targeting' alongside three content types (blog posts, articles, landing pages) — several specific actions, but omits capabilities the body covers (meta descriptions, internal linking, readability), leaving minor coverage gaps.

4 / 5

Completeness

Provides a clear 'what' (write SEO content with specific techniques) but no 'Use when...' trigger clause in the description field, so the 'when' is absent — capped at 3 per the missing-trigger guidance.

3 / 5

Trigger Term Quality

Includes natural terms like 'SEO blog posts', 'articles', 'landing pages' plus multilingual SEO phrases, but misses common user phrasings such as 'SEO content', 'content writing', or 'SEO copywriting'.

4 / 5

Distinctiveness Conflict Risk

The SEO-specific framing (keyword integration, header optimization, snippet targeting) carves a clear niche with minimal conflict risk, though it could overlap slightly with a generic blog-writing skill.

4 / 5

Total

15

/

20

Passed

Validation

81%

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

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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository
MODSetter/SurfSense
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.