Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub ยท Security & Compliance
Insecure Defaults Detection
Detects fail-open insecure defaults (hardcoded secrets, weak auth, permissive security) that allow apps to run insecurely in production. Use when auditing security, reviewing config management, or analyzing environment variable handling.
skill openclawclawhub Free
Detects fail-open insecure defaults (hardcoded secrets, weak auth, permissive security) that allow apps to run insecurely in production. Use when auditing security, reviewing config management, or analyzing environment variable handling.
โฌ 0 downloads โ
0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- SKILL.md, examples.md
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 1.0.0
Provenance
- Publisher
- atlas-secint
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Insecure Defaults Detection
Finds fail-open vulnerabilities where apps run insecurely with missing configuration. Distinguishes exploitable defaults from fail-secure patterns that crash safely. Fail-open (CRITICAL): SECRET = env.get('KEY') or 'default' โ App runs with weak secret Fail-secure (SAFE): SECRET = env['KEY'] โ App crashes if missing
When to Use
Security audits of production applications (auth, crypto, API security) Configuration review of deployment files, IaC templates, Docker configs Code review of environment variable handling and secrets management Pre-deployment checks for hardcoded credentials or weak defaults
When NOT to Use
Do not use this skill for: Test fixtures explicitly scoped to test environments (files in test/, spec/, __tests__/) Example/template files (.example, .template, .sample suffixes) Development-only tools (local Docker Compose for dev, debug scripts) Documentation examples in README.md or docs/ directories Build-time configuration that gets replaced during deployment Crash-on-missing behavior where app won't start without proper config (fail-secure) When in doubt: trace the code path to determine if the app runs with the default or crashes.
Rationalizations to Reject
"It's just a development default" โ If it reaches production code, it's a finding "The production config overrides it" โ Verify prod config exists; code-level vulnerability remains if not "This would never run without proper config" โ Prove it with code trace; many apps fail silently "It's behind authentication" โ Defense in depth; compromised session still exploits weak defaults "We'll fix it before release" โ Document now; "later" rarely comes
Workflow
Follow this workflow for every potential finding:
1. SEARCH: Perform Project Discovery and Find Insecure Defaults
Determine language, framework, and project conventions. Use this information to further discover things like secret storage locations, secret usage patterns, credentialed third-party integrations, cryptography, and any other relevant configuration. Further use information to analyze insecure default configurations. Example Search for patterns in **/config/, **/auth/, **/database/, and env files: Fallback secrets: getenv.*\) or ['"], process\.env\.[A-Z_]+ \|\| ['"], ENV\.fetch.*default: Hardcoded credentials: password.*=.*['"][^'"]{8,}['"], api[_-]?key.*=.*['"][^'"]+['"] Weak defaults: DEBUG.*=.*true, AUTH.*=.*false, CORS.*=.*\* Crypto algorithms: MD5|SHA1|DES|RC4|ECB in security contexts Tailor search approach based on discovery results. Focus on production-reachable code, not test fixtures or example files.
2. VERIFY: Actual Behavior
For each match, trace the code path to understand runtime behavior. Questions to answer: When is this code executed? (Startup vs. runtime) What happens if a configuration variable is missing? Is there validation that enforces secure configuration?
3. CONFIRM: Production Impact
Determine if this issue reaches production: If production config provides the variable โ Lower severity (but still a code-level vulnerability) If production config missing or uses default โ CRITICAL
4. REPORT: with Evidence
Example report: Finding: Hardcoded JWT Secret Fallback Location: src/auth/jwt.ts:15 Pattern: const secret = process.env.JWT_SECRET || 'default'; Verification: App starts without JWT_SECRET; secret used in jwt.sign() at line 42 Production Impact: Dockerfile missing JWT_SECRET Exploitation: Attacker forges JWTs using 'default', gains unauthorized access
Quick Verification Checklist
Fallback Secrets: SECRET = env.get(X) or Y โ Verify: App starts without env var? Secret used in crypto/auth? โ Skip: Test fixtures, example files Default Credentials: Hardcoded username/password pairs โ Verify: Active in deployed config? No runtime override? โ Skip: Disabled accounts, documentation examples Fail-Open Security: AUTH_REQUIRED = env.get(X, 'false') โ Verify: Default is insecure (false/disabled/permissive)? โ Safe: App crashes or default is secure (true/enabled/restricted) Weak Crypto: MD5/SHA1/DES/RC4/ECB in security contexts โ Verify: Used for passwords, encryption, or tokens? โ Skip: Checksums, non-security hashing Permissive Access: CORS *, permissions 0777, public-by-default โ Verify: Default allows unauthorized access? โ Skip: Explicitly configured permissiveness with justification Debug Features: Stack traces, introspection, verbose errors โ Verify: Enabled by default? Exposed in responses? โ Skip: Logging-only, not user-facing For detailed examples and counter-examples, see examples.md.
Category context
Identity, auth, scanning, governance, audit, and operational guardrails.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
2 Docs
- SKILL.md
- examples.md