Menu

Individual skill

recent-discourse-sweep

0upvotes

Use this skill when a decision depends on what the market actually said about a company, product, category or person inside a dated window: before a first touch, before a renewal call, before committing to a positioning or content bet. Produces a sourced synthesis plus a coverage report naming which venues were read, which came back empty, and which were never reached. Trigger phrasings: "what are people saying about X right now", "any chatter on this account", "is this trend real or is it one loud thread", "check the last 30 days", "what changed since we last looked", "the research came back empty".

skills/nadav-david/recent-discourse-sweep/SKILL.md

Read pinned source

Source commit 5d786aad0c7b2ca59b1abf1f601f9407ca261996

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
Yes
Repository scan complete
No
Skill scan complete
No
Observed behavior
Instructions only
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
237
Repository last updated
Oct 20, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

Run this before a touch, a call, or a bet that depends on what is true this month. Produces a sourced synthesis and a coverage report.

## The one-line law

A sweep is only as honest as its coverage report. An empty result means nothing until the venues are proven live.

## The play

1. **Fix the window and list the venues before searching.** Name the window in days, then list every venue you intend to read: open discussion communities, technical forums, video, job postings, filings and preprints, the trade press, short-form social feeds, plain web search. The list is the plan. A venue never listed cannot turn up missing later.

2. **Keep the topic string clean.** The topic is a routing key, not a description: plain words, no brackets, no slashes, no "versus" unless a comparison is wanted. Disambiguation belongs in the query terms. A topic carrying a parenthetical splits silently into two searches, one of them a fragment, and half the budget goes into the fragment. Before sweeping a named company, product or person, read `references/query-plan.md`.

3. **Run the venues one at a time and record each outcome as one of three states:** read-with-results, read-and-empty, never-reached. Three different facts, and collapsing them into "nothing found" is the failure this skill exists to prevent. Diagnosis is in `references/coverage-report.md`, to be read the first time a venue comes back empty.
Back to top