AC trend-jacking
Use to ride a trend — a trending sound, format, meme, hashtag, news moment, or cultural conversation — to earn reach by attaching the brand to something already getting attention (a.k.a. trendjacking / newsjacking). Run when the user says "trend," "trending," "jump on this trend," "trendjack," "newsjack," "is this trend worth doing," "make this go viral," or wants to react to a current moment. Reads brand-profile, voice, and audience first, then runs three gates — FIT, SAFETY, and TIMING — before executing a fast, on-brand remix and handing to the right content skill (tiktok-script, reels-script, caption-writer) and scheduling-and-queue. Refuses to trendjack tragedies or divisive moments and won't force irrelevant trends; live trend discovery needs current scanning — this skill vets and executes. For meme-format craft, cultural fluency, and meme IP/likeness judgment ("make a meme," "is this meme safe"), route to meme-and-culture.
Use to ride a trend — a trending sound, format, meme, hashtag, news moment, or cultural conversation — to earn reach by attaching the brand to something…
As a process C 62/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- 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: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 62/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 2 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 26 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1313 tokens
- low 10 top-level sections: this looks like several domains in one skill
- low No test case covers injection arriving through data
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
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 943: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +5Description quotes 9 example trigger phrases
- +4Structure: 11 headings
- +3Step-by-step instructions: 26 items
- +4Reference files are cited in the instructions (4 of 4)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.