feat(ai): add version metadata to agent skills and surface designDataVersion in MCP primer#1175
Merged
Merged
Conversation
…Version in MCP primer - Add metadata.version to all three published SKILL.md files per agentskills.io spec - Add metadata.designDataVersion to design-data skill (tracks @adobe/spectrum-design-data version) - MCP primer tools now return provenance.designDataVersion for dataset version metrics - Rename tokensVersion → designDataVersion at source (Rust wasm + CLI + all consumers) - Add AVA sync tests to all three skill packages to catch version drift on bumps - Register design-data-skill in moon workspace; add test infra to design-data-skill and s2-docs-mcp Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
🦋 Changeset detectedLatest commit: ab1b1be The changes in this PR will be included in the next version bump. This PR includes changesets to release 3 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Contributor
Run report for ab1b1beeTotal time: 5m 59s | Comparison time: 14m 55s | Estimated savings: 8m 55s (59.8% faster)
Expanded report
Touched files |
… dual source field - Rename parseSkillVersion → parseMetadataField(skillPath, fieldName) in design-data-agent-mcp and s2-docs-mcp test files, matching the general signature already used in design-data-skill — all three helpers now share the same shape - Add comment to both MCP primer handlers explaining the intentional redundancy between top-level source (legacy skill contract) and provenance.source (richer metrics object) Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds version metadata to the three published Agent Skills and surfaces the design-data dataset version in MCP primer tool output — both driven by a leadership metrics discussion about tracking which version of the integration and which token snapshot are in use.
Two version axes are now surfaced:
metadata.versionin SKILL.md frontmatter) — the npm package version of each skill.metadata.designDataVersionin thedesign-dataskill;provenance.designDataVersionin MCP primer output) — the@adobe/spectrum-design-dataversion baked into the wasm at build time viaEMBEDDED_DATA_VERSION.The field was originally named
tokensVersioninternally in the wasm/CLI, but "tokens" is misleading — it maps to the legacy@packages/tokenspackage. This PR renames it todesignDataVersionat source (both Rust producers:sdk/wasm/src/dataset.rsandsdk/cli/src/main.rs) so the public name matches what it represents.Related Issue
N/A — driven by leadership metrics discussion.
Motivation and Context
Metrics teams need to correlate AI tool invocations to specific integration and dataset versions. The MCP
serverInfo.versionalready reports tool version (was already wired). This PR closes the gap for skills (no version field) and for the dataset snapshot version (available in wasm but not propagated to the MCP primer response).How Has This Been Tested?
skill-version.test.js) added to all three skill packages — assert SKILL.mdmetadata.versionmatchespackage.jsonversion;design-dataskill also assertsmetadata.designDataVersionmatchespackages/design-data/package.json. All 4 tests pass locally.design-data-mcpand updated indesign-data-agent-mcp— assertprovenance.designDataVersionis a semver string. These require a wasm rebuild (sdk-wasm:build, CI only) sincewasm-packis not installed locally.sdk/wasm/test/parity.test.js) updated to assertprovenance.designDataVersion— runs in CI with built wasm.grep -rn "tokensVersion" --include=*.rs --include=*.js --include=*.md sdk tools .changesetreturns zero hits (onlysdk/cli/CHANGELOG.mdhistorical entry remains, intentionally untouched).node tools/changeset-linter/src/cli.js check --fail-on-warningspasses.Types of changes
provenance.tokensVersion→provenance.designDataVersionin wasm/CLI output; internal-only crates, acceptable.Checklist: