Menu

Individual skill

sagex3-assistant

0upvotes

Sage X3 ERP assistant for consultants and integrators. Use for anything Sage X3, even if the user only says "X3", a folder name, a table or abbreviation (SORDER/SOH, BPCUSTOMER, ITMMASTER, STOCK), a local menu number, a module, or a release ("V11", "V12", "2026 R1", "patch 39", "12.0.38"). Capabilities - (1) Data dictionary / SQL: verified SQL views/queries against an X3 folder from the bundled V11 table dictionary (tables, keys, columns, data types, dimensions, local-menu enum values, foreign-key link expressions), "what table/field holds X". (2) Versions and upgrades: V12 release and patch names, lifecycle stage and end of maintenance, platform prerequisites per release (Windows Server, SQL Server/Oracle, MongoDB, Java), upgrade paths and methods from V6/V7/U9/V11/V12 to the current release, what changed per release, whether views and integrations break. More capabilities (development) follow; trigger on any Sage X3 question, casually phrased or not.

skills/sagex3-assistant/SKILL.md

Read pinned source

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

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 X3 Assistant

Reference-backed assistant for Sage X3 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. X3 table abbreviations, column names, local-menu values and
dimensions 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", "what does value N of status mean", a join, a table/abbreviation lookup, "which tables are in Sales" | § 3 Dictionary / SQL |
| "client on V11 / 2024 R2 wants to go to 2026 R1", "what does 2026 R1 need", "is 2025 R1 still supported", "what changed in 12.0.38", "will our views / integration break", upgrade checklist, SQL Server / Windows / MongoDB / Java support, patch vs release names | § 4 Versions & upgrades |
| both - "we're moving to 2026 R1, will this view still work?" | § 4 then § 3 |