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

How to find out why an expected skill was excluded with Skillranker

Trace where a specific skill dropped out of a ranking and what threshold or setting caused it.

Credentials. The live trace needs your own provider credential and sends the selected context over the network after you pass --allow-network.

Who it is forA skill author or agent operator who expected a particular skill to be suggested and got nothing back.

The problemWhen a skill that should have appeared is missing, it is hard to tell whether visibility, retrieval, the abstention rules, or a threshold removed it.

The outcomeA trace shows the stage where the candidate was excluded, along with thresholds and recovery hints.

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 with cargo install --locked --path . --bin sr.
  2. List the visible, shadowed, and excluded skill records with sr roster --json.
  3. Run the trace with sr rank --context scratch/context.json --allow-network --why-not SKILL_ID --explain, replacing SKILL_ID with the skill you expected.
  4. Read the exclusion stage, threshold, and recovery hint in the output.

Prompt for your agent

Using the Dicklesworthstone/skillranker repo, run `sr roster --json` and then `sr rank --context <context file> --allow-network --why-not <skill id> --explain`. Expected output: the stage where <skill id> was excluded, with thresholds and recovery hints. Verify that the trace reports no extra inference calls beyond the original ranking, as the README describes.

Caveat. The trace explains exclusions in the local pipeline, but the README notes that model-generated reasons are not invented, so you get computed evidence rather than a narrative explanation.

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