跳到正文
cccskills
免费在 GitHub 公开

codexkit-contract-intake-router

Standardize incoming legal or commercial contract requests into request type, missing information, priority, and review queue. Use when the work is intake routing and request cleanup. Do not use for clause interpretation, negotiation strategy, or legal advice on the agreement itself.

中文简介正在准备中。当前显示原文说明。

查看安装方法

包含的文件(2)

  • SKILL.md2.7 KB
  • agents/openai.yaml181 B

SKILL.md(原文)

安装前可以查看交给 AI 代理的指令内容。

Contract Intake Router

Purpose

Clean up contract intake so legal review starts with the right information.

When to use

  • requests arrive through email or chat with inconsistent detail
  • legal ops needs a clearer intake queue
  • the team wants to separate routing from legal analysis

When not to use

  • the task is clause review or negotiation advice
  • the request needs legal judgment on risk allocation

Inputs

  • intake requests or copied request list
  • requester, counterparty, deadline, and agreement type if available
  • routing rules if known

Procedure

  1. Normalize each request into request type, urgency, and owner.
  2. Flag missing counterparty, deadline, or document context.
  3. Separate routine routing from likely escalation items.
  4. Group requests by review lane where possible.
  5. End with missing-information follow-ups and next queue actions.

Output

  • intake queue
  • missing information list
  • suggested routing lane
  • escalation candidates

Definition of done

  • requests are easier to route than when they arrived
  • missing information is explicit
  • the output avoids pretending to be legal analysis

Examples

  • "Clean up this legal inbox into request type, priority, and missing info."
  • "Turn these contract asks into a structured intake queue for legal ops."

Quality Criteria

  • Trigger conditions and input requirements are unambiguous
  • Each automated step produces a verifiable output
  • Error handling and fallback paths are defined
  • Manual override points are documented

Verification (4C)

CheckQuestion
CorrectnessDoes the workflow produce the expected output for the defined inputs?
CompletenessAre all trigger conditions, edge cases, and error paths handled?
Context-fitIs the automation appropriate for the frequency and criticality of this task?
ConsequenceIf this ran unattended and failed silently, what would the downstream impact be?

Edge Cases

  • Input format varies unexpectedly — Add a normalization step at entry. Alert the operator on format mismatches.
  • Downstream system is unavailable — Queue the output and retry with exponential backoff. Alert after N failures.
  • Partial execution completes — Ensure idempotency — re-running from the start produces the same result without duplication.

Changelog

  • v1.0.0 — Initial release

评价

还没有评价。欢迎分享你的使用感受。

评论

无需登录即可发表。欢迎分享使用感受、提问,或说明在哪些环境下无法运行。

还没有评论。来写第一条吧。

提交后会立即公开。请勿填写邮箱、电话等个人信息。URL 最多 2 个。

0 / 1000 字

此表单受 reCAPTCHA 保护,适用 Google 的隐私权政策和服务条款。

同一仓库的技能

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.

中文简介正在准备中。当前显示原文说明。

hoavdc/CodexKit252026年10月11日 更新

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.

中文简介正在准备中。当前显示原文说明。

hoavdc/CodexKit252026年10月11日 更新

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.

中文简介正在准备中。当前显示原文说明。

hoavdc/CodexKit252026年10月11日 更新

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.

中文简介正在准备中。当前显示原文说明。

hoavdc/CodexKit252026年10月11日 更新

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

中文简介正在准备中。当前显示原文说明。

hoavdc/CodexKit252026年10月11日 更新

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.

中文简介正在准备中。当前显示原文说明。

hoavdc/CodexKit252026年10月11日 更新

查看 hoavdc 的全部技能

报告此技能的问题