Security Reliability Design Review

v1.0.0

Review a system design for security and reliability tradeoffs before implementation begins. Use when: evaluating an architecture proposal or design document...

0· 0·0 current·0 all-time
byHung Quoc To@quochungto
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
CryptoCan make purchases
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
The name, description, and SKILL.md all describe reviewing design documents for security and reliability tradeoffs. The skill declares no binaries, no env vars, no install steps, and no code files — all proportional to an instruction-only design-review capability.
Instruction Scope
Runtime instructions focus on analyzing an input design document and optional contextual constraints (policies, SLAs, compliance). The skill requires only Read/Write tools and optionally Grep, which fit the task. It does not instruct the agent to read unrelated system files, environment variables, or transmit data to unexpected endpoints.
Install Mechanism
No install specification and no code files are present, so nothing is written to disk or downloaded. This is the lowest-risk installation model.
Credentials
The skill requests no environment variables, credentials, or config paths. That is appropriate for a reviewer that operates on user-provided design documents.
Persistence & Privilege
always is false and model invocation is allowed (platform default). The skill does not request permanent system presence or modify other skills' config.
Assessment
This skill is instruction-only and coherent for design reviews: it only needs the design document you supply and does not request credentials or installs. Before using it, avoid pasting secrets or regulated data (PCI, PHI, unredacted PII) into the document you provide; if your design contains sensitive data, redact or summarize those parts. Treat the skill's report as advisory—have a human expert validate recommendations for compliance-critical or high-risk systems. Note the skill is labeled draft and its source is listed as unknown even though a GitHub homepage is provided; if provenance matters, review the GitHub repo before trusting it in production workflows.

Like a lobster shell, security has layers — review code before you run it.

bookforgevk976mk58ch089fgke11r378fbh84j562latestvk976mk58ch089fgke11r378fbh84j562tags:vk976mk58ch089fgke11r378fbh84j562

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

📚 Clawdis

Comments