fix(skills): add Anti-Patterns sections, fix descriptions, quality checks, and required inputs
- Add Anti-Patterns section (3-5 binary checkboxes) to all modified skills - Fix Quality Checks to use binary checkbox format where needed - Rewrite descriptions to verb-when-produces format where needed - Add Required Inputs sections to skills missing them - Fix email-triage frontmatter YAML quoting https://claude.ai/code/session_01MuGKn3a3Gbqoe8uM5Lmuqt
This commit is contained in:
@@ -65,6 +65,14 @@ WARNING: This draft requires review by a qualified legal professional. It does n
|
||||
- [ ] Caveats section lists what would change the analysis
|
||||
- [ ] Disclaimer is included
|
||||
|
||||
## Anti-Patterns
|
||||
|
||||
- [ ] Do not present uncertain legal positions with confident language — areas of legal ambiguity must be flagged explicitly, not smoothed over
|
||||
- [ ] Do not omit the disclaimer — every legal brief output must include the professional review caveat before the user treats it as advice
|
||||
- [ ] Do not structure the brief chronologically — IRAC format (Issue, Rule, Application, Conclusion) must be used regardless of how the user framed the request
|
||||
- [ ] Do not cite cases or statutes from memory without flagging them as [REQUIRES VERIFICATION] — hallucinated citations are worse than no citations
|
||||
- [ ] Do not conflate jurisdiction — legal positions in England & Wales, US, and EU can differ materially; always confirm jurisdiction before stating the rule
|
||||
|
||||
## Example Trigger Phrases
|
||||
- "Draft a legal memo on [issue]"
|
||||
- "Write a legal brief arguing [position]"
|
||||
|
||||
Reference in New Issue
Block a user