The Module SDK: guides and references for coding agents

What the Module SDK contains, how a coding agent reads it through the connector, which skill or reference to open for each job, and how it stays current.

Copy page for AIUpdated November 21, 2026

The Module SDK is the set of guides, references and examples that teach a coding agent how to build a module the way Data Visions expects. Claude, Claude Code, Cursor and other agents read it before they write a file, so the module they build passes the module check the first time more often.

You rarely read the SDK yourself. Your agent does, through the connector. This page explains what is in it, so you know what to point your agent at.

What is in the SDK

PartWhat it is
SKILL.mdThe entry point: the workflow from idea to deploy, the rules every module follows, and a reading guide that sends the agent to the right skill for each task.
CLAUDE.mdA short note an agent loads automatically when it opens the SDK folder. It says: coach first, then read SKILL.md.
QUICKSTART.mdSetup for people working from a copy of the SDK with the command line.
MODULE_SDK.mdThe complete guide in one long file. A fallback; the skills cover the same ground in smaller pieces.
CHANGELOG.mdWhat changed in each SDK version.
VERSIONThe SDK's version number.
skills/How-to guides, one folder per task, each with a SKILL.md.
references/Detailed references: every manifest field, every platform feature, the review rules, the findings format.
examples/A reference module, examples/assets/, that passes validation with no errors or warnings.
platform-assets/The platform's own page scripts and styles (platform-sdk.js, platform.css, platform-forms.js, platform-charts.js and others), so an agent can see the exact functions a module page may call.
browser-extension/The Data Visions browser extension's source, for agents that drive the person's own browser.
The CLIThe dv command line. See Install and sign in to the CLI.

The SDK is versioned. Its version is in VERSION, and the connector reports it each time an agent opens the index.

How an agent reads it: sdk_doc

Agents read the SDK live through the connector's sdk_doc tool, so they always get the current version, not a copy from last month. Connect your agent first: see The Data Visions connector (MCP).

  • With no path, sdk_doc returns the index: the SDK version, the file to start with (skills/starting-a-module/SKILL.md), the workflow file (SKILL.md) and every document it serves, each with its path, a one-line description and its size.
  • With a path, such as references/manifest-schema.md or examples/assets/module.json, it returns that one document.
  • Long documents come in pages of up to 60,000 characters. Each page says where it starts, the document's total length and the next_offset. The agent calls sdk_doc again with offset set to that number for the next page.

What sdk_doc serves: the top-level files (SKILL.md, CLAUDE.md, QUICKSTART.md, MODULE_SDK.md, CHANGELOG.md, VERSION) and everything under skills/, references/, examples/ and platform-assets/. It does not serve the CLI's code or the browser extension; install the CLI instead.

A second tool, platform_features, returns references/platform-features.md directly, paged the same way: the list of everything a module may call on the platform.

Only Workspace Admins can use sdk_doc and platform_features, the same people who can build modules.

Can I download the SDK?

Read it through the connector. A downloadable copy is not offered to workspaces. Reading it live is also safer: manifest rules change between versions, and a module built from an old copy can fail the module check today.

Where an agent starts

An agent's first reads, in order:

  1. sdk_doc with no path, for the index and the version.
  2. skills/starting-a-module/SKILL.md when you want something new. It coaches: it asks what problem you are solving, who uses the module and what data it holds, shows what the platform already provides, and agrees a short plan with you before writing anything.
  3. SKILL.md for the workflow and the rules.
  4. references/review-rules.md before writing code. These are the rules the module check's AI review judges every module by.
  5. examples/assets/ as the pattern to copy, under a new module code (the code ASSETS is already taken).

After that the agent opens skills and references only when it needs them. The SDK is built for that: an agent should not load everything at once.

Skills

Each skill is one task. The agent picks the one that matches what it is doing.

SkillUse it for
starting-a-moduleCoaching from an idea to an agreed plan before any file is written.
connecting-to-platformSigning in, choosing the workspace and checking the session.
editing-manifestWriting module.json: tables, permissions, agent, settings, screens.
writing-toolsWriting @platform_tool functions in ai/tools.py, including tools that run on the Bridge.
writing-agent-skillsWriting SKILL.md packages inside a module's ai/skills/ folder.
using-storageStoring uploaded files and generated files with signed links, never in table columns.
building-for-phonesMaking every page work in the DV Mobile app, phone features through Platform.device, and the mobile manifest section.
registering-datasetsPublishing the module's data to dashboards and the Dashboard Agent.
writing-report-templatesReady-made reports on the module's Reports tab, and per-report permissions.
integrating-modulesConnecting to other modules or outside APIs through declared contracts.
using-integrationsUsing a system the workspace has connected, such as Microsoft 365, without handling credentials.
adding-a-data-sourceWriting a new source adapter so Data Connectors can read a new kind of system.
using-browser-extensionLetting a module's agent open pages, click and read in the person's own Chrome or Edge.
testing-modulesTesting service logic and tools without a running platform or database.
validating-locallyRunning the validator before uploading and fixing what it finds.
writing-qa-proceduresWriting qa/procedures.json: who uses the module and what to test. Required for the Marketplace.
deployingDeploying, updating, logs and troubleshooting, command by command.
using-the-cliWorking a workspace from a terminal for the person signed in.
publishingSubmitting to the Marketplace, tracking review and shipping updates.
sites-with-agentsAsking an agent to make or change a website and connect it to a module.
building-a-siteBuilding, hosting and publishing a workspace's public website.
site-designDesigning a website and writing its copy.
site-checkingChecking every page of a website version before it goes live.

References

ReferenceWhat it covers
references/manifest-schema.mdEvery field in module.json. See Module manifest (module.json) reference.
references/platform-features.mdEverything a module may call on the platform, with the API, the manifest entry and the limits. If it is not listed, a module does not have it.
references/review-rules.mdThe rules (R1 to R11) the module check's AI review applies.
references/validation-findings.mdThe format of every finding (code, why, fix, docs) and the catalogue of findings.
references/tool-decorator.mdThe @platform_tool contract and the tool context.
references/tenant-data-connector.mdHow module code reads and writes its own tables.
references/skill-spec.mdThe format for skills inside a module.
references/agents-and-models.mdHow a module's agent picks its model, whose AI key it uses, and calling a model from module code.
references/integration-contracts.mdDeclaring what a module provides and uses, for other modules and outside services.
references/browser-tool-actions.mdThe actions of the platform's browser tool.
references/module-icons.mdThe required module icon: file rules and how to draw it.
references/module-runbooks.mdShipping step-by-step runbooks with a module's help.

How it stays current

The SDK changes as the platform does. Each change is recorded in CHANGELOG.md, newest first: new skills, new manifest sections, new findings, and findings that will turn from warnings into errors.

  • An agent reading through the connector always gets the live version.
  • If you or your agent work from an older copy, compare its VERSION with the version sdk_doc reports, and read CHANGELOG.md for what changed in between.
  • dv version shows the version of the CLI you installed. If it is behind, update it with the steps the connector's cli_setup tool gives.

Good to know

  • Point your agent at skills/starting-a-module/SKILL.md for anything new. It plans with you first and writes code second.
  • The SDK describes your workspace only. A module you build is owned by your workspace and deployed there.
  • New findings often start as warnings. CHANGELOG.md says when they become errors, so fix them early.
  • For a step-by-step build, see Build a module with a coding agent, start to finish.

Can't find what you need? Contact support.