AF poyo-claude-4-6-api
Claude 4.6 Series Messages API on PoYo / poyo.ai via `https://api.poyo.ai/v1/messages`; use for `claude-sonnet-4-6`, `claude-opus-4-6`, Claude-compatible messages, tools, structured output, prompt cache settings, vision content blocks, streaming, and server-side integration.
Claude 4.6 Series Messages API on PoYo / poyo.ai via https://api.poyo.ai/v1/messages; use for claude-sonnet-4-6, claude-opus-4-6, Claude-compatible messages…
As a process F 61/100 · Will not run — References files that are not bundled: references/api.md, scripts/submit_claude_4_6_messages.sh
How to improve
- The text references files that are not there: add them or drop the references.
- 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: 0. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: references/api.md - warning
missing-refreference to a missing file: scripts/submit_claude_4_6_messages.sh
Process rating: all ten parameters 61/100
- 0Tools and files. 2 referenced file(s) missing: references/api.md, scripts/submit_claude_4_6_messages.sh
- 0Inputs and preconditions. Does not say what the process needs to start
- 60Result and completion. Output format stated, no completion criterion
- 60Failures and branches. 2 branches
- 100Steps. 31 steps
- 100When it triggers. States when to use and when not to
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 758 tokens
- 100Running it twice. No mutating operations
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
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)
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 275: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 31 items
- +3Output format is stated explicitly
Quality base 70; lint remarks subtract, signals add up to 100. Result: 74.