[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75DP1E6V5S1ZC1RM2VC3R5N":3,"skill-same:01M75DP1E6V5S1ZC1RM2VC3R5N":77},{"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":28,"commitSha":29,"skillDirectory":30,"forksCount":13,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":33,"updatedAt":34,"install":35,"resources":48},"01M75DP1E6V5S1ZC1RM2VC3R5N","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.'","AdmiralGallade\u002Fharness-repository","AdmiralGallade","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F59243621?v=4","01M759AG0891RDPWNGJBX1Y2TG","01M759AG10MS924J53ZWJ60AEC",0,"MIT","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fmarketing-skill\u002Fskills\u002Fprompt-engineer-toolkit\u002FSKILL.md",[],[],"2026-11-12 13:55:43",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":14,"metadata":23,"description":7},{"author":24,"updated":25,"version":26,"category":27},"Alireza Rezvani",1772755200000,"1.0.0","marketing","main","f3af6b6781621109871cca9e2989364afc509f3d","harnesses\u002Fclaude-skills\u002Fmarketing-skill\u002Fskills\u002Fprompt-engineer-toolkit","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository","https:\u002F\u002Fgithub.com\u002FAdmiralGallade","Eager to learn!\r\nI'll do anything for more knowledge anywhere.","2026-06-06 07:34:31",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add AdmiralGallade\u002Fharness-repository --skill prompt-engineer-toolkit",{"tool":41,"command":42},"bunx","bunx skills add AdmiralGallade\u002Fharness-repository --skill prompt-engineer-toolkit",{"tool":44,"command":45},"pnpm","pnpm dlx skills add AdmiralGallade\u002Fharness-repository --skill prompt-engineer-toolkit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fmarketing-skill\u002Fskills\u002Fprompt-engineer-toolkit\u002FSKILL.md",true,[49,55,59,63,67,73],{"path":50,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":53,"sourceHtmlUrl":54},"README.md","REFERENCE","参考文档",1244,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fmarketing-skill\u002Fskills\u002Fprompt-engineer-toolkit\u002FREADME.md",{"path":56,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fevaluation-rubric.md",328,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fmarketing-skill\u002Fskills\u002Fprompt-engineer-toolkit\u002Freferences\u002Fevaluation-rubric.md",{"path":60,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":61,"sourceHtmlUrl":62},"references\u002Fprompt-templates.md",1532,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fmarketing-skill\u002Fskills\u002Fprompt-engineer-toolkit\u002Freferences\u002Fprompt-templates.md",{"path":64,"resourceType":51,"resourceTypeDesc":52,"sizeBytes":65,"sourceHtmlUrl":66},"references\u002Ftechnique-guide.md",675,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fmarketing-skill\u002Fskills\u002Fprompt-engineer-toolkit\u002Freferences\u002Ftechnique-guide.md",{"path":68,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":71,"sourceHtmlUrl":72},"scripts\u002Fprompt_tester.py","SCRIPT","脚本",7793,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fmarketing-skill\u002Fskills\u002Fprompt-engineer-toolkit\u002Fscripts\u002Fprompt_tester.py",{"path":74,"resourceType":69,"resourceTypeDesc":70,"sizeBytes":75,"sourceHtmlUrl":76},"scripts\u002Fprompt_versioner.py",8111,"https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fclaude-skills\u002Fmarketing-skill\u002Fskills\u002Fprompt-engineer-toolkit\u002Fscripts\u002Fprompt_versioner.py",[78,86,93,100,107,114],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":18},"01M75JSM6WGJ71BTHM6VC8CJ1X","verify-sign","Add an Artifact Verification (SscaArtifactVerification) step to an existing Harness pipeline to verify Cosign signatures on container or local-stage artifacts. Supports CI, Security, and CD Deploy (containerized step group). Supports Third-Party registries (Docker, ECR, GCR, GAR, ACR), Harness Artifact Registry (HAR), and Harness Local Stage artifacts. Only works with existing pipelines. Use when asked to verify signed artifacts, verify artifact signature, verify-sign, validate Cosign signature, or configure SscaArtifactVerification. Trigger phrases: verify sign, verify artifact, artifact verification, verify signature, verify-sign, SscaArtifactVerification, verify signed image, verify Cosign, HAR verification.","Apache-2.0","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fverify-sign\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":18},"01M75JSDSTP77TFM3JFGBB8QKP","template-usage","Track Harness template dependencies, usage, and adoption via MCP v2 tools. Find which pipelines or other templates reference a given template, analyze update impact, identify unused templates, and compare version adoption. Use when asked about template usage, template references, template dependencies, impact analysis before updating a template, finding unused templates, or tracking template adoption across projects. Trigger phrases: template usage, who uses template, template references, template dependencies, template impact, unused templates, template adoption. Do NOT use for creating or updating templates (use create-template instead).","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Ftemplate-usage\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":18},"01M75JS76Q2KC8PD598H2DZZRA","sign-artifact","Add an Artifact Signing (SscaArtifactSigning) step to an existing Harness pipeline to Cosign-sign container or local-stage artifacts with keyless, key-based, or Vault signing. Supports Third-Party registries (Docker, ECR, GCR, GAR, ACR), Harness Artifact Registry (HAR), and Harness Local Stage artifacts. Place after image build\u002Fpush; optionally upload .sig to the registry. Only works with existing pipelines. Use when asked to sign artifacts, add artifact signing, Cosign sign image, attach signature to registry, or configure SscaArtifactSigning. Trigger phrases: sign artifact, artifact signing, sign image, Cosign sign, add signing step, SscaArtifactSigning, attach signature, sign container image, HAR signing.","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fsign-artifact\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":104,"categories":105,"keywords":106,"publishedAt":18},"01M75JS16EEFFHA44EBNE8KWNT","sei-analytics","Advanced engineering analytics via Harness Software Engineering Insights (SEI) MCP. Configure sprint velocity and estimation accuracy tracking, engineering investment allocation breakdowns, sprint planning with capacity forecasts, and release readiness assessments. Use when asked about sprint analytics, investment allocation, sprint planning, capacity forecasting, or release readiness. Do NOT use for DORA metrics (use dora-metrics instead). Trigger phrases: sprint velocity, sprint analytics, investment allocation, capacity planning, sprint forecast, release readiness, engineering productivity, estimation accuracy, sprint planning, scope creep, code quality trends.","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fsei-analytics\u002FSKILL.md",[],[],{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":18},"01M75JRWE3X3E7V9JFQ4ENZYZM","security-report","Generate security compliance reports using Harness SCS and STO via MCP. Analyze vulnerabilities, SBOMs, and manage exemptions. Use when user says \"security report\", \"vulnerabilities\", \"SBOM\", \"security scan\", \"compliance check\", or asks about application security.","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fsecurity-report\u002FSKILL.md",[],[],{"skillNo":115,"name":116,"nameZh":6,"description":117,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":82,"licenseFileUrl":6,"sourceHtmlUrl":118,"categories":119,"keywords":120,"publishedAt":18},"01M75JRSFJSNZFZRFKX8MSPCS2","scorecard-review","Review service maturity scorecards and compliance using Harness IDP via MCP. Check production readiness, security, and documentation scores. Use when user says \"scorecard\", \"service maturity\", \"production readiness\", \"compliance score\", or asks about service health scores.","https:\u002F\u002Fgithub.com\u002FAdmiralGallade\u002Fharness-repository\u002Fblob\u002Fmain\u002Fharnesses\u002Fharness-skills\u002Fskills\u002Fscorecard-review\u002FSKILL.md",[],[]]