!
Purpose & Capability
The high-level purpose (fetch article content and post to ChainThink) matches the code and instructions. However, the implementation hardcodes a JWT-like token in fetch.sh and asks users to add a token in TOOLS.md in SKILL.md, while the manifest declares no required credentials—this mismatch is inconsistent and unexplained. Also the script calls an 'openclaw browser' CLI and uses jq/curl but the skill declares no required binaries.
!
Instruction Scope
SKILL.md instructs the agent to evaluate JavaScript in the page (window.__NUXT__.data[0]) and then POST to the ChainThink API — which is consistent with the goal. But SKILL.md asks the user to put tokens into TOOLS.md (a place for secrets) and the script contains a hard-coded token; this is scope creep for secret handling. The instructions are specific but they implicitly assume access to a secrets file and to an OpenClaw browser tool that are not declared.
ℹ
Install Mechanism
No install spec (instruction-only) which is low-risk. However the fetch.sh runtime depends on external tools not declared in the manifest: 'openclaw' CLI (openclaw browser action), jq, and curl. The absence of declared required binaries is an implementation inconsistency to be aware of.
!
Credentials
The skill requests no environment variables or credentials in the registry metadata, yet both SKILL.md and fetch.sh require an API token/x-user-id to authenticate to ChainThink. The script embeds a long JWT-like token directly in fetch.sh, and SKILL.md tells users to place a token in TOOLS.md. This is insecure and inconsistent: secrets should be declared and handled via secure env vars or secret storage, not embedded in files or code.
✓
Persistence & Privilege
The skill is not always-enabled and does not request system-wide persistence. It does not modify other skills or system settings. Autonomous invocation is allowed (default) which is normal; no additional privilege flags are present.
Scan Findings in Context
[base64-block] expected: The scanner flagged a base64-like block; this corresponds to the JWT-like token found embedded in SKILL.md and fetch.sh. A token is expected for authenticating to ChainThink, but embedding a token directly in code or documentation is insecure and suspicious.
What to consider before installing
This skill mostly does what its name says, but there are red flags you should address before using it. The implementer embedded a JWT-like token inside fetch.sh and told users to paste a token into TOOLS.md, yet the registry declares no required credentials—this is inconsistent and insecure. Ask the author to: (1) remove any hard-coded token from the code, (2) declare required credentials in the manifest and accept tokens via environment variables or a secrets store (not a plaintext TOOLS.md), (3) document runtime binary requirements (openclaw CLI, jq, curl) so you can run it safely, and (4) confirm the token's owner, scope, and expiry and ideally rotate/revoke the example token shown. Until these issues are fixed, avoid running the script with real secrets or on privileged machines, and consider running it in an isolated environment. Also verify you have the right to repost BlockBeats content to ChainThink (copyright/terms of use).
