Kaspa News Skill

Query the public kaspa.news API for Kaspa ecosystem intelligence. No API keys needed.

Quick Start

CODEBLOCK0

Requirements

• - python3 with requests module
• INLINECODE2
• Internet access to INLINECODE3
• No API keys, no tokens, no auth — all endpoints are public

---

Commands Reference

focused — Curated Community Tweets

Community-curated tweets. Excludes replies. Best for "what's the Kaspa community talking about?"

CODEBLOCK1

builders — Ecosystem/Builder Tweets

Projects building on Kaspa (labeled "Ecosystem" on kaspa.news frontend). Excludes replies.

CODEBLOCK2

top — Highest Engagement Tweets

Sorted by view count (most views first). This is the only command that shows view counts (👁️).

CODEBLOCK3

developers — Developer Tweets

Tweets from known Kaspa core developers. Includes replies (unlike other tweet commands). Shows dev discussions and technical debates.

The script has a built-in list of known dev usernames, but this is only for the default developers command filter. Per-user searches (see below) work for ANY username.

CODEBLOCK4

videos — YouTube Videos

Latest Kaspa-related YouTube videos with view/like counts.

CODEBLOCK5

reddit — Reddit Posts

Latest posts from r/kaspa with upvote scores.

CODEBLOCK6

pulse — AI Pulse Report

AI-generated intelligence report summarizing recent Kaspa ecosystem activity. Single latest report.

CODEBLOCK7

---

Global Options

Option	Description	Default
INLINECODE12	Number of items to show	10
INLINECODE13

Only items from last N hours | all |
| --json | Raw JSON output (for scripting/parsing) | off |
| --sources | Show source links in pulse reports | off |
| -h, --help | Show help text | — |

---

Script Output Format

The script outputs plain text. Here's exactly what each command produces:

Tweet Commands (focused, builders, developers)

CODEBLOCK8

Top Command (includes view counts)

CODEBLOCK9

Videos

CODEBLOCK10

Reddit

CODEBLOCK11

Pulse

CODEBLOCK12

---

🎨 PRESENTATION RULES (MANDATORY FOR ALL AGENTS)

The script outputs plain text. When you present this to a user, follow these rules exactly. This is the approved format — do not deviate.

Tweet Type Emojis

Emoji	Meaning
📝	Regular tweet
💬

