Connect BITHOT to your agent
Agent Skill, MCP, RSS, API — four ways to read the same data: picks, hot list, daily, weekly, and monthly reports. Anonymous read-only, no API key.
Copied configs include a browser-generated anonymous id used only to merge stats — not an account or key. Clearing site data issues a new one. See the privacy notice.
Install once — it keeps working
No API to memorize and no code to write. For Claude Code, Codex, Gemini CLI, and OpenCode. BITHOT does the lookup; the skill only asks and relays. New capabilities show up without reinstalling.
- 1
Send this to your agent
The installer checks the whole package and will not overwrite another skill. On native Windows, don’t paste Bash into PowerShell — have the agent download the three files from the README. On Git Bash, a false “SKILL.md checksum failed” usually means TEMP landed under D:\Temp and sha256sum prefixed the line with \ — run export TMPDIR=/tmp and retry (no checksum bypass). Current installers hash via stdin to avoid that.
Install promptPlease install the BITHOT Skill: https://bithot.news/bithot-skill/README.md Tell me whether I should start a new session. - 2
Start a new session
Most agents read skills only when a session starts. The current chat may not see it.
- 3
Ask one question
What were the five most important crypto stories in the last 24 hours?If the answer names a time range, summarizes the stories, and links titles to BITHOT, it’s installed.
Questions you can ask
Type bithot and you get today’s picks.
Install from the command line
# Shared Agent Skills folder (Codex, Gemini CLI, GitHub Copilot, OpenCode)
bash <(curl -fsSL https://bithot.news/bithot-skill/install.sh) --target agents
# Claude Code
bash <(curl -fsSL https://bithot.news/bithot-skill/install.sh) --target claudeThe shared folder is ~/.agents/skills/bithot, so several agents can find one install. Claude Code also gets a symlink at ~/.claude/skills/bithot without a second copy. You can read install.sh and SKILL.md before running. To skip dedupe stats, replace --actor … with --no-actor.
Didn’t trigger? Check in this order
- The file is named SKILL.md and sits in a skills folder this agent supports.
- Close the old session, start a new one, and ask the check question again.
- Git Bash “checksum failed”: export TMPDIR=/tmp and rerun the install (backslash TEMP path false positive, not a bad package).
- Ask the agent to list its skills and confirm bithot is there.
- Still stuck: send the platform, version, and install path on the feedback page. Don’t send tokens or local files.
Use it without installing the skill
Have the agent read https://bithot.news/api/v1/agent and follow it. The skill reads those same addresses. A remote MCP client can connect the same way. https://bithot.news/api/v1/agent
What it can’t do yet
- The built-in windows are the last 24 hours and the last 7 days. Older search is not guaranteed.
- You get summaries, why-it-matters, the on-site page, and the original link. Full text stays on the BITHOT reader page.