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

Objection To Proof Of Claim

ASecurity

Drafts Objections to Proof of Claim for U.S. bankruptcy courts under 11 U.S.C. § 502. Extracts case facts, identifies evidentiary deficiencies, and articulates grounds for disallowance or reduction. Use when a debtor, trustee, or party in interest challenges a creditor's proof of claim, claim classification, or insufficient documentation.

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

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill objection-to-proof-of-claim --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Objection To Proof Of Claim?

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

Security grade badge for Objection To Proof Of Claim
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-objection-to-proof-of-claim/badge)](https://www.skillsdirectory.com/skills/lev-os-objection-to-proof-of-claim)

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

Download Zip
Files
SKILL.md
---
name: objection-to-proof-of-claim
description: Drafts Objections to Proof of Claim for U.S. bankruptcy courts under 11 U.S.C. § 502. Extracts case facts, identifies evidentiary deficiencies, and articulates grounds for disallowance or reduction. Use when a debtor, trustee, or party in interest challenges a creditor's proof of claim, claim classification, or insufficient documentation.
tags:
  - drafting
  - litigation
  - motion
---

# Objection to Proof of Claim

Draft a litigation-ready objection challenging a creditor's proof of claim in U.S. bankruptcy court, targeting disallowance or reduction under 11 U.S.C. § 502.

## Prerequisites

Collect before drafting:

1. **Bankruptcy petition** — debtor name, case number, chapter, petition date
2. **Proof of claim (POC)** — claim number, filing date, creditor name, amount, stated basis, attachments
3. **Underlying documents** — contracts, invoices, payment history, correspondence
4. **Schedules and SOFA** — debtor's characterization and any discrepancies with POC
5. **Local rules** — formatting, page limits, verification requirements
6. **Bar date order** — claims deadline and timeliness of filing

## Output Structure

### 1. Caption

Format per local rules. Include: court name with district, case number, debtor name (as on petition), chapter, and centered title "OBJECTION TO PROOF OF CLAIM NO. [X]".

### 2. Introduction

- State objector's standing under § 502(a) (debtor, trustee, or party in interest)
- Identify claim number, creditor name, and asserted amount
- Preview objection grounds in one to two sentences — do not argue

### 3. Factual Background

Chronological narrative covering:

- Origin of alleged debt (contract, date, terms)
- Pre-petition payment history and disputes
- Petition date, bar date, and POC filing date relative to bar date
- Discrepancies between schedules and POC
- Documentation attached or missing from POC

Present facts neutrally. Distinguish disputed from undisputed. Every assertion must trace to a producible source document.

### 4. Grounds for Objection

Identify all applicable grounds:

| Ground | Authority | Showing Required |
|---|---|---|
| Insufficient documentation | FRBP 3001(f); § 502(b) | Missing contracts, invoices, or statements |
| Calculation errors | § 502(b)(1) | Incorrect interest, unauthorized fees, principal errors |
| Statute of limitations | § 502(b)(1) + state law | Claim accrued outside limitations period |
| Improper priority | § 503(b), § 507(a)(8), § 506 | Fails statutory priority requirements |
| Improper secured status | § 506(a) | No valid, perfected security interest |
| Lack of standing | § 502(a) | Not real party in interest; deficient assignment chain |
| Duplicative claim | § 502(b)(1) | Duplicates another filed claim |
| Post-petition debt | § 502(b) | Arose post-petition without administrative expense basis |

For each ground: cite statute/rule, state the legal standard, apply facts showing how claim fails.

### 5. Legal Argument

For each argument:

1. State governing standard (statute + controlling case law)
2. Apply burden framework — FRBP 3001(f) prima facie validity shifts to creditor on colorable challenge
3. Connect specific facts to legal standard
4. Anticipate creditor counterarguments

Cite controlling Circuit and BAP authority. Bluebook format with pinpoint cites. Mark unverified citations with [VERIFY].

### 6. Prayer for Relief

In order of preference:

1. Disallow claim in entirety
2. Reduce to $[amount] with basis
3. Reclassify from [current] to [requested] status (if applicable)
4. Fees/costs if statutory or contractual basis exists (cite authority)
5. General relief clause

### 7. Signature Block

Per FRBP 9011: name, bar number, firm, address, phone, email. Include verification under penalty of perjury if required by local rules.

## Checks

- **Tone**: Professional, measured — no inflammatory language
- **Format**: 12pt serif, double-spaced body, single-spaced caption/signature/block quotes, 1-inch margins, page numbers, case footer
- **Citations**: Bluebook with pinpoint cites throughout
- **Evidence**: Every fact must be traceable to an admissible source document
- **Fresh start**: For individual debtors, frame within bankruptcy's rehabilitative purpose where applicable
- **Never** assume secured status, priority, or standing — require creditor to prove each element
- **Never** concede facts favorable to the objector when characterizing disputed matters

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 →