Skip to content
Back to skills

Accounting

ASecurity

Support accounting understanding from basic bookkeeping to professional practice and research.

  • 17 stars
  • 0 votes
  • 0 copies
  • 5 views
  • Added May 27, 2026
businessgoawsapi

Works with

  • cli
  • api

Security analysis

A100/100

Pro scans all 2 files and shows the line behind each finding

Scanned May 27, 2026

npx -y skills add clawic/skills --skill accounting --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Accounting?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Accounting
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/clawic-accounting/badge)](https://www.skillsdirectory.com/skills/clawic-accounting)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: Accounting
description: Support accounting understanding from basic bookkeeping to professional practice and research.
metadata: {"clawdbot":{"emoji":"πŸ“’","os":["linux","darwin","win32"]}}
---

## Detect Level, Adapt Everything
- Context reveals level: vocabulary, transaction complexity, professional credentials
- When unclear, ask about their role before giving specific guidance
- Always ask jurisdiction and entity type before tax or standards advice

## For Small Business Owners: Clarity Without Complexity
- Explain financial statements in practical terms β€” "Accounts receivable growing faster than revenue means clients are paying slowerβ€”cash problems in 60-90 days"
- Warn about mixing personal and business finances β€” probe for red flags: personal cards for business, no separate account; explain audit risk and 3x tax prep cost
- Ask jurisdiction and entity type first β€” sole proprietor, LLC, S-corp, C-corp? Tax obligations vary dramatically
- Teach the progression β€” separate bank account, categorize weekly not yearly, simple software (Wave, QuickBooks), reconcile monthly; don't overwhelm with complexity
- Provide clear "hire a professional" triggers β€” revenue over $75K, multiple income streams, employees, IRS notices, or more than 5 hours/month hating bookkeeping
- Demystify estimated taxes β€” if owing >$1,000, pay quarterly; 90% of current year OR 100% of last year avoids penalties; give specific deadlines
- Flag expensive mistakes with dollar impact β€” missing deductions ($5K-15K/year), misclassifying employees (100% penalty), not tracking mileage ($3K/year lost)
- Recommend weekly ritual over year-end heroics β€” 15 minutes Friday to categorize beats 20 hours reconstructing; year-end reconstruction loses deductions

## For Students: Foundations and Rigor
- Show complete journal entries β€” debits first, credits indented, account names, amounts, narration; proper format professors expect
- State GAAP or IFRS when treatment differs β€” LIFO, R&D capitalization, lease classification; clarify which standard the course follows
- Reinforce fundamental equation β€” A = L + E; trace every entry: debits increase assets/expenses, credits increase liabilities/equity/revenue
- Distinguish accrual vs cash explicitly β€” when is revenue "earned" vs cash "received"; use timeline examples ("service Dec 15, payment Jan 10")
- Walk through full cycle β€” unadjusted trial balance β†’ adjustments β†’ adjusted trial balance β†’ statements β†’ closing entries β†’ post-closing
- Flag common student errors β€” depreciation expense vs accumulated depreciation; AP vs notes payable; forgetting to reverse accruals; draws as expense
- Explain the "why" behind treatments β€” matching principle for depreciation; conservatism for lower-of-cost-or-market; students need reasoning not just rules
- Specify statement and normal balance β€” which statement, current vs non-current, operating vs financing; exams test proper presentation

## For Professionals: Standards and Judgment
- Clarify framework first β€” US GAAP, IFRS, or local GAAP; flag material differences (LIFO, leases, development costs)
- Apply revenue recognition properly β€” 5-step model (ASC 606/IFRS 15): contract, obligations, price, allocation, recognition; never one-liner answers
- Handle leases precisely β€” finance vs operating under GAAP; IFRS 16 treats nearly all as finance for lessees; prompt for term, rate, options, modifications
- Map entity relationships for consolidation β€” ownership %, voting rights, control indicators, VIE; distinguish full consolidation vs equity method
- Maintain audit-ready standards β€” structure by assertions (existence, completeness, valuation, rights, presentation); reference ASC/IFRS paragraphs
- Apply professional skepticism β€” probe for related parties, side agreements, unusual terms; ask materiality before detailed analysis
- Respect ethics and liability β€” never definitive "book X" without disclaiming; flag when external consultation required; refuse earnings management structures
- Flag uncertainty and currency β€” guidance changes (ASUs, IASB amendments); distinguish authoritative vs interpretive; present alternatives when defensible

## For Researchers: Rigor and Evidence
- Distinguish positive from normative β€” does question explain/predict (positive) or prescribe (normative)? Flag when users conflate
- Apply appropriate methodology β€” archival methods, experimental designs, analytical modeling; cite Watts & Zimmerman, Ball & Brown
- Reference tier-1 journal standards β€” TAR, JAR, JAE, CAR, RAS, AOS; explain methodological preferences and review expectations
- Present standard-setting debates with nuance β€” FASB/IASB gaps, fair value controversies, ESG/sustainability mandates; acknowledge trade-offs
- Maintain causal skepticism β€” emphasize identification strategies, endogeneity, selection bias; distinguish correlation from causation
- Engage academic-practice tension β€” acknowledge when findings conflict with practitioner norms; discuss relevance gap
- Cite foundational and current literature β€” Jensen & Meckling, Healy & Wahlen, Dechow; indicate contested or superseded findings
- Recognize international diversity β€” avoid US-GAAP-centric assumptions; enforcement and practice vary by jurisdiction

## For Educators: Concepts and Exams
- Teach double-entry logic before mechanics β€” trace every entry back to accounting equation; build intuition not just memorization
- Use progressive complexity β€” simple cash transactions before accruals; single-step statements before multi-step; basic before complex
- Prepare for CPA/CMA explicitly β€” flag heavily tested topics; explain exam format; provide practice questions matching actual difficulty
- Connect rules to real situations β€” show how textbook entries appear in actual financial statements and software

## For Bookkeepers: Daily Transactions
- Ask for source document first β€” invoice, receipt, bank statement; never create entries from verbal descriptions alone
- Clarify ambiguous categorization β€” "Is this $500 for supplies (expense) or equipment (asset)? Capitalization threshold is typically $2,500"
- Guide reconciliation step-by-step β€” ending bank balance, add deposits in transit, subtract outstanding checks, compare to book balance
- Provide troubleshooting sequence β€” difference divisible by 9 (transposition), half the difference (wrong direction), exact amount in uncleared items
- Warn about duplicates β€” "I see matching vendor + amount + dateβ€”is this the same transaction?"
- Catch posting mistakes β€” prior period dates, round number estimates needing follow-up
- Adapt to specific software β€” provide exact menu paths for QuickBooks Online, Xero, Desktop; never generic instructions

## Always
- Distinguish rules from judgment areas; accounting often requires professional assessment
- Flag when standards may have changed; effective dates matter
- Separate authoritative guidance from common practice
- Never provide tax advice without jurisdiction and entity type confirmation

Files in this skill

  • SKILL.md6.9 KB
  • _meta.json172 B

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…