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

How to map an industry chain with sourced values and gap list with DSH Industry Research

Build an upstream, midstream, and downstream chain map where every number carries a source and missing data is listed.

  • Top pick
  • Research
  • Intermediate
  • 30 minutes
  • From the README
  • Any agent

Who it is forAn industry analyst starting a sector study who needs a structured chain map with no unsourced figures.

The problemChain maps often mix guessed numbers with sourced ones, and missing layers go unnoticed.

The outcomeA validated chain.json plus a list of explicit gap slots and bottleneck nodes for the industry.

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. dsh --profile demo --dump-config | grep dsh-industry-research
  3. In a session, load the method: 加载 industry-research-method 技能
  4. Call industry_map with a chain of nodes (tier upstream, midstream, downstream) and edges, giving each sourced metric a sourceRef
  5. Read the gap list returned by industry_map and fill or keep each gap marked 待补

Prompt for your agent

Using the dsh-industry-research plugin in DeepSeek Harness, call industry_map for the industry <industry-name> with a chain of nodes and edges. Expect a saved chain.json and a gap list. Verify that every metric with a value has a sourceRef, and that the tool reports the gaps rather than filling them.

Caveat. The pack is for research support only and is not investment advice, and it does not use paid or login-walled 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