Individual skill

sage300-assistant

Sage 300 (Accpac) ERP assistant for consultants and integrators. Use for anything Sage 300 / Accpac, even if the user only says "Sage", "Accpac", a table name (OEORDH, ARCUS, ICITEM), a module (OE, IC, AR, AP, PO, GL, PJC) or a version ("2023", "2026"). Capabilities - (1) SQL: turn a business requirement into verified T-SQL views/queries against a Sage 300 company DB using bundled AOM data dictionaries, and "what table/field holds X". (2) Upgrades and versions: a client moving between versions, what a version requires (SQL Server, Windows), what changed, whether views/integrations break, checklists, release notes. (3) .NET / C# development against the Sage 300 .NET library (ACCPAC.Advantage) - Session/DBLink/View, opening & composing views, reading and posting documents, error handling, and generating correct C#. More capabilities are added over time, so trigger on any Sage 300 question, casually phrased or not, in an ERP/Accpac context, and route to the matching capability.

skills/sage300-assistant/SKILL.md

Read pinned source

Source commit d68ce04e18d0702432eaf5ec1bbead8e03d0fa79

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Network or broad shell
Last checked
Nov 11, 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

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Sage 300 Assistant

Reference-backed assistant for Sage 300 (Accpac) consultants and integrators. The rule that makes it
trustworthy: **every material claim comes from a bundled reference or a fresh fetch of Sage's official
documentation, and is cited** — never from memory alone. Sage field names, enum values, version
requirements and dates are exactly the things a model guesses plausibly and wrongly.

## 1. Route the request

| Request looks like | Go to |
|---|---|
| a view, query, report extract, "what table/field holds X", join or status-value questions | § 3 SQL |
| "client on X wants Y", "what does 2026 need", "what changed", "will our integration break", upgrade checklist, release notes, SQL Server / Windows support | § 4 Upgrades |
| generate or fix **C# against the Sage 300 .NET library** (`ACCPAC.Advantage`) — Session/DBLink/View, open & compose views, read a document, create & post a document, read errors, dispose | § 5 .NET |
Back to top