Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Secure Code Warrior
v1.0.0Secure Code Warrior integration. Manage data, records, and automate workflows. Use when the user wants to interact with Secure Code Warrior data.
⭐ 0· 55·0 current·0 all-time
byMembrane Dev@membranedev
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The skill's name/description say it's a Secure Code Warrior integration, but the SKILL.md header requires a Membrane account and network access. The registry metadata lists no required environment variables or primary credential, so the documentation's stated dependency (Membrane account/API access) is not reflected in the declared requirements — an incoherence. The homepage points to getmembrane.com (a third-party proxy/platform) rather than an official Secure Code Warrior endpoint; that may be legitimate but should be explicit.
Instruction Scope
This is an instruction-only skill that explicitly requires network access and a Membrane account; instructions (truncated here) likely direct the agent to call external APIs. Because no required env vars are declared, the SKILL.md may prompt the agent to ask the user for credentials or rely on unconstrained network calls. Instruction-only skills still represent an exfiltration risk if they send user data to an external service. The provided SKILL.md is long and generic; the registry does not make clear which endpoints the agent will call or exactly which secrets it will need.
Install Mechanism
No install spec and no code files are present, so nothing will be written to disk or installed by the platform. That reduces code-execution risk compared with an installer or remote archive.
Credentials
The SKILL.md claims a required Membrane account but the registry lists no required environment variables or primary credential. This is a mismatch: the skill likely needs API credentials (Membrane API key or Secure Code Warrior credentials) but doesn't declare them, which is suspicious and may cause the agent to request sensitive data interactively. The absence of declared credentials prevents proper privilege review before installation.
Persistence & Privilege
The skill does not request permanent presence (always: false) and does not declare any system-level config or path access. Autonomy (disable-model-invocation: false) is the platform default and is not by itself concerning here.
What to consider before installing
Do not install or provide credentials until the developer explains how authentication works and which environment variables or secrets are required. Ask for: (1) a clear list of required env vars (e.g., MEMBRANE_API_KEY, SCW_API_TOKEN) and why each is needed; (2) the exact endpoints the skill calls (Membrane proxy URL vs official Secure Code Warrior API); (3) the repository/source of this skill and an author contact. Prefer skills that declare required credentials in registry metadata. If you must test it, run it in a restricted/sandboxed environment and avoid pasting long-lived secrets; use a limited-scope or ephemeral API key. If the author can't justify why no credentials are declared despite requiring a Membrane account, treat the skill as untrusted.Like a lobster shell, security has layers — review code before you run it.
latestvk979tjjtsybfywhbp0p7x134cs844s3b
License
MIT-0
Free to use, modify, and redistribute. No attribution required.