Install any skill in seconds. Free to start, no credit card required.
Get Started Free →kennyzir/seo-link-strategy
Research backlink opportunities, record contact evidence, and generate personalized local outreach drafts from user-provided product and contact data.
Passed 20 of 22 test cases with the skill, and 4 of 22 without it.
and 20 more in the full report
16 fixed4 passed either way2 still failing0 broke1 errored
Tokens, turns and time describe resource use, not a dollar price.
One of 16 test cases the skill fixed. Same model, same prompt, with and without the skill.
When scripts/email_generator.py runs on candidate contact data and outputs generated email text objects, what value is populated in the delivery_status field of each generated draft?
| Checked | Without skill | With skill |
|---|---|---|
| sets delivery_status value to not-sent | Missed | Passed |
The instructions your model reads when the skill loads.
Build an evidence-backed backlink opportunity list and prepare local outreach drafts. Discovery, evidence capture, draft generation, and external execution are separate states.
This Skill does not ship a current directory of platforms or verified contacts. Candidates come from the user or from research performed at runtime. Never treat a guessed address, old list, search snippet, or role-based email pattern as an observed contact.
Default work is research and local draft preparation. Do not send Gmail or other messages, submit forms, purchase placements, call paid/mutating services, or change remote systems by default.
Before any external side effect:
A draft is not-sent. An opportunity is not a backlink. An attempted submission is not completed unless a real result supports that state.
Each opportunity or contact record must support these fields:
| Field | Requirement |
|---|---|
name | User-provided or runtime-discovered platform/contact label. |
source_url | Exact page where the opportunity or contact evidence was observed. |
observed_at | Past UTC timestamp for the actual observation, or null. Future times are rejected. |
status | observed only with captured evidence and time; otherwise unknown. |
email | One value present in captured evidence, or null; never constructed from hints. |
context | User-supplied limits, conflicts, access failures, or relevance notes. |
Keep sources and observation times when data is handed from research to drafting. If a page cannot be checked, preserve the candidate with status: unknown rather than filling likely values.
Use scripts/contact_discoverer.py after the user or an available research tool supplies candidate URLs and captured page text. The script is offline: it extracts addresses only from the supplied capture and makes no network request.
Input JSON:
test cases passed, vs 4 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.