How do I install the Client Advisory skill?

Run npx skillmds add majiayu000/client-advisory in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Client Advisory safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Client Advisory?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Client Advisory free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Client Advisory?

majiayu000 (@majiayu000) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Client Advisory by majiayu000 — Agent Skill

Name: Client Advisory
Rating: 4.2 (5 reviews)
Author: majiayu000

Client Advisory

Drafts client advisory memoranda translating legal developments into actionable guidance with impact analysis, Bluebook citations, and compliance recommendations. Use when preparing client alerts, regulatory updates, legal bulletins, or proactive advisory summaries.

majiayu000 3f052a8 2 files · 4.5 KB Updated Sep 9, 2026 567 repo stars

File contents

Client Advisory Summary

Produces a professional advisory memorandum that translates recent legal developments into tailored client guidance with impact analysis and numbered action items.

Prerequisites

Legal development(s) — case law, statutory amendments, regulatory updates, agency guidance, or pending legislation
Client profile — industry, jurisdiction(s), operations, and specific legal concerns
Client materials (if available) — contracts, policies, prior advisories, compliance frameworks
Effective dates and deadlines — time-sensitive compliance windows

Quick Start

Gather inputs (developments, client profile, deadlines)
Draft header and executive summary
Analyze each development using the body framework below
Build the recommendations summary table
Run the drafting checklist before delivery

Output Structure

Header

Field	Content
To	Client name / matter ID
From	Attorney / firm
Date	Date of preparation
Re	Concise subject line identifying development(s)

Executive Summary (2–3 paragraphs)

Lead with the most critical development and its immediate implication
Write for a non-lawyer audience while preserving legal precision
State the bottom line: what changed, who is affected, what to do

Body Sections (one per development)

For each development, address:

Component	Content
Development	What changed — statute, rule, holding, agency action
Citation	Full Bluebook citation; mark unverified cites `[VERIFY]`
Effective Date	When it takes effect
Context	Brief origin/purpose (1–2 sentences)
Substantive Changes	Bullet list of new requirements, standards, or rights
Client Impact	Effect on this client's operations, obligations, or rights
Impact Horizon	Immediate / Short-term / Long-term
Impact Type	Compliance obligation / Strategic opportunity / Risk exposure
Recommendations	Numbered action items with deadlines where applicable

Recommendations Summary Table

#	Action Item	Deadline	Priority	Type
1	...	...	High/Med/Low	Compliance/Strategic/Risk

Closing

Note assumptions or limitations in the analysis
Flag areas requiring further fact-gathering
Include specific contact information for follow-up

Drafting Checklist

Every factual assertion tied to a cited source
All citations Bluebook-formatted; uncertain cites marked [VERIFY]
Cross-referenced client contracts/policies against new requirements
Jargon defined on first use or replaced with plain language
Concrete examples illustrating impact on client's actual operations
All deadlines and effective dates explicitly stated
Recommendations are specific and actionable (not "consider reviewing")

Pitfalls

Speculation: Distinguish enacted law from proposed/pending changes; label each clearly
Jurisdiction: Default US; flag state-specific variations where federal and state law diverge
Unconfirmed facts: If analysis depends on unverified client facts, state assumptions explicitly
Length: Target 2–5 pages; bias toward concision
Visual aids: Use comparison tables for before/after changes and timelines for phased implementation

---name: client-advisorydescription: Drafts client advisory memoranda translating legal developments into actionable guidance with impact analysis, Bluebook citations, and compliance recommendations. Use when preparing client alerts, regulatory updates, legal bulletins, or proactive advisory summaries.--- # Client Advisory Summary Produces a professional advisory memorandum that translates recent legal developments into tailored client guidance with impact analysis and numbered action items. ## Prerequisites - **Legal development(s)** — case law, statutory amendments, regulatory updates, agency guidance, or pending legislation - **Client profile** — industry, jurisdiction(s), operations, and specific legal concerns - **Client materials** (if available) — contracts, policies, prior advisories, compliance frameworks - **Effective dates and deadlines** — time-sensitive compliance windows ## Quick Start 1. Gather inputs (developments, client profile, deadlines) 2. Draft header and executive summary 3. Analyze each development using the body framework below 4. Build the recommendations summary table 5. Run the drafting checklist before delivery ## Output Structure ### Header | Field | Content | |-------|---------| | To | Client name / matter ID | | From | Attorney / firm | | Date | Date of preparation | | Re | Concise subject line identifying development(s) | ### Executive Summary (2–3 paragraphs) - Lead with the most critical development and its immediate implication - Write for a non-lawyer audience while preserving legal precision - State the bottom line: what changed, who is affected, what to do ### Body Sections (one per development) For each development, address: | Component | Content | |-----------|---------| | **Development** | What changed — statute, rule, holding, agency action | | **Citation** | Full Bluebook citation; mark unverified cites `[VERIFY]` | | **Effective Date** | When it takes effect | | **Context** | Brief origin/purpose (1–2 sentences) | | **Substantive Changes** | Bullet list of new requirements, standards, or rights | | **Client Impact** | Effect on this client's operations, obligations, or rights | | **Impact Horizon** | Immediate / Short-term / Long-term | | **Impact Type** | Compliance obligation / Strategic opportunity / Risk exposure | | **Recommendations** | Numbered action items with deadlines where applicable | ### Recommendations Summary Table | # | Action Item | Deadline | Priority | Type | |---|------------|----------|----------|------| | 1 | ... | ... | High/Med/Low | Compliance/Strategic/Risk | ### Closing - Note assumptions or limitations in the analysis - Flag areas requiring further fact-gathering - Include specific contact information for follow-up ## Drafting Checklist - [ ] Every factual assertion tied to a cited source - [ ] All citations Bluebook-formatted; uncertain cites marked `[VERIFY]` - [ ] Cross-referenced client contracts/policies against new requirements - [ ] Jargon defined on first use or replaced with plain language - [ ] Concrete examples illustrating impact on client's actual operations - [ ] All deadlines and effective dates explicitly stated - [ ] Recommendations are specific and actionable (not "consider reviewing") ## Pitfalls - **Speculation**: Distinguish enacted law from proposed/pending changes; label each clearly - **Jurisdiction**: Default US; flag state-specific variations where federal and state law diverge - **Unconfirmed facts**: If analysis depends on unverified client facts, state assumptions explicitly - **Length**: Target 2–5 pages; bias toward concision - **Visual aids**: Use comparison tables for before/after changes and timelines for phased implementation

Frequently asked questions