BB webapp-to-capacitor
Plans and executes turning an existing web app, PWA, or SPA into a store-ready Capacitor iOS and Android app. Use when the user wants to wrap a website or PWA as a mobile app, worries about Apple guideline 4.2 minimum functionality or thin-WebView rejection, needs a phased migration plan (static build, Capacitor shell, native UX, plugins, permissions, offline, account deletion, in-app purchase vs web billing, demo account, Play closed testing), or asks what still breaks after the first successful cap sync. Do not use for framework build configuration alone (framework-to-capacitor), Cordova apps (cordova-to-capacitor), final store submission mechanics (capacitor-app-store), or an Apple rejection audit (capacitor-apple-review-preflight).
Plans and executes turning an existing web app, PWA, or SPA into a store-ready Capacitor iOS and Android app.
As a process B 78/100 · Nearly there — weak spots: inputs and preconditions, running it twice
The same skill appears in 1 more place: capgo-skills
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 · 2
✓ No critical or high findings
Medium and low: 2
-
low Broad scope
meta-dynamic-shellSKILL.md:30Shell command executed automatically when the skill loads (Claude Code !`cmd` preamble)!`node -e "const fs=require('fs');if(!fs.existsSync('package.json'))process.exit(0);const pkg=JSON.parse(fs.readFileSync('package.json','utf8'));const names=['@capacitor/core','@capacitor/cli','@capac -
low Broad scope
meta-dynamic-shellSKILL.md:33Shell command executed automatically when the skill loads (Claude Code !`cmd` preamble)!`find . -maxdepth 4 -not -path '*/node_modules/*' \( -name 'capacitor.config.*' -o -name 'vite.config.*' -o -name 'next.config.*' -o -name 'nuxt.config.*' -o -name 'angular.json' -o -name 'svelte.con
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 78/100
- 0Inputs and preconditions. Does not say what the process needs to start
- 30Running it twice. 8 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 85Steps. 44 steps, 1 vague phrases
- 100Tools and files. Tools declared in frontmatter
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2478 tokens
- 100Progress reporting. Reports progress
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
- -2localhost URLs: will not work for another user
- +1No license
- +2Single-language instructions
- +4Description says when NOT to use the skill
- +3Description length 745: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 44 items
- +3Output format is stated explicitly
- +4Has examples (3 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 89.