CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

social-evidence-research

Research public discussion on social platforms and keep every report claim tied to the source material that supports it. Use when researching or comparing how a product, event, or topic is discussed across social platforms or supplied social exports, when turning search results into a cited report, or when auditing a social research report for discovery-only evidence, double-counted reposts, misattributed comments, claims that go beyond the sample, or hidden access gaps.

Quality

93%

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

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

An exemplary instruction-only skill body: lean, method-specific, and fully actionable through enumerated fields, unit examples, and verified one-level-deep templates. The single minor gap is that the audit checklist is framed for auditing others' reports rather than being explicitly wired in as a pre-delivery self-check on the workflow's own output.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: no general definitions (what a repost or export is), no padding, and every line is method-specific instruction ("Write `unknown` for any missing value", "The repeated content of a duplicate group counts once as support"). The one-paragraph intro sets the method frame in three lines; nothing reads as over-explanation of known concepts, so it fits the anchor-5 case rather than the minor-trimming case of 4.

5 / 5

Actionability

For an instruction-only skill the guidance is fully concrete: step 1 enumerates the exact protocol fields to write down, step 3 names the inspected-part units ("the post text, the caption, one comment, the profile, image 2, or video 00:00 to 00:45") and points to the record fields in `references/evidence-record.md`, and step 6 points to the claim-table template in `references/report-template.md`. Per the scoring notes, absence of code is not penalized when guidance is this actionable, and the referenced templates plus acceptance examples cover the common cases.

5 / 5

Workflow Clarity

The eight steps are clearly sequenced, step 1 establishes a protocol checkpoint with an explicit change-recording rule, and the audit section supplies a failure-mode checklist (discovery-only, double-counted, misattributed, beyond-sample, empty-search-as-absence). It falls short of 5 only because there is no explicit instruction to run the audit checklist against the researcher's own claim table before delivering — the validation procedure exists but self-application is implied rather than stated as a checkpoint. It is well above 3 since sequence and checkpoints are present, and this is not a destructive/batch operation so no cap applies.

4 / 5

Progressive Disclosure

The ~55-line body is a method overview, with the bulk detail correctly split into three one-level-deep reference files, each verified to exist with substantive content matching its description. Navigation is well signaled: each reference is cited inline at its workflow step and again in a References section that states what each file contains. References cross-mention each other but nest no deeper than one level, matching the anchor-5 structure.

5 / 5

Total

19

/

20

Passed

Description

88%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 strong description with explicit what-and-when structure, concrete actions, and a third-person voice. The only gaps are a few missing natural synonyms (e.g., "social media") and one broad trigger clause (cited reports from search results) that overlaps slightly with general web-research skills.

Suggestions

Add one or two natural user phrasings such as "social media" or "online discussion" alongside "social platforms" to broaden trigger coverage.

Qualify the cited-report trigger with the social context, e.g. "when turning social platform search results into a cited report", to reduce overlap with general web-research skills.

DimensionReasoningScore

Specificity

Multiple concrete actions are named: "Research public discussion on social platforms", "keep every report claim tied to the source material", and auditing for specific failure modes ("discovery-only evidence, double-counted reposts, misattributed comments, claims that go beyond the sample, or hidden access gaps"). Coverage is comprehensive and uses third person ("Research", "keep"), so no voice penalty applies. Not a 4 because the action list is broad and specific rather than having minor coverage gaps.

5 / 5

Completeness

Explicitly answers what ("Research public discussion on social platforms and keep every report claim tied to the source material that supports it") and when, via a full "Use when..." clause with three concrete trigger scenarios (researching/comparing discussion, turning search results into a cited report, auditing an existing report). Matches the anchor-5 example structure exactly; a missing or weak trigger clause would cap it at 3, which is not the case.

5 / 5

Trigger Term Quality

Good natural-term coverage: "social platforms", "supplied social exports", "search results", "cited report", "reposts", "misattributed comments". Falls short of 5 because common user phrasings like "social media", "online discussion", or platform names are absent, leaving a few natural synonyms uncovered. Clears 3 because the terms present are ones a user would plausibly say rather than pure jargon.

4 / 5

Distinctiveness Conflict Risk

The niche is mostly distinct — terms like "supplied social exports", "double-counted reposts", and "misattributed comments" won't fire for unrelated skills. However, the trigger "when turning search results into a cited report" is generic and could overlap with general web-research or citation-report skills, so it is not the clear-niche, minimal-conflict case of a 5. It is well above 3 because the specific failure modes named are unique to this skill.

4 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

wshobson/agents

Path

plugins/content-marketing/skills/social-evidence-research/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.