Agent Skills for the Scandit SDK
AI agent skills for integrating the Scandit Data Capture SDK.
Each skill is specific to a product and a framework (e.g. SparkScan iOS), and bundles the recommended integration code, up-to-date setup, permissions and license-key wiring, common customization recipes (modes, callbacks, UI tweaks), and migration guidance, SDK version upgrades and, for some products, replacing a third-party scanner, all grounded in Scandit's own documentation. Install once, then just ask your agent for the feature instead of pasting docs snippets into your AI editor.
Installation
Install the plugin. One command, and your agent gets all 86 skills:
npx plugins add scandit/skills
It detects which coding agents you have and installs into each of them. Re-run the same command to pull the latest skills.
Or install from your agent's own marketplace:
| Agent | Install | Updates |
|---|---|---|
| Codex / ChatGPT App | One click install, or search Scandit SDK in the plugin directory | When Scandit publishes a new directory version |
| Claude Code | /plugin install scandit-sdk@claude-plugins-official, or search Scandit SDK in /plugin → Discover | Automatic, on each Scandit release |
| Cursor | One click install, or /add-plugin scandit-sdk in the editor | Automatic, on each Scandit release |
| Codex CLI | codex plugin marketplace add scandit/skillscodex plugin add scandit-sdk@scandit-plugins | codex plugin marketplace upgrade scandit-plugins |
| Copilot CLI | copilot plugin marketplace add scandit/skillscopilot plugin install scandit-sdk@scandit-plugins | copilot plugin update scandit-sdk |
| Everyone else | npx plugins add scandit/skills | Re-run npx plugins add scandit/skills |
Just one skill? Your agent only loads the skills your prompt needs, so the full bundle is the right choice — install once with npx plugins add scandit/skills.
How to use it
Describe what you want in plain language. Your agent loads the right skill on its own, or you can call one explicitly with /skill-name followed by your task.
Not sure which Scandit product you need? Start with data-capture-sdk. It is an advisor, not an integration skill: it asks a few questions about your workflow, recommends the right product, then hands off to the matching implementation skill for your platform. Describe your app, paste a screenshot of the screen you want to add scanning to, or drop in a photo of the label, package or ID you need to capture.
/data-capture-sdk I need to scan barcodes in a warehouse picking app - which Scandit product should I use?
/data-capture-sdk here is a photo of the labels we want to capture - what fits best?
Already know the product? Go straight to its skill.
/sparkscan-ios add a barcode scanner to the home screen of my app
/label-capture-web capture the expiry date and lot number from these pharmacy labels
Migrating? Most implementation skills carry version migration guidance alongside first integration. The Barcode Capture, SparkScan and MatrixScan Batch skills add a guide for replacing a third-party scanner.
/barcode-capture-android migrate this app from the Scandit SDK v6 API to v8
/matrixscan-batch-web we use BarcodeTracking, move us to BarcodeBatch
/sparkscan-android replace our current third-party barcode scanner with SparkScan
Licence keys
These skills write the integration; they don't provision the licence key by themselves. The Scandit MCP server does that part — connect it (claude mcp add --transport http scandit https://ssl.scandit.com/mcp) alongside the skills (npx plugins add scandit/skills) and each implementation skill's ## Licence key section will use it to fetch a trial key straight into your project's .env.
Keys provisioned this way are trials only, and the MCP server's auth is browser-based, so it does not work headless or in CI. Without it, the dashboard flow at https://ssl.scandit.com still works — every skill falls back to that.
Available skills
| Skill | Description |
|---|---|
data-capture-sdk | Product-selection advisor — recommends the right Scandit product for your use case and hands off to the matching implementation skill. |
sparkscan-{framework} | SparkScan integration & migration. Available for android, ios, web, cordova, capacitor, flutter, rn (React Native), kmp (Kotlin Multiplatform). |
barcode-capture-{framework} | BarcodeCapture (single-barcode scanning) integration & migration — BarcodeCaptureSettings, listener wiring, DataCaptureView + BarcodeCaptureOverlay, camera lifecycle, plus 6→7 and 7→8 deltas. Available for android, ios, web, cordova, capacitor, flutter, rn (React Native), kmp (Kotlin Multiplatform). |
barcode-selection-kmp | Barcode Selection (tap or aim to pick one barcode among many) integration — selection types and strategies, session counts, basic-overlay brushes. Available for kmp (Kotlin Multiplatform). |
matrixscan-ar-{framework} | MatrixScan AR (Barcode AR) integration & BarcodeBatch → BarcodeAr migration. Available for android, web, cordova, capacitor, flutter, rn (React Native), kmp (Kotlin Multiplatform). |
matrixscan-count-{framework} | MatrixScan Count (BarcodeCount) integration — counting against a list, status overlays, capture-list and not-in-list workflows, plus pre-7.6 → 7.6 constructor migration. Available for , , , (React Native), (Kotlin Multiplatform). |
Contributing
We welcome feedback that improves the quality of these skills:
- Report issues. File bugs, outdated SDK patterns, or incorrect guidance in the issue tracker.
- Request new skills. If a Scandit product, framework, or workflow you need isn't covered, open a feature request.
Branches: development happens on main, so target it with pull requests. The default dist branch is an install-only copy (no evals or internal tooling) that CI regenerates on every push to main; changes pushed to it are overwritten. Because main is not the default branch, Fixes #N in a PR does not close the issue on merge: close it by hand.
Pre-push check: in a main clone, run git config core.hooksPath internal/githooks once. Every push then runs the skill-auditor structure lint and its tests, and is refused while either reports a finding.
License
See the LICENSE file for licensing information.