CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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 — the declared dark-social method behind ECHO O2. Not for paid-channel attribution reconciliation (platform-claimed vs analytics conversions) — use attribution-reconciler. 暗社交归因/直接流量分解/自报来源字段/分享链路UTM

Quality

88%

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

77%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-engineered instruction-only skill body: a clearly sequenced 8-step procedure with explicit done-when criteria and label enforcement, concrete specs for the UTM taxonomy and self-reported field, and well-signaled one-level references for all detail material. Its weaknesses are noticeable token redundancy — the registry write-path and automation red-line rules are each stated three to four times — and underspecified computation in the decomposition and branded-lift steps.

Suggestions

State the channel-registry write-path rule once (e.g., in the Skill Contract's Writes bullet) and reference it from Procedure step 7 and Save Results instead of repeating the full 'sole writer of memory/channels/' + 'authorized operation: propose' formula three times; do the same for the closed-platform automation red line (currently in the Scope guard, Data Sources, and step 1).

Merge the 'Next Best Skill' section with the Skill Contract's 'Primary next skill' line — they duplicate the same social-measurement-loop handoff — and fold the 'Runtime Reads' list into Reference Materials so owned-community-loop.md is not listed twice.

Add the missing executable details for the two analytical reads: a concrete definition of a deep-URL direct (e.g., sessions landing on URLs longer than N segments or with UTM-less query params) and the lift-comparison method (e.g., a named time-box and baseline window for the GSC branded-query series vs the activity calendar).

DimensionReasoningScore

Conciseness

The body is dense and operational — no space is spent explaining concepts Claude already knows — but there is noticeable redundancy: the registry write-path rule ("sole writer of memory/channels/" / "authorized operation: propose request to registry-events.py") is stated in the Writes bullet, Procedure step 7, and Save Results; the no-automation red line appears three times (Scope guard, Data Sources, step 1); and "Next Best Skill" duplicates the Skill Contract's "Primary next skill". This is more than the "minor instances" of anchor 4 but short of anchor 2's padded sections, since every repetition carries a slightly different operational nuance.

3 / 5

Actionability

Mostly concrete, executable guidance: a worked UTM taxonomy ("utm_source=<surface>&utm_medium=social-share"), exact field wording ("How did you hear about us?" / 「你是怎么知道我们的?」) with a run-then-code timeline ("run 2-4 weeks, then code recurring answers into a short option list"), named heuristics ("deep-URL directs", "mobile-app skew", "private-push correlation … vs the pre-window baseline"), and a runnable command ("python3 scripts/connectors/pageviews.py"). It stops short of anchor 5 because the two flagship analytical steps leave key details to judgment — what counts as a deep-URL page and how the branded-lift comparison against the activity calendar is computed are unspecified.

4 / 5

Workflow Clarity

An 8-step ordered procedure (inventory → hygiene spec → field design → decomposition → lift proxy → declare method → route → report) with an explicit completion checklist ("Done when: the method doc names every heuristic with an Estimated/proxy label and a named source … no derived number presented as Measured") and per-step label enforcement ("Label every split Estimated with its heuristic named"). Memory writes are gated ("Do not write memory without asking"), and no destructive or batch operations exist that would trigger the workflow cap; the only missing element, error-recovery feedback loops, has no failure-prone operation to attach to.

5 / 5

Progressive Disclosure

The core procedure lives inline where it belongs, and all detail material is pushed to clearly signaled, one-level-deep references annotated with purpose in the Reference Materials section (e.g., "owned-community-loop.md — the owned share-loop spec the instrumentation consumes", "CONNECTORS.md — pageviews.py and the GA4/GSC own-data recipes"). No nested reference chains exist. Minor blemish only: the "Runtime Reads" list repeats owned-community-loop.md already linked twice in the body. (Referenced files sit outside this review copy — ../../../references/… — so their existence could not be verified; scoring reflects the SKILL.md's own structure.)

5 / 5

Total

17

/

20

Passed

Description

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

An exemplary description: concrete deliverables with named sub-techniques, quoted user-voice trigger phrases in both English and Chinese, explicit what/when coverage, and an explicit boundary against the sibling paid-channel skill. It is long but dense rather than padded — every clause carries trigger or capability information.

DimensionReasoningScore

Specificity

Lists multiple concrete deliverables — "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)", and "a branded-search-lift proxy from GSC plus Wikipedia pageviews" — with named sub-techniques for each. Coverage is comprehensive across the skill's outputs; anchor 4 would require a minor gap, and none is present.

5 / 5

Completeness

Explicitly answers "when" with concrete trigger phrases ("Use when the user asks to …") and "what" ("produces a share-link/UTM hygiene spec … a branded-search-lift proxy"), and adds an explicit negative boundary ("Not for paid-channel attribution reconciliation … use attribution-reconciler"). Both halves are explicit at the phrase level, matching the top anchor; a 4 would require the "when" to be less specific.

5 / 5

Trigger Term Quality

Four quoted natural user utterances ("figure out where our direct traffic really comes from", "measure dark social", "add a how-did-you-hear-about-us field", "show social drives signups without click data") plus domain synonyms and a bilingual set ("direct traffic", "dark social", "how-did-you-hear-about-us", 暗社交归因/直接流量分解/自报来源字段/分享链路UTM). This matches the comprehensive-synonyms anchor; anchor 4 ("a few natural terms missing") is too low given phrase-level and bilingual coverage.

5 / 5

Distinctiveness Conflict Risk

Clear niche (organic dark-social share loop) with distinct triggers, and it explicitly disambiguates the nearest neighbor ("Not for paid-channel attribution reconciliation (platform-claimed vs analytics conversions) — use attribution-reconciler"), minimizing wrong-skill triggering. Anchor 4's "minor overlap risk" does not apply given the named redirect.

5 / 5

Total

20

/

20

Passed

Validation

75%

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

Validation — 12 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 30 suspicious

Warning

referenced_paths_exist

Referenced path issues: 3 missing, 3 deeper-than-1-level

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

social/observe/dark-social-attributor/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.