Run any Skill in Manus with one click

pulse

Stars1

Forks0

UpdatedJuly 10, 2026 at 01:44

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.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

duthaho

duthaho/skillhub

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Market Research Analysts and Marketing SpecialistsBusiness and Financial Operations Occupations·SOC 13-1161

File Explorer

3 files

SKILL.md

readonly

More from this repository

same repository

bugfix

duthaho/skillhub

Lightweight bug-fixing loop — reproduce → root-cause → fix test-first → verify — deliberately separate from the heavyweight feature workflow so small fixes don't drag a spec-and-plan process behind them. Demands a deterministic reproduction before any code changes, a stated root-cause hypothesis confirmed with evidence (never a shotgun fix), a failing test that captures the bug, and the original repro re-run as proof. Keeps a one-line-per-bug log in out/dev/bugfix-log.md and checks it first, so recurring bugs get recognized instead of re-diagnosed. Use when the user reports something broken, failing, throwing, or flaky, or asks to fix a bug — e.g. "/bugfix login 500s on empty password", "fix this error", "this test is flaky", "why is X crashing". If the fix turns out to need real design work, hand off to feature; the shipping gate is done.

2026-07-191

daybrief

duthaho/skillhub

Morning work briefing — "what does my day look like, in one scan?" Gathers today's calendar and emails needing attention (via connected Google MCP tools when available), recent git activity and unfinished work across your local repos, your open tasks (TODO file / assigned GitHub issues), and a quick radar check on topics you track — all in parallel — and renders one compact, prioritized brief in chat, carrying over unfinished focus items from yesterday's saved brief. Every source is optional and degrades gracefully; strictly read-only (never sends email, never touches the calendar, never pushes). Use at the start of a workday or when the user asks "what's on today", "morning brief", "daybrief", "catch me up", "what should I focus on today". For deep research on one topic use pulse instead.

2026-07-191

scout

duthaho/skillhub

Competitive reconnaissance for your project — what do the repos solving this same problem do better, and what's worth adopting? Finds peer repos (ranked by activity, downloads, dependents — never raw stars), mines what their users beg for — issue reactions, releases, docs claims, every finding with a locator — and verdicts each candidate feature ADOPT/ADAPT/SKIP/WATCH, where SKIP is the default and "a competitor has it" is never a reason. ADOPT items become ready seeds for feature or autopilot; verdicts persist in out/scout/tracker.md so repeat runs open with what changed. Keyless. Use for "what are similar projects doing", "compare us to X", "what are we missing" — e.g. "/scout", "/scout <owner/repo>", "/scout deep <repo>". For X-vs-Y tech choices use verdict; for community buzz use pulse.

2026-07-191

verdict

duthaho/skillhub

Architect-grade technology decision briefs — "which option should we pick, and why?" Takes a decision question (X vs Y vs Z for a stated context: library, database, framework, platform, buy-vs-build) plus your constraints, fans out parallel sub-agents to research each option's project health, community sentiment, technical claims, and operational story, then scores options across weighted criteria and emits an ADR-style recommendation with a full scorecard and cited evidence. Keyless; the recommendation is advisory — you decide. Use when the user must choose between technologies or approaches — e.g. "/verdict postgres vs mongodb for <use case>", "should we use Kafka or NATS", "compare X and Y", "buy vs build", "which framework for this". Also supports "/verdict revisit <brief>" to cheaply re-check a past verdict's revisit-when triggers. For community buzz on a single topic use pulse; for exhaustive fact-checked research use deep-research.

2026-07-191

blueprint

duthaho/skillhub

Human-facing documentation, architecture docs, and mermaid diagrams for a codebase, a module, or a feature — "draw me the architecture, with receipts." Fans out read-only sub-agents to build a grounded component graph first: every node is a real path, every edge backed by a grep-verified import or call — unverifiable edges are dropped, not drawn. Diagrams render from that verified table per a fixed checklist (never freehand mermaid), capped at 5–8 top-level components with drill-down pages; every doc section cites its sources as file:line. Drafts in chat, writes docs/blueprint/ only on your yes, and stamps a manifest with date + commit so /blueprint refresh regenerates only what the diff touched. Use for "generate an architecture diagram", "document this codebase or module for people", "create a mermaid diagram of this feature" — e.g. "/blueprint", "/blueprint the payment flow", "/blueprint refresh". For agent-facing orientation (AGENTS.md) use map; blueprint is the human-facing sibling.

