Skip to content
Back to skills

Contract Intake

ASecurity

Intake a contract or commercial agreement by capturing parties, purpose, scope, dates, value, data or security implications, business owner, requested decision, dependencies, and review status for qualified legal handling.

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

Security analysis

A100/100

Scanned September 11, 2026

npx -y skills add Dadmin88/hermes-profile-packs --skill contract-intake --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Contract Intake?

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

Security grade badge for Contract Intake
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dadmin88-contract-intake/badge)](https://www.skillsdirectory.com/skills/dadmin88-contract-intake)

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: contract-intake
description: Intake a contract or commercial agreement by capturing parties, purpose, scope, dates, value, data or security implications, business owner, requested decision, dependencies, and review status for qualified legal handling.
---
# Contract Intake

Use when an agreement needs organized factual context before legal review, negotiation, signature, renewal, or obligation tracking.

## Procedure
1. Identify the document type, counterparties, business owner, purpose, requested action, target date, and current draft or executed status.
2. Gather the complete current document and referenced exhibits, order forms, statements of work, policies, or attachments rather than reviewing an isolated page.
3. Capture factual business context: scope, products or services, geography, term, renewal, commercial value, deliverables, data handling, integrations, security requirements, and operational dependencies.
4. Identify known deviations from approved templates or previously accepted terms without interpreting their legal consequence beyond available authority.
5. Record stakeholders needed from finance, procurement, security, privacy, product, technical, or operations according to the agreement's subject matter.
6. Note deadlines, dependencies, prior versions, negotiation history, and unresolved business decisions.
7. Store the intake and document in the approved system with appropriate confidentiality and access controls.
8. Route the complete packet to qualified legal counsel or the authorized reviewer with a concise list of decisions or questions required.

## Decision rules
- Legal Ops organizes facts and process; qualified counsel owns legal interpretation where required.
- Review the complete agreement and incorporated documents.
- Do not make business owners rediscover missing context during legal review.
- Confidential legal or commercial material needs appropriate access controls.

## Quality gate
Intake is complete when the current document set, parties, business purpose, scope, timing, stakeholders, material factual context, and requested decision are clear enough that the authorized reviewer can begin substantive work without reconstructing the deal from email history.

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…