All skills
shepsci avatar

/kaggle

@256664c

Unified Kaggle skill. Use when the user explicitly mentions Kaggle, kaggle.com, a Kaggle URL, Kaggle competitions, Kaggle datasets/models/notebooks, Kaggle forums/discussions/writeups, Kaggle benchmarks, hackathons hosted on Kaggle, Kaggle badges, or Kaggle account setup. Do not use for generic ML, GPU/TPU, notebook, dataset, benchmark, or data-science tasks unless the user clearly ties them to Kaggle.

Use this Skill: https://skilld.dev/gh/shepsci/kaggle-skill/kaggle

This session only. Nothing lands on disk.

modulescompetitionshackathonsREADME.md

≈929 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Hackathon Module

Retrieve hackathon overview pages, enumerate writeup submissions, and fetch full writeup bodies from Kaggle's MCP hackathon endpoints. Built around the documented endpoint behavior from the shepsci/kmcp-tools 2026-04-22 audit (which sweeps the live https://www.kaggle.com/mcp server and records exactly which tools work, which fail, and which are role-gated).

When to use

Reach for this module when:

  • The user asks about a Kaggle hackathon, AGI/cognitive evaluation, or writeup collection (e.g., kaggle-measuring-agi, meta-kaggle-hackathon).
  • You need rules / eligibility / rubric extracted from the hackathon overview.
  • You need a complete roster of submissions for downstream evaluation or analysis.
  • You need full writeup bodies with project links resolved.

Prerequisites

  • KAGGLE_API_TOKEN in environment, or a token at ~/.kaggle/access_token. KGAT-prefixed tokens are required for many hackathon endpoints.
  • The competition slug (e.g., kaggle-measuring-agi).
  • Host or judge access if you need download_hackathon_write_ups or get_resolved_writeup_links. Both endpoints are role-gated.

Run the credential checker first if anything is unset:

python3 skills/kaggle/modules/setup/scripts/check_all_credentials.py

Endpoint order

This is the working endpoint sequence — see references/hackathon-endpoints.md for the full taxonomy of which endpoints succeed, which fail, and why.

  1. get_hackathon_overview — rules, eligibility, rubric, prizes
  2. list_hackathon_tracks — resolve numeric track ids → titles
  3. list_hackathon_write_ups — paginated submission roster
  4. get_writeup — full body for each submission (preferred path)
  5. get_writeup_by_topic / get_writeup_by_slug — fallbacks when id missing
  6. get_resolved_writeup_links — host-only enrichment pass

get_hackathon_write_up was broken in the 2026-04-22 audit (generic invocation error in both host and participant contexts) and verified recovered in the 2026-05-04 retest. fetch_writeup.py still uses get_writeup first because it has a simpler arg shape (just writeUpId, no competitionName required) — but the wrapper endpoint is now also viable if you have both args.

Scripts

# Step 1 — pull rules, rubric, eligibility
python3 scripts/hackathon_overview.py --competition kaggle-measuring-agi

# Step 2 — enumerate submissions
python3 scripts/list_writeups.py --competition kaggle-measuring-agi

# Step 3 — fetch full body for one submission (id from step 2)
python3 scripts/fetch_writeup.py --writeup-id 123456
python3 scripts/fetch_writeup.py --topic-id 789012      # fallback
python3 scripts/fetch_writeup.py --competition kaggle-measuring-agi --slug my-team-writeup

All three scripts share the same auth resolution (env → ~/.kaggle/access_token → ~/.kaggle/kaggle.json) via skills/kaggle/shared/mcp_client.py.

Role-aware behavior

Hosts and judges see more than participants. Each script preserves permission-denial responses verbatim as evidence rather than silently dropping them — see the role-specific guidance in references/hackathon-endpoints.md.

Related references

Source: SKILL.md on GitHub

1 alert16d5 checks · Risk SAFE
  • Gen Agent Trust Hub16d

    The 'kaggle' skill is a comprehensive and secure integration for Kaggle platform operations. It implements multiple security best practices, including credential masking, restrictive file permissions, and protection against token leakage to third-party sites. It also handles untrusted user-generated content from forums using explicit boundary markers to prevent prompt injection.

  • Socket16d

    No alerts

  • Snyk16d

    Risk: MEDIUM · 1 issue

  • Runlayer6mo

    28/45 files flagged

  • ZeroLeaks5mo

    Score: 93/100 · 2 sections analyzed

Signed by skilld at 256664c. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 2 months ago.

Activeupdated 3 months ago
homepage
https://github.com/shepsci/kaggle-skill
All 1 allowed tools
Bash Read WebFetch Grep Glob
Other metadata
compatibility
Python 3.11+, pip packages kagglehub>=1.0.0, kaggle>=2.2.3, kagglesdk>=0.1.33,<1.0, requests, python-dotenv. Optional: playwright for browser badges; kaggle-benchmarks for local benchmark task authoring. The competitions module's SPA-scraping steps assume Playwright MCP tools are provided by the host agent; the skill itself does not bundle them.
metadata
{
  "author": "shepsci",
  "version": "2.4.0",
  "primaryEnv": "KAGGLE_API_TOKEN",
  "openclaw": {
    "requires": {
      "bins": [
        "python3",
        "pip3"
      ],
      "env": [
        "KAGGLE_API_TOKEN"
      ]
    }
  }
}

README badge

README badge for shepsci/kaggle-skill