Menu

Individual skill

prompt-master

0upvotes

Prompt-writing guidance: task contracts, examples, structure, chaining, structured output, agent autonomy, tool descriptions, prompt-injection boundaries, and evaluation, with a prompt-reviewer stage. Use whenever an LLM prompt, system prompt, subagent instruction, or tool description is written, improved, or reviewed, including prompts embedded in application or bot code. Skill files use skill-master.

skills/prompt-master/SKILL.md

Read pinned source

Source commit ca44595f459eb84086cec8ed04d47f57bab945f3

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 7, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
303
Repository last updated
Oct 21, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Prompt Master

Treat a prompt as a clear task contract. Add information that changes the result; do not add a
technique merely because it is common in prompt-engineering guides.

## Prompt Essentials

A prompt should communicate the applicable parts of:

- the task and required result;
- context the model cannot infer but needs to perform the task correctly;
- real constraints and the reasons behind non-obvious requirements;
- criteria that distinguish an acceptable result;
- the response format when it matters to the user or a downstream system.
Back to top