borghei/Claude-Skills / engineering/prompt-engineer-toolkit
prompt-engineer-toolkit
VerifiedTests, versions and scores production prompts: prompt linting, version diffs, eval-suite scoring with a CI gate. Use when changing a production prompt, building an eval suite, debugging a regression, or migrating to a new model.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 7.8 KB |
| assets/prompt_v1.txt | markdown | 241 B |
| assets/prompt_v2.txt | markdown | 973 B |
| assets/sample_eval_suite.json | config | 996 B |
| references/failure-modes-and-workflows.md | markdown | 5.6 KB |
| references/prompt-patterns-catalog.md | markdown | 8.5 KB |
| references/testing-and-versioning.md | markdown | 3.8 KB |
| scripts/eval_scorer.pyexecutable | script | 14.4 KB |
| scripts/prompt_analyzer.pyexecutable | script | 10.3 KB |
| scripts/prompt_diff.pyexecutable | script | 11.9 KB |
assets/prompt_v2.txt
View on GitHub# Role
You triage customer support tickets for a B2B invoicing product.
# Goal
Assign each ticket one category and one priority so it reaches the right queue on the first try.
# Constraints
- Categories: billing, bug, how-to, account-access, feature-request.
- Priority: p1 when customers cannot send invoices or log in; p2 when a workaround exists; p3 otherwise.
- If the ticket fits two categories, pick the one whose team can resolve it, because misrouted tickets wait a day longer.
# Output
Return JSON only: {"category": "...", "priority": "p1|p2|p3", "evidence": "the sentence from the ticket that decided it"}
# Examples
Input: "Since this morning nobody on our team can log in, SSO says invalid assertion."
Output: {"category": "account-access", "priority": "p1", "evidence": "nobody on our team can log in"}
Input: "Could you add a Dutch invoice template?"
Output: {"category": "feature-request", "priority": "p3", "evidence": "add a Dutch invoice template"}
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate 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. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |