credentials
Solidprobe all credential-shaped variables in the active sandbox across 19 vectors (saves report to .construct/)
Install
Quality Score: 82/100
Skill Content
Details
- Author
- MaisonDeVolonte
- Repository
- MaisonDeVolonte/construct
- Created
- 1 months ago
- Last Updated
- today
- Language
- Shell
- License
- MIT
Similar Skills
Semantically similar based on skill content — not just same category
scripts
extract the commands your workflow scripts run, then verdict each of them (saves report to .construct/)
credential-rotation-protocol
This skill should be used whenever a live credential (API key, bot token, access token, etc.) needs to be rotated, changed, OR REMOVED ENTIRELY — whether because it leaked, is being proactively refreshed, is being replaced as part of an incident response, or auth is simply being turned off on a service. Disabling/removing a password is the same category of change as rotating it and needs the same consumer inventory — arguably more so, since there's no new value to hand out, only broken consumers to discover the hard way if you skip the check. Also load it whenever verifying that a credential file/rotation is correct, since that's exactly the step that causes leaks if done wrong. Trigger phrases include "rotate this credential", "the key leaked", "update this token everywhere", "credential rotation", "verify the new key works", "did the secret change", "disable the password", "turn off auth", "remove the login requirement", "no longer needs a password".
security-audit
Comprehensive polyglot security audit across 60+ frameworks. Runs SARIF scanners and 12 parallel deep-dive categories (auth, injection, crypto, secrets, supply-chain, MCP/agentic, collection-scoping/BOLA, and more), computes severity over composed attack paths, and emits OWASP-tagged results. Use for 'run security audit', 'security audit', 'audit security', or arguments such as 'mode: delta', 'scope: services/api', 'categories: crypto,mitm,secrets', and 'output: docs/security-audit-output'. Every run must first create .claude-audit/current, write each phase artifact and phase-NN.done marker, emit SARIF 2.1.0 with security-severity and CWE on every result, emit a CycloneDX SBOM, then write the human report last. A report without the machine-readable blackboard is invalid.