CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

link-building

When the user wants backlinks and mentions that lift rankings and AI citations, or asks how to get sites to link or whether a link tactic is safe: link gaps, unlinked mentions, broken links, guest posts, best-of outreach. Never buy links that pass ranking credit: paid or exchanged placements get rel=sponsored or nofollow. For press, see public-relations. For directories, see directory-submissions. For reviews, see referrals. For communities, see community-marketing.

Quality

85%

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

78%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.

A well-structured, information-dense instruction skill: sequenced workflow with validation gates, decision tables instead of prose, and exemplary use of one-level-deep reference files. The main improvement opportunities are adding failure/recovery guidance to the measurement loop, showing one concrete outreach example inline, and moving or de-emphasizing the dated policy reference.

Suggestions

Add an error-recovery branch to the measurement loop (e.g., 'if referring domains grow but rankings don't move after 90 days, re-run the Step 1 gap check') to close the workflow_clarity gap.

Include one short annotated outreach email example in the body so the most common execution step is copy-paste-ready without opening references/prospecting-and-outreach.md.

Move the 'Google's spam policies (updated 2026-08-28)' date into references/risk-policy.md or a maintained section, so the SKILL.md body doesn't carry time-sensitive information that will go stale.

DimensionReasoningScore

Conciseness

The body is dense and judgment-driven ("Domain-level comparisons (DR vs DR) hide the real gap, because a strong domain with an unlinked page still loses") with no basic-concept padding, but minor content could be trimmed — notably the time-sensitive date "Google's spam policies (updated 2026-08-28)", which sits outside any old-patterns/deprecated section and will go stale.

4 / 5

Actionability

Concrete guidance throughout: a four-part qualification checklist (Relevant / Real / Reachable / Worth it), decision tables for gap reading and tactic choice, named tools, and a seven-part output format. It falls short of fully copy-paste-ready because executable specifics (search operators, outreach templates, vendor-vetting steps) are deferred to reference files rather than exemplified in the body.

4 / 5

Workflow Clarity

A clearly sequenced seven-step process with explicit checkpoints at the risky points — the Step 1 bottleneck gate that redirects to seo-audit, and "Don't send outreach on the user's behalf without explicit approval of the list and the copy" for the batch operation. It misses anchor 5 because the measurement table specifies cadence but no error-recovery branches when metrics don't move.

4 / 5

Progressive Disclosure

The body is a well-organized overview and every bundle file is real, one level deep, and clearly signaled at its point of use: "Playbooks for each tactic ... are in [references/tactics.md]", "Templates and a tracker layout are in [references/prospecting-and-outreach.md]", "How to vet a link vendor ... in [references/risk-policy.md]" — matching the clear-overview-with-well-signaled-references anchor.

5 / 5

Total

17

/

20

Passed

Description

87%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.

A strong description with explicit when-trigger phrasing, concrete tactic keywords, and unusually good conflict avoidance through explicit routing to sibling skills. The tactic list is specific but noun-based and omits a few natural search terms like "link building" itself.

DimensionReasoningScore

Specificity

Lists several concrete capabilities ("link gaps, unlinked mentions, broken links, guest posts, best-of outreach") plus a specific safety rule ("paid or exchanged placements get rel=sponsored or nofollow"), but the tactic list is noun-based with minor coverage gaps since adjacent activities are delegated rather than stated, fitting the 'several specific actions' anchor rather than fully comprehensive.

4 / 5

Completeness

Explicitly answers both: the what (earning links and mentions via the listed tactics, with the never-buy-passing-links rule) and the when ("When the user wants backlinks and mentions that lift rankings and AI citations, or asks how to get sites to link or whether a link tactic is safe"), with concrete trigger phrases throughout.

5 / 5

Trigger Term Quality

Natural phrases users would say include "backlinks", "how to get sites to link", "whether a link tactic is safe", and "guest posts", but a few common variations are missing (e.g., "link building" itself, "domain authority", "off-page SEO"), matching the 'good keyword coverage, a few natural terms missing' anchor.

4 / 5

Distinctiveness Conflict Risk

Clear niche (earning links and third-party mentions) with explicit routing to neighboring skills ("For press, see public-relations. For directories, see directory-submissions. For reviews, see referrals. For communities, see community-marketing."), which minimizes overlap and wrong-skill triggering.

5 / 5

Total

18

/

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.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 6 suspicious

Warning

Total

15

/

16

Passed

Repository

coreyhaines31/marketingskills

Path

skills/link-building/SKILL.md

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.