BF asc-in-app-events
Create and localize App Store in-app events, upload event media, and submit or recover event review submissions with asc. Use when managing in-app events, event card or details page assets, or event-specific submission errors.
Promises to manage App Store in-app events: create, localize, upload media, submit for review via CLI. Single instruction file at 1948 tokens, no scripts. Grade B with quality 78, but process score 32 signals gaps—broken references and missing files flagged. Never tested on models or sandbox. Likely functional, but verify on your project first before production use, especially if submission error handling and recovery workflows are critical to your pipeline.
Create and localize App Store in-app events, upload event media, and submit or recover event review submissions with asc.
As a process F 32/100 · No process to follow — References files that are not bundled: ../asc-metadata-sync/references/asset-library.md
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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../asc-metadata-sync/references/asset-library.md
Process rating: all ten parameters 32/100
- 0Tools and files. 1 referenced file(s) missing: ../asc-metadata-sync/references/asset-library.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 6 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 64Steps. 3 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1948 tokens
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
- +1No license
- +2Single-language instructions
- +3Description length 226: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 3 items
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 78.