Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
skill-state-manager
v0.0.1A Meta Skill that manages API keys and state persistence for other tools. Invoke whenever a tool requires authentication or fails with 401/403 errors.
⭐ 1· 48·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
The declared purpose (meta skill to manage API keys) matches the SKILL.md behavior, but the registry metadata lists no required config paths while the instructions mandate writing/reading ~/.claude/skills-state/ and ~/.ai-skills-state/. That mismatch (metadata omits persistent filesystem use) is an incoherence and reduces transparency about what the skill will access.
Instruction Scope
Runtime instructions explicitly tell the agent to pause tool actions, ask the user for secrets in chat, and save them to local JSON files via a Write tool. The instructions do not limit what secrets may be requested, do not require confirming the minimal scope of data to store, and do not specify permissions/encryption — enabling social-engineering-style requests and insecure storage.
Install Mechanism
Instruction-only skill with no install spec or downloaded code. Low installation risk because nothing is written to disk by an installer, but runtime behavior still writes files via the agent's Write tool.
Credentials
No environment variables or credentials are declared, which superficially reduces risk, but the skill's purpose is to collect and persist credentials for other tools. Requiring broad, unspecified secrets (and storing them plaintext) is disproportionate without explicit limits, encryption, or an audit trail.
Persistence & Privilege
The skill requests persistent storage of secrets on-disk (home-directory JSON files) but does not declare that persistence in metadata or provide mitigations (file permissions, encryption, keyring/backing store). Autonomous invocation (allowed by default) combined with the ability to solicit and store secrets increases blast radius if the agent or another skill is compromised.
What to consider before installing
This skill claims to simplify credential handling but leaves important security details out. Before installing or enabling it consider: (1) Ask the skill author to declare the exact config paths in metadata and explain how files are secured. (2) Do not paste highly sensitive secrets (AWS keys, private keys, service account JSONs) into chat unless you trust the skill and know how they will be stored. (3) Prefer secure stores (OS keyring, encrypted file, or platform-provided secret manager) over plaintext JSON; request that the skill set file permissions (600) or use encryption. (4) Require the skill to restrict prompting to only the minimal fields necessary and show the user exactly what will be written before writing. (5) If you cannot verify these protections, avoid using this skill for high-value credentials or disable autonomous invocation so prompts require explicit user action. Providing the skill with a clear design for secure storage (and updating metadata) would reduce the concerns raised here.Like a lobster shell, security has layers — review code before you run it.
latestvk97c4fasdmaw37p6akfa6vqem1844jn9
License
MIT-0
Free to use, modify, and redistribute. No attribution required.