2026-07-191

map

duthaho/skillhub

Codebase orientation for an unfamiliar or large repo — "map this before I work in it." Fans out read-only Explore sub-agents that navigate the code (keyless — grep/glob/read, no embeddings to go stale) along the order that matters: entry points, build/test/lint commands, architecture and key abstractions, conventions and gotchas, test layout. Distills the findings into a lean AGENTS.md at the repo root — the cross-tool standard file many agents auto-load — where every claim points to a real file and nothing survives that isn't load-bearing. Human-in-the-loop: it drafts, you approve, and it never writes or commits into your repo without an explicit yes. Stamps the map with date + commit so /map refresh regenerates only what went stale. Use before working in a repo you or the agent don't know — e.g. "/map", "/map the auth subsystem", "generate an AGENTS.md", "/map refresh". Run it upstream of feature or bugfix; for the end-of-session shipping gate use done.

2026-07-191

name

pulse

description

pulse — community-pulse research

/pulse <topic> [window/flags in plain language]

Answer one question: what is the community actually saying about this topic right now, and what's resonating? You ground every claim in a real source and rank by real engagement — not by what a search engine's editors surfaced.

Inputs

Topic (required): a person, product/company, project/repo, or concept/event.
Window (optional, plain language): default last 30 days. Honor overrides like "last week", "past 6 months", "this year". Record the resolved window.
Any other plain-language steering ("focus on Reddit", "ELI5", "just the drama").

Step 0 — Resolve scope (ask only if genuinely ambiguous)

Run immediately for clear topics. Ask 1–2 quick questions only if:

the name maps to multiple plausible entities (e.g. a common name, an ambiguous product), or
there's no obvious angle and the result would likely research the wrong thing.

Otherwise proceed and state your assumptions in the brief header.

Auto-detect the topic type and weight sources accordingly:

