Skip to content

a5c-ai/babysitter / library/specializations/algorithms-optimization/skills/codeforces-api-client

codeforces-api-client

Verified

Interface with Codeforces API for contest data, problem sets, and submissions

FileKindSize
README.mdmarkdown752 B
SKILL.mdskill md1.9 KB
---
name: codeforces-api-client
description: Interface with Codeforces API for contest data, problem sets, and submissions
allowed-tools:
  - WebFetch
  - Bash
  - Read
  - Write
  - Grep
  - Glob
graph:
  domains: [domain:computer-science]
  specializations: [specialization:algorithms-optimization]
  skillAreas: [skill-area:dynamic-programming, skill-area:graph-algorithms]
  roles: [role:backend-engineer, role:computational-scientist]
---

# Codeforces API Client Skill

## Purpose

Interface with the Codeforces API to fetch contest data, problem sets, submissions, and user statistics for competitive programming workflows.

## Capabilities

- Fetch contest problems and metadata
- Submit solutions and retrieve verdicts
- Access user standings and rating history
- Retrieve editorials and problem tags
- Virtual contest management
- Fetch recent submissions and status
- Access problemset by tags and difficulty

## Target Processes

- codeforces-contest
- progress-tracking
- skill-gap-analysis
- upsolving workflows

## Integration

Uses the official Codeforces API (https://codeforces.com/apiHelp) with proper rate limiting and authentication when required.

## Input Schema

```json
{
  "type": "object",
  "properties": {
    "action": {
      "type": "string",
      "enum": ["getContestProblems", "getUserSubmissions", "getProblemset", "getStandings", "getUserRating"]
    },
    "contestId": { "type": "integer" },
    "handle": { "type": "string" },
    "tags": { "type": "array", "items": { "type": "string" } },
    "count": { "type": "integer", "default": 10 }
  },
  "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": 1900
}
```
receiving-code-reviewobra/superpowersUse when receiving code review feedback, before implementing suggestions, especially if feedback seems unclear or technically questionable - requires technical rigor and verification, not performative agreement or blind implementationStars: 322kUpdated Claude CodeCodexVerifiedInstall
requesting-code-reviewobra/superpowersUse when completing tasks, implementing major features, or before merging to verify work meets requirementsStars: 322kUpdated Claude CodeCodexVerifiedInstall
using-git-worktreesobra/superpowersUse when starting feature work that needs isolation from current workspace or before executing implementation plans - ensures an isolated workspace exists via native tools or git worktree fallbackStars: 322kUpdated Claude CodeCodexVerifiedInstall
verification-before-completionobra/superpowersUse when about to claim work is complete, fixed, or passing, before committing or creating PRs - requires running verification commands and confirming output before making any success claims; evidence before assertions alwaysStars: 322kUpdated Claude CodeCodexVerifiedInstall