dark-social-attributor
Use when the user asks to "figure out where our direct traffic really comes from", "measure dark social", "add a how-did-you-hear-about-us field", or "show social drives signups without click data"; produces a share-link/UTM hygiene spec for owned share surfaces, a self-reported attribution field design that replaces an existing form field (free-text first, coded later), a GA4 direct-traffic decomposition read (deep-URL directs, mobile-app skew, private-push correlation) with every derived number hard-labeled Estimated/proxy, and a branded-search-lift proxy from GSC plus Wikipedia pageviews —
npx skills add aaron-he-zhu/aaron-marketing-skills --skill dark-social-attributor --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Dark Social Attributor Makes the unmeasurable share loop estimable — honestly. Dark social is the traffic that arrives with no referrer because the link traveled through a DM, a group chat (微信群 / WhatsApp / Slack / Discord), a newsletter forward, or an address-bar copy. This skill declares the estimation method and specs the instrumentation; it never turns an estimate into a Measured number. It is the Observe-phase upstream of the ECHO **O** dark-social sub-items (see [echo-benchmark.md](../../../references/echo-benchmark.md)): *dark-social method declared and Estimated-labeled before any social-ROI claim* (ECHO O2) and the *dark-social instrumentation coverage* rows (ECHO O6–O7 — share-link/UTM hygiene live plus a self-reported attribution field running). Its labels are also what keeps the ECHO O1 denominator-integrity veto passable downstream: proxies pass when labeled proxy. **Scope guard**: this skill produces the dark-social method doc and instrumentation specs only. **Paid-channel attribution reconciliation — platform-claimed vs analytics conversions, dedup, incrementality — stays with [attribution-reconciler](../../../ad/scale/attribution-reconciler/SKILL.md)**; this skill
- Quick Start
- Skill Contract
- Handoff Summary
- Data Sources
- Instructions
- Runtime Reads
- Procedure
- Save Results
- Reference Materials
- Next Best Skill
What does the dark-social-attributor skill do?
Use when the user asks to "figure out where our direct traffic really comes from", "measure dark social", "add a how-did-you-hear-about-us field", or "show social drives signups without click data"; produces a share-link/UTM hygiene spec for owned share surfaces, a self-reported attribution field design that replaces an existing form field (free-text first, coded later), a GA4 direct-traffic decomposition read (deep-URL directs, mobile-app skew, private-push correlation) with every derived number hard-labeled Estimated/proxy, and a branded-search-lift proxy from GSC plus Wikipedia pageviews —
How do I install it?
Run `npx skills add aaron-he-zhu/aaron-marketing-skills --skill dark-social-attributor --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From aaron-he-zhu/aaron-marketing-skills, a repository with 2,508 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.