agentleFS
abe238abe238/hotinai/.claude/skills/verify/SKILL.md

verify

Skill4 starsChanged 4 months agoApache-2.0View on GitHub

How to build and drive the real hotin CLI for verification (not tests).

  • Reads credentials
  • Installs packages

189 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use genie-hacks, workfly and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • automagik-devSkill

    genie-hacks

    Browse, search, and contribute community hacks — real-world patterns for provider switching, teams, skills, hooks, cost optimization, and more.

    Also in 3 projects that use this

  • automagik-devSkill

    workfly

    Discover a procedure and build its saved workflow — dynamic discovery, drafted script, adversarial verification, landed in the catalog.

    Also in 3 projects that use this

  • TheKREATORSSkill

    instinct-export

    Export instincts from project/global scope to a file

    Also in 3 projects that use this

  • TheKREATORSSkill

    instinct-import

    Import instincts from file or URL into project/global scope

    Also in 3 projects that use this

  • AviadPSkill

    risk-assess

    Assess the risk and blast radius of a proposed code change before implementing it. Evaluates CI impact, framework-wide vs localized scope, rollback path, and identifies blindspots. Use when user says "what's the risk", "is this safe", "assess the impact", "risk assess", "blast radius", or before applying framework-wide or CI-affecting changes. Do NOT use for code quality review (use code-quality) or plan validation (use design-validator).

    Also in 3 projects that use this

  • diego-tobalinaSkill

    build-fix

    Fix build and compilation errors systematically. Run when build fails.

    Also in 6 projects that use this

  • +2 more from automagik-dev
  • +1 more from TheKREATORS

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 168 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every adapter fetch hits a real public API.

    line 60

“Common” is measured: kept by at least 6 in 10 of the 168 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Verifying hotin

hotin is a stdlib-only Python CLI (pyproject.toml entry point hotin = "hotin.cli:main"). Zero-key core (github, trends, hn, npm) hits real public APIs with no config.

Build a handle

python3 -m venv /tmp/hotin_verify_venv
source /tmp/hotin_verify_venv/bin/activate
pip install --quiet -e .
export XDG_DATA_HOME=/tmp/hotin_verify_xdg   # isolates the sqlite cache from ~/.local/share

hotin is now a real binary on PATH. Config lives at ~/.config/hotin/.env (XDG_CONFIG_HOME, not XDG_DATA_HOME) — setup --check reads it directly, unaffected by the cache override above.

Drive it

  • hotin about / hotin setup --check — no network, sanity check the install.
  • hotin hn --limit 3 — one real live call, fast, good smoke test of the free-text GitHub-reference extraction (hn/reddit/youtube share this mechanism).
  • hotin hot --limit N --json — the real end-to-end surface: fetch_all() across all 8 adapters concurrently, cache, merge, rank. Takes ~25s (the fetch_all timeout ceiling) if any source is slow/failing — see gotcha below. Re-running within 300s (default TTL) should make previously-successful sources report "served from cache" and skip the network.
  • hotin search <query> --json, hotin show <owner/repo> --json — cache-only, instant, exercise the merge/score path without any network.
  • Probe error paths: search with no query (exit 2), negative --limit (exit 2), show on an uncached repo (clean JSON {"error": "not_cached", ...}, exit 0).

Known gotcha: npm always times out

hotin.sources.npm.fetch() does one search request per DEFAULT_QUERIES term, then one THROTTLE-gated (1.5s+jitter) download-stats request per candidate package, sequentially. With 5 query terms × up to 40 results each, that's typically 30-100+ unique candidates — 90-300+ seconds of pure throttle wait, blowing straight through engine.fetch_all's 25s per-cycle budget. Confirmed live 2026-07-19: npm reports "error", "timed out" on every hot run, first run AND subsequent warm-cache runs (since it never successfully populates its own cache entry, it's never "fresh" and always retries the full 25s). This is a known, reliably-reproducible issue, not flaky — don't waste another live run "confirming" it again.

Rebuild the single-file distribution after touching src/hotin/

sh scripts/build_zipapp.sh
python3 dist/hotin.pyz --help
python3 -c "import zipfile; print(zipfile.ZipFile('dist/hotin.pyz').namelist())"  # confirm new files are staged

scripts/build_zipapp.sh does a fresh cp -R src/hotin each run, so new modules are picked up automatically — no manual list to maintain.

Be kind to servers

Every adapter fetch hits a real public API. Don't loop hot/hn/etc. repeatedly to "be sure" — one clean live run per surface is enough evidence. search/show are cache-only and safe to run freely.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.