skill rules designer
v1.2.0Analyzes an existing Claude Code skill and designs an optimal rules/ file structure. Covers three operations: (1) compressing SKILL.md by moving verbose cont...
⭐ 0· 205·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
The name/description (restructure SKILL.md into rules files, encapsulate optional content, add templates, harden wording) matches the instructions and included reference/docs. It requires no binaries, env vars, or installs — appropriate for an instruction-only refactoring helper.
Instruction Scope
Runtime instructions explicitly ask to read the provided skill directory (SKILL.md, rules/*.md, scripts/, assets/) and to present a plan before writing new rules files and updating SKILL.md. Those file reads/writes are coherent with the stated purpose. The SKILL.md also documents waiting for explicit user confirmation before making changes, which limits scope creep — users should still ensure the provided directory is the intended skill directory.
Install Mechanism
No install spec or code files are present; the skill is instruction-only so nothing will be downloaded or written during installation. This is the lowest-risk install posture and matches the skill's operations.
Credentials
The skill requests no environment variables, credentials, or config paths. The instructions do not reference secrets or unrelated system configuration. This is proportionate for a file-restructuring assistant.
Persistence & Privilege
always:false and standard model invocation are used. The skill expects to read and write files inside the user-supplied skill directory (normal for this use). It does not request persistent system-wide privileges or modify other skills' configurations.
Assessment
This skill is internally consistent and appears benign, but be mindful before you run it: 1) Only provide the skill directory you intend the assistant to operate on (do not point it at your home directory or system roots). 2) Confirm the restructuring plan the assistant prints before saying “go” — the SKILL.md claims it will wait for confirmation, which you should enforce. 3) Back up the original SKILL.md (or use version control) before allowing writes so you can recover if edits are unexpected. 4) Note there are no network calls, installs, or credential requests declared; if the assistant later asks for external keys, a URL download, or to operate outside the supplied directory, treat that as suspicious and stop.Like a lobster shell, security has layers — review code before you run it.
latestvk97bpq8p0bk591ah74p3y053e982mpr4
License
MIT-0
Free to use, modify, and redistribute. No attribution required.