CtrlK
BlogDocsLog inGet started
Tessl Logo

seo-offpage

Plan and execute off-page SEO including link building, digital PR, brand mentions, citation building, and external authority signals. Use this skill whenever the user wants to build backlinks, plan a digital PR campaign, list local citations, run guest post outreach, develop linkable assets, recover lost links, or audit a backlink profile for risk. Triggers on link building, backlinks, digital PR, brand mentions, citation building, guest post, outreach, linkable asset, broken link building, HARO, podcast outreach, off-page SEO, anchor text, link velocity, toxic backlinks, disavow. Also triggers when the user is trying to grow domain authority or earn coverage.

63

Quality

75%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/seo-offpage/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is an excellent skill description that comprehensively covers specific capabilities, provides explicit trigger guidance with a rich set of natural keywords, and clearly delineates its scope to off-page SEO. It uses proper third-person voice and follows the best practices demonstrated in the rubric's good examples. The only minor concern is that the description is somewhat long, but the detail is substantive rather than padded.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: link building, digital PR, brand mentions, citation building, guest post outreach, linkable asset development, lost link recovery, backlink profile auditing. Very comprehensive and actionable.

3 / 3

Completeness

Clearly answers both 'what' (plan and execute off-page SEO including link building, digital PR, etc.) and 'when' (explicit 'Use this skill whenever...' clause with detailed trigger scenarios, plus a dedicated 'Triggers on' list).

3 / 3

Trigger Term Quality

Excellent coverage of natural terms users would say, including common variations like 'backlinks', 'guest post', 'HARO', 'toxic backlinks', 'disavow', 'domain authority', 'anchor text', 'broken link building', and 'podcast outreach'. These are terms real users would naturally use.

3 / 3

Distinctiveness Conflict Risk

Clearly scoped to off-page SEO specifically, with distinct triggers like 'backlinks', 'HARO', 'disavow', 'link velocity', and 'citation building' that are unlikely to conflict with on-page SEO, technical SEO, or content creation skills.

3 / 3

Total

12

/

12

Passed

Implementation

50%

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

This is a well-structured strategic skill that provides a solid framework for off-page SEO planning. Its main strengths are the clear 4-strategy taxonomy and the logical workflow sequence. However, it lacks concrete, executable artifacts (specific tool commands, actual template examples, threshold values) that would make it immediately actionable, and the referenced bundle files are missing, weakening the progressive disclosure structure.

Suggestions

Add at least one concrete, copy-paste-ready outreach template inline (even a short one) rather than deferring all examples to a missing reference file.

Include specific validation checkpoints in the workflow, e.g., 'If toxic link ratio exceeds 5% of referring domains, proceed to disavow step before outreach' or 'Verify anchor text distribution before launching new campaigns.'

Provide the referenced bundle files (references/outreach-templates.md and references/linkable-assets-guide.md) or inline their key content to make the skill self-contained.

Tighten the 4-strategy descriptions by removing the Strength/Cost/Volume annotations and condensing each to 2-3 lines — Claude can infer trade-offs from the tactic descriptions.

DimensionReasoningScore

Conciseness

The content is reasonably well-organized but includes some unnecessary elaboration. The 'Strength/Cost/Volume' annotations for each strategy type add bulk that Claude could infer. The failure patterns section, while useful, is somewhat verbose. Several sections like 'Required inputs' and 'When NOT to use' could be tightened.

2 / 3

Actionability

The skill provides a clear strategic framework and workflow steps, but lacks concrete executable examples. There are no specific commands, code snippets, API calls, or copy-paste-ready outreach templates inline. Guidance like 'build the prospecting list' and 'personalized, value-first outreach' is directional rather than executable. The references to outreach templates and linkable assets guide help but aren't provided in the bundle.

2 / 3

Workflow Clarity

The 7-step workflow is clearly sequenced and logically ordered, but lacks explicit validation checkpoints or feedback loops. Steps like 'audit the current profile' don't specify what thresholds trigger action, and there's no 'if X then Y' decision logic. The quarterly disavow review is mentioned but not structured as a validation gate within the workflow.

2 / 3

Progressive Disclosure

The skill references two external files (outreach-templates.md and linkable-assets-guide.md) which is good progressive disclosure design, but these files are not provided in the bundle, making the references unverifiable. The main body itself is fairly long and some content (like the detailed strategy descriptions) could potentially be split into reference files to keep the overview leaner.

2 / 3

Total

8

/

12

Passed

Validation

90%

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

Validation10 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

10

/

11

Passed

Repository
rampstackco/claude-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.