How to run the PairTeX test suite before tagging a release with PairTeX

Related use cases from other repos

• Pull compound and protein records with source provenance

  Query public biology and chemistry databases and get each record with its source endpoint.

  • Scientific Agent Skills
  • Claude Code
  • Codex
  • Cursor
  • Research
  • Intermediate
  View prompt

  Using the scientific-agent-skills repo, read skills/database-lookup/SKILL.md and query PubChem, ChEMBL, and UniProt for <target gene or compound list>. Return a table of identifiers and key properties, with the endpoint and access date for each row. Verify that every row names its source endpoint and flag any database that needs a key you do not have.

  Share Save

• Retrieve speaker-labeled evidence from a group chat locally

  Store a multi-person conversation and pull back who said what for a question, with no API key.

  • Speaker Mem R1
  • Research
  • Intermediate
  View prompt

  Clone the SpeakerMem-R1 repo (2022hpsk/SpeakerMemR1), set up the virtual environment and install the package as its README describes, then run code/speakermem_pkg/examples/quickstart.py. Report the memory stats and the retrieved entries for the questions 'Who handles evaluation?' and 'What does Bob handle?'. Verify that each retrieved entry shows the speaker name.

  Share Save

• Stress-test an architecture decision before committing

  Get independent answers, anonymous reviews, and a reasoned recommendation on a design choice.

  • DSH Council
  • Research
  • Intermediate
  View prompt

  Using the a1exsun/dsh-council repo in DSH Web, run /council on this design question: <design question with both options and the failure scenario>. Return the recommended design, its stated assumptions, and the listed disagreements and blind spots. Verify that every assumption appears in the question context and was not invented.

  Share Save

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