BC 1panel-appstore-skills
Create 1Panel appstore/local-app installation packages for Dockerized applications from official repositories, Docker images, docker-compose.yml files, or a prepared app spec.
Create 1Panel appstore/local-app installation packages for Dockerized applications from official repositories, Docker images, docker-compose.yml files, or a…
As a process C 53/100 · Has gaps — References files that are not bundled: scripts/init.sh
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- 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 · 1
✓ No critical or high findings
Medium and low: 1
-
low Obfuscation
obf-base64-blobscripts/generate_app_package.py:99Long base64-looking blob (quoted — discussed, not commanded)"iVBO…mP8/x8AAwMCAO+/p9sA…YII="
quoted
Files scanned: 12. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
description-no-whendescription does not say WHEN to use the skill (no "use when") - warning
missing-refreference to a missing file: scripts/init.sh
Process rating: all ten parameters 53/100
- 0Tools and files. 1 referenced file(s) missing: scripts/init.sh
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 40Consistency. Frontmatter name (1panel-appstore-skills) differs from the folder (1panel-appstore)
- 50When it triggers. No condition that starts the skill
- 60Result and completion. Output format stated, no completion criterion
- 100Steps. 48 steps
- 100Failures and branches. 1 branches, has a failure section
- 100Execution cost. Instruction body is 1555 tokens
- 100Running it twice. Mutating operations check current state
- low The response is described with custom markup (5 tags): a typed call is more reliable
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 175: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 48 items
- +3Output format is stated explicitly
- +4Has examples (0 code blocks)
- +4Reference files are cited in the instructions (4 of 4)
- +3All 2 scripts are documented
Quality base 70; lint remarks subtract, signals add up to 100. Result: 76.