BC messenger_node
Use this skill whenever you are asked to send or receive messages, manage contacts, read or send mail, manage groups, look up public keys, check FLO balance, send FLO tokens, view transaction history, perform multisig address generation and multisig transactions using the FLO blockchain messenger, query FLO token (fungible token) balances or send tokens, query Bitcoin blockchain (balance, history, transactions, address generation, multisig), or manage local key-value storage. This is the primary way to interact with the decentralized FLO messenger, blockchain, and standard-operations libraries programmatically.
As a process C 52/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
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 · 13
✓ No critical or high findings
Medium and low: 13
-
low Secrets in code
secret-high-entropy-tokenbtc_node.js:25High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)global.floGlobals = { blockchain: "FLO", application: "messenger", adminID: "FMRs…3aQ" };detector -
low Secrets in code
secret-high-entropy-tokendapp_node.js:21High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)global.floGlobals = { blockchain: "FLO", application: "messenger", adminID: "FMRs…3aQ" };detector -
low Secrets in code
secret-high-entropy-tokenflo_node.js:27High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)global.floGlobals = { blockchain: "FLO", application: "messenger", adminID: "FMRs…3aQ" };detector -
low Secrets in code
secret-high-entropy-tokennode_shared.js:22High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)adminID: "FMRs…3aQ"
quoted -
low Secrets in code
secret-high-entropy-tokenreceive_node.js:22High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)adminID: "FMRs…3aQ"
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/floCloudAPI.js:8High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)SNStorageID: floGlobals.SNStorageID || "FNaN…gfk",
detector -
low Secrets in code
secret-password-literalscripts/lib.js:2945Hard-coded password / key literal (may be an example)if (password.constructor == String) password = UTF8…tes(password);
-
low Secrets in code
secret-high-entropy-tokenscripts/lib.js:6643High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)coinjs.developer = '33th…E4G'; //bitcoin
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/lib.js:7253High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)'message': 'i2FL…QZq',
quoted -
low Secrets in code
secret-high-entropy-tokenscripts/lib.js:7260High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)'message': 'lEE5…CEh',
quoted -
low Secrets in code
secret-high-entropy-tokensend_node.js:29High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)adminID: "FMRs…3aQ"
quoted -
low Secrets in code
secret-high-entropy-tokensend_node.js:82High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)const SNStorageID = floCloudAPI.SNStorageID; // "FNaN…gfk"
quoted -
low Secrets in code
secret-high-entropy-tokentoken_node.js:31High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)adminID: "FMRs…3aQ",
quoted
Files scanned: 28. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
name-formatname should be kebab-case (lowercase letters, digits, hyphens) - warning
body-longSKILL.md body ≈ 7727 tokens (recommended < 5000); move details to references/ - note
frontmatter-keyunknown frontmatter key "requires"
Process rating: all ten parameters 52/100
- 0Result and completion. Does not say what the result is
- 0Progress reporting. Says nothing while it works
- 30Inputs and preconditions. Does not say what the process needs to start
- 40Consistency. Frontmatter name (messenger_node) differs from the folder (ranchimall-messenger)
- 55Failures and branches. 1 branches
- 60Tools and files. Uses tools (bash, web, node) that frontmatter does not declare
- 70When it triggers. States when to use, but not when not to
- 70Execution cost. Instruction body is 7727 tokens
- 85Steps. 18 steps, 1 vague phrases
- 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 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
- -31 of 10 scripts are never mentioned in SKILL.md
- +1No license
- +2Single-language instructions
- +3Description length 618: enough signal without eating the budget
- +4Structure: 28 headings
- +3Step-by-step instructions: 18 items
- +4Has examples (14 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 65.