BF design-native-extension-feature
Capture a 2-3 line pitch from the user, draft a product overview (PRD.md) and a technical design (ARCHITECTURE.md) for a third-party `.ppmplugin` native control, then walk through every operation's iOS + Android implementation strategy with opinionated recommendations (library choice, hosting, key APIs, edge cases) and capture the agreed spec in ARCHITECTURE.md §3.<n>. The depth of ARCHITECTURE.md is what lets the scaffold skill generate complete working code instead of TODO placeholders. Iterates with the user until they approve both docs. Optionally seeds from a design doc / FRD URL. PRD.md + ARCHITECTURE.md are the source of truth for every downstream skill (generate, build, assemble). Run this BEFORE any code is generated.
Capture a 2-3 line pitch from the user, draft a product overview (PRD.md) and a technical design (ARCHITECTURE.md) for a third-party .ppmplugin native…
As a process F 46/100 · Will not run — References files that are not bundled: ../../shared/shared-instructions.md, ../../shared/prereq-check.md, ../../shared/naming-conventions.md
What is at stake
Medium-severity findings: the skill is probably honest, but read what alarmed the scanner.
Below is the worst case for this category. The finding here is medium: the guard saw a sign, not a proof.
The skill asks for more than the task needs: broad tool access, credential environment variables, binaries. Every extra permission widens the damage from a mistake or a compromise.
Narrow allowed-tools and the variable list to the minimum; replace binaries with readable sources or scripts.
How to improve
- Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bashallowed-tools: Read Write Edit Bash Glob Grep WebFetch AskUserQuestion Skill
Files scanned: 1. 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
body-longSKILL.md body ≈ 12329 tokens (recommended < 5000); move details to references/ - warning
missing-refreference to a missing file: ../../shared/shared-instructions.md - warning
missing-refreference to a missing file: ../../shared/prereq-check.md - warning
missing-refreference to a missing file: ../../shared/naming-conventions.md - warning
missing-refreference to a missing file: ../../shared/ppmplugin-format.md - warning
missing-refreference to a missing file: ../../shared/error-codes.md - warning
missing-refreference to a missing file: ../../shared/framework-recommendations.md - warning
missing-refreference to a missing file: ../../shared/self-critique-protocol.md - warning
missing-refreference to a missing file: ../../shared/repo-layout.md - warning
missing-refreference to a missing file: ../../shared/shared-instructions.md
Process rating: all ten parameters 46/100
- 0Tools and files. 9 referenced file(s) missing: ../../shared/shared-instructions.md, ../../shared/prereq-check.md, ../../shared/naming-conventions.md
- 0Result and completion. Does not say what the result is
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 8 mutating operations with no state check
- 40Execution cost. Instruction body is 12329 tokens: crowds the task out of the window
- 70Inputs and preconditions. Inputs and preconditions are listed
- 85Steps. 81 steps, 2 vague phrases
- 100Failures and branches. 4 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Progress reporting. Reports progress
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 12 top-level sections: this looks like several domains in one skill
- low The response is described with custom markup (19 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)
- +3Output format is not stated: the model decides each time
- -5TODO / placeholder text left in the skill
- +1No license
- +2Single-language instructions
- +3Description length 736: enough signal without eating the budget
- +4Structure: 21 headings
- +3Step-by-step instructions: 81 items
- +4Has examples (10 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 45.