Agent skill · AI & Agents

employment-law-research

Research a US employment law topic across federal, state, and city jurisdictions and produce structured research notes with proper source attribution. Use this skill any time the user asks about US employment laws, regulations, or pending legislation - from a single jurisdiction question to a 50-state survey. Triggers include phrases like "research [employment law topic]", "what are the laws on [employment topic]", "state-by-state [employment topic]", "help me understand [topic] across the US", or any prompt that asks for a legal landscape overview before another deliverable. Always run this B

lawve-aigithub.com/lawve-aiGitHub ↗
claude-codeNOASSERTION
Install
npx skills add lawve-ai/awesome-legal-skills --skill employment-law-research-yue-deng-wu --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 4
SKILL.md size: 10 KB
Bundled scripts: none
Path: skills/employment-law-research-yue-deng-wu/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 618
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# US Employment Law Research This skill produces a structured research brief on a specific area of US employment law. The note is the input for downstream work like building a dashboard, writing a memo, or briefing a stakeholder. The most important thing the skill does is enforce a clean separation between primary-source claims (the statute says X) and secondary-source claims (Cooley wrote about it last week). Assume the audience is practicing lawyers. Use this skill standalone when the user just wants research, OR as the first step before the `employment-law-dashboard` skill. If a dashboard is the eventual deliverable, complete this skill's workflow first and save the research note before invoking the dashboard skill. ## When to use The skill should fire whenever a user asks for research, comparison, or landscape on a US employment law topic. Examples: - "Research the state of US laws on workplace surveillance." - "What are the pay transparency laws across the US?" - "Help me understand non-compete enforcement state by state." - "I need a brief on pregnancy accommodation requirements nationally." - "Make a dashboard for [employment law topic]" → run this first, then the dashboard

What's inside
Steps it walks through
  1. When to use
  2. Workflow
  3. 1. Clarify scope before researching
  4. 2. Read the source policy
  5. 3. Conduct research
  6. 4. Apply the source policy at writeup time
  7. 5. Produce the research note
  8. 6. Verify
  9. 7. Hand off
  10. Notes on common pitfalls
Ships with 3 files
  • README.md
  • references/source-policies.md
  • references/verification.md
More from awesome-legal-skills
All skills →
About this skill
What does the employment-law-research skill do?

Research a US employment law topic across federal, state, and city jurisdictions and produce structured research notes with proper source attribution. Use this skill any time the user asks about US employment laws, regulations, or pending legislation - from a single jurisdiction question to a 50-state survey. Triggers include phrases like "research [employment law topic]", "what are the laws on [employment topic]", "state-by-state [employment topic]", "help me understand [topic] across the US", or any prompt that asks for a legal landscape overview before another deliverable. Always run this B

How do I install it?

Run `npx skills add lawve-ai/awesome-legal-skills --skill employment-law-research-yue-deng-wu --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From lawve-ai/awesome-legal-skills, a repository with 618 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going