@gonzih/skills-accounting 1.0.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 gonzih
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -0,0 +1,36 @@
+# skills-accounting
+
+Claude Code skills for accountants, CPAs, and bookkeepers.
+
+## Install
+
+```bash
+npx @gonzih/skills-accounting
+```
+
+Then restart Claude Code.
+
+## Skills
+
+| Skill | Invoke | What it does |
+|---|---|---|
+| `tax-memo` | `/tax-memo` | Write a tax research memo: issue, facts, law, analysis, conclusion, client summary |
+| `client-advisory-letter` | `/client-advisory-letter` | Write a client advisory letter: plain-language explanation, implications, recommended actions |
+| `audit-finding-summary` | `/audit-finding-summary` | Summarize an audit finding: condition, criteria, cause, effect, recommendation, management response template |
+| `engagement-letter` | `/engagement-letter` | Draft an engagement letter: scope, fees, timing, client responsibilities, standard terms |
+
+## Usage examples
+
+```
+/tax-memo Does our client's home office qualify for the Section 280A deduction?
+
+/client-advisory-letter The new beneficial ownership reporting requirements under the Corporate Transparency Act
+
+/audit-finding-summary We found 12 of 40 purchase orders lacked required dual approval signatures
+
+/engagement-letter Prepare a 2025 Form 1120S for an S-corp client, fixed fee
+```
+
+## License
+
+MIT

package/install.js

@@ -0,0 +1,15 @@
+#!/usr/bin/env node
+import { copyFileSync, mkdirSync, existsSync } from 'fs';
+import { join } from 'path';
+import { homedir } from 'os';
+
+const skillsDir = join(homedir(), '.claude', 'skills');
+const skills = ['tax-memo', 'client-advisory-letter', 'audit-finding-summary', 'engagement-letter'];
+
+for (const skill of skills) {
+  const dest = join(skillsDir, skill);
+  if (!existsSync(dest)) mkdirSync(dest, { recursive: true });
+  copyFileSync(new URL(`./skills/${skill}/SKILL.md`, import.meta.url).pathname, join(dest, 'SKILL.md'));
+  console.log(`✓ Installed /${skill}`);
+}
+console.log('\nSkills installed! Restart Claude Code to use them.');

package/package.json

@@ -0,0 +1,33 @@
+{
+  "name": "@gonzih/skills-accounting",
+  "version": "1.0.0",
+  "description": "Claude Code skills for accountants, CPAs, and bookkeepers: tax-memo, client-advisory-letter, audit-finding-summary, engagement-letter",
+  "type": "module",
+  "bin": {
+    "skills-accounting": "./install.js"
+  },
+  "scripts": {
+    "postinstall": "node install.js"
+  },
+  "files": [
+    "skills/",
+    "install.js",
+    "README.md",
+    "LICENSE"
+  ],
+  "keywords": [
+    "claude-code",
+    "claude",
+    "skills",
+    "accounting",
+    "tax",
+    "audit",
+    "cpa",
+    "bookkeeping"
+  ],
+  "author": "gonzih",
+  "license": "MIT",
+  "engines": {
+    "node": ">=18"
+  }
+}

package/skills/audit-finding-summary/SKILL.md

