DEDUPED Hot AI repos, turned into use cases Get 5 a day

How to track policy and news for an industry in one timeline with DSH Industry Research

Search topics through the web tool and keep a deduplicated, dated timeline of public sources for an industry.

  • Research
  • Intermediate
  • 45 minutes
  • From the README
  • Any agent

Who it is forA researcher following regulation and sector news who needs a dated record with citations.

The problemPolicy and news for a sector scatter across pages, and it is hard to tell what changed since the last check.

The outcomeA timeline.jsonl with source snapshots, each entry labeled by evidence category, and a delta summary against the previous run.

What you need first

  • DeepSeek Harness installed, with a profile to add plugins to (README tests against dsh-v0.2.1-alpha.1)
  • Node.js and the dsh command available in the terminal
  • A session workspace where the artifact folder (industry-research) can be written
  • Optional: ctx.web mounted and offline left false, needed for industry_track and web-assisted runs

Steps

  1. dsh plugin --profile demo add dsh-industry-research
  2. Confirm ctx.web is mounted and that offline is false in the profile config
  3. Optionally set sourceAllowlist to the public hosts you trust
  4. Call industry_track with the industry name, topics, and a since date
  5. Review the timeline entries and any citation-only entries with their failure notes

Prompt for your agent

With the dsh-industry-research plugin in DeepSeek Harness, call industry_track for the industry <industry-name> with a list of topics and a since date. Expect timeline.jsonl entries and a delta summary. Verify that each entry has an evidence category and that failed snapshots appear as citation-only entries with a note.

Caveat. industry_track fails loud when ctx.web is not mounted or offline is true, so it needs a web-enabled profile.

Share: X LinkedIn Hacker News Email Copy link

Disclaimer

Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page