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

api-catalogAPI catalog 文档

Agent Skill

用于辅助 API 设计、接口文档、请求响应结构和服务集成说明。它适合让 Agent 梳理 endpoint、生成 OpenAPI 草稿、检查字段命名、整理错误码或辅助前后端联调。使用时需要确认真实业务语义、鉴权方式、分页和错误处理规则;涉及生成接口文档时,应避免凭空补字段,最好从现有代码、schema 或接口样例中提取事实。

总安装

17,316

周安装

609

GitHub Stars

37

下载量

6,668
CodexClaudeCursorGemini CLI

安装说明

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

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:api-catalog(API catalog 文档)
来源仓库:https://github.com/tonylofgren/aurora-smart-home
仓库路径:skills/api-catalog
安装命令:
npx skills add https://github.com/tonylofgren/aurora-smart-home --skill 'API Catalog'
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/tonylofgren/aurora-smart-home --skill 'API Catalog'

简介

为 Home Assistant 提供外部 API 连接参考,涵盖 Node-RED、YAML 和自定义组件三种接入方式。

  • 适用于快速集成常见智能家居服务,强调凭证安全管理与代码示例复用。
  • 使用时需区分不同集成模式的适用场景,优先使用 secrets 文件存储敏感信息。
  • 安装方式:通过 npx skills add 从 GitHub 仓库安装,支持主流 AI 开发工具链。
  • 注意:禁止在代码中硬编码 API 密钥,必须通过 credentials 或 secrets 机制管理。

SKILL.md

API Catalog for Home Assistant

Reference skill for connecting external APIs and services to Home Assistant.

Overview

This skill covers authentication patterns and working code examples for connecting popular APIs to Home Assistant via three methods:

  • Node-RED - HTTP request node flows (fastest to get running)
  • HA YAML - rest sensor and rest_command (good for simple polling)
  • Custom integration - Full HACS-publishable Python component (use ha-integration skill)

The Iron Law

CREDENTIALS IN SECRETS - NEVER HARDCODED IN FLOWS OR YAML

API keys belong in Node-RED credentials, ESPHome secrets.yaml, or HA secrets.yaml. Never paste real tokens into chat, flows that get exported, or YAML committed to git.

How to Use This Skill

  1. User mentions an API or service by name
  2. Read the relevant reference file for auth setup and endpoints
  3. Generate working code for the user's chosen method (Node-RED / YAML / integration)
  4. Include credential setup instructions

Reference Files

CategoryFileAPIs Covered
Energy & electricityreferences/energy-apis.mdTibber, Nordpool, Energi Data Service
Weatherreferences/weather-apis.mdSMHI, OpenWeatherMap, yr.no, Tomorrow.io
Transportreferences/transport-apis.mdSL, Trafikverket, Resrobot, Entur (NO)
Smart home cloudsreferences/smarthome-apis.mdShelly Cloud, Tuya IoT, Philips Hue, IKEA Dirigera
Global / otherreferences/global-apis.mdOpenAI, Spotify, Google Calendar, Telegram, GitHub

Authentication Patterns at a Glance

PatternHow it worksExamples
API key in headerAuthorization: Bearer {key} or X-API-Key: {key}Tibber, OpenAI
API key in URL?appid={key} appended to URLOpenWeatherMap
OAuth2Get access token first, refresh periodicallySpotify, Google
Local tokenOne-time press-button auth on devicePhilips Hue
No authPublic API, no credentials neededSMHI, yr.no, Nordpool
Basic authUsername + password Base64-encodedSome local devices

Output Methods

For each API, generate code for the method the user needs:

Node-RED: http request node + function node to parse + api-call-service to push to HA HA YAML: rest sensor platform or rest_command under configuration.yaml Full integration: Use ha-integration skill with the polling-integration template

Common Patterns

Node-RED: API key in header

{
  "type": "http request",
  "method": "GET",
  "url": "https://api.example.com/data",
  "headers": {"Authorization": "Bearer {{env.API_KEY}}"},
  "ret": "obj"
}

Node-RED: GraphQL (Tibber-style)

{
  "type": "http request",
  "method": "POST",
  "url": "https://api.tibber.com/v1-beta/gql",
  "headers": {
    "Authorization": "Bearer {{env.TIBBER_TOKEN}}",
    "Content-Type": "application/json"
  },
  "payload": "{\"query\": \"{ viewer { homes { currentSubscription { priceInfo { current { total } } } } } }\"}",
  "ret": "obj"
}

HA YAML: REST sensor

rest:
  - scan_interval: 300
    resource: https://api.example.com/current
    headers:
      Authorization: !secret example_api_key
    sensor:
      - name: "Example Value"
        value_template: "{{ value_json.data.value }}"
        unit_of_measurement: "°C"

Pre-Output Checklist

  • Credentials use !secret (YAML), Node-RED credentials, or env vars - never hardcoded
  • Rate limits respected (include scan_interval or flow timer accordingly)
  • Error handling included (Node-RED catch node or YAML timeout)
  • For OAuth2: refresh token flow explained
  • Attribution: which API endpoint, what data it returns

Integration

Pairs with:

  • node-red skill - for flow JSON implementation
  • ha-yaml skill - for YAML sensor and automation using the fetched data
  • ha-integration skill - for building a full HACS-publishable Python integration

适合场景

01

用户想查找某类 Agent Skill 时

02

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

03

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

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

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

能力 4

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

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

平台分布

Codex

33.49%
按下载量换算2,233

Claude

29.64%
按下载量换算1,976

Cursor

19.86%
按下载量换算1,324

Gemini CLI

9.47%
按下载量换算631

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

可疑

权限和风险

敏感数据

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

安装前确认

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

来源信息

继续浏览同类 Skills