teamtinvio/jaz-practice
src/skills/practice/SKILL.md
Use this skill whenever an accounting practitioner is doing client work in Jaz — closing the books, filing GST, year-end statutory, onboarding a new client. Covers the practitioner workspace at ~/Documents/Jaz Practice (clients/<slug>/CLIENT.md and engagements/<slug>/ENGAGEMENT.md), engagement routing (monthly-close | quarterly-gst | annual-statutory | onboarding | adhoc), and how the agent loads client context before invoking jaz-jobs blueprints, jaz-recipes recipes, and jaz-api tools. Triggers on intent like "close the books for X", "file GST for Y", "onboard new client Z", "what's outstanding for Acme this month". Pair with jaz-jobs (workflow blueprints), jaz-recipes (IFRS recipes + calculators), jaz-api (REST gotchas), and jaz-conversion (data migration during onboarding).
$ install --global
skillsauthnpx skillsauth add teamtinvio/jaz-ai jaz-practiceInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: Jun 2, 2026, 3:34 AM124.2s8 files scanned
SKILL.md
- name:
- jaz-practice
- version:
- 5.13.9
- description:
- >-
- jaz-jobs:
- >=5.1
- jaz-recipes:
- >=5.1
- jaz-api:
- >=5.1
- jaz-conversion:
- >=5.1
- jaz-cli:
- >=5.1
jaz-practice
Practitioner-side scaffolding. The agent's entry point when an accountant is doing client work in Jaz.
When to Use This Skill
Load jaz-practice when the user's intent is practitioner-shaped — closing the books, filing GST/VAT, year-end statutory, onboarding a new client, mid-quarter review for a specific client. The skill's job is to LOAD CONTEXT (CLIENT.md + ENGAGEMENT.md) before routing the actual accounting work to jaz-jobs (close playbooks), jaz-recipes (IFRS recipes), jaz-conversion (data migration), or jaz-api (raw endpoints).
Trigger phrases: "close the books for X", "file GST for Y", "onboard new client Z", "what's outstanding for Acme this month", "Acme — quarterly close", "year-end statutory for X". When in doubt: if the user names a client or an engagement-type ("monthly close", "GST", "year-end"), load this skill first.
Mental model
| Engineer (cct-toolkit) | Practitioner (jaz-practice) | |-------------------------|------------------------------| | Workspace = a feature being built | Workspace = a client being served | | Sub-folder = task category | Sub-folder = engagement type (recurring/special) | | FEATURE.md hub | CLIENT.md (master) + ENGAGEMENT.md (per-engagement) | | Decisions = architecture | Decisions = accounting treatment (estimate, classification, scope) | | Done = PR merged | Done = engagement signed-off, period locked, deliverable filed |
The persistent unit is the client, not the project. Engineering features come and go; clients accumulate over years. The folder structure must support: historical immutability (last year's audit file is sacred), recurring rhythm (monthly close, quarterly GST), ad-hoc work (M&A, restructuring), and cross-engagement context (the same client's tax position informs their audit risk).
Folder layout
~/Documents/Jaz Practice/ ← override with PRACTICE_HOME env or --root
PRACTICE.md ← firm-level config (one-time)
templates/ ← practitioner-overridable copies of engagement templates
clients/<client-slug>/
CLIENT.md ← master file: legal entity, FY, GST, COA, banks, recurring accruals, materiality
engagements/<engagement-slug>/
ENGAGEMENT.md ← per-engagement: type, period, status, scope, queries, decisions, journal
inputs/ ← raw client docs (statements, invoices, receipts)
workpapers/ ← TBs, analyses, sample selections
deliverables/ ← signed reports, filed returns, board packs
recurring/{monthly,quarterly,annual}/<period>/ ← close packages, GST returns, statutory
correspondence/ ← IRAS letters, ACRA notices
_archive/ ← closed engagements, prior periods
See references/client-md-schema.md and references/engagement-md-schema.md for the full field-by-field schema.
Engagement-type routing (the agent's first move)
When the practitioner expresses intent, route to the right engagement type and load the matching deep reference:
| Practitioner says... | Engagement type | Deep reference | Driver tools |
|----------------------|-----------------|----------------|---------------|
| "Close the books for <client> <month>" | monthly-close | references/monthly-close.md | generate_month_end_blueprint + accrual / depreciation / fx-reval recipes |
| "File GST/F5 for <client> <quarter>" | quarterly-gst | references/quarterly-gst.md | generate_gst_vat_blueprint + generate_vat_ledger |
| "Year-end / annual / statutory for <client>" | annual-statutory | references/annual-statutory.md | generate_year_end_blueprint + generate_audit_prep_blueprint + generate_statutory_filing_blueprint |
| "Onboard <new client>" / "Take over from <prior firm>" | onboarding | references/onboarding.md | practice_onboard_client + jaz-conversion if migrating |
| Anything else | adhoc | (no reference) | Whatever the practitioner names |
How the agent works inside jaz-practice
- Detect the practitioner workspace. If
~/Documents/Jaz Practice/exists (orPRACTICE_HOMEis set), callpractice_list_clientsfirst to surface the available client slugs. If the practitioner's intent names a client, slug it and callpractice_load_client. - One key per session. v5.2.0 uses a single
JAZ_API_KEYper Claude session (set once in connector / settings / env). TheCLIENT.md.jaz_api_key_overridefield is reserved for v5.3 multi-org runtime selection — not yet wired. Don't prompt the practitioner to re-enter a key per client. For multi-org agencies today: use one Jaz org per Claude session and switch sessions when switching orgs. - Anchor work in an engagement. Either find the active engagement for the period (in
practice_load_client's response) or create one withpractice_create_engagement(clientSlug, type, period). The engagement folder gets the type-specific template. - Follow the deep reference. Load
references/<type>.mdfor the canonical playbook — it names every tool / recipe / calculator and every CLIENT.md / ENGAGEMENT.md field. - Surface, don't dump. When invoking blueprints or running reports, surface to the practitioner: top 3 exceptions, top 3 unreconciled items, top 3 unresolved queries. Save full output to
workpapers/<task>.md. - Append progress to ENGAGEMENT.md daily journal so resuming the next session doesn't redo yesterday's work.
- Transition status only when the scope checklist is complete. Don't mark
signed-off/filed/archivedwhile items remain unticked.
Key principle: jaz-practice routes, it does NOT duplicate
The 6 practice_* MCP tools and the CLI command group are filesystem scaffolding only. They never call the Jaz API. All real accounting work goes through:
- jaz-jobs for workflow blueprints (12 playbooks)
- jaz-recipes for IFRS-compliant transaction modeling (16 recipes + 13 calculators)
- jaz-api for direct REST API operations (266 tools, error/field gotchas)
- jaz-conversion for data migration during onboarding
- jaz-cli for terminal-first power users (script automation)
If you find yourself wanting a new "do this accounting work" tool inside jaz-practice, stop — extend the existing skill instead, and add a cross-reference here.
Out of scope
This skill is intentionally focused on accounting workflows. Out of scope:
- KYC / AML / beneficial ownership (firm administration, not accounting work)
- Engagement letters, fee structures, billing rates
- Sign-off log mechanics, partner-review thresholds
- Practice management overhead (CRM, time tracking, invoicing the firm's clients for fees)
Related
jaz-jobs/SKILL.md— 12 workflow blueprints (cross-referenced from each engagement-type playbook)jaz-recipes/SKILL.md— 16 IFRS recipes + 13 calculatorsjaz-api/SKILL.md— REST API gotchasjaz-conversion/SKILL.md— Xero/QB/Sage/MYOB migration playbookjaz-cli/SKILL.md— terminal automation referencereferences/monthly-close.md— canonical monthly-close playbookreferences/quarterly-gst.md— canonical GST/F5 playbookreferences/annual-statutory.md— canonical year-end playbookreferences/onboarding.md— canonical new-client playbookreferences/client-md-schema.md— every CLIENT.md fieldreferences/engagement-md-schema.md— every ENGAGEMENT.md fieldreferences/troubleshooting.md— common error classes + recovery actions
Related Skills
teamtinvio/jaz-pseudo-sql
tools
VerifiedTrustedCommunity
Use this skill when answering ad-hoc data questions that aren't covered by download_export (canonical reports — anomaly, audit, aging, P&L, BS, GL, statement of account) or search_* tools (entity listings with structured filters). Pseudo-SQL is a read-only DSL against Jaz's curated reporting schema — single SELECT statement, ≤100 row sync preview or full async CSV export. Tools: get_pseudo_sql_schema (call FIRST — returns live catalog + downloadable jaz-pseudo-sql.md skill body), preview_pseudo_sql, export_pseudo_sql, get_pseudo_sql_export, run_pseudo_sql_and_download.
4SKILL.mdUpdated May 27, 2026
teamtinvio/jaz-pseudo-sql
tools
VerifiedTrustedCommunity
Use this skill when answering ad-hoc data questions that aren't covered by download_export (canonical reports — anomaly, audit, aging, P&L, BS, GL, statement of account) or search_* tools (entity listings with structured filters). Pseudo-SQL is a read-only DSL against Jaz's curated reporting schema — single SELECT statement, ≤100 row sync preview or full async CSV export. Tools: get_pseudo_sql_schema (call FIRST — returns live catalog + downloadable jaz-pseudo-sql.md skill body), preview_pseudo_sql, export_pseudo_sql, get_pseudo_sql_export, run_pseudo_sql_and_download.
4SKILL.mdUpdated May 27, 2026
teamtinvio/jaz-practice
tools
VerifiedTrustedCommunity
Use this skill whenever an accounting practitioner is doing client work in Jaz — closing the books, filing GST, year-end statutory, onboarding a new client. Covers the practitioner workspace at ~/Documents/Jaz Practice (clients/<slug>/CLIENT.md and engagements/<slug>/ENGAGEMENT.md), engagement routing (monthly-close | quarterly-gst | annual-statutory | onboarding | adhoc), and how the agent loads client context before invoking jaz-jobs blueprints, jaz-recipes recipes, and jaz-api tools. Triggers on intent like "close the books for X", "file GST for Y", "onboard new client Z", "what's outstanding for Acme this month". Pair with jaz-jobs (workflow blueprints), jaz-recipes (IFRS recipes + calculators), jaz-api (REST gotchas), and jaz-conversion (data migration during onboarding).
4SKILL.mdUpdated May 5, 2026
teamtinvio/jaz-recipes
development
VerifiedTrustedCommunity
Use this skill when modeling complex multi-step accounting transactions — anything that spans multiple periods, involves changing amounts, or requires linked entries. Covers 16 IFRS-compliant recipes (prepaid amortization, deferred revenue, loans, IFRS 16 leases, hire purchase, fixed deposits, asset disposal, FX revaluation, ECL, IAS 37 provisions, dividends, intercompany, capital WIP) and 13 financial calculators that produce execution-ready blueprints. Also use when the user mentions depreciation, amortization, lease accounting, loan schedules, or any IFRS calculation.
4SKILL.mdUpdated Apr 30, 2026