backlink

<skill name="backlink" version="3.3" body-format="xml"> <why-xml> The frontmatter above stays YAML because the Skill loader reads it for discovery. Everything below is XML because this Skill is mostly laws and routing, and a law that is easy to skim past is a law that gets broken. Tagged blocks make "which rule did I just violate" answerable by name. </why-xml> <mission> One business Skill for the complete backlink lifecycle. Do not split it back apart, and do not create another browser-extension Skill — OpenCLI and its Chrome extension are the connector underneath this Skill, never a separate business workflow. Two former Skills were merged in on 2026-08-16 and deleted: `backlink-analyzer` (analysis templates, toxicity rubric, outreach — now in three references under its original Apache-2.0 licence) and `browser-harvest` (pulling tables out of logged-in dashboards — now <ref file="references/harvest.md"/>). The harvest knowledge is general-purpose: ad platforms, e-commerce backends, any no-API SaaS report. When a harvesting task has nothing to do with links, load this Skill anyway and read that one reference. </mission> <map> <summary> Two things live here and they answer different questions. **The data files are the asset; the references are how to use them and how not to fool yourself.** </summary> <tree><![CDATA[ backlink/ ├── SKILL.md ← you are here: laws + routing + workflow entry points ├── CONTRIBUTING.md ← how to submit a PR, the data model, th...