Household Document Command Center

# Household Document Command Center

Safety Notice

This listing is from the official public ClawHub registry. Review SKILL.md and referenced scripts before running.

Copy this and send it to your AI assistant to learn

Install skill "Household Document Command Center" with this command: npx skills add harrylabsj/household-document-command-center

Household Document Command Center

Use this skill when the user wants a simple household document organization system without sharing private document contents. Keep the work prompt-only: produce structure, checklists, and planning guidance. Do not create scripts, request uploads, inspect scans, or store sensitive document details.

Privacy boundary

Do not ask for or store document contents, account numbers, government ID numbers, policy numbers, tax IDs, claim numbers, scans, photos, passwords, signatures, or full addresses. Work only with document categories, owner labels, rough dates, renewal dates, and storage locations the user is comfortable naming. If the user offers sensitive details, tell them to keep those details out of the chat and replace them with category labels.

Output format

Return these five sections in order:

  1. Document Map
  2. Folder Taxonomy
  3. Missing-Item List
  4. Naming Convention
  5. 30-Minute Setup Plan

Keep the output practical, household-friendly, and concise. Use placeholders such as [person], [year], [provider], [document-type], and [location] instead of sensitive values.

Document Map

Create a high-level inventory map with category, purpose, likely physical location, likely digital location, owner, review cadence, and action needed. Include only organization-level descriptions.

Recommended categories:

  • Identity and vital records
  • Home and lease or mortgage
  • Insurance
  • Taxes
  • Banking and credit
  • Employment and income
  • Medical and health administration
  • Education
  • Vehicles and transportation
  • Dependents, pets, and caregiving
  • Warranties, receipts, and manuals
  • Legal and estate planning
  • Emergency copies
  • Archive and shred queue

Mark each category as one of:

  • Ready: folder exists and recent items have a home
  • Find: user needs to locate the item
  • Create: user needs to create the folder or index entry
  • Review: user should check date, renewal, or completeness
  • Retire: user can archive or shred according to retention rules

Folder Taxonomy

Provide a simple physical and digital taxonomy. Keep the same names across paper folders and cloud/local folders so the system is easy to maintain.

Suggested top-level folders:

00_Inbox
01_Identity_and_Vital_Records
02_Home
03_Insurance
04_Taxes
05_Money
06_Work_and_Income
07_Health_Admin
08_Education
09_Vehicles
10_Dependents_Caregiving_Pets
11_Warranties_Receipts_Manuals
12_Legal_and_Estate
13_Emergency_Copies
90_Archive
99_Shred_or_Delete_Review

For each top-level folder, add 2-5 optional subfolders only when useful. Avoid deep nesting. Recommend one README-index file or paper index per top-level folder that lists document types, not private contents.

Missing-Item List

Create a missing-item checklist that asks the user to confirm whether each category has a safe home, not to reveal the document itself. Use columns for item category, why it matters, where to look, next action, and deadline.

Example phrasing:

  • Confirm there is a folder for birth, marriage, adoption, or name-change records if relevant.
  • Confirm there is a folder for current insurance declaration pages.
  • Confirm there is a folder for the latest filed tax return and supporting summary records.
  • Confirm there is a folder for emergency contact and household access instructions without listing credentials.

When a document may require professional advice, say so briefly. Do not give legal, tax, medical, or financial advice beyond organization and preparation.

Naming Convention

Recommend names that reveal category and date but not sensitive identifiers.

Use this pattern:

YYYY-MM-DD__category__provider-or-topic__document-type__owner-or-household__status.ext

Examples:

2026-04-15__taxes__federal__return-summary__household__filed.pdf
2026-01-01__insurance__auto__declarations-page__household__current.pdf
2025-11-20__home__maintenance__invoice__household__paid.pdf

Rules:

  • Use lowercase words separated by hyphens inside each field.
  • Use double underscores between fields.
  • Use household, initials, or role labels instead of full names when privacy matters.
  • Use statuses such as draft, current, filed, paid, expired, archived, or review-needed.
  • Never include account numbers, ID numbers, claim numbers, exact street addresses, or passwords in filenames.

30-Minute Setup Plan

Give a timed plan the user can complete quickly:

  • Minutes 0-5: create physical and digital top-level folders.
  • Minutes 5-10: set up 00_Inbox, 90_Archive, and 99_Shred_or_Delete_Review.
  • Minutes 10-18: sort visible documents by category without reading sensitive contents.
  • Minutes 18-23: make the missing-item checklist.
  • Minutes 23-27: rename 3-5 recent digital files using the convention.
  • Minutes 27-30: pick one weekly 10-minute maintenance slot.

End with a small next-action list for the next week: process the inbox, fill the missing-item checklist, and review archive/shred items under applicable retention rules.

Source Transparency

This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.

Related Skills

Related by shared tags or category signals.

General

Aws Fis Experiment Prepare

Use when the user wants to prepare, create, or generate an AWS FIS (Fault Injection Service) experiment configuration. Triggers on "prepare FIS experiment",...

Registry SourceRecently Updated
General

Aws Fis Experiment Execute

Use when the user wants to run a prepared AWS FIS experiment where the CloudFormation stack has already been deployed. Triggers on "execute FIS experiment",...

Registry SourceRecently Updated
General

Warranty Return Dispute Kit

Organizes a defective-product, denied-warranty, or return-window dispute into an evidence packet, timeline, support message, escalation script, contact log,...

Registry SourceRecently Updated
General

Goldman Sachs Co

提供高盛公司历史、业务模式、市场地位及关键数据,助力研究投资银行和金融机构角色分析。

Registry SourceRecently Updated