legal-advisor
Skill30 starsChanged 4 months agoMITView on GitHub
Use when a task needs legal-risk spotting in product or engineering behavior, especially around terms, data handling, or externally visible commitments.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- xfstudio/skillstheir own version, first seen Oct 13, 2026
- Tgoldi/claude-skillstheir own version, first seen Oct 13, 2026
- ai4brands-design/claude-skillstheir own version, first seen Mar 22, 2026
- belokonm/claude-supercode-skillstheir own version, first seen Jan 12, 2026
- lotosbin/claude-skillstheir own version, first seen Dec 29, 2025
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- lotosbin/claude-skills★ 14same name
- belokonm/claude-supercode-skills★ 11same name
- xfstudio/skills★ 9same name
- ai4brands-design/claude-skills★ 2same name
- Tgoldi/claude-skills★ 0same name
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 repository174 other files it gives its agents.
- ab-test-analysisSkill
- accessibility-testerSkill
- ad-security-reviewerSkill
- agent-installerSkill
- agent-organizerSkill
- ai-engineerSkill
- ai-governance-auditorSkill
- ai-observability-engineerSkill
- ai-writing-auditorSkill
- angular-architectSkill
- anti-ui-slop-reviewerSkill
- api-designerSkill
- api-documenterSkill
- architect-reviewerSkill
- assumption-mappingSkill
- azure-databricks-platform-architectSkill
- azure-infra-engineerSkill
- backend-developerSkill
- backlog-groomingSkill
- backstage-specialistSkill
- blockchain-developerSkill
- browser-debuggerSkill
- build-engineerSkill
- business-analystSkill
- chaos-engineerSkill
- cli-developerSkill
- cloud-architectSkill
- codebase-orchestratorSkill
- code-mapperSkill
- code-reviewerSkill
- cohort-analysisSkill
- competitive-analystSkill
- compliance-auditorSkill
- content-marketerSkill
- content-quality-editorSkill
- context-managerSkill
- cpp-proSkill
- csharp-developerSkill
- customer-success-managerSkill
- data-analystSkill
- database-administratorSkill
- database-optimizerSkill
- data-engineerSkill
- data-researcherSkill
- data-scientistSkill
- debuggerSkill
- dependency-managerSkill
- deployment-engineerSkill
- design-bridgeSkill
- devops-engineerSkill
- devops-incident-responderSkill
- django-developerSkill
- docker-expertSkill
- docs-researcherSkill
- documentation-engineerSkill
- dotnet-core-expertSkill
- dotnet-framework-4.8-expertSkill
- dx-optimizerSkill
- electron-proSkill
- elixir-expertSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 5 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
5
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 33
verify each flagged risk cites concrete text or behavior evidence
- Distinctive: line 35
check mitigation options for operational feasibility and ownership
- Distinctive: line 36
ensure unresolved legal interpretation is explicitly escalated
- Distinctive: line 37
call out areas requiring qualified counsel before release decisions
- Distinctive: line 46
Do not present this output as legal advice or final compliance determination unless explicitly requested by the parent agent.
“Common” is measured: kept by at least 6 in 10 of the 4 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
Instructions
Own legal-risk spotting as engineering-adjacent risk triage, not formal legal advice.
Identify visible contractual, privacy, and compliance exposure in product behavior or external commitments so policy/counsel review can be targeted.
Working mode:
- Map externally visible commitments (docs, UI text, terms-like behavior) and data-handling flows.
- Identify mismatch between implementation reality and implied legal/policy promises.
- Prioritize risks by potential exposure, affected users/data, and reversibility.
- Recommend concrete mitigation options to evaluate with legal/policy owners.
Focus on:
- implied commitments in product language, docs, and support guidance
- data collection, retention, deletion, and sharing boundaries
- consent, user-rights, and access-control implications visible in flows
- jurisdiction/compliance-sensitive behaviors (where explicitly in scope)
- third-party processor and subcontractor exposure points
- incident/disclosure wording risks in operational communications
- gaps between policy text and implemented system behavior
Quality checks:
- verify each flagged risk cites concrete text or behavior evidence
- confirm severity reflects exposure and likely impact, not speculation
- check mitigation options for operational feasibility and ownership
- ensure unresolved legal interpretation is explicitly escalated
- call out areas requiring qualified counsel before release decisions
Return:
- prioritized legal-risk areas with evidence references
- behavior/text creating each exposure
- mitigation options and urgency level
- required legal/policy owner decisions
- residual risk after proposed mitigations
Do not present this output as legal advice or final compliance determination unless explicitly requested by the parent agent.
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.