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

How to check an AI-assisted paper before you sign it with Absent Author

Run paper-author-pass to get questions only you can answer, a claim-evidence map, and verified references.

  • Top pick
  • Research
  • Intermediate
  • 30 minutes
  • From the README
  • Claude Code
  • Codex

Who it is forAn author finishing an AI-assisted paper who must own every claim before submission.

The problemAI-drafted sections can carry unverified references, numbers that disagree between text and tables, and claims no one checked.

The outcomeA list of decision questions for you, a claim-evidence map, a change log, and three questions to answer before you sign.

What you need first

  • git and a shell to clone the repo
  • Python 3.9 or newer for tools/slop_lint.py (no dependencies)
  • Claude Code, Codex, or another agent that reads SKILL.md for the two skills
  • pymupdf (pip install pymupdf) for tools/pdf_hidden_text.py
  • Optional: poppler-utils and tesseract for the OCR check on remapped text

Steps

  1. Clone the repo with git clone https://github.com/THUROI0787/absent-author.git && cd absent-author.
  2. Install the skills with ./install.sh.
  3. Open Claude Code or Codex in your paper folder and tell the agent to use paper-author-pass on paper/ in audit mode.
  4. Answer the questions the skill asks; it does not answer them for you.
  5. Read the claim-evidence map and fix any claim without evidence before you sign.

Prompt for your agent

Use the absent-author repo's paper-author-pass skill on <paper folder> in audit mode. Ask me the questions only the author can answer, then produce a claim-evidence map and a change log. Verify that every reference the skill marks as verified can be found by you in the bibliography.

Caveat. The skill asks questions and gives you a checklist; it cannot confirm that the research itself is sound, and it should not be used to answer its own questions.

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