[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M730GKMVC209NVGWEP91MRKG":3,"skill-same:01M730GKMVC209NVGWEP91MRKG":78},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":29,"commitSha":30,"skillDirectory":31,"forksCount":14,"repositoryHtmlUrl":32,"repositoryHomepageUrl":6,"ownerHtmlUrl":33,"ownerBlogUrl":6,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M730GKMVC209NVGWEP91MRKG","prompt-engineer-toolkit",null,"Analyzes and rewrites prompts for better AI output, creates reusable prompt templates for marketing use cases (ad copy, email campaigns, social media), and structures end-to-end AI content workflows. Use when the user wants to improve prompts for AI-assisted marketing, build prompt templates, or optimize AI content workflows. Also use when the user mentions 'prompt engineering,' 'improve my prompts,' 'AI writing quality,' 'prompt templates,' or 'AI content workflow.'","ciciliaETH\u002Fclaude-skills","ciciliaETH","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F94572860?v=4","01M72Z3SEH31MEG7M94G85GE0V","cicilia_eth","01M72Z3SF42XENX7AMJVA7SCQX",0,"MIT","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fskills\u002Fprompt-engineer-toolkit\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: \"prompt-engineer-toolkit\"\ndescription: \"Analyzes and rewrites prompts for better AI output, creates reusable prompt templates for marketing use cases (ad copy, email campaigns, social media), and structures end-to-end AI content workflows. Use when the user wants to improve prompts for AI-assisted marketing, build prompt templates, or optimize AI content workflows. Also use when the user mentions 'prompt engineering,' 'improve my prompts,' 'AI writing quality,' 'prompt templates,' or 'AI content workflow.'\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-06\n---\n\n# Prompt Engineer Toolkit\n\n## Overview\n\nUse this skill to move prompts from ad-hoc drafts to production assets with repeatable testing, versioning, and regression safety. It emphasizes measurable quality over intuition. Apply it when launching a new LLM feature that needs reliable outputs, when prompt quality degrades after model or instruction changes, when multiple team members edit prompts and need history\u002Fdiffs, when you need evidence-based prompt choice for production rollout, or when you want consistent prompt governance across environments.\n\n## Core Capabilities\n\n- A\u002FB prompt evaluation against structured test cases\n- Quantitative scoring for adherence, relevance, and safety checks\n- Prompt version tracking with immutable history and changelog\n- Prompt diffs to review behavior-impacting edits\n- Reusable prompt templates and selection guidance\n- Regression-friendly workflows for model\u002Fprompt updates\n\n## Key Workflows\n\n### 1. Run Prompt A\u002FB Test\n\nPrepare JSON test cases and run:\n\n```bash\npython3 scripts\u002Fprompt_tester.py \\\n  --prompt-a-file prompts\u002Fa.txt \\\n  --prompt-b-file prompts\u002Fb.txt \\\n  --cases-file testcases.json \\\n  --runner-cmd 'my-llm-cli --prompt {prompt} --input {input}' \\\n  --format text\n```\n\nInput can also come from stdin\u002F`--input` JSON payload.\n\n### 2. Choose Winner With Evidence\n\nThe tester scores outputs per case and aggregates:\n\n- expected content coverage\n- forbidden content violations\n- regex\u002Fformat compliance\n- output length sanity\n\nUse the higher-scoring prompt as candidate baseline, then run regression suite.\n\n### 3. Version Prompts\n\n```bash\n# Add version\npython3 scripts\u002Fprompt_versioner.py add \\\n  --name support_classifier \\\n  --prompt-file prompts\u002Fsupport_v3.txt \\\n  --author alice\n\n# Diff versions\npython3 scripts\u002Fprompt_versioner.py diff --name support_classifier --from-version 2 --to-version 3\n\n# Changelog\npython3 scripts\u002Fprompt_versioner.py changelog --name support_classifier\n```\n\n### 4. Regression Loop\n\n1. Store baseline version.\n2. Propose prompt edits.\n3. Re-run A\u002FB test.\n4. Promote only if score and safety constraints improve.\n\n## Script Interfaces\n\n- `python3 scripts\u002Fprompt_tester.py --help`\n  - Reads prompts\u002Fcases from stdin or `--input`\n  - Optional external runner command\n  - Emits text or JSON metrics\n- `python3 scripts\u002Fprompt_versioner.py --help`\n  - Manages prompt history (`add`, `list`, `diff`, `changelog`)\n  - Stores metadata and content snapshots locally\n\n## Pitfalls, Best Practices & Review Checklist\n\n**Avoid these mistakes:**\n1. Picking prompts from single-case outputs — use a realistic, edge-case-rich test suite.\n2. Changing prompt and model simultaneously — always isolate variables.\n3. Missing `must_not_contain` (forbidden-content) checks in evaluation criteria.\n4. Editing prompts without version metadata, author, or change rationale.\n5. Skipping semantic diffs before deploying a new prompt version.\n6. Optimizing one benchmark while harming edge cases — track the full suite.\n7. Model swap without rerunning the baseline A\u002FB suite.\n\n**Before promoting any prompt, confirm:**\n- [ ] Task intent is explicit and unambiguous.\n- [ ] Output schema\u002Fformat is explicit.\n- [ ] Safety and exclusion constraints are explicit.\n- [ ] No contradictory instructions.\n- [ ] No unnecessary verbosity tokens.\n- [ ] A\u002FB score improves and violation count stays at zero.\n\n## References\n\n- [references\u002Fprompt-templates.md](references\u002Fprompt-templates.md)\n- [references\u002Ftechnique-guide.md](references\u002Ftechnique-guide.md)\n- [references\u002Fevaluation-rubric.md](references\u002Fevaluation-rubric.md)\n- [README.md](README.md)\n\n## Evaluation Design\n\nEach test case should define:\n\n- `input`: realistic production-like input\n- `expected_contains`: required markers\u002Fcontent\n- `forbidden_contains`: disallowed phrases or unsafe content\n- `expected_regex`: required structural patterns\n\nThis enables deterministic grading across prompt variants.\n\n## Versioning Policy\n\n- Use semantic prompt identifiers per feature (`support_classifier`, `ad_copy_shortform`).\n- Record author + change note for every revision.\n- Never overwrite historical versions.\n- Diff before promoting a new prompt to production.\n\n## Rollout Strategy\n\n1. Create baseline prompt version.\n2. Propose candidate prompt.\n3. Run A\u002FB suite against same cases.\n4. Promote only if winner improves average and keeps violation count at zero.\n5. Track post-release feedback and feed new failure cases back into test suite.\n","# Prompt Engineer Toolkit\n\n## Overview\n\nUse this skill to move prompts from ad-hoc drafts to production assets with repeatable testing, versioning, and regression safety. It emphasizes measurable quality over intuition. Apply it when launching a new LLM feature that needs reliable outputs, when prompt quality degrades after model or instruction changes, when multiple team members edit prompts and need history\u002Fdiffs, when you need evidence-based prompt choice for production rollout, or when you want consistent prompt governance across environments.\n\n## Core Capabilities\n\n- A\u002FB prompt evaluation against structured test cases\n- Quantitative scoring for adherence, relevance, and safety checks\n- Prompt version tracking with immutable history and changelog\n- Prompt diffs to review behavior-impacting edits\n- Reusable prompt templates and selection guidance\n- Regression-friendly workflows for model\u002Fprompt updates\n\n## Key Workflows\n\n### 1. Run Prompt A\u002FB Test\n\nPrepare JSON test cases and run:\n\n```bash\npython3 scripts\u002Fprompt_tester.py \\\n  --prompt-a-file prompts\u002Fa.txt \\\n  --prompt-b-file prompts\u002Fb.txt \\\n  --cases-file testcases.json \\\n  --runner-cmd 'my-llm-cli --prompt {prompt} --input {input}' \\\n  --format text\n```\n\nInput can also come from stdin\u002F`--input` JSON payload.\n\n### 2. Choose Winner With Evidence\n\nThe tester scores outputs per case and aggregates:\n\n- expected content coverage\n- forbidden content violations\n- regex\u002Fformat compliance\n- output length sanity\n\nUse the higher-scoring prompt as candidate baseline, then run regression suite.\n\n### 3. Version Prompts\n\n```bash\n# Add version\npython3 scripts\u002Fprompt_versioner.py add \\\n  --name support_classifier \\\n  --prompt-file prompts\u002Fsupport_v3.txt \\\n  --author alice\n\n# Diff versions\npython3 scripts\u002Fprompt_versioner.py diff --name support_classifier --from-version 2 --to-version 3\n\n# Changelog\npython3 scripts\u002Fprompt_versioner.py changelog --name support_classifier\n```\n\n### 4. Regression Loop\n\n1. Store baseline version.\n2. Propose prompt edits.\n3. Re-run A\u002FB test.\n4. Promote only if score and safety constraints improve.\n\n## Script Interfaces\n\n- `python3 scripts\u002Fprompt_tester.py --help`\n  - Reads prompts\u002Fcases from stdin or `--input`\n  - Optional external runner command\n  - Emits text or JSON metrics\n- `python3 scripts\u002Fprompt_versioner.py --help`\n  - Manages prompt history (`add`, `list`, `diff`, `changelog`)\n  - Stores metadata and content snapshots locally\n\n## Pitfalls, Best Practices & Review Checklist\n\n**Avoid these mistakes:**\n1. Picking prompts from single-case outputs — use a realistic, edge-case-rich test suite.\n2. Changing prompt and model simultaneously — always isolate variables.\n3. Missing `must_not_contain` (forbidden-content) checks in evaluation criteria.\n4. Editing prompts without version metadata, author, or change rationale.\n5. Skipping semantic diffs before deploying a new prompt version.\n6. Optimizing one benchmark while harming edge cases — track the full suite.\n7. Model swap without rerunning the baseline A\u002FB suite.\n\n**Before promoting any prompt, confirm:**\n- [ ] Task intent is explicit and unambiguous.\n- [ ] Output schema\u002Fformat is explicit.\n- [ ] Safety and exclusion constraints are explicit.\n- [ ] No contradictory instructions.\n- [ ] No unnecessary verbosity tokens.\n- [ ] A\u002FB score improves and violation count stays at zero.\n\n## References\n\n- [references\u002Fprompt-templates.md](references\u002Fprompt-templates.md)\n- [references\u002Ftechnique-guide.md](references\u002Ftechnique-guide.md)\n- [references\u002Fevaluation-rubric.md](references\u002Fevaluation-rubric.md)\n- [README.md](README.md)\n\n## Evaluation Design\n\nEach test case should define:\n\n- `input`: realistic production-like input\n- `expected_contains`: required markers\u002Fcontent\n- `forbidden_contains`: disallowed phrases or unsafe content\n- `expected_regex`: required structural patterns\n\nThis enables deterministic grading across prompt variants.\n\n## Versioning Policy\n\n- Use semantic prompt identifiers per feature (`support_classifier`, `ad_copy_shortform`).\n- Record author + change note for every revision.\n- Never overwrite historical versions.\n- Diff before promoting a new prompt to production.\n\n## Rollout Strategy\n\n1. Create baseline prompt version.\n2. Propose candidate prompt.\n3. Run A\u002FB suite against same cases.\n4. Promote only if winner improves average and keeps violation count at zero.\n5. Track post-release feedback and feed new failure cases back into test suite.\n",{"name":5,"license":15,"metadata":24,"description":7},{"author":25,"updated":26,"version":27,"category":28},"Alireza Rezvani",1772755200000,"1.0.0","marketing","main","04d625a73841ac3f69c0d6ab4a7308680faffe02","marketing-skill\u002Fskills\u002Fprompt-engineer-toolkit","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills","https:\u002F\u002Fgithub.com\u002FciciliaETH","web3 dev, blockchain enthusiast, token reviewer, all about telegram bot.","2026-05-17 05:17:16",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add ciciliaETH\u002Fclaude-skills --skill prompt-engineer-toolkit",{"tool":42,"command":43},"bunx","bunx skills add ciciliaETH\u002Fclaude-skills --skill prompt-engineer-toolkit",{"tool":45,"command":46},"pnpm","pnpm dlx skills add ciciliaETH\u002Fclaude-skills --skill prompt-engineer-toolkit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fskills\u002Fprompt-engineer-toolkit\u002FSKILL.md",true,[50,56,60,64,68,74],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"README.md","REFERENCE","参考文档",1244,"https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fskills\u002Fprompt-engineer-toolkit\u002FREADME.md",{"path":57,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":58,"sourceHtmlUrl":59},"references\u002Fevaluation-rubric.md",328,"https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fskills\u002Fprompt-engineer-toolkit\u002Freferences\u002Fevaluation-rubric.md",{"path":61,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":62,"sourceHtmlUrl":63},"references\u002Fprompt-templates.md",1532,"https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fskills\u002Fprompt-engineer-toolkit\u002Freferences\u002Fprompt-templates.md",{"path":65,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":66,"sourceHtmlUrl":67},"references\u002Ftechnique-guide.md",675,"https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fskills\u002Fprompt-engineer-toolkit\u002Freferences\u002Ftechnique-guide.md",{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"scripts\u002Fprompt_tester.py","SCRIPT","脚本",7793,"https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fskills\u002Fprompt-engineer-toolkit\u002Fscripts\u002Fprompt_tester.py",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"scripts\u002Fprompt_versioner.py",8111,"https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fmarketing-skill\u002Fskills\u002Fprompt-engineer-toolkit\u002Fscripts\u002Fprompt_versioner.py",[79,86,93,100,105,110],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M730RQEKV70CXBH2TQF045GT","ra-qm-skills","12 regulatory & QM agent skills and plugins for Claude Code, Codex, Gemini CLI, Cursor, OpenClaw. ISO 13485 QMS, MDR 2017\u002F745, FDA 510(k)\u002FPMA, ISO 27001 ISMS, GDPR\u002FDSGVO, risk management (ISO 14971), CAPA, document control, auditing. Python tools (stdlib-only).","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fra-qm-skills\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M730QTT31DKCCZC573H22GX6","iso42001-specialist","ISO\u002FIEC 42001:2023 AI Management System (AIMS) specialist for compliance teams running internal audits. Three decisions: (1) Where are the gaps against Clauses 4-10 and what do we close first? (2) What goes in the AI risk register and which Annex A controls treat each risk? (3) What's the 12-month internal audit plan that satisfies Clause 9.2? Use when preparing for certification, scoping internal audit cycles, or onboarding AI systems into an existing ISMS (27001) \u002F QMS (13485) program. NOT an executive AI strategy skill (see chief-ai-officer-advisor). NOT EU AI Act compliance (see compliance-team-eu-ai-act).","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Fiso42001-specialist\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M730Q40HCJJ97V6HGDF4FPS0","eu-ai-act-specialist","EU AI Act (Regulation (EU) 2024\u002F1689) operational compliance for compliance teams. Three Article-level decisions: (1) What's the risk tier of this AI system — prohibited (Art. 5), high-risk (Art. 6 + Annex III), limited-risk (Art. 50), or minimal-risk? (2) For high-risk systems, what's the Article 43 conformity assessment route (Module A internal control vs Module H full QMS + notified body) and what goes in the Annex IV technical documentation? (3) Per organizational role (provider \u002F deployer \u002F importer \u002F distributor \u002F authorized representative), what are the active obligations and deadlines? Use during AI system intake review, when planning conformity assessment, or when scoping deployer obligations. Cites Articles + Annexes for every output. NOT executive AI strategy (see chief-ai-officer-advisor). NOT a legal substitute.","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fskills\u002Feu-ai-act-specialist\u002FSKILL.md",[],[],{"skillNo":101,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":19},"01M730PQWQ9N9FWV52Y14A1NJT","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fcompliance-team-iso42001\u002Fskills\u002Fiso42001-specialist\u002FSKILL.md",[],[],{"skillNo":106,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":107,"categories":108,"keywords":109,"publishedAt":19},"01M730PFX71VE2Q2HFHNYRDKQX","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fra-qm-team\u002Fcompliance-team-eu-ai-act\u002Fskills\u002Feu-ai-act-specialist\u002FSKILL.md",[],[],{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":116,"publishedAt":19},"01M730NW4DAJ4JF9KRXMF35ADB","scrum-master","Advanced Scrum Master skill for data-driven agile team analysis and coaching. Use when the user asks about sprint planning, velocity tracking, retrospectives, standup facilitation, backlog grooming, story points, burndown charts, blocker resolution, or agile team health. Runs Python scripts to analyse sprint JSON exports from Jira or similar tools: velocity_analyzer.py for Monte Carlo sprint forecasting, sprint_health_scorer.py for multi-dimension health scoring, and retrospective_analyzer.py for action-item and theme tracking. Produces confidence-interval forecasts, health grade reports, and improvement-velocity trends for high-performing Scrum teams.","https:\u002F\u002Fgithub.com\u002FciciliaETH\u002Fclaude-skills\u002Fblob\u002Fmain\u002Fproject-management\u002Fskills\u002Fscrum-master\u002FSKILL.md",[],[]]