Skip to content
cccskills
FreePublished on GitHub

codexkit-contract-risk-review

Review commercial contracts, NDAs, MSAs, SOWs, and vendor agreements for obligation clarity, risk allocation, termination, data handling, and negotiation red flags. Use when a user needs a structured contract summary, red flag list, fallback positions, or clause-by-clause review. Do not use as jurisdiction-specific legal advice, litigation strategy, or final legal sign-off.

The English summary is being prepared. Showing the original description.

See how to install

Files included (5)

  • SKILL.md3.3 KB
  • agents/openai.yaml240 B
  • examples/common-mistakes.md861 B
  • examples/good-output.md939 B
  • verification/checklist.md1.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Contract Risk Review

Purpose

Surface business and contractual risk quickly so a human reviewer can negotiate or escalate intelligently.

When to use

  • A contract needs first-pass risk review before legal or procurement sign-off.
  • A business owner wants obligations, liabilities, and red flags summarized.
  • A negotiation needs fallback positions and open questions.

When not to use

  • The user needs formal legal advice for a specific jurisdiction.
  • The task is drafting litigation arguments or dispute strategy.

Inputs

  • contract text or key clauses
  • deal context, commercial goals, and fallback positions
  • known red lines, approval thresholds, and data or security concerns

Procedure

  1. Classify the agreement type and commercial stakes.
  2. Review key clause families: scope, fees, term, liability, IP, confidentiality, data, termination, and dispute language.
  3. Extract obligations, asymmetries, unusual exposure, and missing protections.
  4. Rate issues by business impact and negotiation urgency.
  5. Suggest fallback language or negotiation positions without pretending to replace counsel.
  6. Call out where legal review is mandatory.

Output

  • executive contract summary
  • clause-by-clause risk table
  • top red flags and why they matter
  • fallback positions or negotiation notes
  • unresolved questions for counsel or stakeholders

Definition of done

  • A business owner can see the highest-risk clauses quickly.
  • Missing protections and unclear obligations are explicit.
  • The output states where human legal review is still required.

Examples

  • "Review this vendor MSA and flag the clauses we should negotiate before signing."
  • "Summarize our obligations and main risks in this customer SOW."

Quality Criteria

  • Every finding is tied to a specific evidence source (log, test, metric)
  • Pass/fail criteria are binary and measurable — no subjective judgments
  • Severity levels are assigned with clear thresholds
  • Remediation steps are provided for all critical and high findings

Verification (4C)

CheckQuestion
CorrectnessAre all pass/fail criteria applied against the correct standard or rule?
CompletenessWere all required dimensions or checklist items evaluated?
Context-fitDoes the verification scope match the actual risk level of the deliverable?
ConsequenceIf this passed verification but had a hidden flaw, what is the worst-case impact?

Edge Cases

  • Incomplete data for full assessment — Document which checks were limited and flag for re-verification when data becomes available.
  • Ambiguous pass/fail criteria — Request clarification from the standard owner before scoring. Mark as 'Needs Review'.
  • Multiple overlapping standards — Identify the governing standard and note where others diverge.

Changelog

  • v1.0.0 — Initial release

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Design rigorous A/B test plans with hypothesis, sample size calculation, Minimum Detectable Effect (MDE), randomization strategy, and decision rules. Includes guardrail metrics and rollout playbook. Use when planning product experiments, conversion optimization, or data-driven feature decisions.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

Review REST and GraphQL API designs for consistency, usability, and best practices. Covers naming conventions, versioning strategy, error format, pagination, authentication patterns, and breaking change detection. Use when reviewing API specs, designing new APIs, or auditing existing endpoints.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

Write Architecture Decision Records (ADRs) following the Michael Nygard format. Captures context, options considered, decision rationale, and consequences. Use when making technology choices, framework selections, or any architectural decision that future developers need to understand.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

Assess organizational readiness for financial audits (internal or external). Map assertions to account balances, check evidence completeness, score readiness using a Red/Amber/Green framework, and generate a remediation timeline. Aligned with SOX, IFRS, and GAAP audit standards. Use before scheduled audits or when preparing for first-time compliance.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

Design safe recurring Codex automations with clear prompts, outputs, schedules, and gating rules.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

Refine Product Backlog Items to meet INVEST criteria. Write User Stories with Acceptance Criteria in Given/When/Then format, estimate with Story Points, and flag dependencies. Use before sprint planning when backlog items need grooming. Do not use to prioritize the backlog — that is the Product Owner's decision.

The English summary is being prepared. Showing the original description.

hoavdc/CodexKit25Updated Oct 11, 2026

See all skills by hoavdc

Report a problem with this skill