BC wechat-article-crawler
WeChat Official Account article crawler with x402 micropayments. Requires Chrome browser and interactive WeChat QR login on first use. Harvest articles for research and analysis with pay-as-you-go Base USDC pricing.
As a process C 54/100 · Has gaps — weak spots: result and completion, inputs and preconditions, consistency
How to improve
For the model run — optional
- 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 · 16
✓ No critical or high findings
Medium and low: 16
-
low Secrets in code
secret-high-entropy-tokenblockchain_verifier.py:28High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"usdc_contract": "0x83…913",
detector -
low Secrets in code
secret-high-entropy-tokenblockchain_verifier.py:34High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)"usdc_contract": "0x03…F7e",
detector -
low Secrets in code
secret-high-entropy-tokenblockchain_verifier.py:293High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)self.usdc_contract = "0x83…913"
detector -
low Secrets in code
secret-high-entropy-tokenblockchain_verifier.py:296High-entropy token-like string (may be an id, hash or a credential) (detector / deny-list definition)self.usdc_contract = "0x03…F7e"
detector -
low Secrets in code
secret-high-entropy-tokenconfig.py:6High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)USDC_CONTRACT = "0x83…913"
quoted -
low Secrets in code
secret-high-entropy-tokenconfig.py:9High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)RECEIVING_ADDRESS = "0x17…07A"
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:27High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)receiving_address: "0x17…07A"
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:143High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)RECEIVING_ADDRESS = "0x17…07A"
quoted -
low Secrets in code
secret-high-entropy-tokenSKILL.md:189High-entropy token-like string (may be an id, hash or a credential)Receiving address: 0x17…07A
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:195High-entropy token-like string (may be an id, hash or a credential)3. Send $2.0 USDC to: 0x17…07A
-
low Secrets in code
secret-high-entropy-tokenSKILL.md:328High-entropy token-like string (may be an id, hash or a credential) (quoted — discussed, not commanded)- **Receiving Address**: Double-check `0x17…07A` before sending payments
quoted -
low Secrets in code
secret-high-entropy-tokentest_payment.py:24High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)"usdc_contract": "0x03…F7e",
fixturequoted -
low Secrets in code
secret-high-entropy-tokentest_payment.py:201High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)tx_hash = mock_chain.create_mock_transaction(10.0, "0x17…07A")
fixturequoted -
low Secrets in code
secret-high-entropy-tokentest_payment.py:235High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)tx_hash = mock_chain.create_mock_transaction(100.0, "0x17…07A")
fixturequoted -
low Secrets in code
secret-high-entropy-tokentest_payment.py:287High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)tx_hash = mock_chain.create_mock_transaction(100.0, "0x17…07A")
fixturequoted -
low Secrets in code
secret-high-entropy-tokentest_payment.py:309High-entropy token-like string (may be an id, hash or a credential) (test fixture / example file; quoted — discussed, not commanded)print(" 收款地址: 0x17…07A")fixturequoted
Files scanned: 23. 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 54/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
- 30Running it twice. 6 mutating operations with no state check
- 40Consistency. Frontmatter name (wechat-article-crawler) differs from the folder (wechat-articles-spider)
- 50When it triggers. No condition that starts the skill
- 50Failures and branches. 0 branches, has a failure section
- 100Tools and files. Tools declared in frontmatter
- 100Steps. 60 steps
- 100Execution cost. Instruction body is 2260 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low 16 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 215: enough signal without eating the budget
- +4Structure: 32 headings
- +3Step-by-step instructions: 60 items
- +4Has examples (18 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 84.
External checks
ClawHub: suspicious
The skill is mostly what it claims to be, but it handles WeChat session credentials and payments in ways users should review carefully before installing.
LLM: suspicious (high) · VirusTotal: · 29 May 2026