Skip to content

duthaho/skillhub / .claude/skills/pulse

Community-pulse research on any topic — "what are people saying about X right now." Fans out parallel sub-agents across web search, Hacker News, Reddit, and GitHub; ranks findings by real engagement (points/upvotes/stars/comments); flags rumors; and writes a cited brief to chat plus saved .md and .html files. Use when the user wants the current community conversation / recent buzz / sentiment / "last 30 days" view on a person, product, project, or concept — e.g. "/pulse <topic>", "what's the buzz on X", "what are people saying about X lately", "research recent discussion on X". For exhaustive, adversarially fact-checked web reports, prefer the deep-research skill instead.

FileKindSize
SKILL.mdskill md8.9 KB
references/brief-template.mdmarkdown1.4 KB
references/html-design.mdmarkdown1.3 KB

references/brief-template.md

View on GitHub
# Pulse brief template — the brief rendered in Step 3; read it when composing the brief.

**Pre-render check:** read only the TL;DR — it alone must deliver the
headline state of the conversation, so a reader who stops there leaves
correctly informed. If the real headline sits lower, lift it; don't bolt a
second summary on top.

```markdown
# Pulse: <Topic>

**Window:** <resolved window> · **Run:** <YYYY-MM-DD> · **Type:** <detected type>
**Sources reached:** Web ✓ · Hacker News ✓ · Reddit ✓/fallback/✗ · GitHub ✓/✗

## TL;DR
- 3–5 bullets: the headline state of the conversation right now.

## Since last pulse (<date of previous brief>)
- **New:** <clusters that weren't in the previous brief>
- **Faded:** <previous headline items with no fresh activity>
- **Resolved:** <previously unconfirmed items now confirmed/debunked, with source>
(omit this section entirely on the first pulse for a topic)

## Key Developments
For each ranked cluster:
### <Cluster headline>
What happened + why it resonates. Inline citations with engagement metrics and links.
Merge cross-source coverage here.

## Best Takes
> "<quote>" — <author/handle>, <source> (<engagement>) [link]

## Disputed / Unconfirmed
- <claim> — why it's uncertain, who's pushing back. (omit section if empty)

## Sources
Flat list of every cited URL, grouped by source, with engagement metrics.
```
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall