smithery/libpdf-js

explore-references

Research how a feature works in reference libraries

Installation

$ npx skills add smithery/libpdf-js --skill explore-references

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 smithery/libpdf-js.

npx skills add smithery/libpdf-js

Browse all from smithery/libpdf-js

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

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,463 B
  • docs SUMMARY.md 77 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

You are researching how a feature or concept is implemented in the reference libraries to inform our own implementation.

Your Task

  1. Understand the request - Based on the conversation context, identify what feature or topic to research. Ask the user if unclear.
  2. Search the reference libraries in checkouts/:

- pdfjs/src/core/ - Mozilla's PDF.js (parsing focus) - pdf-lib/src/ - pdf-lib (TypeScript API patterns) - pdfbox/pdfbox/src/main/java/org/apache/pdfbox/ - Apache PDFBox (comprehensive coverage)

  1. Analyze the implementations - How does each library approach this?
  2. Summarize findings - Write a research document to .agents/scratch/

Research Process

Step 1: Search Each Library

For each reference library, search for relevant code:

  • Class definitions and data structures
  • Key methods and algorithms
  • Error handling approaches
  • Edge cases handled
  • Public API surface

Step 2: Compare Approaches

Analyze the differences:

  • What patterns does each library use?
  • What are the tradeoffs of each approach?
  • Which handles edge cases best?
  • Which has the cleanest API?

Step 3: Extract Insights

Identify what we should learn:

  • Best practices to adopt
  • Pitfalls to avoid
  • Edge cases we must handle
  • API patterns that feel ergonomic

Output Format

Write your findings to .agents/scratch/<topic>-research.md with this structure:

# <Topic> Research

## Summary

Brief overview of findings and recommendations.

## pdf.js Approach

- How it works
- Key files: `path/to/file.js`
- Pros/cons

## pdf-lib Approach

- How it works
- Key files: `path/to/file.ts`
- Pros/cons

## PDFBox Approach

- How it works
- Key files: `path/to/File.java`
- Pros/cons

## Recommendations for @libpdf/core

- What approach to take
- Key considerations
- Edge cases to handle

Guidelines

  • Be thorough - This research informs implementation decisions
  • Include code references - File paths and line numbers help future exploration
  • Note edge cases - What weird PDFs do the libraries handle?
  • Consider our constraints - We target Node, Bun, and browsers equally
  • Focus on insights - Don't just describe; analyze and recommend

Begin

Search the reference libraries for the topic determined from the conversation context and compile your research findings.