Token导航 LogoToken导航TokenDH.com
开发敏感数据github未标认证来源可访问许可证需确认审计提醒

alova-server-usagealova 服务器使用情况

Agent Skill

alova-server-usage 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

218

周安装

9

GitHub Stars

3

下载量

71
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:alova-server-usage(alova 服务器使用情况)
来源仓库:https://github.com/alovajs/skills
仓库路径:skills/alova-server-usage
安装命令:
npx skills add https://github.com/alovajs/skills --skill alova-server-usage
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/alovajs/skills --skill alova-server-usage

简介

alova-server-usage 提供 Alova 服务端(Node/Bun/Deno)使用的快速参考索引。

  • 适合在 Codex、Claude、Cursor、Gemini CLI 中查找服务器端 API 用法时使用。
  • 分为两层结构:本文件和官方文档,优先查阅本文件再按需获取官方文档。
  • 安装前需确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。
  • alova 处于活跃开发中,官方实时文档比训练数据更可靠。

SKILL.md

alova banner

Alova Server-Side Usage

For client-side usage, see alova-client skill. For alova openapi usage, see alova-openapi skill.

How to Use This Skill

  1. This file — Quick-reference index: what each API does and when to use it. Read this first.
  2. Official docs (fetch on demand) — For full options, edge cases, or unfamiliar APIs, fetch the URL listed in each section to get the latest accurate information.
Always fetch the official doc before answering questions about specific API options or behaviors — alova is actively developed and live docs are more reliable than training data.

Installation & Setup

See references/SETUP.md for:

  • Installation
  • Creating Alova instance
  • Request adapters
  • Global request sharing and timeout
  • cache logger
  • limit number of method snapshots

Create Method Instance

alova provides a total of 7 request types.

Instance creation functionParameters
GETalovaInstance.Get(url[, config])
POSTalovaInstance.Post(url[, data[, config]])
PUTalovaInstance.Put(url[, data[, config]])
DELETEalovaInstance.Delete(url[, data[, config]])
HEADalovaInstance.Head(url[, config])
OPTIONSalovaInstance.Options(url[, config])
PATCHalovaInstance.Patch(url[, data[, config]])

Parameter Description:

  • url is the request path;
  • data is the request body data;
  • config is the request configuration object, which includes configurations such as request headers, params parameters, request behavior parameters, etc.;

The above functions calling are not sending request, but creates a method instance, which is a PromiseLike instance. You can use then, catch, finally methods or await to send request just like a Promise object, or call send to explicitly send the request.

alovaInstance
  .Get('/api/user')
  .then((response) => {
    // ...
  })
  .catch((error) => {
    // ...
  })
  .finally(() => {
    // ...
  });

// or
try {
  await alovaInstance.Get('/api/user');
} catch (error) {
  // ...
} finally {
  // ...
}

// or
alovaInstance.Get('/api/user').send();

See Method Documentation if need to know full method instance API.

Method Metadata

Add additional information to specific method instances to facilitate their identification or additional information in global interceptor such as different response returning, global toast avoiding. please set method metadata. See -> Method Metadata.

Cache Strategy

Alova has L1 (memory) and L2 (persistent/restore) layers, plus automatic request sharing (dedup).

Set cache globally and scoped

Key rule: prefer hitSource auto-invalidation — it requires zero imperative code and decouples components.

Server Hooks

import from alova/server.

Server hooks wrap a Method instance and return a new hooked Method. They are composable and all support cluster mode when using Redis or file storage adapter.

ScenarioHookKey capabilityDocs
Retry failed requests with backoffretryConfigurable retry attempts with exponential backoffDocs
Distributed captcha sendingsendCaptchaBuilt-in rate limiting for captchaDocs
Rate-limit outgoing requestsRateLimiterToken bucket algorithm, cluster support via RedisDocs
Only one process initiates at a time (cluster)atomizeDistributed lock for token refresh, resource initDocs

Server hooks can be layered one on top of another to combine their behaviors:

// Layer by layer composition: innermost wraps first
// Step 1: create base method
const baseMethod = alovaInstance.Post('/api/order', data);

// Step 2: wrap with rate limiter (outer layer)
const limitedMethod = limiter.limit(baseMethod);

// Step 3: wrap with retry (outermost layer)
const retryableMethod = retry(limitedMethod, { retry: 3 });

// Execute: rate limit check → retry on failure → send request
const result = await retryableMethod();

// Or in one line:
const result = await retry(limiter.limit(alovaInstance.Post('/api/order', data)), {
  retry: 3,
}).send();

Distributed Caching

ScenarioStorage adapter
Single-processDefault in-memory
Multi-process cluster@alova/storage-redis
Single-machine cluster@alova/storage-file

Mock Request

Setup mock data for specific requests. See Mock Request.

Best Practices

  • Provide a folder that uniformly stores request functions, to keep your code organized.
  • Create multiple alova instances for different domains, APIs, or environments.
  • Build BFF layer, API gateway, 3rd-party token auto management with alova. See references/BFF_API_GATEWAY.md.

Common Pitfalls

PitfallFix
RateLimiter state not shared across workersAdd a Redis storage adapter to RateLimiter options
atomize not actually atomic in clusterRequires a shared storage adapter (Redis or File) to coordinate processes

TypeScript

Annotate the response shape on the Method instance — hooks infer from it automatically:

const getUser = (id: number) => alovaInstance.Get<User>(`/users/${id}`);
// or need to transform data.
const getUser = (id: number) =>
  alovaInstance.Get(`/users/${id}`, {
    transform(user: User) {
      return {
        ...user,
        name: user.lastName + ' ' + user.firstName,
      };
    },
  });

const { data } = useRequest(getUser(1)); // data: Ref<User>

📄 TypeScript docs

Custom Adapter

If all preset adapters not meet your needs, custom your own adapter.

Custom Method Key

Change cache, request sharing and state updating matching strategy by setting key. See Custom Method Key.

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35.04%
按下载量换算25

Claude

29.07%
按下载量换算21

Cursor

18.38%
按下载量换算13

Gemini CLI

9.24%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在 warning/failed 结果,不能写成本站确认安全。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills