AC pinterest-growth
The Pinterest growth playbook for 2026. Use when someone wants to "grow on Pinterest," "get traffic from Pinterest," "a Pinterest strategy," a pin cadence/board structure, or to turn blog/product content into pins. Pinterest is a visual SEARCH engine where keyword-optimized, fresh, vertical pins compound into evergreen outbound traffic — optimise for discoverability + clicks, not in-the-moment engagement. Uses the PINS framework. Reads brand-profile + voice-builder first. The agent drafts pins + the schedule; WoopSocial schedules/publishes pins; metrics come from native Pinterest Analytics; nothing is fabricated. For "Pinterest SEO" / "rank my pins" / keyword titles-descriptions route to pinterest-seo; for designing the pin image route to pinterest-pin-design. Pairs with content-recycling.
The Pinterest growth playbook for 2026.
As a process C 56/100 · Has gaps — weak spots: result and completion, when it triggers, inputs and preconditions
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 56/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 5 mutating operations with no state check
- 40Result and completion. Does not say what the result is
- 100Tools and files. No external tools needed
- 100Steps. 12 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1308 tokens
- 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)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 800: enough signal without eating the budget
- +4Structure: 9 headings
- +3Step-by-step instructions: 12 items
- +4Reference files are cited in the instructions (4 of 4)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.