Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Diagrams Generator Pro
v1.1.0Generate professional diagrams including cloud architecture, data charts, academic figures, and more. Triggers on requests like "画架构图", "画图表", "画论文插图", "生成系统...
⭐ 0· 363·3 current·3 all-time
byLiuSir@codehourra
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill claims to generate diagrams and includes libraries, docs, and helper code appropriate for that purpose. Requiring payment for a paid skill is plausible. However, the skill embeds a hardcoded BILLING_API_KEY and SKILL_ID directly in SKILL.md and payment.py instead of declaring them as required credentials or relying on a marketplace billing integration, which is unexpected and reduces transparency.
Instruction Scope
SKILL.md explicitly mandates executing payment verification code 'before any diagram generation' and includes copy-paste Python that will make outbound HTTP requests to an external billing service. That instruction forces runtime network calls and delegation of authorization/flow to an external host. The instructions do not request any other system files, but they do require executing code that will reach out to skillpay.me and may raise exceptions or terminate generation on insufficient balance.
Install Mechanism
There is no install spec and no downloaded binaries — the risk from installation mechanism is low. The skill is instruction‑heavy with one included payment.py module; nothing in the manifest downloads or executes arbitrary archives.
Credentials
The skill declares no required env vars but the code uses os.environ.get('SKILLPAY_USER_ID') and embeds a long-lived BILLING_API_KEY directly in the repository. Embedding a secret in code is poor practice and may allow the remote billing operator to track or charge users. The skill does not request user credentials for diagram services, but it will transmit user identifiers to an external billing endpoint.
Persistence & Privilege
always is false, the skill does not request system-wide configuration changes, and its code does not attempt to modify other skills or agent configuration. It will, however, make network calls at runtime (payment checks).
What to consider before installing
Key points before installing or enabling this skill:
- Mandatory payment step: SKILL.md requires running payment verification before any diagram generation. Expect outbound HTTP requests to https://skillpay.me each time the skill runs.
- Hardcoded API key: The repository includes a static BILLING_API_KEY and SKILL_ID in both SKILL.md and payment.py. This is unusual and risky — a leaked or malicious key can be abused by the service operator. Ask the author why the key is embedded and request moving it to a configured secret (environment variable) or using the platform's billing hooks.
- Privacy & tracking: The skill will send a user identifier (SKILLPAY_USER_ID or a default like "anonymous_user") to an external service. If you care about user privacy or leakage of usage patterns, avoid enabling it until you trust the billing provider.
- Trust the endpoint: skillpay.me is an external service of unknown provenance here. Verify the service, its terms, and whether the API key belongs to the skill author or the marketplace. If you cannot verify, run the skill in a sandboxed environment with restricted network access.
- Safe alternatives: Request the author remove the hardcoded key and require an operator-provided API key (env var), or integrate with the OpenClaw/marketplace billing mechanism so the platform mediates charges.
Concrete actions you can take:
- Ask the skill author for provenance of the billing key and reason it is embedded.
- If you still want to try it, run the skill in a network-isolated sandbox and monitor outgoing requests, or block network egress to skillpay.me until you provide your own trusted billing credential.
- Prefer not to enable autonomous invocation for this skill until you accept its billing behavior.
Given these inconsistencies between declared environment requirements and the embedded secret plus mandatory external calls, treat this skill with caution.Like a lobster shell, security has layers — review code before you run it.
latestvk976vbyancq2tgr18kns9xc78182c3fw
License
MIT-0
Free to use, modify, and redistribute. No attribution required.