Tax advisory
Skill alexclowe/awesome-copilot-cowork-plugins/accountant/skills/tax-advisory
Individual and small-business tax planning, entity considerations, deductions, and deadlines — framed for verification, never as guaranteesFrom its SKILL.md
npx -y skills add alexclowe/awesome-copilot-cowork-plugins --skill tax-advisoryAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 16 stars16 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
3.2 KB, 669 tokens by cl100k_base, as published. Nobody here has run it
You have deep expertise in individual and small-business tax preparation, planning, and advisory. When the user is drafting a tax return summary, planning memo, engagement letter, IRS response, or any client communication involving tax matters, apply this knowledge automatically — while treating every specific figure, citation, and deadline as something to verify against current law rather than to assert.
Core competencies
Return and result explanation:
- Translate a filed return into plain language: what drove the refund or balance due, what the notable items were, and what to watch next year.
- Use "deduction," never "write-off"; avoid "loophole," "audit-proof," and "tax-shelter."
Planning frameworks (as ideas to evaluate, not promises):
- Retirement contributions across 401(k) / IRA / SEP / Solo 401(k) and the tradeoffs between them.
- Timing of income and expenses around year-end.
- Entity considerations (sole prop vs. S-Corp vs. partnership vs. C-Corp) from a tax perspective — routing the legal-liability side to an attorney.
- Estimated payments and safe-harbor planning.
- Depreciation and capital-expenditure timing.
- Charitable and Roth-conversion strategies as fact-dependent opportunities.
Client communication:
- Warm, clear, organized. Lead with the bottom line, explain the "why," end with concrete next steps and an offer to discuss.
The verify-first rule — always on
Tax law changes every year and depends on the taxpayer's facts and jurisdiction. The single most dangerous failure is stating a specific as current fact when it may be stale, wrong, or fact-dependent. Whenever a draft would state one of the following and the user didn't supply it, replace it with a verify-placeholder and keep the explanation intact:
- Citations — IRC section, Treas. Reg., Rev. Proc./Rul., notice, or state/FinCEN cite →
[verify citation] - Deadlines / due dates →
[verify current due date for tax year / return type / jurisdiction](dates shift for weekends, holidays, disaster relief, and vary by form, entity, and state) - Thresholds, rates, limits, penalties →
[verify tax-year figure](never state last year's number as current) - Eligibility / filing / nexus — reframe "qualifies / is required / has nexus / is deductible" to "likely / facts needed / verify current rule" unless the user supplied verified authority
- Dollar amounts the user didn't provide →
[amount] - Outcomes — never guaranteed savings, "audit-proof," or "will pass audit"
Boundaries
This is the accountant's own tax knowledge — within their license, they DO give tax advice, and this skill never interferes with that. It defers to the cpa-practice-standards skill for the narrow lines that leave tax and enter legal, securities/SEC, investment/RIA, audit-defense-beyond-scope, assurance/attestation, or credential-claim territory. Every output is a professional draft; the accountant applies current law to the client's actual facts and is the final reviewer.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.
Gives 0 of the 12 instructions most finance skills give in 669 tokens
Counted across 469 of the 469 authors here whose files we hold, read 2026-08-07
- Extract date vendor amount and descriptionin 15 of 469, across 3 files
- Scan folder for invoice filesin 14 of 469, across 2 files
- Rename files to standard formatin 14 of 469, across 2 files
- Show organization plan before movingin 14 of 469, across 2 files
- Generate summary CSVin 14 of 469, across 2 files
- Organize files by categoryin 13 of 469, across 1 file
- Preserve original filesin 13 of 469, across 1 file
- Flag files missing critical infoin 13 of 469, across 1 file
- Produce the requested output filein 9 of 469, across 4 files
- Build best, base, and worst case scenariosin 9 of 469, across 5 files
- Implement backoff if rate limit errors occurin 8 of 469, across 3 files
- Determine the weighted average cost of capitalin 8 of 469, across 4 files
Said here and by no other author read
- lead with the bottom line
- explain the underlying reasoning
- end with concrete next steps
- use the term deduction never write-off
- route legal-liability questions to an attorney
- replace unverified citations with a verify-placeholder
Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.