b2b-backend-research

Compile external API specifications, library documentation, and technical constraints for integration projects.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/herren-official/product-agents --skill b2b-backend-research
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: b2b-backend-research
Source: https://github.com/herren-official/product-agents/tree/main/skills/b2b-backend/woody/research
Command: npx skills add https://github.com/herren-official/product-agents --skill b2b-backend-research

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill enables targeted external research by gathering API specs, library docs, and technical constraints for planned integrations, reducing risk and rework.

Core Features & Use Cases

  • External API spec discovery: Identify endpoints, auth, rate limits, and versioning.
  • Library/documentation research: Locate official docs, client libraries, and deprecation notices.
  • Use Case: For a new integration with Payment API, research the latest API version, supported auth methods, and data formats to guide implementation.

Quick Start

Provide a target external service name and context to start the research.

Frequently Asked Questions about b2b-backend-research

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I research external API specifications for a vendor integration?

Researching external API specifications involves identifying endpoints, authentication methods, rate limits, and versioning for designated vendor integration projects. It produces structured research deliverables with clear documentation of technical constraints and compatibility notes.

What is included in external API documentation research?

External API documentation research includes identifying endpoints, authentication methods, rate limits, and versioning, alongside locating official docs, client libraries, and deprecation notices. It delivers versioned findings with clear compatibility notes for integration planning.

When do I need to research library documentation and technical constraints?

You need to research library documentation and technical constraints when planning external system integration or vendor selection. It ensures API compatibility checks are met by verifying supported authentication methods and data formats before implementation.

How do I compile API compatibility notes for a new payment integration?

Compiling API compatibility notes for a payment integration involves researching the latest API version, supported authentication methods, and data formats. This yields versioned findings and structured documentation of endpoints to guide implementation.

Can I use this to check vendor API rate limits and authentication methods?

Yes, you can check vendor API rate limits and authentication methods. The research targets external API specs and library docs to produce structured deliverables that document versioning, endpoints, and technical constraints for integration projects.