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

How to find claims in a draft that lack source evidence with DSH Research Report

Seal a draft and read the visible markers to see which claims have no bound evidence.

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

Who it is forA writer or analyst reviewing an AI-drafted document who needs to know which statements have no backing source.

The problemUnsupported statements look as authoritative as sourced ones, so gaps are easy to miss.

The outcomeA sealed report where every unsupported claim carries a visible marker and appears in Appendix A.

What you need first

  • DeepSeek Harness (dsh) installed, as described in the Compatibility section of the README
  • npm available to install the plugin
  • A workspace where the harness can write the default .research-ledger and research-reports directories
  • Source text or workspace files to register as evidence

Steps

  1. Run dsh plugin --profile demo add dsh-research-report if the plugin is not yet installed.
  2. Submit the draft through research_report({ topic: "<topic>", sections: [...], claims: [{ id: "c1", text: "<claim>", evidenceIds: [] }], evidenceRefs: [] }). (inferred, check the README)
  3. Open the generated report.md and search for the unverified marker in the report body.
  4. Read the Appendix A list in report.md and note each claim it names.
  5. Register sources with evidence_add and reseal the report with the new evidence ids bound to those claims.

Prompt for your agent

Using dsh-research-report in DeepSeek Harness, seal a report on the draft at <draft path> with no evidence bound to the claims. Expected output: report.md with unverified markers on each unsupported claim. Verify that every claim with an empty evidenceIds list is marked unverified rather than passed silently.

Caveat. A claim with no evidence is marked unverified, and the plugin cannot find the missing sources for you.

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