BD docs-watch
Check docs.celo.org, docs.minipay.xyz, and other live sources for drift against this repo's cached reference files (contracts, network info, docs sitemap, ecosystem, grants, MiniPay, wFIAT access) and fix or flag it. Use when asked to check docs updates, run the docs watch, or on the scheduled weekly run.
Check docs.celo.org, docs.minipay.xyz, and other live sources for drift against this repo's cached reference files (contracts, network info, docs sitemap…
As a process D 41/100 · Unfinished process — weak spots: result and completion, when it triggers, inputs and preconditions
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 · 3
✓ No critical or high findings
Medium and low: 3
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:71High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)Ripio BridgeDeposit address (`0x46…D47`)
quoted -
low Secrets in code
secret-high-entropy-tokensnapshot.md:232High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)(`0x13…69c`, from the live
quoted -
low Secrets in code
secret-high-entropy-tokensnapshot.md:497High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)CapyFi Comptroller `0x0b…afA` on Celo:
quoted
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 41/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 12 mutating operations with no state check
- 60Tools and files. Uses tools (bash, web) that frontmatter does not declare
- 85Steps. 24 steps, 1 vague phrases
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2455 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (7 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
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 306: enough signal without eating the budget
- +4Structure: 6 headings
- +3Step-by-step instructions: 24 items
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.