Markdown Browser
Analysis
The wrapper code matches its stated purpose, but its npm dependency lockfile points installation at non-HTTPS third-party mirrors, so users should review the install path before using it.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
"resolved": "http://mirrors.tencentyun.com/npm/turndown/-/turndown-7.2.2.tgz"
The lockfile directs dependency retrieval to a non-HTTPS third-party mirror. Because the skill documentation tells users to run npm install, this creates an install provenance and transport-security concern, despite the presence of integrity hashes.
npm install --omit=dev ... node browser.js \ --input /tmp/web_fetch.json
The skill is not purely instructional in use; it expects local package installation and execution of browser.js. This is purpose-aligned for the markdown conversion wrapper but should be understood before installation.
**🛡️ Policy Enforcement**: Automatically parses `Content-Signal` headers. If a site says `ai-train=no`, we flag it immediately.
The wording may sound like automatic enforcement, but the documented behavior is to produce a policy flag for downstream logic. Users should not assume blocked or review-needed content is suppressed automatically.
