ClawHub

Skill Design Guide Skill

v1.3.3

Design better AI skills with proven architecture patterns. Helps you decide Workflow vs Agent, pick the right pattern (Prompt Chaining, Routing, Parallelizat...

⭐ 1· 87·0 current·0 all-time
byhaiyangchen@haiyangchenbj
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
Capability signals
Crypto
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
Name/description (skill design guide) match the actual contents: an architecture decision guide and checklist. The skill requires no env vars, binaries, or installs, which is proportionate for a documentation/guide skill.
✓
Instruction Scope
SKILL.md contains design guidance, patterns, checklists and trigger keywords. It does not instruct the agent to read unrelated system files, access credentials, or transmit data to external endpoints. References are local files included in the repo and meant for on-demand reading as part of design guidance.
✓
Install Mechanism
No install specification and no code files — this is instruction-only. That is the lowest-risk install posture and appropriate for a documentation-style skill.
✓
Credentials
The skill declares no required environment variables, credentials, or config paths. Nothing requested is disproportionate to its purpose as a design guide.
✓
Persistence & Privilege
Flags: always=false (default), user-invocable=true, disable-model-invocation=false. These defaults are normal for a user-invocable skill. The skill does not request persistent system privileges or attempt to modify other skills' configs.
Assessment
This skill is a documentation-only design guide and appears coherent and low-risk: it asks for nothing sensitive and contains no executable install steps. Before installing, verify the source repo (homepage link) if provenance matters, review the trigger keywords so it only loads when you want it, and treat its recommendations as guidance (not enforcement). If you plan to use its templates in production, apply your own security and access guardrails for any scripts/tools you implement based on the guide.

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

latestvk97ccf0fav473fympngtwat51584xxmj

License

MIT-0
Free to use, modify, and redistribute. No attribution required.
Termshttps://spdx.org/licenses/MIT-0.html

Comments