agreement-review

Review active agreements to determine renewal, revision, or sunset.

2|Updated Mar 13, 2026
One-click install
npx skills add https://github.com/Community-Chests/neos-operating-system --skill agreement-review-community-chests
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agreement-review
Source: https://github.com/Community-Chests/neos-operating-system/tree/main/neos-core/layer-01-agreement/agreement-review
Command: npx skills add https://github.com/Community-Chests/neos-operating-system --skill agreement-review-community-chests

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Periodic reviews ensure agreements stay relevant, prevent stagnation, and prevent governance decay by evaluating each agreement's relevance, appropriateness, and consistency, and by proposing renewal, amendment, or sunset.

Core Features & Use Cases

  • Regular evaluation: triggers on scheduled dates or manual requests to revalidate active agreements.
  • Outcome-driven actions: renew as-is, revise through amendment, or sunset with deprecation and archiving.
  • Audit-ready artifacts: produces a standardized review record for the registry and compliance reviews.

Quick Start

Initiate a scheduled review for an agreement in the registry to determine renewal, revision, or sunset.

Frequently Asked Questions about agreement-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate periodic agreement reviews for renewal or sunset?

Periodic agreement reviews are automated by triggering scheduled evaluations on registry entries to determine renewal, revision, or sunset. This process collects version history, feedback, and conflicts to produce a structured review record and update the registry.

What is the process for evaluating an active agreement's relevance and consistency?

Evaluating active agreements involves applying a review workflow to the registry entry to collect current version history, feedback, and conflicts. This identifies whether the agreement needs renewal, amendment, or sunset and produces an audit-ready review record.

How do I prevent governance decay in a compliance registry?

Governance decay is prevented by conducting regular agreement reviews that evaluate relevance, appropriateness, and consistency. Scheduled or manual reviews trigger evaluations that propose renewal, amendment, or sunset to keep agreements current.

Can I trigger manual reviews for active agreements outside of a scheduled cycle?

Yes, manual reviews can be initiated for active agreements in the registry. This triggers the review workflow to collect version history, feedback, and conflicts, producing a structured review record that determines renewal, revision, or sunset.

What artifacts are generated when sunsetting an agreement?

Sunsetting an agreement generates a standardized review record for the registry and compliance audits. This includes deprecation and archiving updates, along with collected version history, feedback, and conflict evaluations from the review workflow.

How do I track amendments and version history during an agreement review?

Amendments and version history are tracked by applying the review workflow to the registry entry. This process collects current version history and feedback, evaluates conflicts, and produces a structured review record that updates the registry accordingly.