How do I install the Atcoder Fetcher skill?

Run npx skillmds@latest add tomevault-io/atcoder-fetcher in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Atcoder Fetcher safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Atcoder Fetcher?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Atcoder Fetcher free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Atcoder Fetcher?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Atcoder Fetcher by tomevault-io — Agent Skill

Name: Atcoder Fetcher
Author: tomevault-io

Atcoder Fetcher

Fetch and format AtCoder problem statements or editorials from a URL. Use this skill when the user provides an AtCoder problem URL (e.g., .../tasks/abcXXX_x), an editorial URL (e.g., .../editorial/XXXX), or refers to a problem by name (e.g., "ABC432 D"). Use when this capability is needed.

tomevault-io Updated Sep 17, 2026

File contents

AtCoder Fetcher

This skill retrieves problem statements and editorials from AtCoder URLs and formats them as Markdown.

Usage

Execute the corresponding Python script using uv run. Important: You must set the correct environment variables for the sandbox environment.

Fetching a Problem Statement

HOME=/home/node UV_CACHE_DIR=/home/node/.cache/uv PATH="/home/node/.local/bin:$PATH" uv run .gemini/skills/atcoder-fetcher/scripts/fetch_problem.py <URL>

Fetching an Editorial

HOME=/home/node UV_CACHE_DIR=/home/node/.cache/uv PATH="/home/node/.local/bin:$PATH" uv run .gemini/skills/atcoder-fetcher/scripts/fetch_editorial.py <URL>

Listing Editorials for a Problem

HOME=/home/node UV_CACHE_DIR=/home/node/.cache/uv PATH="/home/node/.local/bin:$PATH" uv run .gemini/skills/atcoder-fetcher/scripts/list_editorials.py <URL>

URL Construction Rules

If the user provides a contest name and problem letter instead of a full URL, construct the URL using these rules:

1. Problem Statement URL

Pattern: https://atcoder.jp/contests/<contest_id>/tasks/<contest_id>_<problem_letter>
Example: "ABC432 D" -> https://atcoder.jp/contests/abc432/tasks/abc432_d

2. Editorial List URL (Problem-specific)

Pattern: https://atcoder.jp/contests/<contest_id>/tasks/<contest_id>_<problem_letter>/editorial
Example: "ABC432 D Editorials" -> https://atcoder.jp/contests/abc432/tasks/abc432_d/editorial

3. Individual Editorial URL

Pattern: https://atcoder.jp/contests/<contest_id>/editorial/<editorial_id>
Example: https://atcoder.jp/contests/abc432/editorial/12345

Rules for Identifiers

<contest_id>: Lowercase contest name (e.g., abc432, arc150, agc001).
<problem_letter>: Lowercase problem label (e.g., a, b, c, d).
<editorial_id>: A unique numeric identifier for a specific editorial (found in the editorial list).

Environment Variables

The following variables are required in the sandbox:

HOME=/home/node
UV_CACHE_DIR=/home/node/.cache/uv
PATH="/home/node/.local/bin:$PATH"

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: atcoder-fetcherdescription: Fetch and format AtCoder problem statements or editorials from a URL. Use this skill when the user provides an AtCoder problem URL (e.g., .../tasks/abcXXX_x), an editorial URL (e.g., .../editorial/XXXX), or refers to a problem by name (e.g., "ABC432 D"). Use when this capability is needed.---# AtCoder FetcherThis skill retrieves problem statements and editorials from AtCoder URLs and formats them as Markdown.## UsageExecute the corresponding Python script using `uv run`.**Important:** You must set the correct environment variables for the sandbox environment.### Fetching a Problem Statement```bashHOME=/home/node UV_CACHE_DIR=/home/node/.cache/uv PATH="/home/node/.local/bin:$PATH" uv run .gemini/skills/atcoder-fetcher/scripts/fetch_problem.py <URL>```### Fetching an Editorial```bashHOME=/home/node UV_CACHE_DIR=/home/node/.cache/uv PATH="/home/node/.local/bin:$PATH" uv run .gemini/skills/atcoder-fetcher/scripts/fetch_editorial.py <URL>```### Listing Editorials for a Problem```bashHOME=/home/node UV_CACHE_DIR=/home/node/.cache/uv PATH="/home/node/.local/bin:$PATH" uv run .gemini/skills/atcoder-fetcher/scripts/list_editorials.py <URL>```## URL Construction RulesIf the user provides a contest name and problem letter instead of a full URL, construct the URL using these rules:### 1. Problem Statement URL- **Pattern:** `https://atcoder.jp/contests/<contest_id>/tasks/<contest_id>_<problem_letter>`- **Example:** "ABC432 D" -> `https://atcoder.jp/contests/abc432/tasks/abc432_d`### 2. Editorial List URL (Problem-specific)- **Pattern:** `https://atcoder.jp/contests/<contest_id>/tasks/<contest_id>_<problem_letter>/editorial`- **Example:** "ABC432 D Editorials" -> `https://atcoder.jp/contests/abc432/tasks/abc432_d/editorial`### 3. Individual Editorial URL- **Pattern:** `https://atcoder.jp/contests/<contest_id>/editorial/<editorial_id>`- **Example:** `https://atcoder.jp/contests/abc432/editorial/12345`### Rules for Identifiers- `<contest_id>`: Lowercase contest name (e.g., `abc432`, `arc150`, `agc001`).- `<problem_letter>`: Lowercase problem label (e.g., `a`, `b`, `c`, `d`).- `<editorial_id>`: A unique numeric identifier for a specific editorial (found in the editorial list).## Environment VariablesThe following variables are required in the sandbox:- `HOME=/home/node`- `UV_CACHE_DIR=/home/node/.cache/uv`- `PATH="/home/node/.local/bin:$PATH"`---> Converted and distributed by [TomeVault](https://tomevault.io/claim/paruma) — claim your Tome and manage your conversions.

Frequently asked questions