sebastiaanwouters/dotagents

librarian

Use for code research that needs dependency internals, upstream implementation examples, or external prior art. Always delegate to a subagent that investigates with opensrc and web search, then return only distilled findings, versions, paths, and links.

First seen Jan 24, 2026

Installation

$ npx skills add sebastiaanwouters/dotagents --skill librarian

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from sebastiaanwouters/dotagents · top by installs.

npx skills add sebastiaanwouters/dotagents

Browse all from sebastiaanwouters/dotagents

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 1
Default branch main
Open issues 2
Status Active

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,593 B
  • docs SUMMARY.md 270 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 32 installs

SKILL.md

Librarian

Always spawn a subagent first. If subagents unavailable, say blocked; do not do Librarian work in main context. Main agent frames the question, constraints, repo/package names, then waits and integrates only the subagent summary. Subagent first derives exact package/library version from this project: lockfile, manifest, tool config, workspace config, or vendored source. Research that version, not latest, unless user explicitly asks latest. Subagent uses npx opensrc <pkg|owner/repo|pypi:pkg|crates:crate> when internals matter; read opensrc/ + opensrc/sources.json; fetch matching source before guessing. Subagent uses web search for newer ideas, docs, examples, prior art, and “who already solved this”; prefer primary sources, cite links, note dates when recency matters. Use opensrc for how code actually works. Use web for how others use it, compare patterns, or for anything likely newer than local context. Return only: answer, key evidence, exact package/repo/version and where version came from, relevant file paths/symbols, and links. No long logs, no pasted source, no wandering notes. Good prompts: “how is X implemented internally?”, “find examples of Y with Z”, “trace this error into dependency code”, “connect our code to upstream behavior”.