DC placecall
The phone is your last API. Give your agent a voice to call any US business and take action in the real world. PlaceCall handles reservations, inquiries, and quotes - navigating IVRs, holds, and transfers. You get a verified outcome + full transcript. First 250 calls free. Pay only for outcomes.
The phone is your last API.
As a process C 55/100 · Has gaps — weak spots: result and completion, inputs and preconditions
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The skill tells the agent to hide things from you: not to show errors, not to mention actions, to report differently from what was done. You lose the ability to see what the agent really did.
Transparency beats a smooth answer. If the goal is to hide technical noise, ask the agent to "summarise briefly", not to "not mention".
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The instructions or scripts send data out: environment variables, keys, file contents, chat history. You may never notice, because the agent performs the upload as "part of the task".
If the upload is not needed for the task, remove it: catalogs flag such skills and delist them. If it is needed, name the destination explicitly, say what leaves the machine, and give the user a switch.
How to improve
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- For Hermes the description must be one sentence under 60 characters; move the conditions to a "When to Use" section.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 6
-
high Concealment
en-hide-from-userSKILL.md:136Instruction to hide actions from the usershell/terminal tool (`curl`). NEVER tell the user you cannot make calls or that
-
high Concealment
en-hide-from-userSKILL.md:525Instruction to hide actions from the user**Do not retry, and do not tell the user the API is down.** Say which of these
Medium and low: 4
-
medium Exfiltration
net-credential-useSKILL.md:179Credential used in a network call (verify the destination is the intended service)curl -s -H "X-API-Key: $PLACECALL_API_KEY" https://api.voygr.tech/users/me
-
medium Exfiltration
net-credential-useSKILL.md:422Credential used in a network call (verify the destination is the intended service)OUT=$(curl -s --max-time 20 -H "X-API-Key: $PLACECALL_API_KEY" \
-
medium Exfiltration
net-credential-useSKILL.md:455Credential used in a network call (verify the destination is the intended service)curl -s -H "X-API-Key: $PLACECALL_API_KEY" https://api.voygr.tech/calls/$ID
-
medium Exfiltration
net-credential-useSKILL.md:495Credential used in a network call (verify the destination is the intended service)curl -s -H "X-API-Key: $PLACECALL_API_KEY" https://api.voygr.tech/v1/usage
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-long-hermesdescription is 296 chars; the Hermes authoring standard requires ≤ 60 (one sentence, ending with a period) - warning
description-no-whenneither description nor a "## When to Use" section says when to use the skill - warning
body-longSKILL.md body ≈ 7359 tokens (recommended < 5000); move details to references/
Process rating: all ten parameters 55/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 50When it triggers. No condition that starts the skill
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Consistency. The Hermes dialect needs category and tags
- 70Execution cost. Instruction body is 7359 tokens
- 85Steps. 76 steps, 3 vague phrases
- 100Failures and branches. 3 branches, has a failure section
- 100Running it twice. Mutating operations check current state
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 18 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
- +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 296: enough signal without eating the budget
- +4Structure: 25 headings
- +3Step-by-step instructions: 76 items
- +4Has examples (11 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 57.