agentleFS
nisarthnisarth/claude-skills-store/skills/legal/brief/SKILL.md

brief

Skill1 starsChanged 7 months agoMITView on GitHub

Generate contextual briefings for legal work -- daily summary, topic research, or incident response preparation. Use when starting your day and need a scan of legal-relevant items, when researching a specific legal question, or when preparing legal context for an incident. Trigger with "legal brief", "daily legal summary", "research this legal topic", or "brief me on".

81 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use capture, strategy and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • toneron2Skill

    capture

    Capture thoughts to inbox with automatic classification

    Also in 6 projects that use this

  • EpistatesSkill

    strategy

    Plan weekly or monthly X content strategy. Use when the user wants to plan their content calendar, set growth goals, build a content pipeline, or think strategically about their X presence.

    Also in 4 projects that use this

  • aleksander-dytkoSkill

    decision

    Make a product decision with full context from the vault and available sources

    Also in 3 projects that use this

  • dirienSkill

    decide

    Three-agent adversarial debate protocol for strategic decisions. Two advocates steelman opposing positions while a moderator identifies risks and synthesizes a binding consensus. Use when choosing between alternatives, evaluating tradeoffs, or making high-stakes decisions.

    Also in 5 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 7 projects that use this

  • howellsSkill

    reconcile

    Audit a project against current plugin conventions and offer to update structure.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 74 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Always state the date and scope so the briefing can be filed and referenced later.

    line 85
  2. Distinctive:

    When citing regulations, include the specific section number and a plain-language summary.

    line 89

“Common” is measured: kept by at least 6 in 10 of the 74 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Legal Briefing Generator

Generate structured legal briefings tailored to context -- daily summaries, deep-dive topic research with authorities, or rapid incident response preparation with exposure analysis.

Workflow

Step 1: Determine Briefing Type

  • Daily summary: Scan connected sources for legal-relevant items due today or this week. Surface deadlines, pending approvals, and new inbound matters.
  • Topic research: Research a specific legal question. Identify applicable statutes, regulations, and internal precedent. Provide balanced analysis with risk factors.
  • Incident response prep: Assemble legal context for an incident -- preservation obligations, notification requirements, privilege considerations, and regulatory exposure.

Step 2: Gather Source Material

  • Daily: Calendar events, flagged emails, contract deadlines within 14 days, pending signatures, open action items.
  • Topic research: Internal knowledge bases, playbooks, prior memos, governing jurisdiction, and regulatory framework.
  • Incident response: Nature of incident, affected data/systems, jurisdictions, breach notification laws, litigation hold requirements.

Step 3: Analyze and Prioritize

  • Rank items by urgency: immediate, this week, informational.
  • Flag regulatory deadlines with penalties for non-compliance.
  • Identify items requiring outside counsel. Note privilege concerns.
  • For topic research, distinguish settled law from areas of uncertainty.

Step 4: Structure the Briefing

Conclude with concrete next steps, decisions needed, escalation recommendations, and follow-up research.

Output Format

## Legal Briefing: [Type]
**Date**: [YYYY-MM-DD] | **Scope**: [Daily / Topic / Incident]

### Executive Summary
[2-3 sentence overview of key findings and most urgent items]

### Priority Items
| # | Item | Urgency | Owner | Deadline |
|---|------|---------|-------|----------|
| 1 | [Description] | IMMEDIATE | [Name] | [Date] |

### Analysis
[Detailed findings organized by sub-topic]

### Recommended Actions
1. [Action] -- Owner: [Name] -- By: [Date]

Examples

User: "Brief me on what's happening today" Action: Generate a daily legal summary scanning calendar, email, and contract deadlines. Prioritize by urgency and flag anything requiring immediate attention.

User: "Research our obligations under CPRA for employee data" Action: Produce a topic research briefing covering CPRA applicability, exemption sunset dates, required disclosures, and comparison to current privacy notice.

User: "We had a data breach last night -- prep me for the legal response" Action: Generate an incident response briefing with preservation obligations, breach notification statutes by jurisdiction, notification timelines, and privilege protocol.

Best Practices

  • Always state the date and scope so the briefing can be filed and referenced later.
  • For daily briefings, lead with deadlines that carry financial or regulatory penalties.
  • For topic research, present both sides of uncertain questions and note confidence level.
  • For incident response, front-load the earliest mandatory notification deadline.
  • When citing regulations, include the specific section number and a plain-language summary.
  • Include enough context that someone reading cold can act without further research.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.