crypto-news-digest
Skill0 starsChanged 3 months agoMITView on GitHub
Aggregate blockchain and crypto news from multiple sources into one structured daily digest. Use when the user asks for a crypto or blockchain news roundup, a daily digest, "what happened in crypto today", or wants market moves and regulation summarized from several outlets.
In this repository11 other files it gives its agents.
- agent-verificationSkill
- claim-evidenceSkill
- defi-risk-assessmentSkill
- evidence-firstSkill
- flaky-test-detectorSkill
- on-chain-analystSkill
- prompt-injection-hardeningSkill
- refactor-verifierSkill
- skill-security-auditSkill
- smart-contract-reviewSkill
- test-integrity-guardSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 50
Write in the reader's language, plain and skimmable.
- Distinctive: line 82
Every factual claim needs a source.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Crypto News Digest
Crypto news is noisy, duplicated across outlets, and often PR dressed as reporting. A useful digest isn't "everything published today" — it's the few developments that actually moved the market or changed the rules, each from more than one source, organized so the reader can skim in thirty seconds.
Sources to pull from
Draw from several, and prefer primary/established outlets over aggregators: CoinDesk, The Block, CryptoSlate, crypto.news, Decrypt, Yahoo Finance (crypto), CNBC (crypto). Cross-check any single-source claim against at least one other outlet before including it as fact.
What to include (and what to skip)
Include only items that are material:
- Market / price — large moves and the reason behind them (not every percentage wiggle).
- ETF & institutional — flows, filings, approvals, major custody changes.
- Regulation / legal — enforcement actions, new rules, court rulings, government policy that changes what is legal to do.
- Stablecoins — peg events, issuer reserves, new launches, de-pegs.
- Altcoins & DeFi — protocol launches, exploits, notable partnerships.
- Security — hacks, exploits, vulnerabilities disclosed.
- Enterprise / adoption — real integrations, not roadmap announcements.
Skip: every token's daily PR, "X hints at Y" without substance, predictions, and anything with no second source.
Procedure
- Gather from at least 3–4 sources; note which outlets carried each story.
- Filter to the material items using the list above.
- For each item: one fact line + why it matters (one sentence) + the source(s). If sources conflict on a number, give the range and say it's disputed.
- Order by importance (market-moving first), not by category.
- Write in the reader's language, plain and skimmable.
Output structure
# Bản tin Blockchain ngày DD/MM/YYYY
(use the reader's language; adapt section titles to it)
## Thị trường / giá
- <fact> — <why it matters> — <sources>
## ETF & tổ chức
…
## Quy định pháp lý
…
## Stablecoin
…
## Altcoin & DeFi
…
## Bảo mật
…
## Doanh nghiệp / áp dụng
…Boundaries
Every factual claim needs a source; every opinion needs a "why". Do not fabricate a price, a filing, or a ruling — if you cannot verify a number from a source you actually fetched, either omit it or mark it explicitly as unverified. A digest is only worth reading if the reader can trust that what it says is real.
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
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.

