AB tiktok-growth
Use to grow a TikTok account — the TikTok-specific growth strategy that diagnoses where growth is stuck and orchestrates the other skills to fix it. Run when the user says "grow on TikTok," "TikTok growth," "get more followers/views on TikTok," "my TikTok isn't growing," "go viral on TikTok," or "TikTok strategy." Reads brand-profile, social-strategy, and audience first. Built on the 2026 reality that TikTok is an interest graph — follower count is not a ranking factor; completion rate and rewatches drive reach, and search/SEO is a major evergreen pillar. Diagnoses the broken stage of the test-and-expand loop and routes to the right skill (tiktok-script, hook-writer, profile-optimization, content-calendar, hashtag-strategy, trend-jacking, viral-reverse-engineering). Judges via native TikTok analytics — not WoopSocial analytics — and treats followers as a business asset, not the reach mechanism.
Use to grow a TikTok account — the TikTok-specific growth strategy that diagnoses where growth is stuck and orchestrates the other skills to fix it.
As a process B 67/100 · Nearly there — 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: 5. 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 67/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. 3 mutating operations with no state check
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 31 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1588 tokens
- low 12 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 907: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +4Structure: 13 headings
- +3Step-by-step instructions: 31 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.