@@ -0,0 +1,39 @@
+---
+name: audit-finding-summary
+description: Summarize an audit finding using the standard condition, criteria, cause, effect, and recommendation framework, plus a management response template.
+triggers: ["summarize an audit finding", "audit finding summary", "write up an audit finding"]
+---
+
+# Audit Finding Summary
+
+## What this skill does
+Produces a structured audit finding write-up using the five-element framework standard in governmental and internal auditing: condition (what was found), criteria (what should be), cause (why it happened), effect (the risk or impact), and recommendation (what should change). Also generates a management response template for the auditee to complete. Output is suitable for inclusion in an audit report.
+
+## How to invoke
+/audit-finding-summary [finding description]
+
+## Workflow steps
+
+### Step 1 — Understand the finding
+Ask for or extract the key facts: what was observed, in which process or account, over what period, and with what frequency or dollar amount. If the user provides a rough description, identify any missing elements needed to complete the five-element write-up.
+
+### Step 2 — Draft the Condition
+Write a factual, objective description of what the auditors observed. Use specific numbers, dates, and examples where available. Avoid judgment language — state facts only.
+
+### Step 3 — State the Criteria
+Identify the standard, policy, regulation, contract, or best practice against which the condition is measured. Cite the source (e.g., "Per the organization's Procurement Policy, Section 4.2..." or "As required by 2 CFR Part 200...").
+
+### Step 4 — Identify the Cause
+Explain the root cause of the condition — why the gap between the condition and the criteria exists. Distinguish between systemic causes (control design failures) and isolated causes (one-time errors).
+
+### Step 5 — Describe the Effect
+Quantify and qualify the risk or impact: financial exposure, compliance risk, operational inefficiency, or reputational harm. Use specific dollar amounts or percentages where possible.
+
+### Step 6 — Write the Recommendation
+Provide a clear, actionable recommendation addressed to management. Focus on correcting the root cause, not just the symptom. Number recommendations if there are multiple.
+
+### Step 7 — Generate the Management Response template
+Produce a fillable template for management to: agree or disagree with the finding, describe their corrective action plan, assign a responsible party, and commit to a target completion date.
+
+## Example outputs
+A structured finding write-up (Condition / Criteria / Cause / Effect / Recommendation) of approximately 300–500 words, followed by a management response block with labeled fields for management to complete.

package/skills/client-advisory-letter/SKILL.md

@@ -0,0 +1,33 @@
+---
+name: client-advisory-letter
+description: Write a client advisory letter on a financial or tax topic with a plain-language explanation, implications for the client, and recommended actions.
+triggers: ["write a client advisory letter", "client advisory letter", "draft an advisory letter for a client"]
+---
+
+# Client Advisory Letter
+
+## What this skill does
+Drafts a professional client advisory letter suitable for sending on firm letterhead. The letter explains a financial, tax, or regulatory development in plain language, describes how it affects the specific client, and closes with clear recommended actions and next steps. The tone is authoritative but accessible — no jargon without explanation.
+
+## How to invoke
+/client-advisory-letter [topic or financial issue]
+
+## Workflow steps
+
+### Step 1 — Clarify the topic and client context
+Identify the financial or tax topic to address. If not provided, ask for: the client's name (or placeholder), entity type, relevant background, and what the advisor wants the client to understand or do.
+
+### Step 2 — Write the opening and context
+Open with a brief statement of purpose. Provide enough background on the topic (e.g., a law change, a market development, a planning opportunity) that the client understands why the letter is relevant to them.
+
+### Step 3 — Explain the implications for the client
+Describe specifically how this topic affects the client's situation — taxes owed, cash flow, compliance obligations, risk exposure, or planning opportunities. Keep language concrete and avoid unnecessary hedging.
+
+### Step 4 — Recommend actions
+List clear, prioritized actions the client should take. Include deadlines where applicable. Distinguish between actions the firm will handle and actions the client must take themselves.
+
+### Step 5 — Close professionally
+Include a standard closing: an invitation to contact the firm with questions, a disclaimer that the letter is for informational purposes and does not constitute legal advice, and a signature block placeholder.
+
+## Example outputs
+A 1–2 page letter addressed to a named client, structured as context → implications → recommended actions → close, suitable for email delivery or mailing on firm letterhead.

