Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Commitment And Curative

ASecurity

Build the title commitment and clear it: separate Schedule B-I requirements from Schedule B-II exceptions, and decide each defect as cure vs insure-over vs except. Clear the requirements before you close; insure-over only with underwriter approval. Underwriter/jurisdiction specifics are verify-at-use.

7 stars
0 votes
0 copies
0 views
Added 9/23/2026
ai-agents

Security Analysis

A100/100

Scanned 9/23/2026

$npx -y skills add mcorbett51090/RavenClaude --skill commitment-and-curative --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Commitment And Curative?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Commitment And Curative
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/mcorbett51090-commitment-and-curative/badge)](https://www.skillsdirectory.com/skills/mcorbett51090-commitment-and-curative)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: commitment-and-curative
description: "Build the title commitment and clear it: separate Schedule B-I requirements from Schedule B-II exceptions, and decide each defect as cure vs insure-over vs except. Clear the requirements before you close; insure-over only with underwriter approval. Underwriter/jurisdiction specifics are verify-at-use."
---

# Commitment & Curative

Structure the commitment honestly and clear it deliberately. The commitment is the underwriter's promise to insure *if* the requirements are met and *except* what is carved out.

> **Advisory, not legal or underwriting advice.** Commitment forms, standard exceptions, and curative sufficiency are underwriter-/jurisdiction-specific and change — every specific here is `[verify-at-use]`. The binding insurability call is the underwriter's. No PII.

## The commitment's two schedules

| Schedule | Contains | Meaning |
|---|---|---|
| **B-I — Requirements** | What must happen before the policy issues (payoffs, releases, corrective deeds, affidavits, entity docs) | Not satisfied → no policy |
| **B-II — Exceptions** | What the policy will **not** cover (easements, CC&Rs, standard exceptions, matters excepted by choice) | Carved out of coverage |

**Standard vs added exceptions:** know which standard exceptions (survey, mechanic's lien, parties in possession) can be removed and what removes them (survey, affidavit, indemnity) — `[verify-at-use]` against the underwriter's rules.

## The curative decision — cure vs insure-over vs except

| Path | When | Mechanism |
|---|---|---|
| **Cure** | The defect can and should be eliminated | Payoff + release, corrective/quitclaim deed, affidavit, quiet-title action |
| **Insure over** | Cure is impractical and risk is acceptable to the underwriter | Underwriter approval within guidelines (`[verify-at-use]`); often with indemnity |
| **Except** | The matter stays on title and is carved out of coverage | Add to Schedule B-II; disclose to insured |

**The rule:** the path follows the **risk to marketability and the underwriter's appetite** — cure what should be cured, insure over only *with* approval, except knowingly. Clear the requirements **before** you close.

## Workflow

1. From the examination, list every defect and encumbrance (see [`../title-search-and-examination/SKILL.md`](../title-search-and-examination/SKILL.md)).
2. Traverse the **clear a title exception** decision tree for each.
3. Assign each to B-I requirement or B-II exception; draft the curative action or the exception language.
4. Escalate anything off-guideline or above your authority to the underwriter with your read.
5. Track requirement clearance to zero-open before setting the closing.

## Read metrics

| Signal | What it tells you |
|---|---|
| Open requirements at clear-to-close | Whether you are closing on an unclean commitment |
| Curative aging (days from exam to cleared) | Where the pipeline stalls after examination |
| Insure-over rate without documented approval | An unauthorized-risk exposure |

## See also

- Traverse the **clear a title exception (cure vs insure-over vs except)** tree in [`../../knowledge/title-escrow-decision-trees.md`](../../knowledge/title-escrow-decision-trees.md).
- Template: [`../../templates/title-commitment-worksheet.md`](../../templates/title-commitment-worksheet.md); command: [`/clear-title-exceptions`](../../commands/clear-title-exceptions.md).
- Best practice: [`../../best-practices/clear-the-commitment-requirements-before-you-close.md`](../../best-practices/clear-the-commitment-requirements-before-you-close.md).

Attribution

mcorbett51090mcorbett51090
View sourceSee grades on GitHubMore from mcorbett51090 →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

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 (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →