BD hub-api-integration
Help apps and distribution channels integrate PCS Hub into their frontend. Use when user says "/hub-api-integration", "integrate PCS Hub", "embed PCS Hub swap", "PCS Hub integration guide", "how do I add PCS Hub to my wallet", "create a PCS Hub integration spec", or describes wanting to embed PCS Hub quote/swap functionality in an external UI.
As a process D 49/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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
- The SKILL.md body is over 5,000 tokens: move reference detail into references/ and load it when needed.
- 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 · 6
✓ No critical or high findings
Medium and low: 6
-
medium Broad scope
meta-broad-allowed-toolsSKILL.md:1Broad tool permissions pre-approved: Bash(curl:*)allowed-tools: Read Write Edit Glob Grep Bash(curl:*) Bash(jq:*) WebFetch AskUserQuestion
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:145High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition; documentation table row)| 6 | **Approval check** | For ERC-20 source tokens, check allowance via `eth_call` against router `0x5e…68a` before generating calldata. If allowance < `amountI
detectortable -
low Secrets in code
secret-high-entropy-tokenSKILL.md:183High-entropy token-like string (may be an id, hash or a credential) (documentation table row)| Router contract | `0x5e…68a` |
table -
low Secrets in code
secret-high-entropy-tokenSKILL.md:190High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"address": "0x21…3F8",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:205High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"src": "0x21…3F8",
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:206High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)"dst": "0x55…955",
quoted
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
body-longSKILL.md body ≈ 7232 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "slug" - note
frontmatter-keyunknown frontmatter key "homepage"
Process rating: all ten parameters 49/100
- 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. 9 mutating operations with no state check
- 40Consistency. Frontmatter name (hub-api-integration) differs from the folder (pcs-api-integration)
- 50Failures and branches. 0 branches, has a failure section
- 70Execution cost. Instruction body is 7232 tokens
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 44 steps
- 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
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
- +4Description does not say when NOT to use the skill (false activations)
- +2Single-language instructions
- +5Description quotes 6 example trigger phrases
- +3Description length 345: enough signal without eating the budget
- +4Structure: 32 headings
- +3Step-by-step instructions: 44 items
- +3Output format is stated explicitly
- +4Has examples (17 code blocks)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 81.