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

How to assemble an auditable industry report with verified evidence with DSH Industry Research

Combine chain, timeline, and company evidence into a report where each claim points to registered evidence.

  • Research
  • Advanced
  • 60 minutes
  • From the README
  • Any agent

Who it is forA research lead who must hand over an industry report that another reader can audit claim by claim.

The problemReports drift from their sources, and unsourced or undated assertions slip through.

The outcomeA report.md and manifest.json with a source-traceability table, and claims marked by verdict or as unverified.

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. Finish the chain map with industry_map and the timeline with industry_track first
  3. Run company_scan for any companies the report will cover
  4. Call industry_report with the industry name, sections, and optional draft, or let it build the auto-draft
  5. Open report.md and manifest.json and confirm each claim links to an evidence ID

Prompt for your agent

With the dsh-industry-research plugin in DeepSeek Harness, call industry_report for the industry <industry-name>, using the existing chain, timeline, and company artifacts. Expect report.md and manifest.json in the reports folder. Verify that every claim's evidence IDs exist and that the delivery contract passed with no placeholders.

Caveat. The report is research support only, and claims marked unverified on the fallback path still need a human check against their sources.

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