IN

integration-research

Conducts honest research on book service integration capabilities.

Install

mkdir -p .claude/skills/integration-research && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/18014" && unzip -o skill.zip -d .claude/skills/integration-research && rm skill.zip

Installs to .claude/skills/integration-research

Activation

This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.

Use when researching a book service integration (Libby, Goodreads, Google Books, Open Library, Calibre, Audiobookshelf, Amazon, B&N, StoryGraph) to honestly separate official API support from import/share/deep-link support before building or documenting it.
257 chars✓ has a “when” triggerlonger than Claude Code's old 250-char listing cap (fine on current versions)
Intermediate

Key capabilities

  • Research official API availability and authentication models for book services
  • Identify export/import capabilities and supported fields for user data
  • Determine Android share targets, App Links, or stable URLs for parsing
  • Document rate limits and terms of service for target services
  • Provide an honest verdict on ShelfCheck's current integration capabilities
  • Update `docs/integrations/strategy.md` with research findings

How it works

The skill researches a target book service to document its official API, export/import features, Android share/deep link support, authentication model, and rate limits. It then provides a verdict and updates the integration strategy documentation.

Inputs & outputs

You give it
Service name (e.g., 'Libby')
You get back
Verdict (Supported / Partial / Import-only / Share-only / Unsupported), capability breakdown with source URLs, a concrete ShelfCheck recommendation, and the doc

When to use integration-research

  • Assess book service API feasibility
  • Research import options for shelf check
  • Validate integration documentation

About this skill

Integration Research

Force honest, structured research before any ShelfCheck integration is built or documented. Distinguish what is officially supported from what is import/share/deep-link only. Follow the integration strategy.

When to Use

  • Evaluating a new third-party book service.
  • Validating or correcting integration claims in docs.
  • Scoping an integration feature before implementation.

Procedure

For the target service, research and document with citations:

  1. Official API — Is there a public, consumer-accessible API? What auth model?
  2. Export/import — What can the user export (CSV, OPML, tags, timeline)? Which fields?
  3. Android share / deep links — Does it expose share targets, App Links, or stable URLs ShelfCheck can parse?
  4. Auth model — OAuth, API key, none, or unsupported?
  5. Rate limits & terms — Constraints and ToS limits.
  6. Honest verdict — What ShelfCheck can do today vs not.

Hard Rules

  • Never recommend scraping private account data.
  • Never recommend credential login or password storage.
  • Mark every unsupported assumption explicitly.
  • Update docs/integrations/strategy.md with findings.

Output

Verdict (Supported / Partial / Import-only / Share-only / Unsupported), capability breakdown with source URLs, a concrete ShelfCheck recommendation, and the doc update made.

When not to use it

  • When scraping private account data is considered
  • When recommending credential login or password storage
  • When unsupported assumptions are not explicitly marked

Limitations

  • Never recommend scraping private account data
  • Never recommend credential login or password storage
  • Mark every unsupported assumption explicitly

How it compares

This process provides a structured, evidence-based assessment of integration feasibility, ensuring transparency and adherence to hard rules, unlike ad-hoc research that might overlook critical details or make unsupported assumptions.

Compared to similar skills

integration-research side by side with the closest alternatives in the catalog.

SkillInstallsUpdatedSafetyDifficulty
integration-research (this skill)01moNo flagsIntermediate
ena-database27moReviewAdvanced
research-agent16moReviewIntermediate
research-external16moReviewIntermediate

Try saying

Example prompts that trigger this skill in your AI assistant.

You might also like

ena-database

davila7

Access European Nucleotide Archive via API/FTP. Retrieve DNA/RNA sequences, raw reads (FASTQ), genome assemblies by accession, for genomics and bioinformatics pipelines. Supports multiple formats.

27

research-agent

parcadei

Research agent for external documentation, best practices, and library APIs via MCP tools

16

research-external

parcadei

External research workflow for docs, web, APIs - NOT codebase exploration

16

metabolomics-workbench-database

davila7

Access NIH Metabolomics Workbench via REST API (4,200+ studies). Query metabolites, RefMet nomenclature, MS/NMR data, m/z searches, study metadata, for metabolomics and biomarker discovery.

13

gcal-api-research

nspady

Expert research tool for Google Calendar API implementations. PROACTIVELY use when (1) reviewing PRs adding calendar features, (2) planning new event/attendee/recurring event functionality, (3) investigating calendar API issues, (4) validating timezone handling or batch operations. Specializes in recurring events, timezone conversions, multi-calendar support, and edge case identification.

10

protocolsio-integration

K-Dense-AI

Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.

10

Search skills

Search the agent skills registry