Skip to content
Back to skills

Legal Request Triage

ASecurity

Triage incoming legal or legal-adjacent requests by issue type, urgency, jurisdiction or contract context, factual completeness, business impact, deadlines, confidentiality, and the qualified owner needed for interpretation.

  • 16 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 11, 2026
ai-agentsgosecurity

Security analysis

A100/100

Scanned September 11, 2026

npx -y skills add Dadmin88/hermes-profile-packs --skill legal-request-triage --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Legal Request Triage?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Legal Request Triage
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dadmin88-legal-request-triage/badge)](https://www.skillsdirectory.com/skills/dadmin88-legal-request-triage)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: legal-request-triage
description: Triage incoming legal or legal-adjacent requests by issue type, urgency, jurisdiction or contract context, factual completeness, business impact, deadlines, confidentiality, and the qualified owner needed for interpretation.
---
# Legal Request Triage

Use when legal operations receives a question, dispute, contract issue, policy request, notice, claim, or other matter that needs routing rather than immediate substantive advice.

## Procedure
1. Capture the requester, business owner, issue, desired decision, relevant parties, dates, geography or jurisdiction if known, and why the matter is time-sensitive.
2. Collect authoritative documents, communications, notices, contracts, policies, facts, and prior legal guidance relevant to the request.
3. Classify the request by process area such as commercial, privacy, employment, corporate, dispute, IP, regulatory, policy, or another organization-defined category without assuming the legal conclusion.
4. Identify hard deadlines, limitation or notice dates provided by authoritative sources, active incidents, threatened harm, or executive commitments that change urgency.
5. Separate factual questions Legal Ops can resolve from legal interpretation or advice that requires qualified counsel.
6. Identify business, finance, security, product, HR, procurement, or operational stakeholders whose facts or decisions are prerequisites.
7. Apply confidentiality and privilege handling according to organizational policy and counsel direction.
8. Route the complete packet to the correct authorized reviewer with an urgency level and concise statement of the decision needed.

## Decision rules
- Triage determines process and owner; it does not manufacture legal advice.
- Urgency should follow real deadlines and consequence, not requester seniority alone.
- Preserve original notices and communications.
- If jurisdiction or authority is unclear, surface that uncertainty to counsel.

## Quality gate
Triage is complete when the issue, facts, documents, deadlines, business impact, confidentiality, and required decision are clear, factual gaps are visible, stakeholders are identified, and the request reaches the qualified owner without Legal Ops overstating legal conclusions.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…