skills/legal/objection-to-proof-of-claim/SKILL.md
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.
npx skillsauth add casemark/skills objection-to-proof-of-claimInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
Collect before drafting:
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]".
Chronological narrative covering:
Present facts neutrally. Distinguish disputed from undisputed. Every assertion must trace to a producible source document.
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.
For each argument:
Cite controlling Circuit and BAP authority. Bluebook format with pinpoint cites. Mark unverified citations with [VERIFY].
In order of preference:
Per FRBP 9011: name, bar number, firm, address, phone, email. Include verification under penalty of perjury if required by local rules.
development
name: automated-contract-summary language: en description: Generates structured executive summaries of contracts using ML — captures key terms, party obligations, risk allocations, and compliance requirements in a standardized format. Optimized for high-volume review where speed and consistency matter. tags: - summarization - agreement - corporate --- # Automated Contract Summarization Produces standardized executive summaries of contracts using machine learning, capturing essential term
tools
Extracts regulatory obligations from dense regulations across jurisdictions. Breaks down multi-level regulations into clear article-level obligations, classifies applicability to a business, and prioritizes by risk level. Use when translating regulations into actionable compliance requirements.
development
Continuously monitors regulatory landscapes for changes relevant to a specific business. Ingests global regulatory updates, filters by relevance, summarizes impact, and produces an actionable change advisory. Use when tracking regulatory developments affecting a particular product or market.
testing
Compares an organization's existing compliance controls, policies, and procedures against extracted regulatory obligations to identify coverage gaps. Produces a remediation plan with prioritized actions. Use when assessing compliance maturity or preparing for regulatory audits.