BC appstore-data-api
Read-only, normalized public-data reads of App Store applications through the ReplyNodes App Store public-read service: app lookup by track id or bundle id, bounded term search, and related-app listings. Bearer workspace-key authentication or x402 v2 payment negotiation at the gateway, transparent bounded pages, normalized errors, and an explicit unsupported-capability matrix. Public reads only: no purchase, review, account, or other mutation exists, and no platform login material is involved.
As a process C 58/100 · Has gaps — weak spots: inputs and preconditions, consistency, progress reporting
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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: 13. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
frontmatter-yamlSKILL.md: the frontmatter is not valid YAML (YAML parse error: Nested mappings are not allowed in compact mappings at line 3, column 14: description: Read-only, normalized public-data reads of App Store applications … ^ ); fields were read line by line. The usual cause is a colon inside an unquoted value - warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - note
frontmatter-keyunknown frontmatter key "title" - note
frontmatter-keyunknown frontmatter key "contract_version" - note
frontmatter-keyunknown frontmatter key "mode" - note
frontmatter-keyunknown frontmatter key "auth" - note
frontmatter-keyunknown frontmatter key "keywords" - note
frontmatter-keyunknown frontmatter key "search_terms" - note
frontmatter-keyunknown frontmatter key "entrypoint" - note
frontmatter-keyunknown frontmatter key "install_guide" - note
frontmatter-keyunknown frontmatter key "source"
Process rating: all ten parameters 58/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (appstore-data-api) differs from the folder (appstore-api)
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 25 steps
- 100Execution cost. Instruction body is 2235 tokens
- 100Running it twice. Mutating operations check current state
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 11 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)
- +4No input/output examples
- +2Single-language instructions
- +3Description length 498: enough signal without eating the budget
- +4Structure: 12 headings
- +3Step-by-step instructions: 25 items
- +3Output format is stated explicitly
- +4Reference files are cited in the instructions (1 of 1)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 63.