AB webhook-http-request
Webhook - HTTP Request: Make HTTP requests (GET, POST, PUT, DELETE, etc.). Use when an agent needs webhook http request, webhook http request, fetching data from third party rest apis for aggregation or transformation pipelines, submitting form data or json payloads to webhook endpoints for event driven workflows, authenticating with oauth protected services using bearer tokens for secure integrations, polling external services for status updates or job completion in asynchronous workflows.
Webhook - HTTP Request: Make HTTP requests (GET, POST, PUT, DELETE, etc.). Use when an agent needs webhook http request, webhook http request, fetching data…
As a process B 68/100 · Nearly there — weak spots: inputs and preconditions, running it twice, progress reporting
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: 3. 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 68/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 8 mutating operations with no state check
- 60Tools and files. Uses tools (web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 70When it triggers. States when to use, but not when not to
- 100Steps. 75 steps
- 100Failures and branches. 2 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 3656 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 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)
- +1No license
- +2Single-language instructions
- +3Description length 495: enough signal without eating the budget
- +4Structure: 19 headings
- +3Step-by-step instructions: 75 items
- +3Output format is stated explicitly
- +4Has examples (15 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 86.