一键导入
myob-api-integration
Read-only MYOB AccountRight and Essentials API access for historical transaction data extraction
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Read-only MYOB AccountRight and Essentials API access for historical transaction data extraction
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | myob-api-integration |
| description | Read-only MYOB AccountRight and Essentials API access for historical transaction data extraction |
Provides read-only access to MYOB accounting data through the MYOB API. Extracts historical transactions, chart of accounts, contacts, and financial reports for tax analysis.
MYOB API → myob-adapter.ts → canonical-schema.ts → analysis engines
All MYOB data is normalised to the canonical schema (lib/integrations/canonical-schema.ts) before being consumed by analysis engines. This ensures all 16 engines work identically regardless of whether data comes from Xero, MYOB, or QuickBooks.
lib/integrations/adapters/myob-adapter.ts — MYOB API clientlib/integrations/myob-historical-fetcher.ts — Multi-year data synclib/integrations/canonical-schema.ts — Normalised data modellib/integrations/myob-config.ts — OAuth configurationapp/api/auth/myob/route.ts — OAuth 2.0 callbackAll access is read-only:
| MYOB Field | Canonical Field | Notes |
|---|---|---|
| UID | externalId | MYOB unique identifier |
| DisplayID | reference | Account/transaction code |
| Date | date | ISO 8601 |
| Total/Amount | amount | Decimal precision preserved |
| Account.DisplayID | accountCode | GL account code |
| Contact.DisplayID | contactId | Contact reference |
Route complex requests to the right specialist agent or chain of agents. This skill acts as the central brain of an agent swarm — it analyses what the user needs, determines which specialist domain(s) are required, and coordinates parallel or sequential agent execution. Use this skill when a request spans multiple domains (e.g., "research competitors and create a pitch deck"), when you need to decide which specialist should handle an ambiguous request, or when a task requires a multi-step pipeline across different skills. Triggers on: multi-step requests, cross-domain tasks, "coordinate", "plan this out", "I need help with multiple things", or any complex request that touches more than one specialist area. Also triggers when the user seems unsure which tool or approach to use.
>-
>-
>-
>-
Compare entity financial ratios against ATO small business benchmarks to assess audit probability