client-alert-drafting
Draft professional legal client alerts and publications that inform clients about significant legal developments. Use when asked to: write a client alert, draft a legal update, create a publication about new legislation/regulations/case law, or prepare a legal briefing for clients. Supports all practice areas including corporate, litigation, regulatory, employment, tax, IP, and more. Output available as Word (.docx) or Markdown (.md).
What this skill does
*First published on [Skala Legal Skills](https://www.skala.io/legal-skills)* ## Legal Disclaimer This skill is provided for informational and educational purposes only and does not constitute legal advice. The analysis and information provided should not be relied upon as a substitute for consultation with a qualified attorney. No attorney-client relationship is created by using this skill. Laws and regulations vary by jurisdiction and change over time. Always consult with a licensed attorney in your jurisdiction for advice on specific legal matters. The creators and publishers of this skill disclaim any liability for actions taken or not taken based on the information provided. --- # Client Alert Drafting Draft professional legal client alerts following the standards of top-tier law firms. ## Workflow 1. **Gather information** - Understand the legal development (legislation, case, regulation, guidance) 2. **Identify audience** - Determine target clients and their concerns 3. **Draft structure** - Use the standard template below 4. **Write content** - Follow style guidelines 5. **Generate output** - Create .docx or .md file ## Standard Alert Structure ``` TITLE [Date] | [Practice Area] | [Jurisdiction] IN BRIEF [1-2 paragraph executive summary of the key development and its significance] KEY TAKEAWAYS • [Most important point 1] • [Most important point 2] • [Most important point 3] (3-5 bullet points maximum) IN DEPTH [Detailed analysis organized with subheadings] ## Background [Context and history leading to the development] ## The Development [What specifically changed - new law, ruling, regulation] ## Analysis / Implications [What this means for affected parties] ## Practical Considerations / Actions to Consider [Specific guidance for clients] LOOKING AHEAD (optional) [Future developments to watch] CONTACTS [Author names, titles, locations, contact info] --- [Standard disclaimer] ``` ## Writing Style **Tone**: Professional, authoritative, accessible. Avoid unnecessary jargon. **Voice**: Active voice preferred. Write with confidence. **Length guidelines**: - In Brief: 100-200 words - Key Takeaways: 3-5 bullets, 1-2 sentences each - In Depth: 500-2000 words depending on complexity - Total alert: 800-2500 words typical **Principles**: - Lead with the "so what" - why should clients care? - Balance factual reporting with practical guidance - Use clear headings to aid scanning - Cite sources (cases, statutes, regulations) accurately - Cross-reference related firm publications when relevant - Avoid overly academic or theoretical discussion - Focus on business/practical implications ## Content Guidelines **In Brief section**: - Open with the key development in one sentence - Explain significance in 2-3 sentences - Mention who is affected - Preview main takeaway **Key Takeaways**: - Actionable, specific points - Start each with action verb or impact statement - Most important point first - Avoid repeating In Brief content **In Depth section**: - Organize logically with clear subheadings - Include relevant background/context - Explain the legal change precisely - Analyze implications for different stakeholders - Provide practical guidance - Note any uncertainties or open questions **Practical Considerations**: - Numbered list of specific actions - Be concrete and actionable - Consider different client situations - Note timing/deadlines if applicable ## Practice Area Adaptations Adapt emphasis based on practice area: **Regulatory/Compliance**: Focus on compliance requirements, deadlines, penalties **Litigation**: Focus on case holdings, precedential value, procedural implications **Corporate/M&A**: Focus on deal structuring, transaction considerations **Employment**: Focus on employer obligations, employee rights, HR policies **Tax**: Focus on tax consequences, planning opportunities, reporting requirements **IP**: Focus on protection strategies, enforcement implications ## Output Format **Word document (.docx)**: Use the docx skill. Professional formatting with firm-appropriate styling. **Markdown (.md)**: Clean markdown with proper heading hierarchy. Ask the user which format they prefer if not specified. ## Standard Disclaimer Include at end of every alert: ``` This [publication/alert] is provided for informational purposes only and does not constitute legal advice. The information contained herein should not be relied upon or used as a substitute for consultation with legal, accounting, tax, or other professional advisors. [Firm name] expressly disclaims all liability in connection with actions taken or not taken based on any or all of the contents of this publication. ``` ## Quality Checklist Before finalizing, verify: - [ ] Title is clear and informative - [ ] In Brief captures the essence quickly - [ ] Key Takeaways are actionable - [ ] Analysis is accurate and well-organized - [ ] Practical guidance is specific - [ ] Citations are correct - [ ] Tone is professional but accessible - [ ] Length is appropriate for complexity - [ ] Disclaimer is included ## Examples See `references/examples.md` for annotated examples of well-crafted alerts across different practice areas.
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.