Development Checklist Generator
v1.0.0Create effective development checklists (code completion, unit/functional testing, software release) that teams will actually follow. Use this skill whenever...
⭐ 0· 13·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
These labels describe what authority the skill may exercise. They are separate from suspicious or malicious moderation verdicts.
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (development checklist generation) match the SKILL.md and the included checklist templates. The skill optionally accepts a codebase for more specific advice and requests Read/Write tools which are reasonable for producing and saving checklists.
Instruction Scope
SKILL.md confines actions to checklist design, optional codebase scanning for common patterns, and asking clarifying questions. It does instruct the agent to use Read and Write (and optionally Grep/Bash) to examine a codebase; this scope is consistent with the skill's purpose but means the agent may access repository files if provided — verify you want it to read that data.
Install Mechanism
No install spec and no code files — instruction-only — so nothing is downloaded or written by an installer. Low installation risk.
Credentials
No environment variables, credentials, or config paths are requested. The only notable resource access is Read/Write on a codebase (declared). That access is proportionate to generating code-aware checklists but could expose sensitive files if a repository contains secrets.
Persistence & Privilege
always is false and model invocation is normal. The skill does not request persistent or elevated platform privileges beyond normal agent tool access.
Assessment
This skill appears coherent and low-risk for its stated purpose. Before installing or invoking it: (1) confirm you trust the skill source (homepage points to a GitHub repo); (2) be aware that if you provide a codebase the agent will read files (and can optionally write outputs) — do not supply repositories containing secrets you don't want the agent to access; (3) if your environment grants optional shell/grep tools, consider disabling them unless you need deep automated scanning (they could execute commands in some environments); and (4) review generated checklists before committing them to repo or CI to ensure no sensitive information was included and that items match your team's process.Like a lobster shell, security has layers — review code before you run it.
architecturevk975rx5syrbej5a3mg1mqrmxb184p8habookforgevk975rx5syrbej5a3mg1mqrmxb184p8hachecklistsvk975rx5syrbej5a3mg1mqrmxb184p8hadeploymentvk975rx5syrbej5a3mg1mqrmxb184p8halatestvk975rx5syrbej5a3mg1mqrmxb184p8haprocessvk975rx5syrbej5a3mg1mqrmxb184p8haqualityvk975rx5syrbej5a3mg1mqrmxb184p8hasoftware-architecturevk975rx5syrbej5a3mg1mqrmxb184p8hateam-effectivenessvk975rx5syrbej5a3mg1mqrmxb184p8ha
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📚 Clawdis