DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to suggest the right agent skill for each Claude Code step with Skillranker

Connect a Claude Code session to SkillRanker so each next step gets a ranked, advisory skill suggestion.

Credentials. Your provider API key lives in a local .env file, so restrict it with chmod 600 and keep it out of shell history and version control.

Remote script. If you use the curl-piped installer, review the script first, since it downloads and runs code on your machine.

Who it is forA developer using Claude Code on a large skill library who keeps losing time picking which procedure fits the current request.

The problemA big skill library makes choosing a procedure a task of its own, and a plausible but unsuitable skill can waste context and steer the agent wrong.

The outcomeClaude Code hooks request a recommendation for the current session, and failed hook calls fall back quietly without blocking the agent.

What you need first

  • Linux or macOS with a local filesystem that supports Unix permissions
  • Your own credential for a Jev-compatible provider, such as TypeSafe_API_KEY for TypeSafe.ai or Cloudflare account settings
  • Rust toolchain for a source build, or the installer's prerequisites: Bash, Python 3, curl, and sha256sum or shasum
  • Explicit consent to send selected session context over the network for live ranking

Steps

  1. Install sr from your checkout with cargo install --locked --path . --bin sr, or use the installer described in the README.
  2. Create a .env file from the example, run chmod 600 .env, add your own TypeSafe API key, and export the values with set -a, . ./.env, and set +a.
  3. Preview the Claude hook settings change with sr install-hook claude.
  4. Apply the hook change with sr install-hook claude --apply.
  5. Check a live ranking for the selected session with sr rank --allow-network.

Prompt for your agent

Using the Dicklesworthstone/skillranker repo, preview the Claude Code hook change with `sr install-hook claude` for the project at <project path>, then apply it only after I confirm. Expected output: the proposed settings diff, then a confirmation that the hook was applied. Verify that `sr doctor --json` reports the hook as configured and that my TYPESAFE_API_KEY is set without printing its value.

Caveat. Fresh rankings need your own provider credential and network consent, and the README says the recommendation is advisory, so the agent still decides what to consult.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page