Official agent skill

Odata Vocabularies Sync

by SAP in SAP/open-ux-tools

Sync odata-vocabularies package — update all vocabulary resource files to their latest published versions, and optionally add a new vocabulary given its JSON URL.

OfficialApache-2.0Auto-check passed

Install Odata Vocabularies Sync

skills CLI
$ npx skills add SAP/open-ux-tools --skill odata-vocabularies-sync -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install SAP/open-ux-tools odata-vocabularies-sync --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/SAP/open-ux-tools.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/odata-vocabularies-sync .claude/skills/odata-vocabularies-sync && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
odata-vocabularies-sync
GitHub stars
158
Token cost
~1.5k tokens
SKILL.md length
676 words
Files
1
Skills in repo
9
Repo updated
First seen
Licence
Apache-2.0

At a glance

Sync odata-vocabularies package — update all vocabulary resource files to their latest published versions, and optionally add a new vocabulary given its JSON URL.

  • Works in 5 steps: Add a new vocabulary (only when a URL… → Run the update tool → Audit and fix README → …
  • Asked to update vocabularies
  • SKILL.md covers Step 1 — Add a new vocabulary…, Step 2 — Run the update tool, Step 3 — Audit and fix README and Step 4 — Run tests and update…, plus 1 more section
  • Calls pnpm

What it does

Odata Vocabularies Sync is an agent skill from SAP/open-ux-tools, published by the product's own GitHub organization. Sync odata-vocabularies package — update all vocabulary resource files to their latest published versions, and optionally add a new vocabulary given its JSON URL. Use when asked to update vocabularies, refresh vocabulary resources, or add a new vocabulary to @sap-ux/odata-vocabularies.

Its SKILL.md is about 1.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

The repository describes itself as: Enable community collaboration to jointly promote and facilitate best in class tooling capabilities. The licence is Apache-2.0.

When your agent uses it

  • Asked to update vocabularies
  • Refresh vocabulary resources
  • Add a new vocabulary to @sap-ux/odata-vocabularies

Example prompts

  • “/odata-vocabularies-sync”

Workflow steps

5 steps, taken from the step headings in SKILL.md.

  1. Add a new vocabulary (only when a URL argument is provided)
  2. Run the update tool
  3. Audit and fix README
  4. Run tests and update snapshots
  5. Report

What it can do on your machine

Read from SKILL.md and the folder at commit ddeddbe. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pnpm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use pnpm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Odata Vocabularies Sync loads about 1.5k tokens when it runs. Until then it costs about 78 tokens; SKILL.md has 676 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~78
When it runs · the whole SKILL.md, loaded when a task matches
~1.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from SAP/open-ux-tools at commit ddeddbe, republished under its Apache-2.0 licence (© SAP). 676 words, ~1,548 tokens.

Download SKILL.mdSave it as .claude/skills/odata-vocabularies-sync/SKILL.md (or your agent's skills folder).
name
odata-vocabularies-sync
description
Sync odata-vocabularies package — update all vocabulary resource files to their latest published versions, and optionally add a new vocabulary given its JSON URL. Use when asked to update vocabularies, refresh vocabulary resources, or add a new vocabulary to @sap-ux/odata-vocabularies.
argument-hint
(optional) URL of the new vocabulary in JSON format (ending in .json), e.g. https://sap.github.io/odata-vocabularies/vocabularies/SomeNew.json — XML URLs are…
metadata.author
sap-fiori-tools
metadata.version
1.0.0

odata-vocabularies-sync

Keeps the packages/odata-vocabularies package in sync with the upstream OData vocabulary sources.

  • No argument — update all existing vocabulary resource files to their latest published versions.
  • With a URL argument — register and add the new vocabulary first, then update everything.

All file edits are relative to packages/odata-vocabularies/.

Note: com.sap.cds.vocabularies.* files (ObjectModel, AnalyticsDetails) are hand-crafted and not managed by this skill. Do not attempt to add them via a URL.


Step 1 — Add a new vocabulary (only when a URL argument is provided)

1a. Fetch and inspect the vocabulary JSON

Fetch the JSON at the provided URL (must end in .json — XML URLs are not supported by the update tool). Extract:

  • namespace — the key of the top-level schema object (e.g. Org.OData.NewThing.V1 or com.sap.vocabularies.NewThing.v1)
  • alias — the value of $Alias inside that schema object (e.g. NewThing)

Determine the vocabulary family from the namespace:

  • Starts with Org.OData. → OASIS vocabulary
  • Starts with com.sap.vocabularies. → SAP vocabulary
  • Starts with com.sap.cds. → CDS vocabulary — stop. These files are hand-crafted and cannot be added via this skill. Explain this to the user.
  • Anything else → stop and ask the user to confirm the family before proceeding.
1b. Edit tools/update.ts

Add an entry to SUPPORTED_VOCABULARIES in alphabetical order within the existing entries:

typescript
'<namespace>': {
    uri: '<the provided URL>'
},

Note: The entry can include update: false to pin the vocabulary and exclude it from future automatic updates (e.g. com.sap.vocabularies.CDS.v1 uses this because it is hand-maintained). Omit the field for normal auto-updating behaviour.

1c. Edit src/resources/index.ts

Make all six additions. All six are mandatory — missing any one will cause a runtime error.

  1. Import — insert alphabetically by alias in the single import block (OASIS and SAP imports are interleaved by alias, not grouped by family):

    typescript
    import <Alias> from './<namespace>.js';

    Use the $Alias value from the JSON as the import identifier. Exception: if the alias is a reserved JS keyword or built-in (e.g. JSON, Map, Error), prefix it to form a valid identifier (e.g. JSON → ODataJSON). Also check existing imports for precedent — some aliases are shortened for brevity (e.g. Authorization → Auth).

  2. Namespace union type — add to the matching family type:

    • OASIS → OasisVocabularyNamespace
    • SAP → SapVocabularyNamespace
    typescript
    | '<namespace>'
  3. Alias union type — add to the matching family type:

    • OASIS → OasisVocabularyAlias
    • SAP → SapVocabularyAlias
    typescript
    | '<Alias>'
  4. NAMESPACE_TO_ALIAS Map:

    typescript
    ['<namespace>', '<Alias>'],
  5. ALIAS_TO_NAMESPACE Map:

    typescript
    ['<Alias>', '<namespace>'],
  6. vocabularies Record:

    typescript
    '<namespace>': <Alias>,
1d. Edit src/loader.ts

Add the namespace to SUPPORTED_VOCABULARY_NAMESPACES in alphabetical order within its family block:

typescript
'<namespace>',
1e. Edit README.md

Add the alias to the correct bullet list in the "Supported Vocabularies" section, in alphabetical order:

  • OASIS namespace → OASIS Vocabularies list
  • SAP namespace → SAP Vocabularies list
* <Alias>

Show full SKILL.md (269 more words)Show less

Step 2 — Run the update tool

This fetches the latest JSON for every registered vocabulary (including any newly added one) and regenerates all src/resources/*.ts resource files.

Run from the repo root:

bash
pnpm --filter @sap-ux/odata-vocabularies update:vocabularies

If the tool fails, stop and report the full error output before proceeding.


Step 3 — Audit and fix README

Cross-check the README against the registered vocabularies and add any missing entries.

  1. Read src/resources/index.ts and collect all namespaces from NAMESPACE_TO_ALIAS, split by family:

    • OASIS: namespaces starting with Org.OData.
    • SAP: namespaces starting with com.sap.vocabularies. excluding com.sap.vocabularies.CDS.v1
    • Skip all com.sap.cds. namespaces (hand-crafted, not listed in README)
  2. For each collected namespace, read the corresponding generated resource file src/resources/<namespace>.ts and extract the $Alias value — this is the authoritative published alias used as the display name in README.

  3. Read README.md and find the two bullet lists under "Supported Vocabularies":

    • The OASIS Vocabularies list
    • The SAP Vocabularies list
  4. For each alias not yet present in the correct list, insert it in alphabetical order.

If the README is already complete, do nothing.


Step 4 — Run tests and update snapshots

bash
pnpm --filter @sap-ux/odata-vocabularies test -- -u

Report any test failures that are not snapshot-related. Snapshot updates are expected only when vocabulary content has actually changed (either upstream drift detected by the update tool, or a newly added vocabulary). If snapshots change beyond what was updated, inspect the diff before accepting — it may indicate a regression.


Step 5 — Report

Summarise what was done:

  • If a new vocabulary was added: confirm the namespace, alias, family, and all files changed.
  • If any README entries were missing and added, list them.
  • List vocabulary resource files regenerated by the update tool.
  • Confirm tests pass.

© SAP, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in .agents/skills/odata-vocabularies-sync of SAP/open-ux-tools.

Open the folder on GitHubat commit ddeddbe

Compare with similar skills

Odata Vocabularies Sync next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Odata Vocabularies Sync compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Odata Vocabularies Sync this skillSAP/open-ux-tools158—~1.5kAutomated safety check: PassApache-2.0
React Syncvercel/next.js143k—~486Automated safety check: PassMIT
Claude-Mem Cloud Syncthedotmack/claude-mem99k—~1kAutomated safety check: NotesApache-2.0
Agent Resource Allocatorruvnet/ruflo74k2 repos~4.9kAutomated safety check: PassMIT
Agent Sync Coordinatorruvnet/ruflo74k2 repos~4kAutomated safety check: PassMIT
Resourceswindmill-labs/windmill18k—~1.7kAutomated safety check: PassCustom licence

Similar skills

  • React Sync

    vercel/next.js

    Official

    Build local React changes in the bundle variants consumed by Next.js, sync them into a local Next.js checkout, and test the resulting integration.

    143k GitHub stars~486 tokensUpdated today
    Auto-check passed
  • Claude-Mem Cloud Sync

    thedotmack/claude-mem

    Checks claude-mem cloud sync status and guides you through connecting a cmem.ai Pro account without the sync token ever passing through the chat.

    99k GitHub stars~1k tokensUpdated 2 days ago
    Agent WorkflowsAuto-check: notes
  • Agent skill for resource-allocator - invoke with $agent-resource-allocator

    74k GitHub starsUsed in 2 repos~4.9k tokens
    Auto-check passed
  • Agent skill for sync-coordinator - invoke with $agent-sync-coordinator

    74k GitHub starsUsed in 2 repos~4k tokens
    Auto-check passed
  • Resources

    windmill-labs/windmill

    MUST use when managing resources.

    18k GitHub stars~1.7k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • Resource Hints

    thedaviddias/Front-End-Checklist

    A skill your agent uses when auditing slow page loads, heavy assets, or rendering delays related to Use resource hints for faster loading.

    74k GitHub stars~430 tokensUpdated 4 days ago
    Frontend & DesignAuto-check passed

More from SAP/open-ux-tools

All 9 skills in this repo
  • Eslint Rule Development

    SAP/open-ux-tools

    Official

    Develop a new ESLint rule for @sap-ux/eslint-plugin-fiori-tools.

    158 GitHub stars~3k tokensUpdated yesterday
    Auto-check passed
  • Official

    A skill your agent uses when writing, fixing, extending, or reviewing OPA5 integration tests for SAP Fiori Elements applications - whether the app uses OData V4 (sap.fe.test library) or OData V2…

    158 GitHub stars~3.6k tokensUpdated yesterday
    Auto-check passed
  • Official

    Add visual filters (chart-based) to SAP Fiori Elements filter bar or value help using CAP or ABAP RAP.

    158 GitHub stars~3k tokensUpdated yesterday
    Auto-check passed
  • Official

    Add analytical chart (chart + table hybrid) to SAP Fiori Elements List Report using aggregated data.

    158 GitHub stars~3.5k tokensUpdated yesterday
    Auto-check passed
  • Sap Fiori App Development

    SAP/open-ux-tools

    Official

    Guidelines for SAP Fiori app development for CAP and standalone projects.

    158 GitHub stars~1.7k tokensUpdated yesterday
    Auto-check passed
  • Sap Fiori Eslint Plugin

    SAP/open-ux-tools

    Official

    Configure, migrate, or run ESLint with @sap-ux/eslint-plugin-fiori-tools in SAP Fiori projects (standalone or CAP).

    158 GitHub stars~640 tokensUpdated yesterday
    Auto-check passed

Questions about Odata Vocabularies Sync

What does Odata Vocabularies Sync do?

Sync odata-vocabularies package — update all vocabulary resource files to their latest published versions, and optionally add a new vocabulary given its JSON URL. Odata Vocabularies Sync is an agent skill from SAP/open-ux-tools, published by the product's own GitHub organization. Sync odata-vocabularies package — update all vocabulary resource files to their latest published versions, and optionally add a new vocabulary given its JSON URL.

When should I use Odata Vocabularies Sync?

Odata Vocabularies Sync fits situations like: asked to update vocabularies; refresh vocabulary resources; add a new vocabulary to @sap-ux/odata-vocabularies.

How do I install Odata Vocabularies Sync in Claude Code?

Run `npx skills add SAP/open-ux-tools --skill odata-vocabularies-sync -a claude-code`. Or copy the skill folder (.agents/skills/odata-vocabularies-sync in SAP/open-ux-tools) into .claude/skills/odata-vocabularies-sync in your project. Claude Code loads it when a task matches its description.

How do I install Odata Vocabularies Sync in Codex?

Run `npx skills add SAP/open-ux-tools --skill odata-vocabularies-sync -a codex`. Or copy the skill folder (.agents/skills/odata-vocabularies-sync in SAP/open-ux-tools) into .agents/skills/odata-vocabularies-sync in your project. Codex loads it when a task matches its description.

Can I use Odata Vocabularies Sync in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add SAP/open-ux-tools --skill odata-vocabularies-sync -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/odata-vocabularies-sync, .gemini/skills/odata-vocabularies-sync, .github/skills/odata-vocabularies-sync and .opencode/skills/odata-vocabularies-sync in your project.

What does Odata Vocabularies Sync need to run?

Going by SKILL.md and its folder, Odata Vocabularies Sync needs the command-line tools its instructions call (pnpm).

Does Odata Vocabularies Sync access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Odata Vocabularies Sync safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Odata Vocabularies Sync use?

Odata Vocabularies Sync is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Odata Vocabularies Sync use?

About 1.5k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Odata Vocabularies Sync?

Skills that share tags, products or a category with Odata Vocabularies Sync: React Sync (vercel/next.js, 143k stars), Claude-Mem Cloud Sync (thedotmack/claude-mem, 99k stars), Agent Resource Allocator (ruvnet/ruflo, 74k stars) and Agent Sync Coordinator (ruvnet/ruflo, 74k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Odata Vocabularies Sync?

SAP (a GitHub organization, an official publisher) maintains it in SAP/open-ux-tools, which has 158 GitHub stars. The repository holds 9 skills in this directory. The repository was last updated on October 10, 2026.

Source: SAP/open-ux-tools on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.