[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72ZJ9RZ2F1EBKTPC3QC3KYQ":3,"skill-same:01M72ZJ9RZ2F1EBKTPC3QC3KYQ":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":13,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M72ZJ9RZ2F1EBKTPC3QC3KYQ","prompt-engineer",null,"Writes, refactors, and evaluates prompts for LLMs — generating optimized prompt templates, structured output schemas, evaluation rubrics, and test suites. Use when designing prompts for new LLM applications, refactoring existing prompts for better accuracy or token efficiency, implementing chain-of-thought or few-shot learning, creating system prompts with personas and guardrails, building JSON\u002Ffunction-calling schemas, or developing prompt evaluation frameworks to measure and improve model performance.","andrewthomastaylor\u002FSkills","andrewthomastaylor","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F249856925?v=4","01M72Z00NZWQPWA1TVXZPKXXWJ","01M72Z00PJ210Z6DAD1N93P2HG",0,"MIT","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fprompt-engineer\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: prompt-engineer\ndescription: Writes, refactors, and evaluates prompts for LLMs — generating optimized prompt templates, structured output schemas, evaluation rubrics, and test suites. Use when designing prompts for new LLM applications, refactoring existing prompts for better accuracy or token efficiency, implementing chain-of-thought or few-shot learning, creating system prompts with personas and guardrails, building JSON\u002Ffunction-calling schemas, or developing prompt evaluation frameworks to measure and improve model performance.\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.2.0\"\n  domain: data-ml\n  triggers: prompt engineering, prompt optimization, chain-of-thought, few-shot learning, prompt testing, LLM prompts, prompt evaluation, system prompts, structured outputs, prompt design, context management, lost-in-the-middle, context degradation, token optimization, attention budget\n  role: expert\n  scope: design\n  output-format: document\n  related-skills: test-master, rag-architect, debugging-wizard\n---\n\n# Prompt Engineer\n\nExpert prompt engineer specializing in designing, optimizing, and evaluating prompts that maximize LLM performance across diverse use cases.\n\n## When to Use This Skill\n\n- Designing prompts for new LLM applications\n- Optimizing existing prompts for better accuracy or efficiency\n- Implementing chain-of-thought or few-shot learning\n- Creating system prompts with personas and guardrails\n- Building structured output schemas (JSON mode, function calling)\n- Developing prompt evaluation and testing frameworks\n- Debugging inconsistent or poor-quality LLM outputs\n- Migrating prompts between different models or providers\n\n## Core Workflow\n\n1. **Understand requirements** — Define task, success criteria, constraints, and edge cases\n2. **Design initial prompt** — Choose pattern (zero-shot, few-shot, CoT), write clear instructions\n3. **Test and evaluate** — Run diverse test cases, measure quality metrics\n   - **Validation checkpoint:** If accuracy \u003C 80% on the test set, identify failure patterns before iterating (e.g., ambiguous instructions, missing examples, edge case gaps)\n4. **Iterate and optimize** — Make one change at a time; refine based on failures, reduce tokens, improve reliability\n5. **Document and deploy** — Version prompts, document behavior, monitor production\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Prompt Patterns | `references\u002Fprompt-patterns.md` | Zero-shot, few-shot, chain-of-thought, ReAct |\n| Optimization | `references\u002Fprompt-optimization.md` | Iterative refinement, A\u002FB testing, token reduction |\n| Evaluation | `references\u002Fevaluation-frameworks.md` | Metrics, test suites, automated evaluation |\n| Structured Outputs | `references\u002Fstructured-outputs.md` | JSON mode, function calling, schema design |\n| System Prompts | `references\u002Fsystem-prompts.md` | Persona design, guardrails, injection defense |\n| Context Management | `references\u002Fcontext-management.md` | Attention budget, degradation patterns, context optimization |\n\n## Prompt Examples\n\n### Zero-shot vs. Few-shot\n\n**Zero-shot (baseline):**\n```\nClassify the sentiment of the following review as Positive, Negative, or Neutral.\n\nReview: {{review}}\nSentiment:\n```\n\n**Few-shot (improved reliability):**\n```\nClassify the sentiment of the following review as Positive, Negative, or Neutral.\n\nReview: \"The battery life is incredible, lasts all day.\"\nSentiment: Positive\n\nReview: \"Stopped working after two weeks. Very disappointed.\"\nSentiment: Negative\n\nReview: \"It arrived on time and matches the description.\"\nSentiment: Neutral\n\nReview: {{review}}\nSentiment:\n```\n\n### Before\u002FAfter Optimization\n\n**Before (vague, inconsistent outputs):**\n```\nSummarize this document.\n\n{{document}}\n```\n\n**After (structured, token-efficient):**\n```\nSummarize the document below in exactly 3 bullet points. Each bullet must be one sentence and start with an action verb. Do not include opinions or information not present in the document.\n\nDocument:\n{{document}}\n\nSummary:\n```\n\n## Constraints\n\n### MUST DO\n- Test prompts with diverse, realistic inputs including edge cases\n- Measure performance with quantitative metrics (accuracy, consistency)\n- Version prompts and track changes systematically\n- Document expected behavior and known limitations\n- Use few-shot examples that match target distribution\n- Validate structured outputs against schemas\n- Consider token costs and latency in design\n- Test across model versions before production deployment\n\n### MUST NOT DO\n- Deploy prompts without systematic evaluation on test cases\n- Use few-shot examples that contradict instructions\n- Ignore model-specific capabilities and limitations\n- Skip edge case testing (empty inputs, unusual formats)\n- Make multiple changes simultaneously when debugging\n- Hardcode sensitive data in prompts or examples\n- Assume prompts transfer perfectly between models\n- Neglect monitoring for prompt degradation in production\n\n## Output Templates\n\nWhen delivering prompt work, provide:\n1. Final prompt with clear sections (role, task, constraints, format)\n2. Test cases and evaluation results\n3. Usage instructions (temperature, max tokens, model version)\n4. Performance metrics and comparison with baselines\n5. Known limitations and edge cases\n\n## Coverage Note\n\nReference files cover major prompting techniques (zero-shot, few-shot, CoT, ReAct, tree-of-thoughts), structured output patterns (JSON mode, function calling), context management (attention budgets, degradation mitigation, optimization), and model-specific guidance for GPT-4, Claude, and Gemini families. Consult the relevant reference before designing for a specific model or pattern.\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fdata-ml\u002Fprompt-engineer\u002F)\n","# Prompt Engineer\n\nExpert prompt engineer specializing in designing, optimizing, and evaluating prompts that maximize LLM performance across diverse use cases.\n\n## When to Use This Skill\n\n- Designing prompts for new LLM applications\n- Optimizing existing prompts for better accuracy or efficiency\n- Implementing chain-of-thought or few-shot learning\n- Creating system prompts with personas and guardrails\n- Building structured output schemas (JSON mode, function calling)\n- Developing prompt evaluation and testing frameworks\n- Debugging inconsistent or poor-quality LLM outputs\n- Migrating prompts between different models or providers\n\n## Core Workflow\n\n1. **Understand requirements** — Define task, success criteria, constraints, and edge cases\n2. **Design initial prompt** — Choose pattern (zero-shot, few-shot, CoT), write clear instructions\n3. **Test and evaluate** — Run diverse test cases, measure quality metrics\n   - **Validation checkpoint:** If accuracy \u003C 80% on the test set, identify failure patterns before iterating (e.g., ambiguous instructions, missing examples, edge case gaps)\n4. **Iterate and optimize** — Make one change at a time; refine based on failures, reduce tokens, improve reliability\n5. **Document and deploy** — Version prompts, document behavior, monitor production\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Prompt Patterns | `references\u002Fprompt-patterns.md` | Zero-shot, few-shot, chain-of-thought, ReAct |\n| Optimization | `references\u002Fprompt-optimization.md` | Iterative refinement, A\u002FB testing, token reduction |\n| Evaluation | `references\u002Fevaluation-frameworks.md` | Metrics, test suites, automated evaluation |\n| Structured Outputs | `references\u002Fstructured-outputs.md` | JSON mode, function calling, schema design |\n| System Prompts | `references\u002Fsystem-prompts.md` | Persona design, guardrails, injection defense |\n| Context Management | `references\u002Fcontext-management.md` | Attention budget, degradation patterns, context optimization |\n\n## Prompt Examples\n\n### Zero-shot vs. Few-shot\n\n**Zero-shot (baseline):**\n```\nClassify the sentiment of the following review as Positive, Negative, or Neutral.\n\nReview: {{review}}\nSentiment:\n```\n\n**Few-shot (improved reliability):**\n```\nClassify the sentiment of the following review as Positive, Negative, or Neutral.\n\nReview: \"The battery life is incredible, lasts all day.\"\nSentiment: Positive\n\nReview: \"Stopped working after two weeks. Very disappointed.\"\nSentiment: Negative\n\nReview: \"It arrived on time and matches the description.\"\nSentiment: Neutral\n\nReview: {{review}}\nSentiment:\n```\n\n### Before\u002FAfter Optimization\n\n**Before (vague, inconsistent outputs):**\n```\nSummarize this document.\n\n{{document}}\n```\n\n**After (structured, token-efficient):**\n```\nSummarize the document below in exactly 3 bullet points. Each bullet must be one sentence and start with an action verb. Do not include opinions or information not present in the document.\n\nDocument:\n{{document}}\n\nSummary:\n```\n\n## Constraints\n\n### MUST DO\n- Test prompts with diverse, realistic inputs including edge cases\n- Measure performance with quantitative metrics (accuracy, consistency)\n- Version prompts and track changes systematically\n- Document expected behavior and known limitations\n- Use few-shot examples that match target distribution\n- Validate structured outputs against schemas\n- Consider token costs and latency in design\n- Test across model versions before production deployment\n\n### MUST NOT DO\n- Deploy prompts without systematic evaluation on test cases\n- Use few-shot examples that contradict instructions\n- Ignore model-specific capabilities and limitations\n- Skip edge case testing (empty inputs, unusual formats)\n- Make multiple changes simultaneously when debugging\n- Hardcode sensitive data in prompts or examples\n- Assume prompts transfer perfectly between models\n- Neglect monitoring for prompt degradation in production\n\n## Output Templates\n\nWhen delivering prompt work, provide:\n1. Final prompt with clear sections (role, task, constraints, format)\n2. Test cases and evaluation results\n3. Usage instructions (temperature, max tokens, model version)\n4. Performance metrics and comparison with baselines\n5. Known limitations and edge cases\n\n## Coverage Note\n\nReference files cover major prompting techniques (zero-shot, few-shot, CoT, ReAct, tree-of-thoughts), structured output patterns (JSON mode, function calling), context management (attention budgets, degradation mitigation, optimization), and model-specific guidance for GPT-4, Claude, and Gemini families. Consult the relevant reference before designing for a specific model or pattern.\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fdata-ml\u002Fprompt-engineer\u002F)\n",{"name":5,"license":14,"metadata":23,"description":7},{"role":24,"scope":25,"author":26,"domain":27,"version":28,"triggers":29,"output-format":30,"related-skills":31},"expert","design","https:\u002F\u002Fgithub.com\u002FJeffallan","data-ml","1.2.0","prompt engineering, prompt optimization, chain-of-thought, few-shot learning, prompt testing, LLM prompts, prompt evaluation, system prompts, structured outputs, prompt design, context management, lost-in-the-middle, context degradation, token optimization, attention budget","document","test-master, rag-architect, debugging-wizard","main","cb7b4065bacb4b06224de86d509ccef568f68b79","claude-skills\u002Fskills\u002Fprompt-engineer","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor","2026-05-29 06:53:07",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add andrewthomastaylor\u002FSkills --skill prompt-engineer",{"tool":44,"command":45},"bunx","bunx skills add andrewthomastaylor\u002FSkills --skill prompt-engineer",{"tool":47,"command":48},"pnpm","pnpm dlx skills add andrewthomastaylor\u002FSkills --skill prompt-engineer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fprompt-engineer\u002FSKILL.md",true,[52,58,62,66,70,74],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fcontext-management.md","REFERENCE","参考文档",7570,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fprompt-engineer\u002Freferences\u002Fcontext-management.md",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fevaluation-frameworks.md",23737,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fprompt-engineer\u002Freferences\u002Fevaluation-frameworks.md",{"path":63,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fprompt-optimization.md",17619,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fprompt-engineer\u002Freferences\u002Fprompt-optimization.md",{"path":67,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fprompt-patterns.md",16180,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fprompt-engineer\u002Freferences\u002Fprompt-patterns.md",{"path":71,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fstructured-outputs.md",19093,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fprompt-engineer\u002Freferences\u002Fstructured-outputs.md",{"path":75,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fsystem-prompts.md",18970,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Fprompt-engineer\u002Freferences\u002Fsystem-prompts.md",[79,88,96,103,110,117],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":83,"licenseFileUrl":84,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":18},"01M732GDQJ0CWHBAW4D7ENMA3N","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fskill-creator\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fskill-creator\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":92,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":18},"01M731QVEE2QCT389Z3X1JWFVQ","humanizer-zh","去除文本中的 AI 生成痕迹。适用于编辑或审阅文本，使其听起来更自然、更像人类书写。\n基于维基百科的\"AI 写作特征\"综合指南。检测并修复以下模式：夸大的象征意义、\n宣传性语言、以 -ing 结尾的肤浅分析、模糊的归因、破折号过度使用、三段式法则、\nAI 词汇、否定式排比、过多的连接性短语。","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fhumanizer-zh\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fhumanizer-zh\u002FSKILL.md",[],[],{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"publishedAt":18},"01M731AMWEC72GFFNFS55F0TTC","returns-reverse-logistics","Codified expertise for returns authorization, receipt and inspection, disposition decisions, refund processing, fraud detection, and warranty claims management. Informed by returns operations managers with 15+ years experience. Includes grading frameworks, disposition economics, fraud pattern recognition, and vendor recovery processes. Use when handling product returns, reverse logistics, refund decisions, return fraud detection, or warranty claims.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Freturns-reverse-logistics\u002FSKILL.md",[],[],{"skillNo":104,"name":105,"nameZh":6,"description":106,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":18},"01M7319BJFM3CBX39C85QWSMD1","quality-nonconformance","Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing. Informed by quality engineers with 15+ years experience across FDA, IATF 16949, and AS9100 environments. Includes NCR lifecycle management, CAPA systems, SPC interpretation, and audit methodology. Use when investigating non-conformances, performing root cause analysis, managing CAPAs, interpreting SPC data, or handling supplier quality issues.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Fquality-nonconformance\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":18},"01M7318DPHWK6CEVCVT7PHNKDZ","production-scheduling","Codified expertise for production scheduling, job sequencing, line balancing, changeover optimization, and bottleneck resolution in discrete and batch manufacturing. Informed by production schedulers with 15+ years experience. Includes TOC\u002Fdrum-buffer-rope, SMED, OEE analysis, disruption response frameworks, and ERP\u002FMES interaction patterns. Use when scheduling production, resolving bottlenecks, optimizing changeovers, responding to disruptions, or balancing manufacturing lines.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Fproduction-scheduling\u002FSKILL.md",[],[],{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":83,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":18},"01M7315ZE0J0AB6KTQAFGCYF5V","logistics-exception-management","Codified expertise for handling freight exceptions, shipment delays, damages, losses, and carrier disputes. Informed by logistics professionals with 15+ years operational experience. Includes escalation protocols, carrier-specific behaviors, claims procedures, and judgment frameworks. Use when handling shipping exceptions, freight claims, delivery issues, or carrier disputes.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Flogistics-exception-management\u002FSKILL.md",[],[]]