Hook Rewriter

v1.0.0

Rewrite weak or generic hooks into stronger, creator-native opening lines that capture attention in the first 1-3 seconds for short-form content.

0· 103·0 current·0 all-time
byLeroyCreates@leooooooow
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name, description, and requested inputs all match a hook-rewriting task. There are no unrelated environment variables, binaries, or config paths requested. One minor note: the skill has no homepage or source URL, so provenance is unknown but that does not contradict the stated purpose.
Instruction Scope
SKILL.md limits runtime behavior to diagnosing and rewriting hooks, producing multiple variants, labeling, and flagging risky claims. It does not instruct reading unrelated files, accessing env vars, or sending data to external endpoints.
Install Mechanism
No install spec and no code files — the skill is instruction-only, so nothing is downloaded or written to disk.
Credentials
The skill requires no credentials, env vars, or config paths. All inputs are user-provided content fields appropriate to the task.
Persistence & Privilege
always is false and autonomous invocation is allowed (the platform default). There is no request for persistent system presence or modification of other skills or agent-wide config.
Assessment
This skill appears coherent and low-risk: it only contains instructions for rewriting short-form hooks and asks for user-provided inputs. Before installing, consider: (1) provenance — there is no homepage or source repo listed, so you can't verify the author or review a codebase (the skill is instruction-only, but author legitimacy may matter for trust); (2) review outputs for legal/accuracy issues — the skill is designed to rewrite marketing hooks and may suggest language that could overclaim or violate platform policies, so always vet variants before publishing; and (3) permissions — although the skill requests no credentials or installs, allowing any skill to be invoked autonomously gives it the ability to run without prompting in some workflows, so enable autonomous use only if you trust the skill or plan to review its outputs.

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

latestvk970eeevehvc4ss9eswv43cahn8371ra

License

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

Comments