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
- noelceta/content-enginetheir own version, first seen Nov 16, 2026
- MiguelARojas3103/rtovar-aiostheir own version, first seen Nov 15, 2026
- nazmirket/skillstheir own version, first seen Nov 15, 2026
- sufficiently-advanced-ai/imitheir own version, first seen Nov 12, 2026
- grainulation/grainulatortheir own version, first seen Nov 12, 2026
- fjwood69/moritheir own version, first seen Nov 10, 2026
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.
toneron2Skillcapture
Capture thoughts to inbox with automatic classification
Also in 6 projects that use this
EpistatesSkillstrategy
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-dytkoSkilldecision
Make a product decision with full context from the vault and available sources
Also in 3 projects that use this
dirienSkilldecide
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
JaimeGBASkillingest
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
howellsSkillreconcile
Audit a project against current plugin conventions and offer to update structure.
Also in 3 projects that use this
Other versions81 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 81
- anthropics/knowledge-work-plugins★ 36ksame name
- suboss87/FDEOps★ 940same name
- with-pebbly/aseprite-ai-artist★ 697same name
- educlopez/ui-craft★ 441same name
- github/lever★ 279same name
- dylanroscover/Embody★ 219same name
- yofine/skills★ 154same name
- grainulation/grainulator★ 86same name
- g2i-ai/agents★ 52same name
- gregmos/memoforge★ 38same name
71 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository164 other files it gives its agents.
- instrument-data-to-allotropeSkill
- literature-reviewSkill
- nextflow-developmentSkill
- scientific-problem-selectionSkill
- scvi-toolsSkill
- single-cell-rna-qcSkill
- discover-brandSkill
- enforce-voiceSkill
- generate-guidelinesSkill
- csat-reportSkill
- customer-escalationSkill
- customer-researchSkill
- draft-responseSkill
- kb-articleSkill
- sentiment-analysisSkill
- ticket-triageSkill
- analyzeSkill
- build-dashboardSkill
- create-vizSkill
- data-context-extractorSkill
- data-modelingSkill
- data-pipelineSkill
- etl-designSkill
- explore-dataSkill
- sql-queriesSkill
- statistical-analysisSkill
- validate-dataSkill
- write-querySkill
- accessibility-reviewSkill
- component-librarySkill
- design-critiqueSkill
- design-handoffSkill
- design-systemSkill
- frontend-designSkill
- research-synthesisSkill
- user-researchSkill
- ux-copySkill
- wireframingSkill
- Agent DevelopmentSkill
- CLAUDE.md ManagementSkill
- MCP Server BuilderSkill
- Plugin DevelopmentSkill
- Prompt EngineeringSkill
- Skill CreatorSkill
- curriculum-designSkill
- lesson-planningSkill
- quiz-generatorSkill
- study-guideSkill
- tutoringSkill
- api-designSkill
- architectureSkill
- ci-cd-pipelineSkill
- code-reviewSkill
- database-migrationSkill
- debugSkill
- dependency-auditSkill
- deploy-checklistSkill
- documentationSkill
- error-handlingSkill
- git-workflowSkill
- The first 60 shown.
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
- Distinctive: line 85
Always state the date and scope so the briefing can be filed and referenced later.
- Distinctive: line 89
When citing regulations, include the specific section number and a plain-language summary.
“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.
Files
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.
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
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.

