Skip to content

Restructure benchmarks skill and rename to kaggle-benchmarks#1012

Open
nicholaskang-us wants to merge 1 commit into
Kaggle:mainfrom
nicholaskang-us:restructure-benchmarks-skill
Open

Restructure benchmarks skill and rename to kaggle-benchmarks#1012
nicholaskang-us wants to merge 1 commit into
Kaggle:mainfrom
nicholaskang-us:restructure-benchmarks-skill

Conversation

@nicholaskang-us
Copy link
Copy Markdown

@nicholaskang-us nicholaskang-us commented May 15, 2026

This PR restructures the benchmarks skill to adhere to the Agent Skills standard and completes the truncated content.

What problem are we solving

  • The benchmarks skill was previously nested under references, which is not an auto-activatable location for Agent Skills-compliant agents (added a new folder)
  • Not properly formatted with the skills table with a description/version at the top
  • There were no references pointing agents to the official SDK repository or DeepWiki documentation

What changes are proposed

  • Renamed and relocated the skill directory to to match the folder-name standard for auto-activation
  • Updated the YAML frontmatter with proper name (), rich description with keywords, and metadata fields
  • Added links to official SDK resources so agents have a direct reference for writing benchmark task files

@dolaameng
Copy link
Copy Markdown
Contributor

@nicholaskang-us I think @rosbo and @stevemessick has a plan to organize the skills. Let's consult them first.

@dolaameng dolaameng requested review from rosbo and stevemessick May 15, 2026 16:49

## Prerequisites

- Python 3.11+
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm curious if there is a way to specify using the Python required by kaggle-cli without embedding the version number here. Actually, I think you can delete this and just rely on the kaggle installation to enforce it.


```
kaggle benchmarks (alias: kaggle b)
├── auth — Fetch Model Proxy credentials
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How well does this play with kaggle auth login? (Do we really need both?)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants