Debt Collection Recovery
v1.0.0Generates compliant debt recovery strategies, collection letter sequences, payment plans with interest, aging analyses, skip tracing, statute mapping, and wr...
⭐ 0· 530·0 current·0 all-time
by@1kalin
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (debt collection/recovery playbook) match the SKILL.md content: letter templates, aging analysis, payment plans, statute mapping and write-off rules. No unrelated credentials, binaries, or installs are requested.
Instruction Scope
Instructions and templates stay within the debt-collection domain. The SKILL.md includes skip-tracing checklists and state statute summaries; while domain-appropriate, skip tracing can involve handling personal data and statute summaries should be independently verified for accuracy—the file also contains upsell links to external paid context packs.
Install Mechanism
Instruction-only skill with no install spec and no code files, so nothing is written to disk or downloaded during install.
Credentials
The skill requests no environment variables, credentials, or config paths—proportional to an instruction-only playbook.
Persistence & Privilege
The skill does not request always:true, does not modify other skills, and has no install behavior. It can be invoked by agents normally, which is expected for a skill of this type.
Assessment
This skill is internally consistent and low technical risk because it is instruction-only and requests no credentials. Before using it in production: (1) verify the statute-of-limitations numbers and FDCPA guidance with current, authoritative legal sources or counsel (the playbook may be outdated or incomplete); (2) be cautious with skip-tracing—it can involve sensitive personal data and local privacy rules; (3) review any outbound links or paid 'context packs' before entering payment or business data; and (4) if you will automate sending collection communications, implement safeguards to avoid improper/illegal messaging (time-of-day limits, dispute-handling, recordkeeping).Like a lobster shell, security has layers — review code before you run it.
FDCPAvk979sp45sn28rdrfjagccx1q4n817vygaccounts receivablevk979sp45sn28rdrfjagccx1q4n817vygcollectionsvk979sp45sn28rdrfjagccx1q4n817vygfinancevk979sp45sn28rdrfjagccx1q4n817vyglatestvk979sp45sn28rdrfjagccx1q4n817vyg
License
MIT-0
Free to use, modify, and redistribute. No attribution required.