feishu-common

Centralize Feishu tenant token management and HTTP requests with retry logic.

1|Updated Mar 15, 2026
One-click install
npx skills add https://github.com/family3253/skill --skill feishu-common-family3253
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: feishu-common
Source: https://github.com/family3253/skill/tree/main/skills/feishu-common
Command: npx skills add https://github.com/family3253/skill --skill feishu-common-family3253

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Centralizes Feishu tenant token management and robust request handling for OpenClaw Feishu skills, reducing token churn and API errors.

Core Features & Use Cases

  • Tenant token acquisition and cache
  • Retry and timeout handling
  • Authenticated request wrapper with token refresh

Quick Start

Install this skill and import getToken and fetchWithAuth to your Feishu integrations.

Frequently Asked Questions about feishu-common

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

FAQPage Schema
How do I manage Feishu tenant token acquisition and caching in OpenClaw?

Feishu tenant token management is handled by calling getToken to acquire and cache tokens, reducing token churn and API errors for OpenClaw integrations. It centralizes acquisition so individual skills do not need separate logic.

What's the best way to add retry logic to Feishu API requests?

The best way to add retry logic to Feishu API requests is using the fetchWithRetry helper, which provides built-in timeout and automatic retry handling for robust HTTP requests. It minimizes API errors without adding external dependencies.

Does this Feishu auth helper require any external dependencies?

No, the Feishu auth helper requires zero external dependencies, providing a lightweight and dependency-minimized client for OpenClaw integrations. It uses environment-driven configuration to manage tokens and requests.

How do I automatically refresh an expired Feishu tenant token during an API call?

You automatically refresh an expired Feishu tenant token by wrapping your API call with the fetchWithAuth function, which handles token refresh internally. It ensures authenticated requests succeed even if the cached token expires.

Why does my Feishu integration keep failing with token churn and API errors?

Feishu integrations fail with token churn and API errors when token management and request handling are decentralized. Using a shared helper with tenant token caching and retry logic centralizes control and reduces these failures.