Menu

Hot votes

Hot this week

Explore weekly community picks for agent skills. One confirmed vote per GitHub account, submitted through MCP. Paid placements never affect votes.

Nov 2, 2026 – Nov 8, 2026

1 vote this week

Voting open
  1. #1

    anthropics/skills

    1 vote

How Hot works

GitHub stars show how many people bookmarked a repository. Hot shows which skills people recommend this week, voted from their own coding agent.

Why a second metric

Stars can be bought or inflated. A Hot vote needs a real GitHub account at least 30 days old, counts once a week, and comes from someone who connected hotskills to their agent. That makes Hot harder to fake than stars. It is not impossible, so a sudden burst of votes from new accounts is held for a manual check.

Where your vote goes

  • The Hot this week ranking at the top of this page, refreshed every hour.
  • The weekly archive below, when the week closes on Sunday.
  • The weekly newsletter features the top Hot picks.
  • The heat score of the skill: votes are one of six signals, with a weight of 10% and a cap of 20 votes a week, so a vote campaign cannot dominate it.
  • Advertising never touches votes, this ranking or heat.

Vote from your agent in four steps

  1. Connect once

    Create a free key, then add the hotskills MCP server to your agent. For Claude Code:

    claude mcp add --scope user --transport http hotskills 'https://hotskills.dev/mcp' --header 'Authorization: Bearer ${HOTSKILLS_API_KEY}'

  2. Ask in plain words

    Write to your agent as you would to a colleague:

    This skill saved me hours this week. Vote for example-org/release-notes-skill as this week’s hot skill on hotskills.

  3. Your agent calls vote_hot

    The agent sends one MCP tool call with the repository name:

    {
  "jsonrpc": "2.0",
  "id": 7,
  "method": "tools/call",
  "params": {
    "name": "vote_hot",
    "arguments": { "repo": "example-org/release-notes-skill" }
  }
}

  4. Confirm

    Your client asks you to confirm. Nothing is recorded until you say yes. Then the agent answers:

    Your vote for example-org/release-notes-skill is recorded for 2026-11-02.

    If your client cannot show a confirmation form, the agent asks you in the chat and sends the vote again with a one-time token.

Changed your mind? Ask for another skill before Sunday ends (Europe/Rome). The new vote replaces the old one.

The repository in this example is made up.

When a vote does not count

Your account is younger than 30 days
The vote is refused: “Hot voting requires an active GitHub account at least 30 days old.”
It is your own repository
The vote is refused: “You cannot vote for your own repository.”
You vote again in the same week
The new vote replaces the previous one. The confirmation says so: “This replaces your current vote for this week, if any.”
The skill cannot receive votes
Skills held back by our security checks, and skills that ask agents to vote for them, answer: “This skill can't receive Hot votes right now.”
A sudden burst of votes
Votes from many new accounts on one skill within an hour are held for a manual check and do not count until released: “Your vote for example-org/release-notes-skill is held for an abuse review and is excluded from the ranking.”
You say no
Nothing changes: “Voting cancelled; no vote was changed.”

The rules

  • One vote per GitHub account each week, Monday to Sunday (Europe/Rome).
  • Accounts must be at least 30 days old.
  • You cannot vote for your own repository.
  • Advertising never affects votes or this ranking.
  • Only totals are published, never who voted.
Explore the MCP connection
Back to top