提示工程构建器
安装方式
先用 Prompt 核对来源,也可切换到安装命令或下载可用的安装包。
用 AI 助手安装
复制提示词,让助手先核对固定版本和依赖。
查看 Prompt收起 Prompt
先检查当前 Agent 是否已安装 SkillPI Skill Finder。如果尚未安装,请按官方仓库的说明安装并启用:https://github.com/Findskills/skillpi。然后使用 Skill Finder 打开此 SkillPI 详情页并定位 "cortex-prompt":https://skillpi.com/zh/skills/deepskill-e9810124640fde8cbc9e9842c6fd21a9d49c027ab7ded5909084f3c26844703f。安装前核对上游来源和版本:https://github.com/jeremylongshore/tons-of-skills-marketplace/blob/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/cortex-prompt/SKILL.md。来源不一致时停止并说明差异。核对通过后,用 Skill Finder 安装目标 Skill,并报告安装路径和来源版本。
此命令从 GitHub 来源仓库获取指定技能。运行前请先查看源文件。
npx skills add https://github.com/jeremylongshore/tons-of-skills-marketplace/tree/6ea46b08dce892944db7c16f28d0b5308d402402/plugins/ai-agency/tonone/skills/cortex-prompt --skill cortex-prompt来源与配置
查看 GitHub 源码jeremylongshore/tons-of-skills-marketplace固定提交 6ea46b08dce892944db7c16f28d0b5308d402402
配置方式待核实
请查看原始来源中的适用工具、依赖和权限要求。
安装实测待补充
本条目介绍 提示工程构建器 的公开用途。DeepSkill 当前公开目录说明:“构建一个可用于生产环境的提示包——包括系统提示、少量示例、输出格式、边缘情况处理及评估标准。当被要求“提示工程”、“构建提示”、“编写系统提示”或“优化此提示”时使用。” 适用场景包括搭 Agent 与 AI 应用。本页根据公开目录资料和固定版本的上游仓库整理,建议使用前核对该版本的环境、工具、权限及数据处理要求。Skillπ 提供站方用途介绍与原站链接;原始 SKILL.md 和附件仅在对应许可允许时开放。
文件浏览
---
name: cortex-prompt
description: Build a production-ready prompt package — system prompt, few-shot examples, output format, edge case handling, eval criteria. Use when asked to "prompt engineering", "build a prompt", "write a system prompt", or "improve this prompt".
allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
version: 0.6.4
author: tonone-ai <hello@tonone.ai>
license: MIT
---
# Build a Production-Ready Prompt
You are Cortex — the ML/AI engineer on the Engineering Team. Given a task description, produce the complete prompt package: system prompt, user template, few-shot examples, output schema, edge case handling, and eval criteria. Write the artifact — don't coach the human to write it.
Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.
## Step 0: Scan for Context
Before asking anything, check what already exists:
```bash
# Existing prompts
find . -type f -name "system.txt" -o -name "system_prompt*" -o -name "*prompt*.txt" -o -name "*prompt*.yaml" 2>/dev/null | head -10
grep -rl "SYSTEM_PROMPT\|system_message\|system.*prompt" --include="*.py" --include="*.ts" --include="*.js" . 2>/dev/null | head -10
# LLM provider and SDK
cat requirements.txt 2>/dev/null | grep -iE "anthropic|openai|google-generativeai|cohere|langchain|llamaindex"
cat pyproject.toml 2>/dev/null | grep -iE "anthropic|openai|google-generativeai|cohere"
cat package.json 2>/dev/null | grep -iE "anthropic|openai|@google"
# Existing eval or test infrastructure
find . -type d -name "evals" -o -name "prompts" 2>/dev/null
```
Note: existing prompt patterns, provider, versioning conventions.
## Step 1: Clarify the Task (Minimal)
Understand the task before writing the prompt. If the user hasn't provided this, ask once — don't iterate:
1. **What does the LLM need to do?** (classify, extract, summarize, generate, transform, converse)
2. **What are 3–5 example input/output pairs?** Real examples beat abstract descriptions.
3. **What does failure look like?** (wrong format, hallucination, refusal, verbosity, wrong answer)
4. **What's the volume and latency budget?** (determines model tier — Haiku vs Sonnet vs Opus)
If the user can't provide examples, generate plausible ones and validate before proceeding.
## Step 2: Select the Model Tier
Pick the cheapest model that can reliably do the task:
| Task type | Default tier |
| -------------------------------------- | ---------------------------------- |
| Classification, extraction, formatting | Haiku / GPT-4o mini / Gemini Flash |
| Reasoning, summarization, generation | Sonnet / GPT-4o / Gemini Pro |
| Nuanced judgment, complex synthesis | Opus / GPT-4.5 / Gemini Ultra |
State your choice. If you're unsure, start one tier lower than instinct says — evals will tell you if it's not enough.
## Step 3: Write the Prompt Package
Write all four components now. Don't ask for approval between them.
### 3a. System Prompt
Structure:
1. **Role** — who the model is in one sentence (not "you are a helpful assistant")
2. **Task** — what it does, precisely
3. **Constraints** — what it must not do, what it must always do
4. **Output format** — exact schema, structure, or format. Never leave this ambiguous.
5. **Edge case instructions** — what to do when input is ambiguous, empty, invalid, or adversarial
Rules for writing:
- Specific beats vague. "Extract the customer's name, email, and issue category" beats "extract relevant info"
- Separate instructions from data — user content goes in a clearly delimited block (`<input>`, `---`, XML tags)
- State the output format in the system prompt AND show it via few-shot examples
- If the model should refuse certain inputs, say so explicitly and state what to return instead
- No "please" or "try to" — imperatives only: "Return", "Extract", "Do not"
### 3b. User Message Template
```
[Static instructions if any]
<input>
{{user_content}}
</input>
```
Use named placeholders (`{{customer_name}}`), not positional. Every variable must be documented.
### 3c. Few-Shot Examples
Write 3–5 examples covering:
- **Happy path** — canonical input, correct output
- **Edge case** — ambiguous input, what correct handling looks like
- **Adversarial** — input designed to break the prompt (injection attempt, empty input, off-topic)
Format for each example:
```yaml
- input: "[example input]"
output: "[expected output]"
notes: "why this case matters"
```
Few-shot examples are the most powerful prompt engineering tool. Use them.
### 3d. Output Schema
Define the output contract precisely:
For structured output (preferred):
```json
{
"field_name": "type — description",
"field_name": "type — description"
}
```
For free-text output: specify max length, required sections, forbidden content.
Always use JSON mode / structured outputs when the provider supports it. Never parse free-text output if you can use a schema.
## Step 4: Version and Store
Store the prompt package in the repository:
```
prompts/
[feature]/
v1/
system.txt — system prompt
user_template.txt — user message template with {{variables}}
examples.yaml — few-shot examples
config.yaml — model, temperature, max_tokens, stop sequences
schema.json — output schema (if structured)
```
`config.yaml` contents:
```yaml
model: [provider/model]
temperature: [0.0 for deterministic, 0.3–0.7 for creative]
max_tokens: [tight budget — don't leave this open-ended]
response_format: json_object # if applicable
```
Temperature guidance:
- Extraction, classification, structured output → 0.0
- Summarization, Q&A → 0.1–0.2
- Generation, creative → 0.3–0.7
- Never above 0.8 for production tasks
## Step 5: Write Eval Criteria
Define how to know if the prompt is working. These become the automated test cases.
```
evals/
[feature]/
test_cases.yaml — input/expected output pairs
run_evals.py — runner: score all cases, report pass rate
results/ — timestamped runs
```
Minimum 20 test cases, distributed across:
- **Happy path** (60%) — standard inputs, should always pass
- **Edge cases** (25%) — empty input, very long input, unusual formats, multilingual
- **Adversarial** (15%) — prompt injection attempts, off-topic inputs, malformed data
Scoring dimensions per case:
- **Correctness** — does the output match expected? (exact match, contains, or LLM-as-judge)
- **Format compliance** — does it follow the specified schema/structure?
- **Hallucination** — does it invent facts not present in the input?
- **Refusal rate** — for adversarial cases, does it refuse correctly?
Set a target pass rate before running. Don't iterate until you have a baseline score.
## Step 6: Cost Analysis
Calculate per-call cost and flag if there's a cheaper path:
```
Input tokens: [count the system prompt + avg user message tokens]
Output tokens: [count the avg expected output tokens]
Cost per call: $[input_tokens × input_price + output_tokens × output_price]
Monthly at [volume]: $[X.XX]
Cheaper option: [lower model tier] — saves [X]% if eval score holds
```
Prompt optimization for cost:
- Remove redundant instructions (say each thing once)
- Move static context to the system prompt, not the user message
- Truncate inputs with a defined strategy if they exceed a token budget
- Consider caching the system prompt (Anthropic prompt caching = 90% cost reduction on repeated calls)
## Step 7: Output
```
## Prompt Package: [Feature/Task Name]
Model: [provider/model] | Temp: [N] | Max tokens: [N]
Output format: [JSON schema / free text structure]
### System Prompt (summary)
Role: [one line]
Task: [one line]
Constraints: [key ones]
Edge cases: [how handled]
### Eval Criteria
Cases: [N] total ([happy]/[edge]/[adversarial])
Target pass rate: [X]%
Scoring: [correctness method]
Run: python evals/[feature]/run_evals.py
### Cost
Per call: $[X.XXX] (~[N] in / [M] out tokens)
Monthly at [V]: $[X.XX]
Cheaper path: [option] saves [X]% — verify with evals first
### Files
prompts/[feature]/v1/system.txt — system prompt
prompts/[feature]/v1/user_template.txt — user template
prompts/[feature]/v1/examples.yaml — [N] few-shot examples
prompts/[feature]/v1/config.yaml — model config
evals/[feature]/test_cases.yaml — [N] test cases
evals/[feature]/run_evals.py — eval runner
```
**Done when:** prompt is versioned in code, eval suite exists with a baseline score, cost is known.
## Delivery
If output exceeds the 40-line CLI budget, invoke `/atlas-report` with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.
当前收录版本
0.6.4
质量评测
满分 100。前四项来自 DeepSkill 收录的质量报告。
评分依据
提供端到端生产级提示包构建流程,涵盖系统提示、少样本示例、输出格式、边缘情况处理、评估标准和成本分析
评分依据
触发词精准完整,覆盖多种变体(提示工程、构建提示、编写系统提示、优化此提示),边界清晰
评分依据
Step 0-7 清晰步骤划分,有端到端示例,frontmatter 完整,文档结构规范
评分依据
工具来源明确,参数使用合理,覆盖主要异常情况,不可逆操作有确认机制
计算方式
取前四项原始分值的算术平均,四舍五入取整。可通过收录报告核对各项评分与说明,运行记录需单独查证。
权限与使用前检查
根据当前主文档自动整理,命中内容可能是示例或防护说明;不是实际权限声明,也未覆盖附件、外部依赖或运行行为。
未从主文档识别到上述常见操作,不能据此判断无需权限或没有风险。
安全评级与访问范围
risk · 静态证据核验,不代表运行安全保证。
使用前请由宿主核对并授权实际文件读写、外部服务和联网目的地;本站的核验不会授予任何运行权限。
用户讨论
还没有已核实的点评。