Individual skill
sageintacct-assistant
Sage Intacct ERP assistant for consultants and integrators. Use for anything Sage Intacct, even if the user only says "Intacct", an object name (APBILL, GLBATCH, SODOCUMENT, CUSTOMER, ITEM), a function (readByQuery, query, lookup), the xmlgw.phtml gateway, a sender ID, DTD 3.0, Platform Services, Smart Events or the REST API. Capabilities - (1) XML Web Services API integration development: generate and review XML requests and code from the bundled developer portal extraction, Sage's 3.0 request schema and a 2026 Release 3 object-definition snapshot: envelope, sessions, errors and recovery, query/readByQuery grammar and paging, formats, multi-entity, limits, 197 object pages (1,694 operations, parameter tables, examples) in 17 modules, 52 generic and 243 legacy functions, exact names and valid values for 632 objects (21,342 fields), Order Entry, Purchasing and Inventory guidance, and a 36-rule review checklist. The REST API is not reference-backed yet. Trigger on any Sage Intacct question.
skills/sageintacct-assistant/SKILL.md
Source commit d68ce04e18d0702432eaf5ec1bbead8e03d0fa79
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 7, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 10
- Repository last updated
- Oct 21, 2026
- License
- MIT
Observed agent integration: claude-code
- accpac Repository topic
- agent-skills Repository topic
- claude-code Repository topic
- claude-skills Repository topic
- erp Repository topic
- sage300 Repository topic
- sql-server Repository topic
- sapb1 Repository topic
- sapbusinessone Repository topic
- claude Repository topic
- engineering Derived category
- operations Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
.claude-plugin/plugin.jsonasset · 1,696 bytesMAINTENANCE.mddoc · 13,572 bytesREADME.mddoc · 4,831 bytesSKILL.mdcore · 16,913 bytesSKILL.mdcore · 16,913 bytesevals/evals.jsonasset · 10,335 bytesicon.pngasset · 99,173 bytesreferences/INDEX.mddoc · 1,346 bytesreferences/xml-api/INDEX.mddoc · 10,663 bytesreferences/xml-api/api-basics.mddoc · 26,552 bytesreferences/xml-api/common-mistakes.mddoc · 9,776 bytesreferences/xml-api/functions.mddoc · 50,714 bytesreferences/xml-api/objects.mddoc · 366,919 bytesreferences/xml-api/objects/accounts-payable.mddoc · 290,500 bytesreferences/xml-api/objects/accounts-receivable.mddoc · 278,432 bytesreferences/xml-api/objects/cash-management.mddoc · 173,849 bytesreferences/xml-api/objects/company-console.mddoc · 256,627 bytesreferences/xml-api/objects/consolidations.mddoc · 92,115 bytesreferences/xml-api/objects/construction.mddoc · 496,599 bytesreferences/xml-api/objects/contracts-rev-mgmt.mddoc · 312,640 bytesreferences/xml-api/objects/customization-services.mddoc · 20,051 bytesreferences/xml-api/objects/data-delivery-service.mddoc · 17,765 bytesreferences/xml-api/objects/employee-expenses.mddoc · 129,777 bytesreferences/xml-api/objects/general-ledger.mddoc · 321,364 bytesreferences/xml-api/objects/inventory-control.mddoc · 330,034 bytesreferences/xml-api/objects/order-entry.mddoc · 152,589 bytesreferences/xml-api/objects/platform-services.mddoc · 51,942 bytesreferences/xml-api/objects/project-resource-mgmt.mddoc · 159,272 bytesreferences/xml-api/objects/purchasing.mddoc · 210,348 bytesreferences/xml-api/objects/sales-tax-vat-gst.mddoc · 20,784 bytesreferences/xml-api/oe-po-inventory.mddoc · 15,782 bytesreferences/xml-api/snapshot/INDEX.mddoc · 2,523 bytesreferences/xml-api/snapshot/fields-01.mddoc · 998,504 bytesreferences/xml-api/snapshot/fields-02.mddoc · 999,330 bytesreferences/xml-api/snapshot/fields-03.mddoc · 441,472 bytesreferences/xml-api/snapshot/objects.mddoc · 73,481 bytesscripts/build_functions_reference.pyruns · 16,446 bytesscripts/build_object_snapshot.pyruns · 13,502 bytesscripts/build_xml_api_reference.pyruns · 24,279 bytesscripts/dump_object_definitions.pyruns · 24,209 bytesscripts/fetch_developer_portal.pyruns · 4,575 bytesscripts/package_skill.pyruns · 3,031 bytesscripts/test_build_object_snapshot.pyruns · 12,043 bytes
Read excerpt
# Sage Intacct Assistant
> **Version disclaimer:** the bundled references are an extraction of the **Sage Intacct developer portal**
> (developer.intacct.com, the XML API reference and guides) fetched on **2026-10-13** and of Sage's **DTD 3.0 request
> schema** (`api.xsd`, 2024-05-07), plus an **object-definition snapshot** (`inspect` and `lookup` results of a clean
> developer company on **2026 Release 3**, custom fields removed). The portal carries no release stamp, so names and
> rules are "as documented on that date"; Sage releases quarterly (2026 Release 3 went live 7 August 2026) and labels the XML API **"(Legacy)"**: new
> objects and features ship on the **REST API** (generally available since 2025 Release 1), which has no bundled
> reference yet. Every company differs in subscriptions, transaction definitions, custom fields, dimensions,
> entities and workflows, so tell the user to confirm names and allowed values with `lookup` / `inspect` on their
> company.
Reference-backed assistant for Sage Intacct consultants and integrators. The rule that makes it trustworthy:
**every material claim comes from a bundled reference and is cited**, never from memory alone. Object names, field