Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Prompting

ASecurity

Guide for writing effective system prompts for LLM agents. Use when creating or editing system prompts for applications, agent configurations, or development tools.

896 stars
0 votes
0 copies
1 views
Added 9/19/2026
ai-agentsapi

Works with

api

Security Analysis

A100/100

Pro scans all 5 files and shows the line behind each finding

Scanned 9/19/2026

$npx -y skills add cashew-labs/libretto --skill prompting --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Prompting?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Prompting
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/cashew-labs-prompting/badge)](https://www.skillsdirectory.com/skills/cashew-labs-prompting)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: prompting
description: |
  Guide for writing effective system prompts for LLM agents. Use when creating or editing system prompts for applications, agent configurations, or development tools.
---

# Prompting

## Philosophy

LLMs are intelligent by default. System prompts set direction and impose constraints, not explain reasoning.

Start minimal. Observe failures. Add targeted fixes. Every instruction must justify its token cost by solving a real problem.

Do not explain existing capabilities, list obvious practices, add preventive instructions, or repeat information.

## Structure

Use markdown sections and paragraphs. Each section describes one behavior or constraint.

State what to do or avoid. Explain why if non-obvious. Show correct behavior with examples.

### Formatting

Headings up to level 3. Plain paragraphs. No bold, italics, or emojis. Code blocks for commands. Lists only for distinct enumerable items.

## Examples

Wrap examples in `<example>` tags with user/assistant prefixes. One pair per tag.

```
<example>
user: What's the capital of France?
assistant: Paris
</example>
```

Use brackets for tool actions instead of showing invocations:

```
<example>
user: Find all TODO comments
assistant: [searches codebase]
Found 3 TODOs: ...
</example>
```

## Include

Behaviors the model gets wrong by default. Domain constraints. Output format requirements. Safety boundaries. Tool integrations.

## Omit

Reasoning instructions. Problem-solving approaches. Common sense behaviors. Ethical guidelines. Capability descriptions.

## Iteration

Start minimal. Test with real inputs. Identify failures. Add targeted fixes. Remove unnecessary instructions.

Track which instructions prevent which failures. If you cannot identify the specific problem an instruction solves, remove it.

## Model-Specific Guidance

Consult references/ for model-specific patterns:

- references/claude.md - XML structure, countering sycophancy, trigger words, parallel execution
- references/gpt.md - Contradiction sensitivity, role hierarchy, verbosity control, metaprompting
- references/gemini.md - Conciseness, tool explanations, library checks, context placement
- references/codex.md - OpenAI Codex models, tool implementations, autonomy patterns, compaction

Attribution

cashew-labscashew-labs
View sourceSee grades on GitHubMore from cashew-labs →
SSkills Directory ProSkills Directory

Get any skill into Claude in one click.

Download any skill as a ZIP for Claude.ai, Claude Desktop, or .claude/skills. $9/mo.

See Pro

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills Directory ProSkills Directory

Get any skill into Claude in one click.

Download any skill as a ZIP for Claude.ai, Claude Desktop, or .claude/skills. $9/mo.

See Pro

Related Skills

Caveman

Ultra-compressed communication mode that cuts output tokens while keeping technical accuracy. Levels: lite, full, ultra and the wenyan variants. Use for /caveman, "caveman mode", "talk like caveman", "be brief" or "less tokens".

1074701 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

696561 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3351 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

691 votes
View all in ai-agents →