Scanned Inc.
Official@scannedinc · United States
We build clever technology devices and software that make it easy to simplify your life.
Agent Skills by Scanned Inc.
Showing 4 vetted skills indexed across 1 GitHub repositories.
scannedincxojo-ide
Drive a running Xojo IDE from the command line to analyze, build, and run projects.
scannedincxojo
Converts official Xojo documentation into a local searchable Markdown tree with symbol indexes.
scannedincxojo-lint
Validate and conservatively format Xojo text-format project files.
scannedincxojo-migrate
Migrate Xojo desktop projects from API 1.0 to API 2.0 with confidence-tiered conversion rules.
Frequently Asked Questions About Scanned Inc.
FAQPage SchemaWhat tasks can I perform with Scanned Inc.'s Xojo skills?▼
You can drive a running Xojo IDE to open, build, run, and stop projects; look up over fifteen thousand documented language members; lint and format .xojo_project, .xojo_code, and .xojo_window files; and migrate desktop projects from API 1.0 to API 2.0 with vetted conversion rules.
Who are these Xojo skills designed for?▼
They target Xojo developers maintaining desktop, web, mobile, or console projects, especially engineers modernizing legacy API 1.0 codebases, enforcing pre-commit validation, or needing authoritative API 2.0 signatures instead of outdated online examples.
How does the Xojo API 1.0 to API 2.0 migration work?▼
The xojo-migrate skill performs a rule-driven, confidence-tiered rewrite committed one category at a time, fixing index bases, sentinels, and epoch shifts. It is user-invoked only: run /xojo:xojo-migrate in Claude Code or $xojo-migrate in Codex yourself.
What prerequisites do these Xojo skills require?▼
The xojo-ide skill requires a running Xojo IDE with the bundled xojoctl command. The xojo skill relies on a local copy of the official Xojo documentation with deprecation indexes. The lint and migrate skills operate on Xojo projects saved in text format.
When should I use the xojo documentation skill instead of answering from memory?▼
Always, before using any Xojo class, property, method, event, or constant. Most online Xojo examples use removed API 1.0 syntax, so the local documentation confirms exact signatures, deprecation status, the deprecating release, and the API 2.0 replacement.