CtrlK
BlogDocsLog inGet started
Tessl Logo

social-media-scraping-scrapecreators

Compatibility alias for the original ScrapeCreators social scraping skill. Use scrapecreators-api for current endpoint guidance and the task-specific Brand Growth research skills for finished analysis.

60

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/social/capabilities/social-media-scraping-scrapecreators/SKILL.md
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.

The body is an exemplary minimal redirect stub: it explains why the legacy slug exists, gives concrete successor slugs for both API mechanics and deliverable workflows, and closes with a sharp behavioral rule against stopping at raw API responses. It is token-efficient and unambiguous, with only the intent-to-workflow mapping left implicit. For its purpose as a compatibility alias, the content is strong.

DimensionReasoningScore

Conciseness

The ~25-line body is lean with zero padding: "This legacy slug remains available so existing installations do not break" and "Do not stop at a raw API response when the user asked for research or a recommendation" each earn their tokens, and nothing explains concepts Claude already knows. It matches anchor 5 ("lean and efficient; assumes Claude's competence; every token earns its place") — there is nothing to trim without losing function.

5 / 5

Actionability

The routing is concrete and executable for an instruction-only skill: named slugs "scrapecreators-api", "comment-mining", "competitor-social-research", etc. give exact next actions, and the closing rule is specific behavioral guidance. It is a 4 rather than 5 because the mapping from user intent to which of the eight task-specific workflows is left implicit — a minor gap in coverage of the common case.

4 / 5

Workflow Clarity

This is a simple single-purpose skill (a redirect) and the single action is unambiguous: step 1 "Use scrapecreators-api" for mechanics, step 2 "Use a task-specific workflow for the final deliverable", each with a concrete enumerated target. Per the simple-skill guidance the unambiguous single action scores 5; there are no destructive or batch operations requiring validation checkpoints.

5 / 5

Progressive Disclosure

The skill is under 50 lines with no need for external reference files (none exist in references/, scripts/, or assets/, and the body points only to other skills, not nested files), and the title plus numbered list with bulleted targets is well organized. This matches the rubric guidance that under-50-line skills with well-organized sections and no external-reference needs score 5.

5 / 5

Total

19

/

20

Passed

Description

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

The description is honest and appropriately brief for a deprecated compatibility alias, clearly stating what it is and where to go instead. However, it lacks any "when to use" trigger guidance and has thin natural-keyword coverage, so it would rarely be selected deliberately and risks overlapping with its own successors. As a redirect stub it serves its purpose, but judged as a skill description it is mediocre.

Suggestions

Add an explicit trigger clause, e.g. "Use only when an existing installation references this legacy skill slug; otherwise use scrapecreators-api directly."

Include natural keywords users would actually say (e.g. "social media scraping", "scrape posts, comments, or profiles") so the alias resolves correctly when triggered by user phrasing.

State the alias's concrete behavior upfront ("Redirects to scrapecreators-api for endpoint guidance and to Brand Growth research skills for analysis") so the 'what' is a capability statement rather than only a label.

DimensionReasoningScore

Specificity

"Compatibility alias for the original ScrapeCreators social scraping skill" names the domain, and "Use scrapecreators-api for current endpoint guidance" plus "task-specific Brand Growth research skills for finished analysis" are 1-2 concrete directives, but coverage of what the skill itself does is minimal. It sits above anchor 2 ("names the domain but actions are minimal") because the redirect targets are concrete, and below anchor 4 because no capability list of its own is given.

3 / 5

Completeness

The "what" is clear ("Compatibility alias for the original ScrapeCreators social scraping skill" that keeps existing installations from breaking), but there is no "Use when..." clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not a 4 because the "when" is entirely missing rather than merely imprecise, and not a 2 because the "what" is explicit and concrete.

3 / 5

Trigger Term Quality

"social scraping", "social", and the brand term "ScrapeCreators" are relevant keywords, but common natural phrases users would say (e.g. platform names like Instagram/TikTok, "scrape comments", "social media data") are absent. It matches anchor 3 ("some relevant keywords but missing common variations or synonyms") rather than 4, since keyword coverage is thin for a domain with many natural phrasings.

3 / 5

Distinctiveness Conflict Risk

By design this is an alias for the same domain as "scrapecreators-api" and overlaps with eight task-specific research skills, so it can trigger for the wrong skill despite explicitly deferring to them by name. It is above anchor 2 because the named brand and explicit successor references make the intent distinguishable, but below anchor 4 because the overlap with its own replacement skill is inherent, not minor.

3 / 5

Total

12

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

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

Warning

Total

15

/

16

Passed

Repository
gooseworks-ai/goose-skills
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.