⏳ This skill is pending AI review.

Scores will appear once the review pipeline completes.

version unknown

maintain-ranking-scripts

cooler333@cooler333⭐ 15 stars· last commit 3d ago· 0 open issues

Maintain and improve the scripts that auto-generate this repo's star-ranked "Awesome Claude Code" README. Use when editing helpers/fetch.py, helpers/render.py, or helpers/config.json — tuning scope/category rules, changing the repos.json schema or README layout — and when running the CLASSIFICATION AUDIT to curate helpers/filtered.json and fix scope_filter false positives. Does NOT run the daily refresh (CI cron does that) and does NOT hand-curate an include list (discovery is an exhaustive sweep).

Choose how to use this skill

You do not need every option. Choose the path your AI client supports. The stable page stays the same; versioned files are immutable.

1. Native installer

This listing has no registered native installer command. Use the complete package or source fallback below, depending on what your client supports.

Do not guess an installer command or replace an existing version without reviewing the diff.

2. Complete package recommended

Download the ZIP when available. It includes SKILL.md plus the references, security notes and version metadata.

No complete ProSkills package is published for this listing yet.

3. Prompt-only

Copy the prompt above when the agent can read the stable page or when you want to adopt the workflow without installing a skill.

Need only the instruction file?

Download SKILL.md only if your client requires a single file. The complete ZIP is safer for a full installation because it preserves the references and release context.

No path installs or executes anything by itself. Your agent still needs access to the project files. Before updating, compare the installed version and review the diff.

—/10

// RATINGS

⭐GitHub Stars
⭐⭐ 15 on GitHubGitHub ↗

Growing

🟢ProSkills Score
—
📍

Not yet listed on ClawHub or SkillsMP

// README

Awesome Claude Code & Agent Tools

Updated 2026-11-12 15:28 UTC

Contents

Trending this week

#NameStars+StarsGrowth
1rea⭐ 454.5k+21,334+4.9%
51security-audit-skill⭐ 70.9k+10,355+17.1%
63t3code⭐ 57.9k+10,322+21.7%
50dsh-our-free-model⭐ 71.1k+9,125+14.7%
3skills (mattpocock)⭐ 322.7k+8,236+2.6%

Top 30

#NameStarsPos+StarsCategoryDescription
1rea⭐ 454.5k—+21,334MCP server / toolingReverse engineer anything with agents, from app behavior down to native binaries.
2openclaw⭐ 394.4k—+445OtherThe AI that really does things. Any OS. Any Platform. The lobster way. 🦞
3skills (mattpocock)⭐ 322.7k—+8,236Claude Code skillsSkills for Real Engineers. Straight from my .agents directory.
4superpowers⭐ 316.6k—+3,811Claude Code skillsAn agentic skills framework & software development methodology that works.
5ECC⭐ 301.8k—+4,159MCP server / toolingThe agent harness performance optimization system. Skills, instincts, memory, security, and research-first development for Claude Code, Codex, Opencode, Cursor and beyond.
6deepseek-harness⭐ 279.6k—+6,102Agent harnessDeepSeek Harness: Everything is a Plugin.
7hermes-agent⭐ 262.9k—+2,136Agent harnessThe agent that grows with you
8andrej-karpathy-skills⭐ 232.5k—+2,706Claude Code skillsA single CLAUDE.md file to improve Claude Code behavior, derived from Andrej Karpathy's observations on LLM coding pitfalls.
9skills (anthropics)⭐ 193.5k—+5,896Official AnthropicPublic repository for Agent Skills
10ponytail⭐ 189.6k—+4,601Prompts & system promptsMakes your AI agent think like the laziest senior dev in the room. The best code is the code you never wrote.
11agency-agents⭐ 167.9k—+1,205Agent harnessA complete AI agency at your fingertips - From frontend wizards to Reddit community ninjas, from whimsy injectors to reality checkers. Each agent is a specialized expert with personality, processes, and proven deliverables.
12claude-code⭐ 155.4k—+783Official AnthropicClaude Code is an agentic coding tool that lives in your terminal, understands your codebase, and helps you code faster by executing routine tasks, explaining complex code, and handling git workflows - all through natural language commands.
13cc-switch⭐ 153.9k—+1,827MCP server / toolingA cross-platform desktop All-in-One assistant for Claude Code, Codex, OpenCode,DeepSeek Harness and more. Only official website: ccswitch.io
14spec-kit⭐ 149.5k—+1,793Spec-driven dev💫 Toolkit to help you get started with SDD or any other process!
15ui-ux-pro-max-skill⭐ 148.5k—+2,984Claude Code skillsAn AI skill that provides design intelligence for building professional UI/UX across multiple platforms.
16graphify⭐ 146.6k—+3,771MCP server / toolingTurn any codebase, with its docs, SQL schemas, configs, and PDFs, into a queryable knowledge graph. A /graphify skill for Claude Code, Cursor, Codex, and Gemini CLI: local deterministic AST parsing, every edge explained, no vector store.
17gstack⭐ 141.3k—+1,638OtherUse Garry Tan's exact Claude Code setup: 23 opinionated tools that serve as CEO, Designer, Eng Manager, Release Manager, Doc Engineer, and QA
18awesome-design-md⭐ 127.2k—+1,481Coding agent CLIA collection of DESIGN.md files analysis by popular brand design systems. Drop one into your project and let coding agents generate a matching UI.
19generative-ai-for-beginners⭐ 123.4k—+392Learning & guides21 Lessons, Get Started Building with Generative AI
20orca⭐ 123.2k+2+6,866Coding agent CLIOrca lets you run a fleet of coding agents (e.g. Claude Code, Codex) with your own subscription. Available on desktop, mobile and remote runtime.
21browser-use⭐ 120.8k-1+724MCP server / toolingOpen-source Python library for AI browser agents, plus Browser Use Cloud: stealth browsers and a hosted agent API.
22caveman⭐ 119.3k-1+1,636Prompts & system prompts🪨 why use many token when few token do trick. Viral skill + proxy for coding agents that cuts 65% of tokens by talking like a caveman.
23claude-mem⭐ 116.5k+1+3,109Claude Code skillsPersistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
24agent-skills⭐ 116.4k-1+3,020Claude Code skillsProduction-grade engineering skills for AI coding agents.
25taste-skill⭐ 114.0k+1+3,595Claude Code skillsAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
26paperclip⭐ 113.3k-1+2,022Claude Code skillsThe open-source app everyone uses to manage agents at work
27impeccable⭐ 108.8k+1+5,260Claude Code skillsThe design vocabulary for your coding agent. Steer with polish and bolder, review with critique and audit, catch AI slop before it ships.
28open-design⭐ 107.3k-1+1,263Claude Code skillsThe 1st Collaborative AI Design Agent Workspace. Local-first and open source. Create motion, prototypes, websites, apps, dashboards, presentations, images, and videos with your team and AI agents. Share work, exchange feedback, and iterate together in one workspace.
29awesome-mcp-servers⭐ 97.6k—+326MCP server / tooling

