CC viralhunt
Discover what's trending/going viral across TikTok, Instagram, X, Facebook, Pinterest, Bluesky, Douyin, Reddit, Mastodon, Tumblr, Hacker News and news RSS, learn the best time to post on each network from measured viral posts, find the top hashtags, trending sounds and best communities, make on-brand images from the organization's templates, leave complete posts as drafts for a person to review (or review them yourself), translate a post into a linked project's language, and schedule or publish posts to the user's own connected social accounts — powered by the ViralHunt.io API. Use this when the user has a ViralHunt account or token (or wants one) and asks to find viral or trending content in a niche through ViralHunt, to research what is performing on social right now, to know when or where to post, to run a standing content job for a brand, to check or review ViralHunt drafts, or to draft, schedule or publish social posts through their ViralHunt-connected accounts. Do not use it for social media advice that needs no data, for operating a social network's own app or API directly, or for other scheduling tools.
Discover what's trending/going viral across TikTok, Instagram, X, Facebook, Pinterest, Bluesky, Douyin, Reddit, Mastodon, Tumblr, Hacker News and news RSS…
As a process C 60/100 · Has gaps — weak spots: result and completion, inputs and preconditions, execution cost
How to improve
- Shorten the description to 1024 characters.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- error
description-longdescription is 1128 chars, limit 1024 - warning
body-longSKILL.md body ≈ 17789 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 60/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 10Execution cost. Instruction body is 17789 tokens: crowds the task out of the window
- 30Running it twice. 111 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 100Steps. 109 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 6 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 20 top-level sections: this looks like several domains in one skill
- low The skill ranks results itself: that belongs to the system behind the tool, not the model
- low The response is described with custom markup (8 tags): a typed call is more reliable
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +3Description length 1128: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +4Structure: 21 headings
- +3Step-by-step instructions: 109 items
- +4Has examples (7 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 51.