Prompt Engineering

v1.0.0

Advanced expert in prompt engineering, custom instructions design, and prompt optimization for AI agents

0· 251·0 current·0 all-time
byTyler Snyder@tysnyder
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
The name/description (prompt engineering expert) match the provided files (SKILL.md, README, BEST_PRACTICES, TECHNIQUES, EXAMPLES). There are no unrelated requirements (no cloud credentials, no platform binaries) that would be incoherent for this kind of skill.
Instruction Scope
Runtime instructions are documentation and examples for crafting and evaluating prompts. They do not instruct the agent to read system files, exfiltrate data, call arbitrary external endpoints, or access credentials. Integration notes mention using Agent SDK/Files API for legitimate workflows but the skill does not include steps that would automatically transmit data.
Install Mechanism
There is no install spec and no code files to execute — this is instruction-only documentation, which is the lowest-risk install profile.
Credentials
The skill requests no environment variables, credentials, or config paths. Sample snippets reference the Anthropic client but don't require the skill to store or access secrets itself.
Persistence & Privilege
The skill does not request always:true and makes no claims about modifying other skills or system-wide settings. It is user-invocable and does not request elevated or persistent privileges.
Assessment
This appears to be a coherent, documentation-only prompt-engineering skill and is safe from a privilege/credential perspective. Before installing: (1) skim the README/SKILL.md to confirm it matches your expectations, (2) do not paste secrets, API keys, or private documents into prompts when testing, and (3) if you integrate it with your Agent SDK or Files API, supply credentials only to the SDK/environment — the skill itself does not need them. If you see later versions requesting env vars, downloads, or commands that read system files or contact unknown URLs, treat that as a red flag and re-evaluate.

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

latestvk97affbpxczy1kk1p8rshqevns82amfm

License

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

Comments