Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Review code with secure-by-default standards, prioritize exploitable risks, and deliver minimal-diff fixes with evidence and regression checks.
Review code with secure-by-default standards, prioritize exploitable risks, and deliver minimal-diff fixes with evidence and regression checks.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
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.
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.
On first use, read setup.md for integration guidelines. If local memory is needed, ask for consent before creating ~/security-best-practices/.
Use this skill for secure-by-default implementation, targeted vulnerability reviews, and prioritized security reports with actionable fixes. Activate when the user requests security guidance, hardening, risk triage, or remediation planning.
Memory lives in ~/security-best-practices/. See memory-template.md for setup. ~/security-best-practices/ |- memory.md # Stable context, preferences, and activation boundaries |- findings-log.md # Findings registry with severity and status `- exceptions.md # Approved security exceptions and review dates
Load only the minimum file needed for the current request. TopicFileSetup processsetup.mdMemory templatememory-template.mdFull review workflowreview-playbook.mdSeverity model and scoringseverity-model.mdSafe remediation patternsremediation-patterns.mdRisk exception logexceptions.md
Before any conclusions, confirm: System boundary (service, module, endpoint, or workflow) Stack evidence (language, framework, deployment context) Threat assumptions (external attacker, internal misuse, privilege level) No evidence, no finding.
Evaluate every review against a consistent baseline: Authn/authz boundaries Input validation and output encoding Secrets handling and configuration safety Dependency and supply chain posture Logging, error handling, and data exposure controls Use review-playbook.md to keep scans systematic instead of ad hoc.
Each finding must include: Severity from severity-model.md File path and line references Concrete evidence snippet Impact statement in plain language Minimal safe fix direction Avoid speculative findings without repository evidence.
Rank by practical risk, not by checklist volume: Reachability from untrusted inputs Privilege required by attacker Blast radius if exploited Ease of abuse and repeatability High confidence, exploitable issues come first.
Fix one finding at a time: Prefer small diffs that preserve existing behavior Add tests when security fixes alter code paths Flag expected behavior changes before implementing Re-run project validation after each fix batch Use remediation-patterns.md for safe rollouts.
If the user accepts a known risk: Record rationale in exceptions.md Define expiry or next review date Keep the exception scoped to the specific context Never apply broad silent overrides.
Reporting generic best practices without file evidence -> low-trust output that teams cannot action. Flooding with low-severity noise -> critical vulnerabilities get ignored. Proposing major refactors as "quick fixes" -> teams reject security work due to delivery risk. Ignoring framework defaults and deployment context -> false positives and wrong remediations. Declaring a system "secure" after one pass -> hidden regressions remain untested.
Data that leaves your machine: None by default from this skill itself. Data that stays local: Review preferences and finding history in ~/security-best-practices/. Exception rationale in local memory files only. This skill does NOT: Exfiltrate source code to undeclared third-party endpoints. Mark unresolved risks as fixed. Perform hidden destructive changes.
Install with clawhub install <slug> if user confirms: auth - Authentication design and hardening. authorization - Access control and permission boundaries. encryption - Key management and cryptographic hygiene. firewall - Network exposure review and policy controls. devops - Secure delivery, CI checks, and operational safeguards.
If useful: clawhub star security-best-practices Stay updated: clawhub sync
Identity, auth, scanning, governance, audit, and operational guardrails.
Largest current source with strong distribution and engagement signals.