Matplotlib
zLanqing/codex-claude-academic-skills
Low-level plotting library for full customization. An agent skill from zLanqing/codex-claude-academic-skills.
Check .meta.yml and snapshot .dvc files for spelling typos using codespell.
$ npx skills add owid/etl --skill check-metadata-typos -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install owid/etl check-metadata-typos --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/owid/etl.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/check-metadata-typos .claude/skills/check-metadata-typos && rm -rf skills-srcUse ~/.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/
Install the "check-metadata-typos" agent skill from https://github.com/owid/etl/tree/master/.claude/skills/check-metadata-typos into .claude/skills/check-metadata-typos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-metadata-typos", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/owid/etl/tree/master/.claude/skills/check-metadata-typosType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add owid/etl --skill check-metadata-typos -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install owid/etl check-metadata-typos --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/owid/etl.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/check-metadata-typos .agents/skills/check-metadata-typos && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "check-metadata-typos" agent skill from https://github.com/owid/etl/tree/master/.claude/skills/check-metadata-typos into .agents/skills/check-metadata-typos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-metadata-typos", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add owid/etl --skill check-metadata-typos -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install owid/etl check-metadata-typos --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/owid/etl.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/check-metadata-typos .cursor/skills/check-metadata-typos && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "check-metadata-typos" agent skill from https://github.com/owid/etl/tree/master/.claude/skills/check-metadata-typos into .cursor/skills/check-metadata-typos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-metadata-typos", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/owid/etl.git --path .claude/skills/check-metadata-typos--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add owid/etl --skill check-metadata-typos -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install owid/etl check-metadata-typos --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/owid/etl.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/check-metadata-typos .gemini/skills/check-metadata-typos && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "check-metadata-typos" agent skill from https://github.com/owid/etl/tree/master/.claude/skills/check-metadata-typos into .gemini/skills/check-metadata-typos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-metadata-typos", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install owid/etl check-metadata-typosInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add owid/etl --skill check-metadata-typos -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/owid/etl.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/check-metadata-typos .github/skills/check-metadata-typos && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "check-metadata-typos" agent skill from https://github.com/owid/etl/tree/master/.claude/skills/check-metadata-typos into .github/skills/check-metadata-typos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-metadata-typos", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add owid/etl --skill check-metadata-typos -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install owid/etl check-metadata-typos --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/owid/etl.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/check-metadata-typos .opencode/skills/check-metadata-typos && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "check-metadata-typos" agent skill from https://github.com/owid/etl/tree/master/.claude/skills/check-metadata-typos into .opencode/skills/check-metadata-typos/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "check-metadata-typos", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
check-metadata-typosCheck .meta.yml and snapshot .dvc files for spelling typos using codespell.
Check Metadata Typos is an agent skill from owid/etl. Check .meta.yml and snapshot .dvc files for spelling typos using codespell. Use when user mentions typos, spelling errors, metadata quality, or wants to check metadata files for mistakes.
Its SKILL.md is about 2.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Data & Analytics. The repository describes itself as: A compute graph for loading and transforming OWID's data. The licence is MIT.
8 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit d5ba5a6. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
uvpythonFrom the folder's file list and the shell code blocks in SKILL.md.
No URLs in SKILL.md. Its commands use uv, which can reach the network depending on how they are called.
From URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Check Metadata Typos loads about 2.9k tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 934 words of instructions outside code blocks.
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.
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.
The full file from owid/etl at commit d5ba5a6, republished under its MIT licence (© owid). 934 words, ~2,936 tokens.
.claude/skills/check-metadata-typos/SKILL.md (or your agent's skills folder).Check metadata files for spelling typos using comprehensive spell checking.
Ask the user which scope they want to check:
etl/steps/data/garden/energy/2025-06-27/electricity_mix).meta.yml files in etl/steps/data/{garden,meadow,grapher}/ (automatically excludes ~3,570 archived steps).dvc files in snapshots/ (~7,915 files)Note: Archived steps and snapshots (defined in dag/archive/*.yml) are automatically excluded from checking as they are no longer actively maintained.
IMPORTANT: Check if codespell is installed before attempting to use it. Since codespell is now a dev dependency in the project, it should already be installed, but verify first to avoid reinstalling unnecessarily.
# Check if codespell is installed
if ! .venv/bin/codespell --version &> /dev/null; then
echo "codespell not found, installing..."
uv add --dev codespell
else
echo "codespell is already installed"
fiIf codespell is not installed and uv add --dev codespell fails, explain to the user how to install it manually.
IMPORTANT: Do not check archived steps and snapshots as they are no longer in use.
Archived steps and snapshots are defined in dag/archive/*.yml files:
To exclude them, extract their paths and create a list of active files:
# Extract archived step paths to a file
for step_type in garden meadow grapher; do
grep -h "data://${step_type}/" dag/archive/*.yml 2>/dev/null | \
grep -o "data://${step_type}/[^:]*" | \
sed 's|data://|etl/steps/data/|' | \
sed 's|$|.meta.yml|'
done > /tmp/archived_files.txt
# Extract archived snapshots
grep -rh "snapshot://" dag/archive/*.yml 2>/dev/null | \
grep -o "snapshot://[^:]*" | \
sed 's|snapshot://|snapshots/|' | \
sed 's|$|.dvc|' | \
sort -u >> /tmp/archived_files.txt
# Create list of all metadata files
find etl/steps/data/garden -name "*.meta.yml" > /tmp/all_meta_files.txt
find etl/steps/data/meadow -name "*.meta.yml" >> /tmp/all_meta_files.txt
find etl/steps/data/grapher -name "*.meta.yml" >> /tmp/all_meta_files.txt
find snapshots -name "*.dvc" >> /tmp/all_meta_files.txt
# Filter out archived files
grep -vFf /tmp/archived_files.txt /tmp/all_meta_files.txt > /tmp/active_meta_files.txt
echo "Total files to check: $(wc -l < /tmp/active_meta_files.txt)"Use the existing .codespell-ignore.txt file to filter out domain-specific terms.
Whichever option the user picked, write that scope's file list to /tmp/codespell_targets.txt and check it. Steps 5 and 6 reuse that one file, so the fix and the verification cannot act on a wider scope than the check did. Never point a later step at a different list.
For option 1 (current step only):
Ask the user for the path, then normalize it. This scope has to accept three shapes, because /create-snapshot step 5 calls it on a single new snapshot file:
etl/steps/data/garden/energy/2025-06-27/electricity_mix) → every .meta.yml in itsnapshots/who/2026-04-22/mortality) → the matching .dvc.meta.yml or .dvc → itself# For specific step or single file (option 1)
TARGET="<user_provided_path>"
.venv/bin/python - "$TARGET" > /tmp/codespell_targets.txt <<'PY'
import glob, os, sys
target = sys.argv[1].rstrip("/")
if os.path.isdir(target):
paths = sorted(glob.glob(f"{target}/*.meta.yml")) + sorted(glob.glob(f"{target}/*.dvc"))
elif os.path.isfile(target):
paths = [target]
else:
# A snapshot stem: snapshots/<namespace>/<version>/<short_name>, extension unknown.
paths = sorted(glob.glob(f"{target}.*.dvc")) or sorted(glob.glob(f"{target}.dvc"))
print("\n".join(paths))
PY
cat /tmp/codespell_targets.txt | xargs .venv/bin/codespell \
--ignore-words=.codespell-ignore.txtTwo ways this scope silently checks nothing, both of which must be treated as an error rather than a clean result:
.dvc target matched by a *.meta.yml-only pattern. A snapshot path has no .meta.yml in it, so a .meta.yml-only search returns an empty list and codespell reports no typos on a file it never opened. The normalizer above exists for exactly this case.ls <path>/*.meta.yml: under zsh a glob matching nothing aborts the command before the redirect, so no file is written and a wider list left over from an earlier run gets reused.Always report the number of files in /tmp/codespell_targets.txt before running codespell. If it is 0, say the path matched nothing and ask for a corrected one — never fall through to a wider scope, and never report "no typos found".
For option 2 (all ETL metadata - garden, meadow, grapher):
# For all ETL step metadata (option 2)
find etl/steps/data/garden -name "*.meta.yml" > /tmp/all_step_files.txt
find etl/steps/data/meadow -name "*.meta.yml" >> /tmp/all_step_files.txt
find etl/steps/data/grapher -name "*.meta.yml" >> /tmp/all_step_files.txt
grep -vFf /tmp/archived_files.txt /tmp/all_step_files.txt > /tmp/codespell_targets.txt
cat /tmp/codespell_targets.txt | xargs .venv/bin/codespell \
--ignore-words=.codespell-ignore.txtNote: Excluding archived steps reduces the scope by ~3,570 files and focuses on actively maintained metadata.
For option 3 (snapshot metadata):
# For all snapshot metadata (option 3)
find snapshots -name "*.dvc" > /tmp/all_snapshot_files.txt
grep -vFf /tmp/archived_files.txt /tmp/all_snapshot_files.txt > /tmp/codespell_targets.txt
cat /tmp/codespell_targets.txt | xargs .venv/bin/codespell \
--ignore-words=.codespell-ignore.txtNote: the prose worth checking in a snapshot .dvc lives under meta.origin — description, description_snapshot, title, title_snapshot, citation_full, attribution. Older files instead use the deprecated meta.source.description / meta.source.published_by; both shapes are still in the repo (~2,000 files on origin, ~6,000 on source). codespell reads the whole file either way, so no filtering is needed — but report hits by their real field path, and don't "fix" a typo by migrating a file from source to origin (that's a separate change, out of scope here). ~736 archived snapshots are excluded.
For option 4 (all metadata):
# For all metadata - ETL and snapshots (option 4)
# Use the active_meta_files.txt created in step 1
cp /tmp/active_meta_files.txt /tmp/codespell_targets.txt
cat /tmp/codespell_targets.txt | xargs .venv/bin/codespell \
--ignore-words=.codespell-ignore.txtExtract typos from codespell output and present them in a structured format:
Example output format:
Found 15 typos across 8 files:
Most common:
- "inmigrant" → "immigrant" (5 occurrences in 2 files)
- "seperate" → "separate" (3 occurrences in 1 file)
- "accomodation" → "accommodation" (2 occurrences in 1 file)
Detailed list:
[file.meta.yml:123] inmigrant → immigrant
[file.meta.yml:456] seperate → separate
...After presenting results, ask the user:
For automatic fixes, let codespell apply its own corrections — it rewrites only the words it flagged, at the positions it flagged them. Run it over /tmp/codespell_targets.txt, the list step 2 wrote for the scope the user chose:
cat /tmp/codespell_targets.txt | xargs .venv/bin/codespell \
--ignore-words=.codespell-ignore.txt --write-changesNever widen the scope here. --write-changes rewrites every file it is given, so pointing this at /tmp/active_meta_files.txt (the option-4 list) after the user asked for one step would silently edit thousands of unrelated files. The list must be the one that produced the reported typos — if /tmp/codespell_targets.txt is missing or you are unsure it matches, re-run step 2 for the chosen option before fixing anything.
For reviewed fixes, apply each one with the Edit tool, matching enough surrounding words to be unambiguous.
Never fix with an unanchored sed substitution. sed -i 's/word/word/g' file rewrites every occurrence in the file, including the ones you decided to ignore — inside URLs, domain names, and ALL-CAPS acronyms (see Notes). It also silently rewrites a word codespell never flagged on that line. sed -i '' is BSD-only on top of that, so it breaks on Linux (CI, cloud sandbox) where the same command needs sed -i.
After applying fixes, re-run codespell over the same scope to verify all typos were corrected:
cat /tmp/codespell_targets.txt | xargs .venv/bin/codespell \
--ignore-words=.codespell-ignore.txtShould return 0 results. If the user chose to review typos one by one and deliberately skipped some, expect exactly those to remain — say which, rather than reporting the check as failed.
IMPORTANT: Delete any temporary files created during the check:
rm -f /tmp/archived_files.txt /tmp/all_meta_files.txt /tmp/active_meta_files.txt \
/tmp/all_step_files.txt /tmp/active_step_files.txt \
/tmp/all_snapshot_files.txt /tmp/active_snapshot_files.txt \
/tmp/codespell_output.txt
The only persistent files should be:
- The `.codespell-ignore.txt` whitelist (if it doesn't exist, create it)
- Modified `.meta.yml` files (if fixes were applied)
**Do NOT create new persistent files in the repo like:**
- ❌ `TYPO_CHECK_REPORT.md`
- ❌ `scripts/analyze_typos.py`
- ❌ `scripts/advanced_spell_checker.py`
All analysis logic should be embedded in this command execution, not saved as separate files.
---
## Error Handling
- Check if codespell is installed first (see step 0). If not installed and `uv add --dev codespell` fails, explain to the user how to install it manually with `uv sync` or check their Python environment
- If no `.meta.yml` or `.dvc` files are found in the specified scope, inform the user
- If codespell finds no typos, congratulate the user on clean metadata!
- If file modification fails, report which files couldn't be updated
---
## Notes
- Always use American English spelling (e.g., "combating" not "combatting")
- Technical field names (like variable names with underscores) are typically safe to ignore
- **Acronyms in ALL CAPS should be ignored** - they are almost always legitimate acronyms (e.g., TE, INE, DIEA)
- **URLs and domain names should be ignored** - codespell may flag parts of URLs (e.g., "ine.es", "corona.fo") but these are correct
- When in doubt about a flagged word, ask the user before fixing© owid, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in .claude/skills/check-metadata-typos of owid/etl.
Open the folder on GitHubat commit d5ba5a6
Check Metadata Typos 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Check Metadata Typos this skillowid/etl | 159 | — | ~2.9k | Automated safety check: Pass | MIT | |
| MatplotlibzLanqing/codex-claude-academic-skills | 4.7k | 17 repos | ~2.9k | Automated safety check: Pass | MIT | |
| Exploratory Data Analysisspacering-net/codeg | 3.9k | 14 repos | ~3.6k | Automated safety check: Pass | MIT | |
| Scikit LearnzLanqing/codex-claude-academic-skills | 4.7k | 16 repos | ~3.9k | Automated safety check: Pass | BSD-3-Clause | |
| Chart Visualizationbytedance/deer-flow | 84k | 2 repos | ~840 | Automated safety check: Pass | MIT | |
| TimesFM Forecastinggoogle-research/timesfm | 34k | — | ~4.7k | Automated safety check: Pass | Apache-2.0 |
zLanqing/codex-claude-academic-skills
Low-level plotting library for full customization. An agent skill from zLanqing/codex-claude-academic-skills.
spacering-net/codeg
Perform comprehensive exploratory data analysis on scientific data files across 200+ file formats.
zLanqing/codex-claude-academic-skills
Machine learning in Python with scikit-learn. An agent skill from zLanqing/codex-claude-academic-skills.
bytedance/deer-flow
Picks a suitable chart type from 26 options for your data, maps the data to that chart's parameters and generates a chart image through a JavaScript script.
google-research/timesfm
Forecasts any univariate time series zero-shot with Google's TimesFM model, returning point forecasts and calibrated prediction intervals without training.
vercel/next.js
Benchmark React or Next.js changes on Vercel Sandbox VMs with paired A/B statistics: react PR/commit vs base, or Next.js PR/commit vs base, measured end-to-end through the bench/render-pipeline app…
owid/etl
Find every OWID surface that references a chart, indicator, MDIM, or explorer — articles (links vs embeds), explorers, narrative charts, data insights, static viz, key-chart slots, MDIM views.
owid/etl
Add a scatter view (with GDP per capita on x) to existing OWID charts via the admin API, mirroring the admin UI's "Add scatter type" defaults, then retire the old standalone "X vs.
owid/etl
Add new survey question codes (e.g. An agent skill from owid/etl.
owid/etl
Build or refresh an OWID static visualization end to end — resolve what data it needs from an old static viz image, an indicator, or a grapher chart; check both the ETL catalog and the producer's…
owid/etl
Propose redirects from (soon-to-sunset) grapher charts to the matching views of published MDIMs.
owid/etl
Take (soon-to-sunset) OWID explorers to redirected MDIMs, end to end.
Categories
Check .meta.yml and snapshot .dvc files for spelling typos using codespell. Check Metadata Typos is an agent skill from owid/etl.dvc files for spelling typos using codespell.
Check Metadata Typos fits situations like: user mentions typos; spelling errors; metadata quality; wants to check metadata files for mistakes.
Run `npx skills add owid/etl --skill check-metadata-typos -a claude-code`. Or copy the skill folder (.claude/skills/check-metadata-typos in owid/etl) into .claude/skills/check-metadata-typos in your project. Claude Code loads it when a task matches its description.
Run `npx skills add owid/etl --skill check-metadata-typos -a codex`. Or copy the skill folder (.claude/skills/check-metadata-typos in owid/etl) into .agents/skills/check-metadata-typos in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add owid/etl --skill check-metadata-typos -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/check-metadata-typos, .gemini/skills/check-metadata-typos, .github/skills/check-metadata-typos and .opencode/skills/check-metadata-typos in your project.
Going by SKILL.md and its folder, Check Metadata Typos needs the command-line tools its instructions call (uv and python). Our summary lists: Python 3.
SKILL.md contains no URLs. Its commands use uv, which can reach the network depending on how they are called. This is read from the text; nothing was executed.
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.
Check Metadata Typos is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.9k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Check Metadata Typos: Matplotlib (zLanqing/codex-claude-academic-skills, 4.7k stars), Exploratory Data Analysis (spacering-net/codeg, 3.9k stars), Scikit Learn (zLanqing/codex-claude-academic-skills, 4.7k stars) and Chart Visualization (bytedance/deer-flow, 84k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
owid (a GitHub organization) maintains it in owid/etl, which has 159 GitHub stars. The repository holds 35 skills in this directory. The repository was last updated on October 9, 2026.
Source: owid/etl on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.