scienceskillscommon

Provide a unified HTTP client with rate limiting, retries, and backoff for scientific APIs.

3|Updated Apr 15, 2026
One-click install
npx skills add https://github.com/syahrilTGR/Template-Research --skill scienceskillscommon-syahriltgr
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: scienceskillscommon
Source: https://github.com/syahrilTGR/Template-Research/tree/main/.agents/skills/science_skills_common
Command: npx skills add https://github.com/syahrilTGR/Template-Research --skill scienceskillscommon-syahriltgr

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires urllib, gzip, and includes scripts (resource) components.

What problem does it solve?

This Skill addresses the complexity of interacting with various APIs in scientific research by providing a unified HTTP client with built-in rate limiting, retries, and backoff mechanisms.

Core Features & Use Cases

  • Unified HTTP Client: Offers a single entry-point for API interactions, reducing the complexity of managing multiple clients.
  • Rate Limiting: Ensures compliance with API usage limits, preventing overages and potential account suspension.
  • Retry Mechanism: Automatically retries failed requests, handling transient errors and improving reliability.
  • Backoff Strategy: Implements exponential backoff with jitter, reducing the likelihood of server overload.
  • Use Case: Ideal for researchers and data scientists who need to fetch data from APIs like PubMed, ChemBL, or UniProt, ensuring smooth and efficient data retrieval.

Quick Start

Use the http_client module from the scienceskillscommon package to fetch data from an API endpoint.

Frequently Asked Questions about scienceskillscommon

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

FAQPage Schema
How do I handle rate limiting when fetching data from scientific APIs like PubMed?

A retry mechanism automatically retries failed HTTP requests to handle transient errors. It implements exponential backoff with jitter, reducing the likelihood of server overload and improving the reliability of fetching data from scientific databases.

What is the best way to manage multiple API interactions for scientific research?

The best way to manage multiple API interactions is using a unified HTTP client as a single entry-point. This reduces the complexity of managing multiple clients and simplifies fetching data from scientific databases like PubMed, ChemBL, or UniProt.

Do I need urllib and gzip to fetch data from scientific databases?

Yes, you need urllib and gzip to fetch data from scientific databases. The unified HTTP client requires urllib for executing HTTP requests and gzip for data decompression, ensuring smooth and efficient data retrieval from scientific APIs.

Why does my API interaction fail when fetching large datasets from scientific databases?

Yes, this unified HTTP client is suitable for data scientists needing to fetch data from scientific APIs. It provides efficient API interactions with built-in rate limiting, retries, and backoff, making it ideal for scientific research workflows.