Token导航 LogoToken导航

Agent Skill · 研究检索

prompt-engineering(及时工程)

用于辅助提示词、系统指令、Agent 行为约束和工作流模板的整理。它适合让 Agent 规范任务边界、统一输出格式、拆分操作步骤或优化提示词可复用性。使用时需要保留真实业务约束,不要把示例当硬规则;涉及自动执行、外部工具或高风险操作时,应在提示词中明确确认步骤、权限边界和失败处理方式。

prompt-engineering 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 46,467。

总安装 776周安装 33GitHub Stars 10下载 272核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:prompt-engineering(及时工程)
来源仓库:https://github.com/oakoss/agent-skills
仓库路径:skills/prompt-engineering
安装命令:
npx skills add https://github.com/oakoss/agent-skills --skill prompt-engineering
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/oakoss/agent-skills --skill prompt-engineering

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于辅助提示词、系统指令、Agent 行为约束和工作流模板的整理。它适合让 Agent 规范任务边界、统一输出格式、拆分操作步骤或优化提示词可复用性。使用时需要保留真实业务约束,不要把示例当硬规则。涉及自动执行、外部工具或高风险操作时,应在提示词中明确确认步骤、权限边界和失败处理方式。

prompt-engineering 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/prompt-engineering

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/oakoss/agent-skills --skill prompt-engineering;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

prompt-engineering 怎么安装?

在终端执行 npx skills add https://github.com/oakoss/agent-skills --skill prompt-engineering。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

prompt-engineering 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

prompt-engineering 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

prompt-engineering 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

prompt-engineering 用的人多吗?

公开数据是累计安装 776 次,近一周安装 33 次,下载 272 次,GitHub 10 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

prompt-engineering 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
prompt-engineering

及时工程 · 本页

77610需要联网未明确通过

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

Prompt Engineering

Advanced prompt design for LLMs and autonomous agents. Covers reasoning patterns, template systems, optimization workflows, agentic orchestration, extended thinking, and tool use prompting.

When to use: Designing prompts that require structured reasoning, building agent loops, optimizing LLM output quality, creating reusable prompt templates, configuring extended thinking for complex tasks, or designing multimodal prompts with images and text.

When NOT to use: Simple factual queries, direct lookups, or creative writing that benefits from open-ended generation.

Key Principles

  1. Explicit over implicit -- Modern models (Claude 4.x, GPT-4.1) follow instructions literally. Be specific about desired output, format, and behavior rather than relying on the model to infer intent.
  2. Objective over instruction -- For reasoning models (OpenAI o-series, Claude with extended thinking), state the goal rather than prescribing step-by-step methods. These models plan natively.
  3. Structure signals intent -- Use XML tags, clear delimiters, and consistent formatting to communicate prompt structure. Models trained on structured prompts parse them more reliably than plain text.
  4. One good example beats many rules -- Few-shot examples with consistent formatting anchor model behavior more effectively than verbose instructions.
  5. Feedback loops are built-in -- Design prompts that ask the model to verify, critique, or score its own output before finalizing.
  6. Token economy matters -- Every extra token adds latency and cost. Compress context, remove filler, and front-load critical information.

Model-Specific Considerations

Claude 4.x models follow instructions with high precision. They take prompts literally and do exactly what is asked -- no more, no less. Use XML tags to structure prompt sections (<rules>, <context>, <output_format>). Frame instructions positively (describe what to do, not what to avoid). Provide context or motivation behind instructions so Claude can generalize. Extended thinking and interleaved thinking provide native reasoning capabilities.

OpenAI o-series models (o3, o4-mini) use internal reasoning tokens before responding. Use developer messages instead of system messages. Write detailed function descriptions as interface contracts. Do not add explicit reasoning prompts -- these models reason natively and additional planning prompts can hurt performance. Pass back persisted reasoning items for multi-turn conversations.

GPT-4.1 and standard models benefit from explicit step-by-step instructions, few-shot examples, and structured output schemas. These models do not have native reasoning loops, so CoT prompting and structured thinking protocols add measurable value.

