Install
$ agentstack add skill-rondoflow-rondoflow-accounting-practice-learning-guide ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: rondoflow
- Source: rondoflow/rondoflow
- License: MIT
- Homepage: https://rondoflow.app
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.