CF polygon-pos-dev
Comprehensive guide for Polygon PoS blockchain development. Use when deploying smart contracts to Polygon, testing on Amoy testnet, getting test tokens from faucets, or verifying contracts on Polygonscan. Supports Foundry framework with deployment scripts and testing strategies.
Comprehensive guide for Polygon PoS blockchain development.
As a process F 46/100 · Will not run — References files that are not bundled: assets/sample-contracts/HelloWorld.sol, assets/sample-contracts/.env.example
What is at stake
The skill contains fragments that, in the wrong hands, cost money or data. Below: what the installer risks and what the author should do.
The skill contains commands that delete files, rewrite disks or execute code fetched from the network. The agent may run them without asking if it believes the instructions require it.
Replace destructive commands with safe equivalents that ask for confirmation, scope them to one folder, and stop piping curl into a shell: pin a version and a checksum.
How to improve
- Address the high-severity findings: each costs 18 safety points. If one is a false positive, add the rule id to guard.allow in spec.yaml.
- 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 · 8
-
high Dangerous commands
cmd-pipe-to-shellreferences/foundry-deployment.md:10Downloads and executes remote code from an unrecognised host (pipe to shell)curl -L https://foundry.paradigm.xyz | bash
-
high Dangerous commands
cmd-pipe-to-shellSKILL.md:117Downloads and executes remote code from an unrecognised host (pipe to shell)curl -L https://foundry.paradigm.xyz | bash
Medium and low: 6
-
medium Dangerous commands
cmd-pipe-to-shellSKILL.md:69Downloads and executes remote code from an unrecognised host (pipe to shell) (quoted — discussed, not commanded)- Foundry installed: `curl -L https://foundry.paradigm.xyz | bash && foundryup`
quoted -
low Exfiltration
net-credential-usereferences/foundry-deployment.md:55Credential used in a network call (verify the destination is the intended service) (detector / deny-list definition; the skill's own vendor host)amoy = { key = "${POLYGONSCAN_API_KEY}", url = "https://api-amoy.polygonscan.com/api" }detectorvendor-host -
low Exfiltration
net-credential-usereferences/foundry-deployment.md:56Credential used in a network call (verify the destination is the intended service) (detector / deny-list definition; the skill's own vendor host)polygon = { key = "${POLYGONSCAN_API_KEY}", url = "https://api.polygonscan.com/api" }detectorvendor-host -
low Secrets in code
secret-high-entropy-tokenreferences/testing-strategies.md:194High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file)address usdcAddress = 0x27…174;
fixture -
low Exfiltration
net-credential-useSKILL.md:144Credential used in a network call (verify the destination is the intended service) (detector / deny-list definition; the skill's own vendor host)amoy = { key = "${POLYGONSCAN_API_KEY}", url = "https://api-amoy.polygonscan.com/api" }detectorvendor-host -
low Exfiltration
net-credential-useSKILL.md:145Credential used in a network call (verify the destination is the intended service) (detector / deny-list definition; the skill's own vendor host)polygon = { key = "${POLYGONSCAN_API_KEY}", url = "https://api.polygonscan.com/api" }detectorvendor-host
Files scanned: 4. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: assets/sample-contracts/HelloWorld.sol - warning
missing-refreference to a missing file: assets/sample-contracts/.env.example
Process rating: all ten parameters 46/100
- 0Tools and files. 2 referenced file(s) missing: assets/sample-contracts/HelloWorld.sol, assets/sample-contracts/.env.example
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 70Inputs and preconditions. Inputs and preconditions are listed
- 70Execution cost. Instruction body is 4175 tokens
- 100Steps. 97 steps
- 100Consistency. Name and required fields are in place
- 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 17 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)
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 279: enough signal without eating the budget
- +4Structure: 52 headings
- +3Step-by-step instructions: 97 items
- +4Has examples (29 code blocks)
- +4Reference files are cited in the instructions (3 of 3)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 79.