Multimodal models (GPT-4o, Claude with vision, Gemini) accept images alongside text. Provide context about what each image represents, use clear action verbs, and crop images to relevant regions. Label multiple images explicitly and specify their relationship.

Quick Reference

PatternAPI / TechniqueKey Point
Zero-shot CoT"Let's think step by step" triggerElicits reasoning without examples
Few-shot CoTExplicit reasoning chain examplesOne good example beats many rules
Self-consistencyMultiple paths + majority voteHigher accuracy on complex tasks
Tree-of-ThoughtsGenerate 3+ strategies, eliminate weakestParallel exploration with pruning; high cost
ReAct loopThought-Action-Observation cycleAgent reasons and acts in unison
System promptRole + Expertise + Guidelines + FormatFoundation for all LLM behavior
Prompt templateModular composition with variable slotsReusable, validated, cacheable
A/B testingStatistical comparison of prompt variantsIsolate variables, measure significance
Extended thinkingBudget-controlled deep reasoning (Claude)Let model think before responding
Interleaved thinkingThink between tool calls (Claude 4)Reason after each tool result
Think toolNo-op tool for structured reasoning spaceGives agents a place to reason mid-turn
Reasoning modelsObjective-based prompting for o3/o4-miniLet the model plan its own reasoning
Structured thinkingUnderstanding-Analysis-Execution protocolForces verification before acting
XML structuringTags to delimit prompt sectionsModels parse structured prompts reliably
Multimodal promptingText + image context for vision modelsProvide spatial context and clear action verbs
Confidence scoringModel self-reports certainty per claimQuantifies reliability of output
Token optimizationCompress context, remove filler wordsReduce latency and cost

Common Mistakes

MistakeCorrect Pattern
Overloading a single prompt with too many instructionsUse hierarchical rules with clear priority ordering
Forcing rigid step-by-step on reasoning modelsUse objective-based prompts; reasoning models plan natively
Setting max output tokens too low for reasoning modelsAllocate sufficient tokens for internal chain-of-thought
Using static examples for complex tasksSelect examples dynamically via semantic similarity
Inconsistent formatting across few-shot examplesAll examples must follow identical input-output structure
Manually parsing unstructured LLM outputUse JSON mode or structured output schemas
Ignoring token budget allocationReserve tokens for system prompt, examples, input, and response
Skipping baseline measurement before optimizingEstablish metrics first, then change one variable at a time
Using CoT prompts on reasoning modelsRedundant; these models reason natively without explicit triggers
Telling models what NOT to do instead of what to doFrame instructions positively: describe the desired behavior
Passing thinking blocks back as user text (Claude)Pass thinking blocks unmodified in assistant message only
Over-prompting reasoning models to "plan more"Additional planning prompts can degrade reasoning model performance

Prompt Engineering Workflow

  1. Define the objective -- State what the prompt should achieve and how success is measured
  2. Choose the right pattern -- Match the task to CoT, ReAct, ToT, or simple prompting based on complexity
  3. Select the model tier -- Route to lightweight, standard, or reasoning models based on task difficulty
  4. Write the baseline prompt -- Start simple; use system prompt structure with XML tags for complex cases
  5. Add examples -- Include 1-3 few-shot examples with consistent formatting if the task requires them
  6. Test and measure -- Establish baseline metrics (accuracy, latency, token usage) on representative inputs
  7. Analyze failures -- Categorize errors (format, factual, logical, incomplete) and address the most impactful
  8. Iterate one variable -- Change one element at a time to isolate what improves performance
  9. Version and deploy -- Track prompt versions alongside performance data for rollback capability

Delegation

  • Explore prompt variants and compare model responses: Use Explore agent to test prompt strategies across different inputs
  • Build multi-step agentic workflows with tool use: Use Task agent to implement and validate ReAct loops and autonomous chains
  • Design hierarchical prompt architecture for complex systems: Use Plan agent to structure prompt systems with verification loops
If the expert-instruction skill is available, delegate system prompt design and agent persona crafting to it.

References

平台分布

Codex

37.95%
按下载量换算103

Claude

29.53%
按下载量换算80

Cursor

19.56%
按下载量换算53

Gemini CLI

10.85%
按下载量换算30

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills