Maybe publish a skill.md file updated for each release of Objo

aosborne

Maybe publish a Skill.md file with each release of Objo. See https://agentskills.io/specification. They notably improve AI support for coding. Reduce hallucinations and boost end-user productivity. It is just a thought.

Garry

Thanks, this is a good suggestion.

Objo Studio already provides an MCP server, giving coding agents access to the live solution, compilation, safe editing, and the documentation bundled with that Studio release. An official SKILL.md would complement MCP by supplying portable Objo-specific rules and workflows, reducing incorrect assumptions based on Xojo, Visual Basic, or other BASIC dialects. It would also remain useful when Studio is not connected.

I've put this feature on the roadmap: Publish a versioned Objo Agent Skill. The plan is to publish a compact, installable skill matched to each release, with focused reference material and guidance to use Studio’s version-matched MCP documentation whenever available.

Thanks for pointing me towards the Agent Skills specification 🙂

aosborne

One of the solutions I use a lot is Gembox software. They do a great job in this regard. Here is an example of what they do: https://www.gemboxsoftware.com/support/ai-coding It might help. Cheers.

Garry

This is now done, and it will be available in the next release.

What you'll get

Every Objo Studio release now publishes an official Objo Agent Skill: an installable skill following the Agent Skills specification, usable with Claude Code, Codex, and any other agent that supports the format. These links will be live when the next version of Studio is published.

Stable download (always the current release): https://downloads.objo.dev/skills/objo-agent-skill.zip
Version-matched download: https://downloads.objo.dev/skills/objo-agent-skill-<version>.zip (with .sha256 checksums alongside)
Browsable source: docs.objo.dev/skills/objo/SKILL.md

To install it, extract the archive so you have an objo folder (containing the uppercase SKILL.md) inside your agent's skills directory - for example ~/.claude/skills/ for Claude Code - then restart the agent. Full instructions, including how to choose the version matching your installed Studio, are here: Objo Agent Skill.

What it does

The skill is deliberately compact. The entry file carries the rules that matter most:

Objo is its own statically typed language, not Xojo or Visual Basic: # comments, Var rather than Dim, zero-based indexing, short-circuit And/Or, the App class entry point, and the Me/Self distinction in event handlers - plus a table of the most common mistakes agents make when translating from other BASIC dialects.
When syntax or an API is uncertain, the agent is told to check the documentation before writing code - never guess, and never assume a Xojo framework class exists in Objo.
Three focused references ship inside the skill for when more detail is needed: language essentials, common Studio project workflows, and MCP usage.

How it works with the MCP server

The two complement each other. The MCP server (Studio 26.8.5 and later) gives a connected agent live tools - reading and editing the open solution, compiling, and saving under explicit permissions - plus the documentation bundled with your installed Studio. The skill directs the agent to prefer that version-matched documentation whenever Studio is connected, and routes live project work through the safe MCP behaviours: version-checked edits, rereading after version conflicts, compiling after changes, and saving only when you've authorised it. The skill itself adds no tools and no permissions - everything still runs through the permissions you granted in Studio. It also remains useful on its own when Studio isn't connected at all.

Each release's archive is built from the same documentation commit that release bundles, and its metadata records the Studio version and documentation revision it matches - so a version-matched skill and a version-matched Studio always agree.

Thanks again for the suggestion (and for the GemBox link) which was a useful comparison point.

aosborne

This is going to be a massive productivity booster. Great work. Super cool watching you turn this stuff around quickly.