Skip to content

Guide · Agent skill

How to use the Create Data Context agent skill

Updated · written with AI from the project's own documentation and checked against our catalogue data

The create-data-context skill is an agent skill from the MiMo-Code project that turns your knowledge of a dataset into a written, inspectable semantic layer. It records which metric definition is canonical, which dashboard or table is the trusted source, and what caveats to check before answering. This guide explains what an agent skill is, how to install this one, how to trigger it with plain requests, and what to review before you share the output.

Create Data ContextXiaomiMiMo/MiMo-Code · MIT

Quick start

  1. 1Download and unzip the skill. Download the ZIP from this page and unzip it so the skill folder contains SKILL.md.
  2. 2Place it in the skills folder. Move the folder into ~/.claude/skills/ for personal use or a project's .claude/skills/ folder for one project. Alternatively, upload it under Settings → Capabilities → Skills in the Claude apps.
  3. 3Make the data sources readable. Make sure the agent can access the repositories, dashboards or docs that define your metrics.
  4. 4Ask for a semantic layer. Describe the area in plain language, for example asking to save data context for a specific metric set.
  5. 5Review the source inventory and layer. Check the listed sources, conflicts and caveats, and correct any definitions that do not match your understanding.
  6. 6Cite and refine later. Cite the saved layer path or installed link in later prompts, and ask to refine definitions, add sources or update caveats as your understanding changes.

What an agent skill is and what this one does

An agent skill is a folder containing a SKILL.md file with instructions that a compatible AI agent (such as Claude Code or Codex) reads when a request matches the skill's description. The agent then follows those instructions for that task.

This skill creates, updates, inspects, or repairs Data Analytics semantic layers. A semantic layer here is an explicit artifact you can inspect and cite later. It captures how future analyses should interpret the data, for example which metric definition is canonical, which dashboard or table is the best source of truth, and what caveats should be checked before answering.

  • Keeps the generated skill compact and puts detailed metric definitions, tables, query patterns, caveats and evidence into linked reference files.
  • Favors durable sources such as transformation code, tests, maintained metric docs and verified dashboards over looser signals like query history or team discussion.
  • Keeps source conflicts visible instead of silently choosing one.
  • Writes a source inventory listing what was checked, what is missing and which sources are lower-confidence.

Install the create-data-context skill

Download the ZIP for this skill from this page and unzip it. For Claude Code, place the unzipped skill folder in your personal skills directory ~/.claude/skills/, or in a project's .claude/skills/ folder if you want it available only inside that project.

If you use the Claude apps, you can instead upload the skill under Settings → Capabilities → Skills.

  • Personal: ~/.claude/skills/ (available across your projects).
  • Project: .claude/skills/ inside the project folder (available only in that project).
  • Claude apps: Settings → Capabilities → Skills, then upload.

Trigger the skill with natural requests

The skill is selected when your request matches its description. The description covers creating or maintaining a semantic layer and saving data context. Ask in plain language, and say what you want the layer to cover.

Use this skill only for saving data context or creating, updating, inspecting or repairing a semantic layer. For ordinary data work such as answering a metric question, building a report or checking a dataset, the skill routes you to the Data Analytics index skill instead.

  • "Save data context for our weekly revenue metrics."
  • "Create a semantic layer for the subscriptions reporting area."
  • "Inspect the existing churn semantic layer and tell me where its sources conflict."
  • "Repair the orders semantic layer; the dashboard link it cites no longer exists."

Where the saved layer goes

The skill chooses one destination based on the runtime. In a local Codex setup it writes to $CODEX_HOME/skills/<area>-semantic-layer, or to ~/.codex/skills/<area>-semantic-layer if $CODEX_HOME is unavailable and the default location is clearly in use. In ChatGPT with a personal Skills library, it installs into that library and returns a link. If no persistent destination is available, it returns a portable skill package and states that it has not been installed persistently.

After creating or updating a layer, the skill offers a weekly refresh automation. It does not create one without your explicit approval unless you asked for recurring refresh.

What to provide so the layer is useful

The skill works from the sources you let it read. Give it access to the places where your metric logic lives, such as repositories, dashboards or docs. Before crawling, it builds a list of what it checked and what is missing. Where a source is thin, it returns a practical plan for what to collect next instead of a full layer.

  • Repositories containing transformation code and tests.
  • Maintained metric documentation and verified dashboards.
  • Table metadata the agent can read.
  • Requires Python 3 to run the bundled helper scripts.

Review the output before sharing it and check safety notes

This skill runs bundled scripts (scripts/data_analytics_preflight.py, scripts/validate_data_context_contract.py and scripts/record_plugin_install_suppression.py) and is not network-free in every workflow, so review what it runs in your environment. The skill tries to avoid copying raw sensitive data, credentials, row-level examples or long private messages into generated files, but you should still review outputs before sharing them, because generated files could capture sensitive details.

  • Do not use it on sensitive datasets where generated files might capture row-level data or credentials.
  • Check every generated definition and caveat against the source it cites.
  • Keep the generated files in a location you control if they describe private systems.

What people use it for

  • Recording the canonical definition of revenue, churn or active users so later analyses use the same meaning.
  • Naming the trusted dashboard or table for a reporting area and listing the caveats to check before answering.
  • Producing a written source inventory that shows what is trusted, lower-confidence and missing for a data lead's review.
  • Repairing an existing semantic layer whose cited source has changed or disappeared.
  • Planning which sources to collect before a semantic layer is complete enough to save.

Frequently asked questions

Is the create-data-context skill free?

The skill is released under the MIT licence, as stated on this page. Check the licence file in the source repository for the full terms. It runs inside a compatible agent such as Claude Code or Codex, which have their own access terms.

What do I need to run create-data-context?

You need a runtime that reads SKILL.md skills, such as Claude Code, Codex or a compatible agent. You also need access to the data sources you want documented and Python 3 to run the bundled helper scripts.

Where do I install the create-data-context skill?

Download the ZIP from this page and unzip it into ~/.claude/skills/ for personal use or a project's .claude/skills/ folder. In the Claude apps you can upload it under Settings → Capabilities → Skills.

Does create-data-context use the network?

This page lists it as not using the network, but it runs bundled Python scripts. Review those scripts before use, especially in sensitive environments.

What is the difference between this skill and the Data Analytics index skill?

This skill creates and maintains semantic-layer skills that record definitions and trusted sources. The Data Analytics index skill handles ordinary data work such as answering metric questions, building reports or checking datasets.

Why won't the skill save my layer somewhere?

If no supported persistent skill destination is available in the current run, it returns a portable skill package and says it has not been installed persistently. Check that your runtime exposes a Codex skills folder or a personal Skills library.

New agent skills, repos and AI tools — every week

The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.

Our verdict

Use this skill if you repeatedly answer questions about the same metrics and want a documented, citable set of definitions, or if you lead a data team that needs a written inventory of trusted and missing sources. Skip it for ad hoc questions or report building, which belong to the Data Analytics index skill, and for sensitive datasets where generated files might capture row-level data or credentials.

Download the skill