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

Dischargeability Complaint

ASecurity

Drafts a U.S. bankruptcy adversary complaint under 11 U.S.C. §523 to determine non-dischargeability of debt. Use when a creditor, assignee, or subrogee needs a complaint for Bankruptcy Court with §523 theories (fraud, fiduciary defalcation, willful/malicious injury). Trigger when inputs include debtor case data, petition/§341 dates, transaction facts, and target §523 subsections.

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

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill dischargeability-complaint --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Dischargeability Complaint?

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

Security grade badge for Dischargeability Complaint
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-dischargeability-complaint/badge)](https://www.skillsdirectory.com/skills/lev-os-dischargeability-complaint)

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

Download Zip
Files
SKILL.md
---
name: dischargeability-complaint
description: Drafts a U.S. bankruptcy adversary complaint under 11 U.S.C. §523 to determine non-dischargeability of debt. Use when a creditor, assignee, or subrogee needs a complaint for Bankruptcy Court with §523 theories (fraud, fiduciary defalcation, willful/malicious injury). Trigger when inputs include debtor case data, petition/§341 dates, transaction facts, and target §523 subsections.
tags:
  - drafting
  - litigation
  - pleading
---

# Dischargeability Complaint

Drafts a court-ready adversary complaint under 11 U.S.C. §523 for U.S. bankruptcy proceedings, with jurisdiction/venue allegations, evidence-anchored counts, and FRBP compliance.

## Quick Start

Collect before drafting:

- **Standing**: Plaintiff's enforcement right (original creditor, assignee, successor, subrogee)
- **Case data**: Court, case number, chapter, petition date, first §341 date, conversion status
- **Deadline posture**: FRBP 4007(c) timing — confirm filing window or extension basis
- **Evidence**: Contracts, account records, correspondence, payment history, admissions, fiduciary documents
- **§523 theories**: Map each subsection to its required elements under controlling circuit law
- **Damages**: Principal, contractual interest, statutory interest, fees, costs
- **Local rules**: Caption format, paragraph style, line numbering, font/margins, filing protocol

## Core Workflow

### 1. Build complaint scaffold

| Section | Content | Verify |
|---|---|---|
| Caption | Court name, bankruptcy case no., adversary caption, parties | District matches debtor case |
| Jurisdiction/Venue | 28 U.S.C. §§1334, 157(b)(2)(I), 1409; core proceeding | Explicitly alleged |
| Parties | Names, addresses, standing chain | Standing complete |
| Procedural posture | Petition date, §341 date, Rule 4007(c) timing | Within deadline or extension stated |
| Factual narrative | Chronological facts with dates and sources | Each allegation tied to exhibit |
| Counts | Per-theory allegations for each §523 subsection | All elements and remedies included |
| Prayer | Non-dischargeability, amount, interest, fees, costs | Amounts traceable to evidence |
| Verification | Perjury statement and signature block | Authorized signer confirmed |
| Service checklist | Filing-ready package | Complete |

### 2. Plead theory-specific elements

| Theory | Elements | Style |
|---|---|---|
| §523(a)(2)(A) | False representation, scienter, reliance, proximate causation, damages | Fact-dense: who/what/when/where/how |
| §523(a)(2)(B) | Materially untrue financial statement | Attach supporting financials, explain materiality |
| §523(a)(4) | Express fiduciary relationship, breach, fraud/defalcation | Distinguish express fiduciary duty from contractual/statutory |
| §523(a)(6) | Willful and malicious injury | Show intentional conduct + substantial certainty of harm |

### 3. Apply paragraph construction rules

- Number all paragraphs; keep short-to-medium length for readability.
- Fraud allegations must satisfy Rule 9(b): identify statement, communicator, medium, date, and falsity.
- Incorporate prior paragraphs by reference at each count's start.
- Use separate counts per theory — prevents collapse if one fails.
- Cross-reference facts; do not repeat full blocks.

### 4. Produce mandatory sections

1. Complaint heading and title
2. Jurisdiction and venue
3. Parties / standing
4. Factual background
5. Procedural timing
6. Count I: §523(a)(2)(A)
7. Count II: §523(a)(4) *(if applicable)*
8. Count III: §523(a)(6) *(if applicable)*
9. Prayer for relief
10. Verification
11. Signature block
12. Service/filing checklist

## Legal Constraints

- **FRBP 7001**: Adversary proceeding form governs structure.
- **FRBP 7009 / Rule 9(b)**: Heightened pleading for fraud allegations.
- **FRBP 7012 / Rule 12(b)(6)**: Frame for plausibility to resist dismissal.
- **FRCP 11**: Remove weak, conclusory, or unsupported allegations — sanctions exposure.

## Pitfalls and Checks

- Reconcile all damages figures against attached evidence.
- Confirm every element has at least one direct fact anchor.
- No allegation may rest on speculation — separate facts from legal inference.
- Do not mix circuit authority; use only jurisdiction-verified standards.
- Do not plead causes outside §523 scope.
- Keep tone objective — factual allegations only, no inflammatory language.
- Include `[VERIFY]` placeholders for unresolved legal standards or local-rule citations.
- Confirm attorney signature, bar status, and filing authorization before finalizing.
- Preserve exhibit organization and authentication trail.

---

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

Springboot Security

Java Spring Boot 服务中关于身份验证/授权、验证、CSRF、密钥、标头、速率限制和依赖安全的 Spring Security 最佳实践。

2456590 votes

Security Review

Use this skill when adding authentication, handling user input, working with secrets, creating API endpoints, or implementing payment/sensitive features. Provides comprehensive security checklist and patterns.

2456590 votes

Paperclip Task Bridge

Create, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.

805540 votes

Summarize Status

Write a short, colloquial summary for a Paperclip summary slot: open with the 1–3 specific, concrete actions the reader needs to take right now to unblock the work, then a brief plain-language status, streaming progress as it works.

805540 votes

Paperclip Evals

Choose, inspect, validate, and report Paperclip Runner or Product E2E evaluations while preserving evidence, provenance, cost, and failure classification.

805540 votes
View all in security →