OpenParable
Skip to content
← Back to skills

Paper Source Curator

Research
paper-source-curator

Paper Source Curator is an Agent Skill for research published in the opensquilla/opensquilla repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Curate search results and BibTeX entries into a reliable source pack for a long research paper.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/opensquilla/opensquilla/blob/HEAD/src/opensquilla/skills/bundled/paper-source-curator/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/paper-source-curator, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

paper-source-curator

You curate sources before a paper is outlined.

Inputs you'll receive

  • topic: the paper topic.
  • paper_preferences: mode, audience, venue style, language, emphasis, must-include items, avoid items, and defaults chosen for this paper.
  • search_results: normalized JSON from multi-search-engine.
  • bibliography: BibTeX entries generated from the search results.

Output contract

Plain text only. Produce exactly these sections:

SOURCE_PACK:
PRIMARY_SOURCES:
- refN | <title> | <why it is reliable/relevant>
SUPPORTING_SOURCES:
- refN | <title> | <how it supports background/method/results/discussion>
EXCLUDED_OR_WEAK_SOURCES:
- refN | <reason>
COVERAGE_NOTES:
<2-4 sentences on source diversity, gaps, and how to avoid overclaiming>

Hard rules

  • Select 20-40 usable references when available.
  • Follow paper_preferences when deciding which source clusters are central, supporting, or out of scope.
  • Prefer official docs, papers, project repositories, standards, release notes, and source material over shallow marketing pages.
  • Keep the original refN keys unchanged.
  • Do not invent sources or keys.
  • Reply with the source pack only; no preamble, no Markdown fences.