mcpbeat Sign in

Cowork Tax Prep Organizer Skill for Claude

Sweep your folders and downloads for tax documents and build a CPA-ready package -- checklist by form type, everything renamed and organized, a missing-document chase list, and flagged items worth asking your accountant about. Organization, not tax advice.

841 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
235
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/OneWave-AI/claude-skills --skill cowork-tax-prep-organizer

The instruction itself

5 sections, as written by the author

Cowork Tax Prep Organizer

Do the part of tax season that actually eats the weekend: finding, identifying, and organizing the documents. Input: one or more folders (Downloads, a documents dump, last year's tax folder for reference). Output: an organized package a CPA can work from and a precise list of what is still missing. This skill organizes; it does not compute taxes or give tax advice.

Workflow

  • Build the personal checklist. From last year's return or folder (if provided) and a few questions (W-2 employment? contract income? brokerage accounts? mortgage? dependents? business entity?), build the expected-documents list: W-2s, 1099-NEC/MISC/INT/DIV/B/R, 1098s, K-1s, property tax bills, charitable receipts, estimated-payment confirmations, prior-year return.
  • Sweep. Walk the folders and identify every tax-relevant document by content, not just filename -- payers, form types, tax year. Match each to the checklist. Flag wrong-year documents (the 2024 1099 hiding in the 2025 pile) and duplicates (the same W-2 downloaded three times).
  • Organize. On approval, copy -- never move -- into a clean structure: tax-2025/income/, deductions/, investments/, business/, prior-year/, with names like 1099-nec-acme-corp-2025.pdf. Write INDEX.md mapping checklist to files.
  • Chase list. Output what is expected but missing, with where it likely lives ("Interest income appeared last year from Chase -- no 1099-INT found; check the bank's tax documents page, typically posted by Jan 31"). Sort by what blocks filing vs. nice-to-have.
  • Ask-your-CPA list. Flag items a preparer should look at -- not conclusions: home-office-looking expenses for the self-employed, a brokerage form showing wash-sale codes, K-1 arrived vs. expected, estimated payments that do not sum to the notes. Phrase each as a question for the professional.

Rules

  • Never compute tax liability, deductions, or refunds. Identify, organize, and question -- the CPA concludes.
  • Copy, never move. Source folders stay intact.
  • Tax year discipline: every document is tagged with its year, and wrong-year files are quarantined in the report, not the package.
  • "MISSING" means "not found in the provided folders" -- state what was searched.
  • Treat everything as sensitive: no SSNs, account numbers, or dollar amounts in console output or digests; specifics live only in the package files.
  • If both spouses' or multiple entities' documents are mixed, separate them explicitly and confirm the split before organizing.

Scheduled Mode

As a monthly Cowork scheduled task during January-April: re-sweep Downloads and the documents folder for newly arrived forms, file them into the package, and update the chase list -- so tax weekend becomes tax hour.

Quick Commands

  • "Organize my tax docs from [folder]" -- full workflow
  • "What am I missing?" -- steps 1, 2, 4
  • "Build my checklist" -- step 1 only
  • "Anything my CPA should see?" -- step 5 against the organized package

Other skills for the same job

different authors, same section of the catalogue
Create Technical Spike
by github
vendor ×1

Create time-boxed technical spike documents for researching and resolving critical development decisions before implementation.

2k tokens
Spec To Backlog
by openai
vendor ×1

Automatically convert Confluence specification documents into structured Jira backlogs with Epics and implementation tickets. When an agent needs to: (1) Create Jira tickets from a Confluence page, (2) Generate a backlog from a specification, (3) Break down a spec into implementation tasks, or (4) Convert requirements into Jira issues. Handles reading Confluence pages, analyzing specifications, creating Epics with proper structure, and generating detailed implementation tickets linked to the Epic.

12k tokens
Grill With Docs
by sanity-io
vendor ×1

Grilling session that challenges your plan against the existing domain model, sharpens terminology, and updates documentation (CONTEXT.md, ADRs) inline as decisions crystallise. Use when user wants to stress-test a plan against their project's language and documented decisions.

2k tokens
Clinical Decision Support Documents
by BioTender-max
×1

Guidelines for clinical decision support (CDS) documents: biomarker-stratified cohort analyses and GRADE-graded treatment reports. Covers structure, executive summaries, evidence grading (1A–2C), stats (HR, CI, survival), and biomarker integration. Use for pharma research docs, clinical guidelines, regulatory submissions.

3k tokens
Clinical Decision Support
by christophacham
×1

Generate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.

83k tokens scripts
Secure Workflow Guide
by christophacham
×1

Guides through Trail of Bits' 5-step secure development workflow. Runs Slither scans, checks special features (upgradeability/ERC conformance/token integration), generates visual security diagrams, helps document security properties for fuzzing/verification, and reviews manual security areas.

4k tokens
Adr Log
by ComeOnOliver
×1

Document architecture decisions with ADR (Architecture Decision Records). Use when making significant technical decisions, choosing between alternatives, or when onboarding needs context on past decisions.

7k tokens
Plan Approval
by ComeOnOliver
×1

Plan-approval workflow patterns for user control over AI actions in Claude Code Waypoint Plugin. Use when planning complex changes, need user approval before execution, want to prevent mistakes, or need to document proposed changes. Covers plan creation, approval checkpoints, plan deviation tracking, revision management, and learning from approved/rejected plans.

8k tokens

How to use it

Copy the folder

Take onewave-ai/cowork-tax-prep-organizer from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.