Prompts
v1.0.0Deep prompt engineering workflow—task spec, constraints, examples, evaluation sets, iteration protocol, regression testing, and safety alignment. Use when im...
⭐ 0· 69·0 current·0 all-time
by@clawkk
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name and description match the content of SKILL.md: a six-stage prompt engineering workflow. The skill requests nothing (no env vars, binaries, or config paths) that would be unexpected for this purpose.
Instruction Scope
SKILL.md stays on topic (task spec, constraints, examples, eval sets, iteration, shipping). It does not instruct the agent to read unrelated files, access credentials, or transmit data to external endpoints. Suggestions to log prompt version IDs and to align with an llm-evaluation skill are reasonable operational notes, not secret access.
Install Mechanism
No install spec (instruction-only). Nothing is written to disk or downloaded, which minimizes risk and is appropriate for a guidance-style skill.
Credentials
The skill declares no required environment variables, credentials, or config paths. There are no disproportionate secret or config requests relative to the stated purpose.
Persistence & Privilege
always is false and model invocation is allowed (platform default). The skill does not request persistent system-wide privileges or to modify other skills' configs.
Assessment
This is a safe, instruction-only prompt-engineering workflow and appears coherent with its description. Before using in production: (1) review any downstream tooling or CI integrations you’ll connect to (regression suites, logging) because those may require credentials or network access outside this skill; (2) avoid pasting secrets into prompts or eval sets; (3) if you link this guidance to other skills (e.g., an llm-evaluation harness), inspect those skills for their required permissions; (4) consider adding concrete CI/runbook steps if you plan automated regression testing so you know what systems will be touched. Otherwise it’s appropriate to use as a prompt-engineering checklist.Like a lobster shell, security has layers — review code before you run it.
latestvk979fjsdrazvdts99bxp3qgxd983pp32
License
MIT-0
Free to use, modify, and redistribute. No attribution required.