CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

share-of-voice-tracker

Use when the user asks to "track our share of voice", "what share of the conversation do we own vs competitors", or "trend our SOV this quarter"; computes SOV% = brand mentions ÷ (brand + competitor panel mentions) per platform per period on a LOCKED competitor panel — a panel switch invalidates the trend (restart the series and log the break; the ECHO O3 rule) — plus a sentiment-weighted SOV variant (sentiment labeled Estimated unless human-coded) and a Wikipedia-pageviews attention-share alternative; built from keyless listening connectors, gdelt.py news echo, and user exports — public counts only, closed platforms are never scraped. Not for backlink or offsite SEO signals — use offsite-signal-analyzer. 声量份额/竞品声量对比/提及份额/注意力份额

Quality

94%

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

92%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 strong contract-style skill body: precise formula, named tooling, a genuine validation checkpoint (the panel-break rule), and clean one-level-deep reference structure. The only real cost is repetition — governance and routing sentences are restated three to five times, which inflates token spend without adding information.

Suggestions

State the channel-facts governance rule (registry-events.py propose → memory/events/channels.ndjson, channel-registry as sole writer of memory/channels/) once — e.g., in Save Results — and drop the repeats in the Scope guard and Promotes bullets.

Consolidate sibling-skill routing: the competitor-tracker and social-pulse-monitor links each appear 4–5 times; the Reference Materials and Next Best Skill sections alone are sufficient once the Promotes bullet points there.

DimensionReasoningScore

Conciseness

The body is dense and assumes competence — no concept over-explanation — but the channel-registry governance sentence ("Registry-grade channel facts go only to `memory/events/channels.ndjson` via an authorized `operation: propose` request to `registry-events.py`") is repeated three times and the competitor-tracker/social-pulse-monitor routing links each appear 4–5 times across sections. This is efficient overall with trimmable repetition, matching anchor 4; it is not 5 because every token does not earn its place, and not 3 because nothing explains concepts Claude already knows.

4 / 5

Actionability

Guidance is fully executable for an instruction-only skill: the exact formula "SOV% = brand ÷ (brand + panel total)", named connector scripts (hn.py, bluesky.py, gdelt.py with "≥5s between calls", pageviews.py), concrete memory paths, a four-value per-cell label taxonomy (Measured/proxy/Estimated/User-provided), a NEEDS_INPUT fallback, and ready-to-use Quick Start prompts. This matches the top anchor for copy-paste-ready specificity covering the common cases.

5 / 5

Workflow Clarity

The eight numbered steps are correctly sequenced (lock panel → break check → pull counts → compute → variants → trend → report) with an explicit validation step: the panel-break check prescribes exactly what to do on failure (log a dated break marker, re-lock, restart, never splice). The "Done when" section acts as a completion checklist and termination rules are stated. This matches the anchor for clear sequence with explicit validation and checklists.

5 / 5

Progressive Disclosure

The 89-line body is well-sectioned (Quick Start, Skill Contract, Data Sources, Instructions, Save Results, Reference Materials, Next Best Skill) and all references are one level deep, each annotated with what it contains (echo-benchmark.md for the O3/O1 rules, CONNECTORS.md for recipes and rate limits, skill-contract.md for the handoff format). No bundle directories ship with this skill — the referenced paths are external cross-links in the parent repo — and they are clearly signaled and easy to navigate, matching the top anchor.

5 / 5

Total

19

/

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.

A model trigger description: verbatim user phrasings, an exact formula, named variants, explicit boundary routing to a sibling skill, and multilingual synonyms, all in third person. Its only weakness is density — at ~120 words it carries contract-level detail that some hosts may truncate — but no rubric dimension is harmed by it.

DimensionReasoningScore

Specificity

The description lists multiple concrete, formula-level actions — "computes SOV% = brand mentions ÷ (brand + competitor panel mentions) per platform per period", "a sentiment-weighted SOV variant", and "a Wikipedia-pageviews attention-share alternative" — with comprehensive coverage of the skill's scope. It matches the anchor for multiple specific concrete actions with no coverage gaps, rather than the score-4 anchor's "minor gaps".

5 / 5

Completeness

Both what and when are answered explicitly: the what is the SOV computation with its variants and the panel-break rule, and the when opens with "Use when the user asks to ..." followed by three concrete trigger phrases. This matches the anchor for clearly and explicitly answering both with concrete trigger phrases, not the score-4 anchor where the when "could be more explicit".

5 / 5

Trigger Term Quality

It quotes natural user phrasings verbatim ("track our share of voice", "what share of the conversation do we own vs competitors", "trend our SOV this quarter") and adds synonyms including the abbreviation SOV and Chinese terms (声量份额/提及份额/注意力份额). This is comprehensive natural-term coverage including synonyms, matching the top anchor.

5 / 5

Distinctiveness Conflict Risk

The skill carves a clear niche (the SOV number on a locked competitor panel) and includes an explicit negative trigger — "Not for backlink or offsite SEO signals — use offsite-signal-analyzer" — minimizing wrong-skill activation. Distinct triggers and minimal conflict risk match the top anchor; the score-4 anchor's "minor overlap risk" does not fit given the explicit disambiguation.

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: 32 suspicious

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

12

/

16

Passed

Repository

aaron-he-zhu/aaron-marketing-skills

Path

social/observe/share-of-voice-tracker/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.