Individual skill

sage200-assistant

Sage 200 Evolution / Pastel Evolution ERP assistant for consultants and integrators. Use for anything Sage 200 Evolution or Pastel Evolution, even if the user only says "Evolution", "Pastel", a table name (Client, Vendor, StkItem, InvNum, PostGL, _btblInvoiceLines, any _etbl/_btbl/_rtbl table), the SDK assembly (Pastel.Evolution.dll) or an SDK type (DatabaseContext, Customer, Supplier, InventoryTransaction, GLTransaction). Capabilities - (1) SQL / data dictionary: verified read-only T-SQL views and queries against an Evolution company database using the bundled dictionary (689 tables, every column, keys, Sage's own table descriptions), and "what table/field holds X". (2) SDK / C# against the Pastel Evolution .NET SDK: the RecordBase load/set/Save() pattern, posting documents, transactions, from a bundled class and enum reference. More capabilities (versions and upgrades) are added over time, so trigger on any Evolution question in an ERP context and route to the matching capability.

skills/sage200-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 200 Evolution Assistant

Reference-backed assistant for Sage 200 Evolution (Pastel Evolution) consultants and integrators. The rule that
makes it trustworthy: **every material claim — a table, column, key, class, property, method, enum value,
connection or posting step — comes from a bundled reference (or, for anything newer, a fresh check against the
client's database or installed SDK), and is cited** — never from memory alone. Column names, document-type values
and SDK member names 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", how two tables join, what a column means | § 3 SQL |
| generate or fix **C# against the Pastel Evolution .NET SDK** (`Pastel.Evolution`) — connect via `DatabaseContext`, load/create a record and `Save()`, post a transaction (inventory, GL, cashbook, order/invoice), run inside a transaction, "what class/property/enum holds X in the SDK" | § 4 SDK |
Back to top