Skip to content
Back to skills

Prompt Engineering

ASecurity

Comprehensive prompt engineering framework for designing, optimizing, and iterating LLM prompts. Use when creating prompts, optimizing existing prompts, or improving AI instructions.

  • 30 stars
  • 0 votes
  • 3 copies
  • 8 views
  • Added June 11, 2026
development

Security analysis

A100/100

Scanned June 11, 2026

npx -y skills add sabahattink/antigravity-fullstack-hq --skill prompt-engineering --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Prompt Engineering?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Prompt Engineering
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/sabahattink-prompt-engineering/badge)](https://www.skillsdirectory.com/skills/sabahattink-prompt-engineering)

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

Download with Pro
SKILL.md
---
name: prompt-engineering
description: Comprehensive prompt engineering framework for designing, optimizing, and iterating LLM prompts. Use when creating prompts, optimizing existing prompts, or improving AI instructions.
---

# Prompt Engineering

## Workflow

```
User Request
|
+-- "Create a prompt" --> EXPLORATION PHASE
+-- "Optimize this prompt" --> OPTIMIZATION PHASE
+-- "Fix this issue" --> ANALYSIS PHASE
```

## Phase 1: Exploration

Before creating any prompt, understand:

- What task will this prompt accomplish?
- Who will use it?
- What does success look like?
- What are the constraints?

## Phase 2: Analysis

### Task Classification

| Dimension | Options |
|-----------|---------|
| Complexity | Simple vs multi-step |
| Output | Creative vs analytical vs structured |
| Stakes | High vs experimental |

### Strategy Selection

| Task Type | Approach |
|-----------|----------|
| Simple | Direct instructions |
| Complex | Chain-of-thought |
| Creative | Role setting |
| Structured | Format specs + examples |

## Phase 3: Implementation

### Version 1 - Minimal
- Core instructions only
- Test basic functionality

### Version 2 - Enhanced
- Add examples
- Clarify ambiguities
- Add constraints

### Version 3+ - Optimized
- Refine wording
- Remove redundancy

## Key Techniques

### Role Setting

```
As an experienced code reviewer, analyze...
```

### Chain-of-Thought

```
Think step-by-step:
1. First, identify...
2. Then, analyze...
3. Finally, conclude...
```

### Few-Shot Learning

```
Example 1:
Input: "Great product"
Output: { "sentiment": "positive" }

Now analyze: "It was okay"
```

### Explicit Constraints

```
- Limit to 3 paragraphs
- Focus on technical aspects only
- Do not include pricing
```

## Prompt Template

```markdown
## Context
[Background information]

## Role (Optional)
You are a [ROLE] with expertise in [DOMAIN].

## Task
[Clear instruction]

## Constraints
- Constraint 1
- Constraint 2

## Output Format
[Format specification]

## Examples (Optional)
[Input/Output examples]
```

## Common Mistakes

| Mistake | Fix |
|---------|-----|
| Vague instructions | Be specific |
| No examples | Add 1-2 examples |
| Too many rules | Simplify |
| No format spec | Define output structure |

Attribution

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

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.