AC lanbow-ads-skills
End-to-end Meta (Facebook/Instagram) advertising system orchestrator covering the full ad lifecycle: strategy research, creative generation, campaign delivery, and post-campaign optimization. Use when: (1) Planning and executing a complete Meta Ads campaign from scratch (2) Running the full ads lifecycle: research → create → launch → review → optimize (3) User says "run ads", "launch campaign", "full ads system", "ads pipeline", "广告投放全流程" (4) User needs guidance on which ads skill to use for their current task (5) Coordinating between strategy, creative, delivery, and review phases This skill orchestrates 4 sub-skills: ads-strategy-researcher (insights), creative_gen (creatives), lanbow-ads (delivery), and post-campaign-review (optimization). Each can also be used independently.
As a process C 50/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
- 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: 11. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 50/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 15 mutating operations with no state check
- 40Consistency. Frontmatter name (lanbow-ads-skills) differs from the folder (lanbow-claw-skill)
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 70Execution cost. Instruction body is 4762 tokens
- 85Steps. 50 steps, 2 vague phrases
- 100Failures and branches. 4 branches, has a failure section
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 10 top-level sections: this looks like several domains in one skill
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
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 789: enough signal without eating the budget
- +4Structure: 22 headings
- +3Step-by-step instructions: 50 items
- +4Has examples (4 code blocks)
- +4Reference files are cited in the instructions (9 of 9)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 92.