Detected type	Source emphasis
Person (dev/tech)	GitHub (velocity) + Hacker News + web + Reddit
Person (non-tech)	Web + Reddit (skip/deprioritize GitHub)
Product / company	Reddit + web + Hacker News (GitHub if it's a tool)
Project / repo / tool	GitHub + Hacker News + Reddit + web
Concept / event	Web + Hacker News + Reddit (skip GitHub)

Do light entity resolution first when useful (e.g. the canonical subreddit, the GitHub owner/repo or username, the official site) so sub-agents search the right handles rather than guessing.

Step 1 — Fan out: parallel source sub-agents

Spawn the relevant source sub-agents concurrently (one message, multiple Agent calls). Skip sources the topic type deprioritizes. Give each the topic, resolved entities, and the time window. Each sub-agent must return structured findings: for every item — title, url, source, engagement (the raw metric + its kind), date, and a 1–2 sentence snippet. Then it deepens its top 2–3 items (below). Each gathers ~8–10 candidates before deepening.

Use subagent_type: "Explore" (read-only, fast) for fetch-heavy sources.

Effort scaling: match the fan-out to the ask. A niche topic or an explicit "quick check" needs only the 2 best-matched sources from the table; the full fan-out is for broad or clearly hot topics. Lossless hand-off: if a sub-agent's deepened findings run long (many quotes/threads), have it write the full extracts to out/pulse/.work/<source>.md and return just its ranked summary — read the files at synthesis instead of losing detail in the relay.

Web sub-agent

Use WebSearch with several query variations (topic + "news"/"review"/"discussion"
- recency terms). Prefer results inside the window.
Authority over SEO: prefer primary sources (official posts, the actual thread/repo, named practitioners) over SEO-optimized aggregators and listicle farms. A claim that appears only on low-quality aggregator sites is low-trust — mark it accordingly.
Engagement proxy: publication prominence + how often a story recurs across results.
Deepen top 2–3: WebFetch the article and extract the core claim + any quotes.

Hacker News sub-agent (free Algolia API — most reliable signal)

Search: WebFetch → https://hn.algolia.com/api/v1/search?query=<TOPIC>&tags=story&numericFilters=created_at_i>UNIX_START (compute UNIX_START with a real shell command — e.g. date -d '30 days ago' +%s — never guess the timestamp; for relevance over recency use /search instead of /search_by_date).
engagement = points and num_comments.
Deepen top 2–3: fetch https://hn.algolia.com/api/v1/items/<objectID> and pull the highest-signal top-level comments (the actual takes).

Reddit sub-agent (best-effort, keyless)

Try WebFetch on public JSON: https://www.reddit.com/search.json?q=<TOPIC>&sort=top&t=month (map t to the window: week/month/year), and/or https://www.reddit.com/r/<SUB>/search.json?...&restrict_sr=1.
engagement = ups (upvotes) and num_comments.
Deepen top 2–3: fetch the thread JSON (<permalink>.json) and pull top comments.
Fallback chain on 403/empty: first retry the same JSON paths on old.reddit.com (often served when www is blocked); if that also fails, use WebSearch for site:reddit.com <topic> and WebFetch the threads. Note in the brief that Reddit was reached via fallback.

GitHub sub-agent (keyless REST, 60 req/hr)

Repo/tool topic: https://api.github.com/search/repositories?q=<TOPIC>&sort=stars, then for the chosen repo pull recent commits, releases, and open/closed PR counts to gauge shipping velocity.
Person topic: resolve the username, then users/<u> + recent users/<u>/events (public) to summarize what they're shipping.
engagement = stars, recent commit/PR/release cadence.

If a source returns nothing usable after its fallback, record it as unreachable — do not fabricate.

Step 2 — Synthesize (main agent)

Check for a previous pulse (delta memory): look for earlier out/pulse/<slug>-*.md files for this topic. If one exists, read the most recent one and compute the delta for a Since last pulse section: which clusters are new, which previous stories have faded, and which previously Disputed/Unconfirmed items have since been confirmed or debunked (say which, with a source). This is what makes repeat pulses on a tracked topic useful — the delta, not a second snapshot. Skip silently on the first run for a topic.
Dedup & cluster: merge the same story appearing across sources into one cluster; keep the strongest engagement signal and cite all sources in the cluster.
Rank clusters by engagement (normalize across kinds — treat HN points, Reddit upvotes, GitHub stars, and comment volume as comparable "this resonated" signals; weight recency within the window).
Flag reliability: explicitly tag rumors, speculation, single-source claims, and contested items as Disputed/Unconfirmed. Never let a rumor read as fact.
Pull Best Takes: 2–5 genuinely notable/clever/viral quotes, each attributed with its source and engagement.

Step 3 — Emit the brief

Render the brief in chat per references/brief-template.md (read it when you reach this step), then save it as .md and a self-contained .html file (see Output files). Cite inline as ([source], <engagement>) with a linked URL.

If the user asked for ELI5, prepend a short plain-language summary above TL;DR.

Output files

Save to ./out/pulse/ in the current working directory:

out/pulse/<slug>-<YYYY-MM-DD>.md — the markdown brief verbatim.
out/pulse/<slug>-<YYYY-MM-DD>.html — a bespoke, distinctively designed brief (see below). Self-contained: inline <style>, no JavaScript, links preserved, engagement metrics visible, responsive, print-friendly.

<slug> = topic lowercased, non-alphanumerics → hyphens. Compute the date with a shell command (e.g. date +%F) — do not guess it. Create out/pulse/ if needed; the briefs are the user's to commit or ignore — don't edit .gitignore for them.

Tell the user the two saved paths at the end.

Designing the HTML brief

Design the .html via the frontend-design skill using the brief in references/html-design.md; if unavailable, fall back to a clean self-contained dark-mode, no-JS layout.

Guardrails

Keyless only. Never request or use API keys. Degrade gracefully.
No fabrication. Every claim → a real fetched source. Mark unreachable sources honestly in the header.
Recency discipline. Stay inside the window; if a pivotal item is older, include it but label it as background/older context.
Engagement is the spine. Order by what resonated, show the numbers inline.
Speed over exhaustiveness. This is a pulse, not a dossier — for the latter, point to deep-research.