Quote tweet (user's own comment only — NOT the quoted source tweet) | | ↩️ | Reply |

What the Script Already Does (don't redo these)

• - ✅ Picks correct emoji (📝/💬/↩️)
• ✅ Shows relative time ("10h", "1d", "5m" — no "ago")
• ✅ Expands t.co links to real URLs
• ✅ Strips trailing t.co image links
• ✅ Decodes HTML entities (& → &, > → >)
• ✅ Truncates at 300 chars
• ✅ Adds SOURCE link on every tweet
• ✅ Shows 👁️ views ONLY on top command

What YOU (the presenting agent) Must Do

X/Twitter Linkification

Convert plain text @handles, #hashtags, and $CASHTAGS into clickable links:

• - @username → [@username](https://x.com/username) — links to X profile
• INLINECODE20 → [#hashtag](https://x.com/search?q=%23hashtag) — links to X search
• INLINECODE22 → [$KAS](https://x.com/search?q=%24KAS) — links to X search

Important:

• - Only linkify REAL handles/hashtags/cashtags
• INLINECODE24, #4, #10BPS (numbers) are NOT hashtags — leave as-is
• INLINECODE27 inside email addresses are NOT handles — leave as-is
• Link to x.com (NOT twitter.com, NOT Telegram)

Pulse Report Formatting

When presenting pulse reports, reformat the summary into grouped sections:

CODEBLOCK13

Pulse formatting rules:

• - Group by category with ━━━ Category ━━━ separators
• Bold project/feature names
• One line per item, max 1-2 sentences
• Use emojis as bullet prefixes (🔧💵🔐💬🌉⚡🏦📊📈💎🎤📱)
• Key people to name: @hashdag (Yonatan Sompolinsky), @michaelsuttonil (Michael Sutton), @OriNewman (Ori Newman)

---

🔍 Per-User Tweet Search

When someone asks for tweets from a specific person (e.g., "show me @michaelsuttonil tweets from last 2 weeks"), this works for ANY username — not limited to the 9 built-in dev names.

How to Query

Fetch ALL endpoints and merge (always go wide):

CODEBLOCK14

Or use the --json output and filter with jq/python inline.

Security note: never interpolate raw user input directly into jq programs. Always pass user values via --arg / --argjson.

How to Present Per-User Results

Group by date (newest first). Standalone posts first, then replies.

CODEBLOCK15

Per-user format rules:

• - 📅 Feb 17 date headers with em dash + brief theme summary
• INLINECODE33 separator between date groups
• Standalone posts first (📝/💬), replies below (↩️)
• Replies: INLINECODE34
• Omit trivial replies ("100%", "sure", "thanks") unless notable
• End with brief editorial summary of themes across the period
• Always search the FULL time range asked — never shorten it
• Show everything found — don't pre-filter or narrow results

---

❌ DO NOT (hard rules)

These are locked rules. Violating any of these = wrong output.

Rule	Why
❌ Don't edit, trim, rewrite, or summarize tweet text	Show user's exact words
❌ Don't merge same-author tweets together

Every tweet is separate |
| ❌ Don't show the quoted tweet's source text | Quote tweets show ONLY the user's own comment |
| ❌ Don't show sentiment percentages (bullish/bearish %) | User explicitly forbids this |
| ❌ Don't show "N tweets analyzed" counts | User explicitly forbids this |
| ❌ Don't show model name in pulse output to users | Internal detail |
| ❌ Don't add bold to @usernames in tweet output | Script format is final |
| ❌ Don't add extra emojis or separator lines to tweets | Script format is final |
| ❌ Don't add "(latest N)" to section headers | Clean headers only |
| ❌ Don't add type labels like "— 📝 Tweet" after time | Emoji prefix is enough |
| ❌ Don't use markdown tables for tweets | Use the line-by-line format |
| ❌ Don't say "according to the pulse report" | Just present the info directly |
| ❌ Don't add engagement metrics (❤️/🔁) to any command except top | Only top shows 👁️ |
| ❌ Don't link @handles to Telegram | Always link to x.com |
| ❌ Don't strip [SOURCE] links | They're always shown |

---

✅ DO (best practices)

Practice	Detail
✅ Run the script, present its output	Don't fabricate or cache old data
✅ Linkify @handles → x.com profiles

[@user](https://x.com/user) |
| ✅ Linkify #hashtags → x.com search | [#kaspa](https://x.com/search?q=%23kaspa) |
| ✅ Linkify $CASHTAGS → x.com search | [$KAS](https://x.com/search?q=%24KAS) |
| ✅ Group pulse reports by category | Use ━━━ separators |
| ✅ Bold project names in pulse | Makes scanning easy |
| ✅ Keep it scannable on mobile | Short lines, emojis, no walls of text |
| ✅ For per-user search: go wide | Search ALL endpoints, full time range |
| ✅ Use --json for custom filtering | Then format manually |

---

Trigger Phrases

Use this skill when the user says anything like:

• - "kaspa news", "what's happening in kaspa", "kaspa tweets"
• "kaspa pulse", "kaspa report", "kaspa update"
• "kaspa devs", "what are kaspa developers saying"
• "kaspa videos", "kaspa youtube"
• "kaspa reddit"
• "show me tweets from @someone" (per-user search)
• "top kaspa tweets", "trending kaspa"
• Any mention of kaspa.news

---

Architecture Notes

• - API base: https://kaspa.news/api (fixed; no env override)
• API returns cached data — query params like ?limit= are ignored server-side
• All filtering is client-side — script fetches full dataset, filters with jq
• No auth needed — all endpoints are public, no API keys
• No runtime env vars required
• Script outputs plain text — the presenting agent handles linkification
• FORMAT_LOCK.md in the skill directory is the canonical format specification