// HOW IT'S BUILT

// FILES

2 files shipped with this skill. Inline text is the catalog copy. The upstream link is the source repository.

  • .claude/skills/maintain-ranking-scripts/SKILL.md7.9 KBupstream ↗
    ---
    name: maintain-ranking-scripts
    description: Maintain and improve the scripts that auto-generate this repo's star-ranked "Awesome Claude Code" README. Use when editing helpers/fetch.py, helpers/render.py, or helpers/config.json — tuning scope/category rules, changing the repos.json schema or README layout — and when running the CLASSIFICATION AUDIT to curate helpers/filtered.json and fix scope_filter false positives. Does NOT run the daily refresh (CI cron does that) and does NOT hand-curate an include list (discovery is an exhaustive sweep).
    ---
    
    # maintain-ranking-scripts
    
    Maintain the scripts behind this repo's auto-generated, star-ranked README of the
    Claude Code / skills / agents / MCP ecosystem.
    
    ## What this repo's pipeline does
    
    1. **`helpers/fetch.py`** (network only) does an **exhaustive** star-bucketed sweep
       of every public repo at or above `min_stars` (the Search API caps each query at
       1,000 results, so the star range is split into adaptive buckets, then
       concatenated). Because the sweep is exhaustive, **discovery is complete by
       construction** — there are no scoped queries that could miss a popular repo. It
       writes two files and nothing else:
       - **`helpers/repos.json`** — the full universe (every repo ≥ `min_stars`),
         metadata only. The single source of truth for everything downstream.
       - **`helpers/out_of_scope.json`** — AUTO classification: universe entries that
         **fail** `scope_filter` (not AI/Claude). Regenerated every run; never
         hand-edited.
       It does **not** categorize, write briefs, rank-to-top-N, fetch READMEs, or apply
       any denylist.
    2. **`helpers/render.py`** (no network) selects the published set —
       `repos.json` minus `out_of_scope.json` minus `helpers/filtered.json` minus
       `helpers/non_english.json` (which it derives itself, see below) minus
       archived, top `render.render_count` by stars — writes
       **`helpers/repos_to_render.json`**, then **categorizes**, builds the short
       **briefs** (from description / topics), and lays out **`README.md`**: a Table of
       Contents, the **Trending this week** cut, the Top-N leaderboard, the long tail
       split into per-category tables, and a footer of links. **The README body is tables
       only** — the prose (scope, column definitions, disclaimer, licensing) lives in
       hand-maintained docs, not in `render.py`; see "Where the static docs live" below.
    3. **`helpers/trend.py`** (no network, git only) supplies the **momentum** columns
       (`Pos`, `+Stars`) and the Trending cut: it reads an *older committed version of
       `repos.json`* straight out of git history — the newest snapshot at least
       `render.trend.window_days` old. **One baseline feeds both columns**, so they always
       describe the same span. No extra API calls and no new state file; the daily commits
       **are** the star history. Best-effort: no git, a depth-1 clone, or history shorter
       than the window drops both columns and the Trending section, and the README still
       renders.
    4. **CI** (`.github/workflows/`): `refresh-ranking.yml` runs the sweep+render daily
       and commits the artifacts; `render-on-edit.yml` re-renders (no network) when a
       human edits `filtered.json` (NOT `config.json` — scope/min_stars are sweep-time,
       so config edits wait for the next sweep). **Both check out with `fetch-depth: 0`**
       — the default depth-1 clone would silently render without the momentum columns.
    
    The ≥`min_stars` universe partitions as `repos.json` ⊇ (`out_of_scope.json` ∪
    `filtered.json` ∪ `non_english.json`). See `reference.md` for the full file contracts and schema.
    
    ## Where the static docs live
    
    `render.py` holds **no prose** beyond the README's one-line header and the footer link
    row. Everything explanatory is a hand-maintained file, edited directly (never
    generated):
    
    | file | holds |
    |------|-------|
    | `docs/METHODOLOGY.md` | how the list is built; what every column means; where `Pos`/`+Stars` come from |
    | `CONTRIBUTING.md` | which files are generated, and which lever to pull to change the output |
    | `docs/DISCLAIMER.md` | no-endorsement, third-party links, trademarks, removals, and the licensing note |
    | `LICENSE` | the CC0-1.0 text itself — the only place it lives; don't restate it in a doc |
    
    Keep the README body noise-free: a new explanation belongs in `METHODOLOGY.md`, not in
    a note under a table. Don't restate config values (`min_stars`, `window_days`) in these
    docs — reference the key so `config.json` stays the single source of truth.
    
    The scripts are **stdlib-only** (no pip installs) and must stay that way.
    
    ## The three exclusion sets (orthogonal)
    
    - **`out_of_scope.json` — AUTO, CI-owned.** "Not AI/Claude." Derived from
      `repos.json` + `scope_filter` every run. **Never hand-edit it** — if something is
      misclassified, fix the *rules* in `config.json` (single source of truth).
    - **`non_english.json` — AUTO, render-owned.** "Description isn't English."
      Derived by `render.py` from `repos.json` every run: any otherwise-publishable
      repo whose GitHub description is ≥ `render.non_english_threshold` non-Latin
      letters, recorded with its measured share. **Never hand-edit it** — move the
      threshold in `config.json` instead. Sited at render because that is where a repo
      becomes *visible*; it needs no network, so it costs the offline half nothing.
    - **`filtered.json` — MANUAL, human-owned.** Repos that *are* AI/Claude-adjacent
      (they pass scope) but are excluded as **redundant**. Each entry is
      `{ "repo_id": "owner/name", "reason": "..." }` (a bare string is also tolerated).
      This is the **only** editorial lever; there is **no allowlist**. Established
      categories:
      1. **Competing coding-agent CLIs / editors** — single-vendor / non-Claude
         (e.g. `google-gemini/gemini-cli`, `openai/codex`, `voideditor/void`).
      2. **API gateways / proxies / resellers** (e.g. `songquanpeng/one-api`,
         `BerriAI/litellm`, `QuantumNous/new-api`).
      3. **Generic AI apps / clients / platforms** — chat UIs, low/no-code builders,
         "AI second brain" apps (e.g. `danny-avila/LibreChat`, `khoj-ai/khoj`).
      4. **Leaked / rights-infringing content** — republished proprietary system
         prompts, credentials, closed-source material (e.g.
         `asgeirtj/system_prompts_leaks`). Excluded on legal/editorial grounds.
      5. **Non-English README** — the published list is English-language. The
         *description* half of this rule is automatic (`non_english.json` above); a
         repo with an English description but a primarily non-English **README**
         still belongs here, because reading a README needs the network and
         `render.py` never networks. **Bilingual is fine as long as the main one is
         English** — `farion1231/cc-switch` ships an English `README.md` with
         translations beside it and stays. Nothing enforces this half, so it decays
         silently — re-check it in every audit (step 5 below).
    
      (Generic **non-AI** repos that match only by keyword belong in neither file —
      they fail `scope_filter` and land in `out_of_scope.json` automatically.)
    
    ## Working on this
    
    - **Adjust scope** (what counts as in-ecosystem) — `scope_filter` in `config.json`.
      This drives `out_of_scope.json`. Loosen a term to rescue a false positive; tighten
      to push a keyword-only match out. **`scope_filter` and `min_stars` are applied by
      `fetch.py` during the sweep, not by render** — editing them takes effect on the next
      daily sweep (or a manual `fetch.py` run / a `refresh-ranking` `workflow_dispatch`).
      A push to `config.json` does NOT trigger the on-edit re-render (that would publish a
      README that ignores the change); only `filtered.json` edits re-render instantly.
    - **Improve categorization** — `category_rules` (`topic_map` / `keyword_rules`) in
      `config.json`; `render.py` assigns the category and groups by it. If you add a new
      category, also add its heading to `render.category_order` (must stay in sync, or it
      falls into "Other"). Rules are applied in this order, first hit wins:
      `match_owner` → keyword r
  • README.mdupstream ↗

    Contents are not inlined in the catalog. Open the upstream file.

Plain-text copy, no login: /skill-bundles/cooler333-awesome-claude-code-claude-skills-maintain-ranking-scripts.md

// REPO STATS

15 stars
0 open issues
Last commit: 3d ago