literature-engineer_skill

This skill builds a large, verifiable candidate pool of literature with stable IDs and provenance for evidence-first surveys.
  • Python

109

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill willoscar/research-units-pipeline-skills --skill literature-engineer

  • SKILL.md5.5 KB

Overview

This skill builds a large, verifiable candidate pool of literature for evidence-first surveys. It expands multi-route recalls (offline imports, arXiv/semantic routes, and snowballing), normalizes metadata, and emits a stable, provenance-rich papers/papers_raw.jsonl ready for dedupe, ranking, and citation generation. The skill blocks rather than fabricates when the target pool or stable identifiers cannot be reached.

How this skill works

The skill ingests offline exports and optional snowball files, labels provenance per input, and merges records. If network is enabled it performs arXiv and Semantic Scholar-style retrievals and online snowballing. It canonicalizes identifiers (arXiv id, DOI, canonical URL), unions provenance across duplicates, and writes papers/papers_raw.jsonl, a human CSV, and a concise retrieval report with route counts and missing-meta stats.

When to use it

  • You need to expand candidate literature to at least 1,200 records before mapping or writing.
  • Stage C1 of an evidence-first survey pipeline: prepare upstream evidence and citations prior to drafting.
  • You have partial offline exports and want to merge plus backfill stable IDs/provenance.
  • You plan to run dedupe/rank, citation generation, or mapping and need standardized input.
  • You want an auditable retrieval report showing route coverage and missing metadata.

Best practices

  • Always aim for >=1200 verifiable records; do not accept fabricated entries under any circumstance.
  • Provide as many offline exports as available under papers/imports/ and papers/snowball/ before online runs.
  • Enable --online and --snowball when possible to backfill IDs and expand via cited-by/reference graphs.
  • Review retrieval_report.md for coverage buckets and missing-meta counts; add more exports or enable network if targets aren’t met.
  • Prefer exports that include arXiv IDs or DOIs (arXiv/OpenReview/ACL) to minimize missing stable identifiers.

Example use cases

  • Merge multiple conference and arXiv exports into a single provenance-rich candidate pool for deduping and ranking.
  • Run an offline-first pipeline in a restricted environment, then enable --online to backfill IDs and run snowballing when network is available.
  • Seed a large survey with pinned canonical IDs (classic papers) plus keyword retrieval to ensure must-cite anchors.
  • Produce a papers/papers_raw.jsonl that downstream citation generators and mapping tools can consume without additional normalization.

FAQ

The skill flags the shortfall in retrieval_report.md and will not fabricate entries; add more offline exports or enable online/snowball modes to reach the target.

Are fabricated or guessed IDs allowed?

No. Every record must include a verifiable stable identifier (arXiv id or DOI or trusted URL) and provenance; fabrication is a hard guardrail.

Can I run fully offline?

Yes. The skill supports offline-only runs by merging provided exports, but missing IDs/abstracts are common—use online options to backfill when possible.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
literature-engineer skill by willoscar/research-units-pipeline-skills | VeilStrat