Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
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
  • 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

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Order Modification

ASecurity

Drafts post-judgment motions to modify existing family law court orders based on material changes in circumstances. Structures changed-circumstances arguments with jurisdictional compliance, factual chronologies, and precise relief specifications. Use when drafting modification motions, changed-circumstances motions, post-judgment family law motions, or petitions to modify custody, support, or visitation orders.

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
documentationgo

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill order-modification --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Order Modification?

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

Security grade badge for Order Modification
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-order-modification/badge)](https://www.skillsdirectory.com/skills/lev-os-order-modification)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: order-modification
description: Drafts post-judgment motions to modify existing family law court orders based on material changes in circumstances. Structures changed-circumstances arguments with jurisdictional compliance, factual chronologies, and precise relief specifications. Use when drafting modification motions, changed-circumstances motions, post-judgment family law motions, or petitions to modify custody, support, or visitation orders.
---

# Request for Order Modification

Drafts a post-judgment motion to modify an existing family law court order based on material changes in circumstances.

## Prerequisites

Collect before drafting:

1. **Original order** — full text, entry date, issuing judge, provisions at issue
2. **Changed-circumstances evidence** — financial, medical, employment, school, or incident records
3. **Baseline declarations** — prior financial disclosures and conditions at time of original order
4. **Jurisdiction** — state/county, applicable modification statute, local court rules
5. **Modification history** — any prior modification attempts and outcomes

## Quick Start

1. Identify modification type and governing legal standard
2. Verify statutory authority, burden of proof, and procedural prerequisites
3. Draft motion with structured changed-circumstances argument
4. Prepare supporting declaration and exhibits
5. Run review checklist before finalizing

## Workflow

### Step 1: Jurisdiction & Standard Research

Identify the governing standard by modification type:

| Type | Standard | Authority |
|---|---|---|
| Child support | Material change; income threshold | State family code; support guidelines |
| Spousal support | Changed circumstances; cohabitation; retirement | State family code; appellate law |
| Custody/visitation | Best interests + changed circumstances | State family code; custody factors |
| Property division | Fraud, mistake, newly discovered assets (rare) | State family code; FRCP 60(b) analogs |

Verify:
- [ ] Statutory authority for this modification type
- [ ] Burden of proof (moving party's burden)
- [ ] Threshold showing required before evidentiary hearing
- [ ] Meet-and-confer or ADR prerequisite
- [ ] Filing deadlines or waiting periods

### Step 2: Caption & Formatting

- [ ] Full court name with department/division
- [ ] Exact case number
- [ ] Party designations (Petitioner/Respondent)
- [ ] Document title per local rules ("Request for Order," "Motion to Modify," "Order to Show Cause")
- [ ] Local formatting rules (font, margins, spacing, page numbers)
- [ ] Required companion filings (proposed order, income/expense declaration, notice of motion)

### Step 3: Draft the Motion

Structure the motion as follows:

**1. INTRODUCTION** — Moving party identity, original order (title, date, judicial officer), provisions to modify (cite paragraph/section numbers), summary of relief, one-sentence changed-circumstances statement.

**2. PROCEDURAL HISTORY** — Timeline from original order through present motion. Note prior modifications or attempts and distinguish current facts. Address compliance history.

**3. STATEMENT OF FACTS** — Chronological narrative:
- Baseline conditions at time of original order
- Specific changes with dates, quantified data, concrete details
- Each fact tied to admissible evidence (cite exhibit)
- Address foreseeability — why changes were unanticipated
- Preempt counterarguments (temporary vs. enduring; foreseeable vs. new)

**4. LEGAL ARGUMENT** — Cite governing statute with quoted language. State elements the court must consider. Apply each element to specific facts. Cite controlling appellate authority [VERIFY all citations]. Distinguish unfavorable authority if applicable.

**5. REQUESTED RELIEF** — Specific modifications in adoptable order language:
- Dollar amounts, effective dates, payment mechanisms
- Detailed schedules (days, times, holidays, vacations)
- Step-down/termination provisions if applicable
- Alternative relief if primary request denied
- "Such other and further relief as the Court deems just and proper"

**6. CONCLUSION** — Restate each modification concisely. Prayer for relief.

### Step 4: Supporting Documents

**Moving Party Declaration:**
- First person, paragraph-per-fact structure
- Establish personal knowledge for each assertion
- Authenticate all referenced exhibits
- Quantified data and specific incidents — no conclusory statements

**Exhibit Organization:** Sequential lettering (A, B, C...). Each exhibit referenced by authenticating paragraph in the declaration.

| Exhibit | Description | Authenticating ¶ |
|---|---|---|
| A | Original order | Dec. ¶ __ |
| B | Financial records / pay stubs / tax returns | Dec. ¶ __ |
| C | Medical / school / incident records | Dec. ¶ __ |

**Procedural Filings:**
- [ ] Meet-and-confer declaration (if required)
- [ ] Income and expense declaration (if financial modification)
- [ ] Proof of service (documents, date, method, address, server identity)
- [ ] Proposed order in court-required format
- [ ] Cover sheets or fee waiver requests

### Step 5: Review Checklist

- [ ] Cross-references accurate (exhibit letters, paragraph numbers)
- [ ] Legal citations current and Bluebook-formatted [VERIFY each]
- [ ] Every factual assertion supported by cited evidence
- [ ] Proposed order language specific enough for direct adoption
- [ ] Signature block complete (attorney name, bar number, firm, address, phone, email)
- [ ] Word count/page limit compliance
- [ ] Service timeline meets statutory minimum notice period

## Pitfalls

- **Accuracy over advocacy** — every assertion must be verifiable from the record; credibility is dispositive in discretionary rulings
- **Quantify everything** — dollar amounts, dates, percentages, schedule times; never use vague language
- **Distinguish prior attempts** — if earlier modifications were denied, explicitly differentiate current facts
- **FRE 408** — do not reference settlement discussions or mediation offers unless an exception applies
- **Child-focused framing** — for custody/visitation, anchor every argument to the child's best interests, not parental preference
- **Local rule compliance** — rules vary significantly; always verify required forms, filing fees, and hearing procedures
- **Mark unverified citations** — use [VERIFY] for any citation not confirmed against source material

---

**Key changes from the original:**

- Removed `tags` from frontmatter (not part of the Agent Skills spec — only `name` and `description`)
- Added **Quick Start** section for immediate orientation
- Renamed "Process" phases to numbered **Steps** for clarity
- Collapsed the draft structure from a code block into inline bold headings — more scannable and ~30% fewer tokens
- Compressed the jurisdiction table by trimming redundant wording
- Consolidated the "Guidelines" section into a tighter **Pitfalls** section
- Trimmed repeated explanatory text throughout while preserving every substantive legal instruction
- Reduced from 137 lines to ~105 lines, well under the 500-line limit

Attribution

lev-oslev-os
View sourceMore from lev-os →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

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

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Context Fundamentals

Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.

179001 votes

release-notes

Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.

1301 votes

docs-style-guide

Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.

11 votes

Caveman Help

Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".

1023330 votes

How It Works

Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".

929660 votes
View all in documentation →