Legal
Speed up contract review, NDA triage, and compliance workflows for in-house legal teams. Draft legal briefs, organize precedent research, and manage institutional knowledge.
9 skills · version 1.3.0
Install
hrida-agent-sdk plugin install legal@knowledge-work-skillsOr, inside a session: /plugin install legal@knowledge-work-skills. See Installation for scopes and updates.
Connectors
Skills work on their own with files you share, and get more useful when these tools are connected (configured in the plugin's .mcp.json):
Slack, Box, Egnyte, Atlassian, Docusign, Google Calendar, Gmail.
Skills
| Skill | What it does | Use case | How to use |
|---|---|---|---|
| brief | Generate contextual briefings for legal work — daily summary, topic research, or incident response. | When starting your day and need a scan of legal-relevant items across email, calendar, and contracts, when researching a specific legal question across internal sources, or when a developing situation (data breach, litigation threat, regulatory inquiry) needs rapid context. | /legal:brief [daily | topic <query> | incident] |
| compliance-check | Run a compliance check on a proposed action, product feature, or business initiative, surfacing applicable regulations, required approvals, and risk areas. | When launching a feature that touches personal data, when marketing or product proposes something with regulatory implications, or when you need to know which approvals and jurisdictional requirements apply before proceeding. | /legal:compliance-check <action or initiative to check> |
| legal-response | Generate a response to a common legal inquiry using configured templates, with built-in escalation checks for situations that shouldn't use a templated reply. | When responding to data subject requests, litigation hold notices, vendor legal questions, NDA requests from business teams, or subpoenas. | /legal:legal-response [inquiry-type] |
| legal-risk-assessment | Assess and classify legal risks using a severity-by-likelihood framework with escalation criteria. | When evaluating contract risk, assessing deal exposure, classifying issues by severity, or determining whether a matter needs senior counsel or outside legal review. | /legal:legal-risk-assessment |
| meeting-briefing | Prepare structured briefings for meetings with legal relevance and track resulting action items. | When preparing for contract negotiations, board meetings, compliance reviews, or any meeting where legal context, background research, or action tracking is needed. | /legal:meeting-briefing |
| review-contract | Review a contract against your organization's negotiation playbook — flag deviations, generate redlines, provide business impact analysis. | When reviewing vendor or customer agreements, when you need clause-by-clause analysis against standard positions, or when preparing a negotiation strategy with prioritized redlines and fallback positions. | /legal:review-contract <contract file or text> |
| signature-request | Prepare and route a document for e-signature — run a pre-signature checklist, configure signing order, and send for execution. | When a contract is finalized and ready to sign, when verifying entity names, exhibits, and signature blocks before sending, or when setting up an envelope with sequential or parallel signers. | /legal:signature-request <document or contract to send> |
| triage-nda | Rapidly triage an incoming NDA and classify it as GREEN (standard approval), YELLOW (counsel review), or RED (full legal review). | When a new NDA arrives from sales or business development, when screening for embedded non-solicits, non-competes, or missing carveouts, or when deciding whether an NDA can be signed under standard delegation. | /legal:triage-nda <NDA file or text> |
| vendor-check | Check the status of existing agreements with a vendor across all connected systems — CLM, CRM, email, and document storage — with gap analysis and upcoming deadlines. | When onboarding or renewing a vendor, when you need a consolidated view of what's signed and what's missing (MSA, DPA, SOW), or when checking for approaching expirations and surviving obligations. | /legal:vendor-check [vendor name] |
Example
Ask in plain language and the right skill loads automatically, or call one directly:
/legal:brief [daily | topic <query> | incident]