본문으로 건너뛰기
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(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

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 / 1,000자

이 양식은 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의 스킬 모두 보기

이 스킬의 문제 신고