By emerose
A libkit-backed bibliographer for a personal collection of academic articles: add/import papers from DOI, arXiv, PMID/PMCID, Semantic Scholar id, or PDF; auto-fetch metadata; file PDFs into a human-readable author tree; full-text + semantic search; HTML viewer; audit.
Manage a personal collection of academic articles — add papers from a DOI, arXiv ID, PMID/PMCID, Semantic Scholar ID, or a PDF (auto-fetching metadata from Crossref/arXiv/PubMed/Semantic Scholar), keep PDFs organized on disk in a human-readable author tree, search and browse the library, run semantic search inside the papers, generate BibTeX, bulk-import a folder of PDFs, and run dedupe/integrity checks. It also **discovers new papers** on a topic across many scholarly search APIs (OpenAlex, Semantic Scholar, Europe PMC, PubMed, Crossref, arXiv) and banks them into the library. Use this skill whenever the user wants to save, file, organize, look up, or tidy research papers, build or maintain a bibliography or reading list, run a literature search / find papers on a topic, import a folder of PDFs into their paper collection, find duplicate papers, recover or fix metadata for scanned/untitled PDFs, search the contents of their papers, or export citations — even if they don't say "bibliographer." Triggers include "add this paper," "save this arXiv link," "what papers do I have on X," "find papers on X," "do a literature search," "what's published on X," "import these PDFs," "make a bibliography," "find the DOI/metadata for these PDFs," "search my papers for X," "check my library for duplicates," or "export BibTeX." For a tree of internal scientific experiments (raw lab/CRO data, extracted measurements, analysis, grounded claims), use the scientist skill instead.
Manage a tree of scientific experiments end to end — one folder per experiment holding raw lab/CRO deliverables, extracted data, re-derived analysis, grounded claims, reports, and internal summaries — as one provenance-tracked pipeline raw→data→analysis→claims. Extract raw measurements out of CRO files (Excel .xlsx/.xls, GraphPad Prism .pzfx/.prism, Word/PDF/ PowerPoint) into tidy deterministic data/ CSVs; re-derive analysis (EC50/Hill fits, stats, summaries, figures) from that data; assert grounded scientific claims (each a re-runnable pytest spec linking a statement to sha-pinned evidence with a strength); and index everything into a libkit store for semantic + full-text search — with claims and internal summaries the highest-value searchable content. Use this skill whenever the user wants to turn CRO spreadsheets / Prism / reports into clean data, (re)generate or audit an experiment's data or analysis, fit a dose-response, make or check a grounded claim, ask "what's the evidence for X," "which study has the Day-29 knockdown numbers," or "everything we ran with ASO 7," file a new CRO/lab delivery, scaffold a new experiment folder, keep a README/summary current, or trace a result back to the original measurements — even if they don't say "scientist." For a personal library of published academic papers (DOIs, arXiv, PMIDs, PDFs), use bibliographer instead.
Own this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimOwn this plugin?
Verify ownership to unlock analytics, metadata editing, and a verified badge. GitHub access is read-only (username + org membership).
Sign in to claimBased on adoption, maintenance, documentation, and repository signals. Not a security audit or endorsement.
A collection of Agent Skills
for Claude and other LLM agents, packaged as a
Claude Code plugin marketplace.
Each skill is a self-contained folder under skills/ — a SKILL.md (name +
description frontmatter, then instructions) plus any bundled scripts, references, and
tests.
There are two skills today, and they are complements: bibliographer manages the published literature you read, scientist manages the experiments you run. Both are research tools, and both keep their searchable index in libkit rather than a bespoke database.
| bibliographer | scientist | |
|---|---|---|
| Manages | a personal library of published papers | a tree of internal experiments |
| Inputs | DOI · arXiv · PMID/PMCID · S2 id · PDF | CRO/lab files (Excel, Prism, Word/PDF/PPT) |
| On disk | PDFs filed into a human-readable author tree | one folder per experiment, raw → data → analysis → claims → report |
| Answers | "what do I have on X," "find the DOI for these scans" | "what's the evidence for X," "which study has the Day-29 numbers" |
| CLI | bib | sci (+ a pytest plugin for claims) |
Add a paper from a DOI, arXiv ID, PMID/PMCID, Semantic Scholar ID, or a bare PDF, and the metadata is fetched automatically (Crossref / arXiv / PubMed / Semantic Scholar / Unpaywall) and the PDF filed into a human-readable author tree. From there:
enrich — recover metadata for untitled or scanned PDFs;index.html);Built on libkit as its single store — no separate database — through a bundled
bib CLI. See skills/bibliographer/SKILL.md.
Manage a tree of scientific experiments — one folder per experiment — end to end as a single pipeline where every arrow records provenance:
raw/ → data/ → analysis/ → claims → report
raw/ — the CRO/lab originals, untouched.data/ — tidy, faithful CSVs extracted from raw/ (Excel .xlsx/.xls,
GraphPad Prism .pzfx/.prism, Word/PDF/PowerPoint). No computation lives here; an
extraction audit checks that every data/ value is grounded in raw/.analysis/ — re-derivations from data/: EC50/Hill fits, stats, summaries, and
figures, each sha-pinned to the inputs and recipe that produced it.[claim:<id>], ground a third-party fact on a library paper with [lit:<id>], embed
only grounded figures/tables, and render to PDF/HTML via pandoc.Everything is indexed into a libkit store for semantic + full-text search — with
claims and summaries the highest-value searchable content — so you can ask "what's
the evidence for the dose-dependent effect" or "which study has the lumbar-cord
numbers." sci trace walks any claim or report back down to the original measurements,
and sci reproduce re-runs a derivation to confirm its artifacts still reproduce.
One sci CLI drives the deterministic operations; a pytest plugin runs the claims. See
skills/scientist/SKILL.md, and the per-phase detail under
skills/scientist/references/.
Both skills store their searchable index in libkit,
which embeds every document, so an embedding backend is required. Either set
DEEPINFRA_API_KEY for remote embeddings (no local model), or install
libkit[fancychunk-*] for local ones. See .env.example for the
available keys.
/plugin marketplace add emerose/skills
/plugin install bibliographer@emerose-skills
/plugin install scientist@emerose-skills
Claude Code clones this repo, discovers the skills, and invokes them automatically when
relevant (or manually via /bibliographer:bibliographer / /scientist:scientist).
bib CLI, as a standalone toolInstall the bundled command with uv so it's on your
PATH everywhere:
npx claudepluginhub emerose/skills --plugin scientistInteract with Apple Reminders on macOS using AppleScript
Comprehensive skill pack with 66 specialized skills for full-stack developers: 12 language experts (Python, TypeScript, Go, Rust, C++, Swift, Kotlin, C#, PHP, Java, SQL, JavaScript), 10 backend frameworks, 6 frontend/mobile, plus infrastructure, DevOps, security, and testing. Features progressive disclosure architecture for 50% faster loading.
A growing collection of Claude-compatible academic workflow bundles. Covers scientific figures, manuscript writing and polishing, reviewer assessment, citation retrieval, data availability, paper reading, literature search, response letters, paper-to-PPTX conversion, and evidence-grounded Chinese invention patent drafting. Rules are organized as reusable skill folders with explicit workflows and quality checks.
v9.44.1 — Patch release for Gemini environment/version detection and qwen auth gating. Run /octo:setup.
Harness-native ECC operator layer - 67 agents, 271 skills, 92 legacy command shims, reusable hooks, rules, selective install profiles, and production-ready workflows for Claude Code, Codex, OpenCode, Cursor, and related agent harnesses
UI/UX design intelligence. 67 styles, 161 palettes, 57 font pairings, 25 charts, 15 stacks (React, Next.js, Vue, Svelte, Astro, SwiftUI, React Native, Flutter, Tailwind, shadcn/ui, Nuxt, Jetpack Compose). Actions: plan, build, create, design, implement, review, fix, improve, optimize, enhance, refactor, check UI/UX code. Projects: website, landing page, dashboard, admin panel, e-commerce, SaaS, portfolio, blog, mobile app. Elements: button, modal, navbar, sidebar, card, table, form, chart. Styles: glassmorphism, claymorphism, minimalism, brutalism, neumorphism, bento grid, dark mode, responsive, skeuomorphism, flat design. Topics: color palette, accessibility, animation, layout, typography, font pairing, spacing, hover, shadow, gradient.
This skill should be used when users need to generate ideas, explore creative solutions, or systematically brainstorm approaches to problems. Use when users request help with ideation, content planning, product features, marketing campaigns, strategic planning, creative writing, or any task requiring structured idea generation. The skill provides 30+ research-validated prompt patterns across 14 categories with exact templates, success metrics, and domain-specific applications.