Ask an AI assistant to write you a WebSocket client in Delphi and it will produce something confident, well structured, and subtly wrong. A property that does not exist. A component placed in the wrong unit. An API that was removed three releases ago. Then you spend twenty minutes finding out which of the four plausible lines is the one that does not compile.
The reason is simple. These models learned from public code, and the eSeGeCe components are commercial, so the model has never read them. It knows the shape of a Delphi component library and fills in the rest from memory of other libraries.
We have published agent skills to close that gap. They are free, MIT licensed, and you do not need a licence to install them.
What an agent skill is
A skill is a folder of Markdown that an agent loads on demand. Ours carry the public API of each library: every component, its properties, events and methods, the unit or namespace it lives in, the edition that includes it, and real examples taken from the demos that ship with the product. They are generated from the library source at every release, so they describe the version you actually have rather than the one the model half remembers.
Everything lives in one repository, github.com/esegece-com/agent-skills, packaged as six plugins.
Installing them
In Claude Code and GitHub Copilot CLI, add the marketplace once and install the plugins you want:
/plugin marketplace add esegece-com/agent-skills
/plugin install sgcwebsockets-delphi@esegeceIn Codex CLI:
codex plugin marketplace add esegece-com/agent-skills
codex plugin add sgcwebsockets-delphi@esegeceIn VS Code, open the Command Palette and run "Chat: Install Plugin From Source". For Cursor and any other agent that reads a skills folder, copy the skill folder out of the repository into .cursor/skills/, .claude/skills/, .github/skills/, .agents/skills/ or .junie/skills/, depending on the agent.
The six plugins are sgcwebsockets-delphi, sgcwebsockets-dotnet, sgcsign-delphi, sgcopenapi-delphi, sgcindy-delphi and sgcbiometrics-delphi.
Why sgcWebSockets is 18 skills, not one
sgcWebSockets registers 222 components. One skill covering all of them would be too large to be useful: the agent would load the whole library to answer a question about MQTT. So it is split by area, 18 skills covering the WebSocket core, message brokers, the sgc subprotocols, exchange feeds, AI and LLM, service integrations, HTTP and transports, authentication, P2P and WebRTC, IoT, and six more for the sgcHTML widgets.
An agent asked to connect to an MQTT broker loads the message broker skill and nothing else. The .NET plugin follows the same idea with 7 skills.
What is inside one
Each skill opens with a hand-written playbook: what the skill is for, the uses clause or using directive you need, the questions worth asking the developer before writing any code, and the mistakes that actually catch people out. After that comes the generated material, the full API reference with both the Delphi and the C++Builder signature for every member, C# for the .NET plugin, the option and enumeration type pages so the agent uses a constant that exists, examples distilled from the shipped demos, and the edition each component requires.
That last point saves a particular kind of wasted afternoon. "The component is not on my palette" is usually an edition question, not an installation one, and the skill answers it before you ask.
Being straight about .NET
The shipping .NET assembly exposes 70 of the 222 components the Delphi library registers. Rather than let an agent guess, the .NET plugin ships a generated coverage page that names the 152 which are Delphi only, with the unit each one lives in. An agent that would otherwise invent a plausible C# API now has somewhere to look, and the honest answer to "can I do this in C#" is one page away.
Privacy
A skill is documentation. Nothing executes, nothing is sent anywhere, and no telemetry is collected. The skills carry the public and published API only, so method bodies, private fields and protected members are deliberately excluded. Installing them does not put the library source on your disk or anyone else's.
Keeping them current
The skills are regenerated from the library source at every release, so they follow the product instead of drifting behind it. Re-run the install command to pick up a new version. If an API in your code does not match what the agent describes, check reference/history.md inside the skill, because the usual explanation is that the two of you are on different builds.
Full details and the manual install paths are on the AI agent skills page.
If an agent still gets something wrong with the skills installed, that is a documentation bug and we would like to hear about it. Open an issue on GitHub or get in touch — you will get a reply from the people who wrote the code.