Best use case
atcoder-client is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Interface with AtCoder for Japanese competitive programming contests
Teams using atcoder-client should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/atcoder-client/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How atcoder-client Compares
| Feature / Agent | atcoder-client | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Interface with AtCoder for Japanese competitive programming contests
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
SKILL.md Source
# AtCoder Client Skill
## Purpose
Interface with AtCoder platform for accessing Japanese competitive programming contests, problems, and submissions.
## Capabilities
- Fetch contest problems with translations
- Submit solutions and track results
- Access AtCoder Problems difficulty ratings
- Virtual contest participation
- Retrieve user submission history
- Access editorial content
## Target Processes
- atcoder-contest
- progress-tracking
- skill-gap-analysis
## Integration
Uses AtCoder web interface and AtCoder Problems API for difficulty ratings and problem metadata.
## Input Schema
```json
{
"type": "object",
"properties": {
"action": {
"type": "string",
"enum": ["getContestProblems", "getProblem", "getSubmissions", "getDifficulty", "getUserStats"]
},
"contestId": { "type": "string" },
"problemId": { "type": "string" },
"username": { "type": "string" }
},
"required": ["action"]
}
```
## Output Schema
```json
{
"type": "object",
"properties": {
"success": { "type": "boolean" },
"data": { "type": "object" },
"error": { "type": "string" }
},
"required": ["success"]
}
```
## Usage Example
```javascript
{
"action": "getContestProblems",
"contestId": "abc300"
}
```Related Skills
client-server
Client-server architecture skill for authority models and validation.
mcp-mock-client
Create mock MCP client for server testing with request/response simulation.
codeforces-api-client
Interface with Codeforces API for contest data, problem sets, and submissions
process-builder
Scaffold new babysitter process definitions following SDK patterns, proper structure, and best practices. Guides the 3-phase workflow from research to implementation.
babysitter
Orchestrate via @babysitter. Use this skill when asked to babysit a run, orchestrate a process or whenever it is called explicitly. (babysit, babysitter, orchestrate, orchestrate a run, workflow, etc.)
yolo
Run Babysitter autonomously with minimal manual interruption.
user-install
Install the user-level Babysitter Codex setup.
team-install
Install the team-pinned Babysitter Codex workspace setup.
retrospect
Summarize or retrospect on a completed Babysitter run.
resume
Resume an existing Babysitter run from Codex.
project-install
Install the Babysitter Codex workspace integration into the current project.
plan
Plan a Babysitter workflow without executing the run.