Skip to content
TrustedSkillsbeta
Back to all skills

Check Metadata Typos

Checked
owid·vlatest·data·MIT

This skill automatically identifies and corrects common typos in metadata fields, ensuring data accuracy and consistency for improved searchability.

Install on your platform

This skill no longer installs under the name check-metadata-typos. SKILL.md is marked internal, so the skills CLI hides it.

We check each listing against its upstream repository with the rules the skills CLI uses, last on 2026-10-21. We don't show a command we know will fail.

Repository install instructions

What we know about this skill

Publisher

owid

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned owid/etl at 6173f8e9ff.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Scanned
1 file, 245 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill scans metadata fields within datasets to identify and flag spelling errors, ensuring data integrity before processing. It specifically targets common typos in column names, variable labels, and descriptive attributes often found in ETL workflows.

When to use it

  • Before loading raw data into a database or analytics pipeline to prevent downstream query failures.
  • During the initial ingestion phase of an ETL job to clean up messy source files from external vendors.
  • When collaborating on shared datasets where inconsistent naming conventions have caused confusion among team members.
  • As a validation step prior to generating reports that rely on specific metadata keys for filtering or grouping.

Key capabilities

  • Detects misspelled words and incorrect capitalization in metadata strings.
  • Provides a list of flagged fields with suggestions for correction based on common patterns.
  • Integrates seamlessly into existing data transformation pipelines without manual intervention.
  • Supports multiple file formats including CSV, JSON, and Parquet headers.

Example prompts

"Run check-metadata-typos on my latest sales export to find any misspelled column names." "Scan the metadata of this research dataset for typos that might break my Python analysis script." "Identify spelling errors in the variable labels before I start aggregating the customer feedback data."

Tips & gotchas

Ensure your source files have consistent encoding (preferably UTF-8) to avoid false positives caused by character interpretation issues. This tool focuses on text-based metadata; it will not correct structural errors like missing commas or malformed JSON syntax.