package/skills/engagement-letter/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: engagement-letter
+description: Draft an engagement letter covering scope of services, fees, timing, client responsibilities, and standard terms.
+triggers: ["draft an engagement letter", "write an engagement letter", "engagement letter"]
+---
+
+# Engagement Letter
+
+## What this skill does
+Drafts a professional engagement letter between an accounting or advisory firm and a client. Covers scope of services, fee structure, engagement timeline, client responsibilities, and standard terms (limitations of liability, dispute resolution, confidentiality). Output is suitable for review by counsel before use and can serve as the basis for a signed agreement.
+
+## How to invoke
+/engagement-letter [service type and client details]
+
+## Workflow steps
+
+### Step 1 — Gather engagement details
+If not provided, ask for: firm name, client name and entity type, services to be performed (e.g., tax return preparation, audit, bookkeeping, advisory), the engagement period, fee structure (fixed, hourly, retainer), and any known special terms or prior relationship context.
+
+### Step 2 — Draft the opening and parties section
+Identify the parties, the date, and the purpose of the letter. State clearly that the letter constitutes the agreement between the firm and the client for the described services.
+
+### Step 3 — Define the scope of services
+List the specific services the firm will provide. Be explicit about what is included and, where helpful, what is excluded. Avoid vague language like "assist with" — use specific deliverables and service descriptions.
+
+### Step 4 — State fees and billing terms
+Describe the fee structure clearly: fixed fee, hourly rate, retainer amount, or blended arrangement. Include billing frequency, payment due dates, late payment terms, and handling of out-of-pocket expenses.
+
+### Step 5 — Outline timing and deliverables
+State the expected timeline, key milestones, and delivery dates. Note dependencies on client-provided information.
+
+### Step 6 — State client responsibilities
+List what the client must provide or do: timely delivery of records, access to personnel, approval of drafts, maintenance of underlying books and records. Clarify that the firm relies on client-provided information.
+
+### Step 7 — Include standard terms
+Draft standard boilerplate: limitation of liability (cap on firm's liability), dispute resolution (mediation/arbitration clause), confidentiality, document retention, termination rights, and governing law. Flag that these terms should be reviewed by the firm's legal counsel before use.
+
+### Step 8 — Close with signature block
+Include a signature block for both parties: authorized firm representative and client. Include a line for the client to acknowledge and return the letter.
+
+## Example outputs
+A 2–4 page engagement letter in formal business letter format with clearly labeled sections, ready for the firm's attorney to review and adapt to their jurisdiction and professional standards.

package/skills/tax-memo/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: tax-memo
+description: Write a structured tax research memo covering issue, facts, applicable law, analysis, conclusion, and a client-friendly summary.
+triggers: ["write a tax memo", "tax research memo", "draft a tax memo"]
+---
+
+# Tax Memo
+
+## What this skill does
+Produces a formal tax research memo organized into standard sections: issue presented, relevant facts, applicable law (IRC sections, regulations, rulings, case law), legal analysis, conclusion, and a plain-language client summary. The memo follows the structure used by CPA firms and tax counsel for documentation and opinion support.
+
+## How to invoke
+/tax-memo [topic or issue]
+
+## Workflow steps
+
+### Step 1 — Identify the issue
+Clarify the specific tax question or questions to be addressed. If the user has not provided enough facts, ask for the client's situation, entity type, transaction details, and relevant dates.
+
+### Step 2 — Gather facts
+Summarize the relevant facts as provided. Flag any missing information that would affect the analysis and note assumptions made.
+
+### Step 3 — Research applicable law
+Identify and cite the governing authority: Internal Revenue Code sections, Treasury Regulations, Revenue Rulings, Revenue Procedures, IRS notices, and relevant Tax Court or Federal Circuit decisions. Note the weight of authority (primary vs. secondary).
+
+### Step 4 — Analyze the law against the facts
+Apply the cited authorities to the specific facts. Address favorable and unfavorable authority. Identify planning opportunities or risk areas. Note any open questions or areas of uncertainty.
+
+### Step 5 — State the conclusion
+Provide a clear conclusion for each issue with a confidence level (e.g., should, more likely than not, could). Recommend any protective actions such as disclosures or elections.
+
+### Step 6 — Write the client-friendly summary
+Translate the conclusion into plain language the client can understand. Avoid jargon. State what it means for them and what (if anything) they need to do.
+
+## Example outputs
+A memo with headed sections — Issue, Facts, Law, Analysis, Conclusion, Client Summary — suitable for inclusion in a client file, shared with counsel, or used to support a tax return position.