# Design MCP Prompts for AI Workflows

MCP server authors need prompt templates that are clear, reusable, and easy to test. This skill provides practical rmcp patterns for arguments, context, examples, and conversation flows.

## Install

```bash
npx skillstore add emillindfors/mcp-prompts-guide
```

## Metadata

- Status: approved
- Slug: emillindfors-mcp-prompts-guide
- Skillstore revision: r1
- Version status: missing
- Tree hash: b7d1b5d3a9d89c07d4bcd5a3c656dda1084bb0774cb19fb9f71e257ad7e0a353
- Author: EmilLindfors
- GitHub username: EmilLindfors
- License: MIT
- Repository: https://github.com/EmilLindfors/claude-marketplace/tree/main/plugins/rust-mcp-server/skills/mcp-prompts-guide
- Ref: a06681402992ceae98ba04d54cfd4ab004862696
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: external\_commands
- Quality score: 77
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/emillindfors-mcp-prompts-guide
- Manifest: https://skillstore.pages.dev/api/skills/emillindfors-mcp-prompts-guide/manifest

## Capabilities

- Explains how MCP prompts expose reusable message templates to users.
- Shows Rust rmcp examples for listing prompts and returning prompt responses.
- Demonstrates required and optional prompt arguments with default values.
- Covers prompt patterns for code review, API design, learning, debugging, and refactoring.
- Includes examples for context-rich prompts, few-shot prompts, and prompt tests.

## Use Cases

- Build Prompt Templates: Create reusable prompts with clear names, descriptions, required arguments, and structured messages.
- Add Project Context: Design prompts that include documentation, examples, dependencies, and project guidelines before the user task.
- Test Prompt Behavior: Plan unit and integration tests that verify prompt listing, argument handling, and response structure.

## Prompt Templates

### Create a Basic Prompt

```
Help me create a basic MCP prompt named [prompt_name]. It should take [required_argument] and guide the assistant to [goal].
```

### Design Prompt Arguments

```
Review my prompt goal: [goal]. Suggest required arguments, optional arguments, defaults, and validation rules for an MCP prompt.
```

### Add Context Injection

```
Design an MCP prompt for [task] that injects [context_sources]. Include message structure, context sections, and safeguards for irrelevant context.
```

### Evaluate Prompt Quality

```
Audit this MCP prompt design for clarity, argument safety, context quality, test coverage, and user experience. Return concrete improvements.
```

## Limitations

- Provides guidance and examples, not a complete ready-to-run MCP server.
- Focuses on Rust rmcp patterns and may need adaptation for other SDKs.
- Does not include automated validation for prompt injection resistance.
- Example snippets use simplified error handling for teaching purposes.

## Best Practices

- Define clear prompt names, descriptions, and argument requirements before writing message content.
- Validate dynamic arguments before inserting them into prompt text or system messages.
- Test each prompt with valid inputs, missing inputs, and realistic user tasks.

## Anti Patterns

- Do not hide important behavior inside vague prompt descriptions.
- Do not insert untrusted arguments into high-authority messages without review.
- Do not ship prompts without tests for required arguments and response structure.

## Security Audit

- Audited at: 2026-07-06T15:04:57.965\+00:00
- Summary: All static findings are false positives caused by Markdown code fences around Rust examples in SKILL.md. The skill is instructional content about MCP prompt design, and I found no evidence of executable shell commands, prompt injection, data exfiltration, or malicious intent.

## Stats

- Views: 154
- Downloads: 10
- Favorites: 0
- Popularity score: 0