x-pulse — Claude Code command: what it does, how to install
x-pulse scans X via Grok x_search for topic trends, popular angles, and post ideas, then saves the research note to your vault.
MIT ★ 5,412 updated 2026-10-24
/plugin marketplace add eugeniughelbur/obsidian-second-brain
/plugin install obsidian-second-brain@obsidian-second-brainWhat x-pulse does
Part of the obsidian-second-brain suite, this command triggers scripts.research.x_pulse using uv run. It breaks down active discussions into emerging angles, underexplored gaps, effective hooks, and tone patterns. The agent immediately prints these findings alongside drafted post suggestions.
Output notes are saved automatically to Research/X-pulse/YYYY-MM-DD - <slug>.md while adhering to references/ai-first-rules.md. Generated documents include an agent preamble, detailed frontmatter, inline quotes, and [[wikilinks]] for key concepts. An update line is also written to log.md.
The environment requires uv to run the underlying Python module. If no discourse occurred in the preceding 72 hours, the command suggests broadening your query or trying /research instead.
What it helps with
- discover trending talking points and prominent voices on X
- extract working hooks and angles for upcoming social posts
- archive AI-readable research briefs directly into an Obsidian vault
Example prompts for the agent
- /x-pulse AI automation
- scan X for vibe coding
- what should I post about local models today
How to install x-pulse
1Plugin marketplace
/plugin marketplace add eugeniughelbur/obsidian-second-brain/plugin install obsidian-second-brain@obsidian-second-brain2Manually: put the files in place
.claude/commands/x-pulse.mdCall it with /x-pulse. For all projects use ~/.claude/commands/
Manually: put the files in place
~/.codex/prompts/x-pulse.mdCall it with /prompts:x-pulse. Codex marks this format deprecated in favour of skills
Manually: put the files in place
.github/prompts/x-pulse.prompt.mdManually: put the files in place
.gemini/commands/x-pulse.tomlGemini stores commands as TOML: the prompt text goes into the prompt field
Questions about x-pulse
How to install x-pulse in Claude Code?
Run /plugin marketplace add eugeniughelbur/obsidian-second-brain, followed by /plugin install obsidian-second-brain@obsidian-second-brain. Alternatively, configure .claude/commands/x-pulse.md.
What does x-pulse do?
It uses Grok x_search to map recent discussions around a topic, highlights working angles, and produces ready-to-use post ideas.
What happens when recent activity is missing?
When the script finds no conversations over the last 72 hours, it recommends broadening the subject or running /research for web-wide results.
Source text
x-pulse.md · MIT
---
description: Scan X for what's trending in a topic - themes, voices, hooks, and post ideas powered by Grok x_search
category: research
triggers_en: ["x pulse", "what is trending on twitter", "scan x for", "twitter pulse"]
triggers_de: ["X-Puls", "was ist auf Twitter im Trend", "X durchsuchen nach", "Twitter-Puls"]
triggers_es: ["x pulse", "qué es tendencia en twitter", "escanea x en busca de", "pulso de twitter"]
triggers_pt: ["x pulse", "o que está em alta no x", "escaneie o x em busca de", "pulso do twitter"]
triggers_zh: ["看看 X 上这个话题的趋势", "推特上这个话题有什么热点", "扫描 X 上的热门讨论", "分析这个主题的社交媒体风向"]
---
Use the obsidian-second-brain skill. Execute `/x-pulse [topic]`:
1. Resolve the topic from the user's argument. Multi-word topics are fine ("AI automation", "vibe coding"). If no topic was given, ask: "What topic should I scan X for?"
2. Run the script from the skill root (its absolute path was given at session start as **Skill root**; substitute it for `SKILL_ROOT`):
```bash
uv run --directory "SKILL_ROOT" -m scripts.research.x_pulse "<topic>"
```
3. The script returns a structured pulse: WHAT'S HOT (themes with rep posts + voices), WHAT'S UNDEREXPLORED (gaps), HOOKS THAT ARE WORKING, VOICE & TONE WORKING, POST IDEAS FOR YOU TODAY. Show the full output to the user verbatim.
4. **Default save behavior: saves automatically.** The script writes an AI-first note to `Research/X-pulse/YYYY-MM-DD - <slug>.md` with the AI-first vault rule applied (preamble, frontmatter, recency markers, sources verbatim). It also appends a one-line entry to `log.md`.
5. After printing, mention to the user the file path that was saved (the script prints this on stderr, surface it cleanly).
6. Plain English triggers that route to this command: "what's hot on X about [topic]", "X pulse on [topic]", "what should I post about [topic] today", "scan X for [topic]", "trends on X about [topic]".
7. If the script reports "No active discourse found in last 72h on this topic", offer to either broaden the topic or try `/research [topic]` instead (Perplexity for general web research).
8. If the script fails with a clear error, surface it verbatim. Auto-retry on transient errors is handled inside the script.
---
**AI-first rule:** Every note created or updated by this command MUST follow `references/ai-first-rules.md` - `## For future agent` preamble, rich frontmatter (`type`, `date`, `tags`, `ai-first: true`, plus type-specific fields), recency markers per external claim, mandatory `[[wikilinks]]` for every person/project/concept referenced, sources preserved verbatim with URLs inline, and confidence levels where applicable. If that path does not resolve from your working directory, search upward for it; if you still cannot read it, say so before writing rather than producing a note that silently skips the rule. The vault is for future agent retrieval - not human reading.
**Anti-fabrication:** Search exhaustively before claiming any note, person, or file is absent - false absence is the most common failure mode - and never invent facts, entities, or dates (mark unknowns as `TBD`). See the anti-fabrication and search-completeness hard rules in `references/ai-first-rules.md`.
© Eugeniu Ghelbur · MIT · eugeniughelbur/obsidian-second-brain