BC admakeai-api
Create, edit, and ship ad creative via the AdMakeAI API — ad images, edits, batch ad sets, ad copy, UGC video, Meta uploads/analytics. Use it when a request is about making, publishing, or reporting ads. Default to read and list calls; confirm every write or credit-spending action with the user. Trigger words: create, generate, make, design, produce, brainstorm, batch, vary, mock up, upload, publish, push, ship, draft, list, browse, find, get, fetch, look up, audit, or recap ads, ad creatives, product photos, lifestyle shots, UGC, ad copy, hooks, headlines, ad sets, campaigns, competitor ads, competitor research, Meta ads, Facebook ads, or ad analytics. Also use when the user mentions AdMakeAI, admakeai, ad images, ad generator, ad image API, or wants to know their AdMakeAI credit balance.
Create, edit, and ship ad creative via the AdMakeAI API — ad images, edits, batch ad sets, ad copy, UGC video, Meta uploads/analytics.
As a process C 58/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
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 · 5
✓ No critical or high findings
Medium and low: 5
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Bash Read Write WebFetch
-
low Exfiltration
net-credential-useSKILL.md:62Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)curl -H "x-api-key: $ADMAKEAI_API_KEY" \
security skill -
low Exfiltration
net-credential-useSKILL.md:82Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)curl -H "x-api-key: $ADMAKEAI_API_KEY" \
security skill -
low Exfiltration
net-credential-useSKILL.md:86Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)curl -X POST -H "x-api-key: $ADMAKEAI_API_KEY" \
security skill -
low Exfiltration
net-credential-useSKILL.md:92Credential used in a network call (verify the destination is the intended service) (documentation of a security skill)curl -H "x-api-key: $ADMAKEAI_API_KEY" \
security skill
Files scanned: 2. 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 58/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. 40 mutating operations with no state check
- 40Consistency. Frontmatter name (admakeai-api) differs from the folder (admakeai)
- 60Failures and branches. 2 branches
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 4794 tokens
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 17 steps
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (7 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
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +2Single-language instructions
- +3Description length 800: enough signal without eating the budget
- +4Structure: 24 headings
- +3Step-by-step instructions: 17 items
- +4Has examples (3 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.