Token导航 LogoToken导航

Agent Skill · 研究检索

nest-devices(巢装置)

nest-devices 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

nest-devices 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为接触敏感数据;许可证为 MIT,暂无第三方扫描结果,按安装量在研究检索类的 73,675 个 Skill 里排第 6,443。

总安装 22,167周安装 615GitHub Stars 公开资料未说明下载 4,371核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT

安装方式

通过对话安装

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

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

命令行安装

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

AgentSkills.tonpx skills
npx skills add clawdbot/skills --skill "nest-devices"

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

nest-devices 用于发现和安装 AI 代理的技能,增强系统灵活性。适合需要动态扩展功能或接入第三方工具的场景。通过 npx 命令从 clawdbot/skills 仓库安装指定技能。注意权限控制,避免自动执行未经验证的外部脚本。建议核对仓库更新频率和兼容性后再使用。

nest-devices 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/nest-devices

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add clawdbot/skills --skill "nest-devices";命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

nest-devices 怎么安装?

在终端执行 npx skills add clawdbot/skills --skill "nest-devices"。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

nest-devices 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

nest-devices 需要什么权限?

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

nest-devices 是免费的吗?

来源标注的许可证是 MIT。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

nest-devices 用的人多吗?

公开数据是累计安装 22,167 次,近一周安装 615 次,下载 4,371 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

nest-devices 安全吗?

没有查到第三方扫描结果,安全性无法从公开资料判断,安装前请自行审查源码、依赖和命令行为。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 许可证明确为 MIT,商用和分发边界好判断。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 没有第三方扫描结果,安全性只能靠自己读源码判断。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 要求有安全扫描结论才肯安装的团队。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
nest-devices

巢装置 · 本页

22,167—接触敏感数据MIT未收录

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
nest-devices
description
Control Nest smart home devices (thermostat, cameras, doorbell) via the Device Access API. Use when asked to check or adjust home temperature, view camera feeds, check who's at the door, monitor rooms, or set up temperature schedules.
metadata
clawdbot
emoji
🏠

Nest Device Access

Control Nest devices via Google's Smart Device Management API.

Setup

1. Google Cloud & Device Access

  1. Create a Google Cloud project at console.cloud.google.com
  2. Pay the $5 fee and create a Device Access project at console.nest.google.com/device-access
  3. Create OAuth 2.0 credentials (Web application type)
  4. Add https://www.google.com as an authorized redirect URI
  5. Link your Nest account to the Device Access project

2. Get Refresh Token

Run the OAuth flow to get a refresh token:

# 1. Open this URL in browser (replace CLIENT_ID and PROJECT_ID):
https://nestservices.google.com/partnerconnections/PROJECT_ID/auth?redirect_uri=https://www.google.com&access_type=offline&prompt=consent&client_id=CLIENT_ID&response_type=code&scope=https://www.googleapis.com/auth/sdm.service

# 2. Authorize and copy the 'code' parameter from the redirect URL

# 3. Exchange code for tokens:
curl -X POST https://oauth2.googleapis.com/token \
  -d "client_id=CLIENT_ID" \
  -d "client_secret=CLIENT_SECRET" \
  -d "code=AUTH_CODE" \
  -d "grant_type=authorization_code" \
  -d "redirect_uri=https://www.google.com"

3. Store Credentials

Store in 1Password or environment variables:

1Password (recommended): Create an item with fields: project_id, client_id, client_secret, refresh_token

Environment variables:

export NEST_PROJECT_ID="your-project-id"
export NEST_CLIENT_ID="your-client-id"
export NEST_CLIENT_SECRET="your-client-secret"
export NEST_REFRESH_TOKEN="your-refresh-token"

Usage

List devices

python3 scripts/nest.py list

Thermostat

# Get status
python3 scripts/nest.py get <device_id>

# Set temperature (Celsius)
python3 scripts/nest.py set-temp <device_id> 21 --unit c --type heat

# Set temperature (Fahrenheit)
python3 scripts/nest.py set-temp <device_id> 70 --unit f --type heat

# Change mode (HEAT, COOL, HEATCOOL, OFF)
python3 scripts/nest.py set-mode <device_id> HEAT

# Eco mode
python3 scripts/nest.py set-eco <device_id> MANUAL_ECO

Cameras

# Generate live stream URL (RTSP, valid ~5 min)
python3 scripts/nest.py stream <device_id>

Python API

from nest import NestClient

client = NestClient()

# List devices
devices = client.list_devices()

# Thermostat control
client.set_heat_temperature(device_id, 21.0)  # Celsius
client.set_thermostat_mode(device_id, 'HEAT')
client.set_eco_mode(device_id, 'MANUAL_ECO')

# Camera stream
result = client.generate_stream(device_id)
rtsp_url = result['results']['streamUrls']['rtspUrl']

Configuration

The script checks for credentials in this order:

  1. 1Password: Set NEST_OP_VAULT and NEST_OP_ITEM (or use defaults: vault "Alfred", item "Nest Device Access API")
  2. Environment variables: NEST_PROJECT_ID, NEST_CLIENT_ID, NEST_CLIENT_SECRET, NEST_REFRESH_TOKEN

Temperature Reference

SettingCelsiusFahrenheit
Eco (away)15-17°C59-63°F
Comfortable19-21°C66-70°F
Warm22-23°C72-73°F
Night17-18°C63-65°F

Real-Time Events (Doorbell, Motion, etc.)

For instant alerts when someone rings the doorbell or motion is detected, you need to set up Google Cloud Pub/Sub with a webhook.

Prerequisites

  • Google Cloud CLI (gcloud) installed and authenticated
  • Cloudflare account (free tier works) for the tunnel
  • Clawdbot hooks enabled in config

1. Enable Clawdbot Hooks

Add to your clawdbot.json:

{
  "hooks": {
    "enabled": true,
    "token": "your-secret-token-here"
  }
}

Generate a token: openssl rand -hex 24

2. Create Pub/Sub Topic

gcloud config set project YOUR_GCP_PROJECT_ID

# Create topic
gcloud pubsub topics create nest-events

# Grant SDM permission to publish (both the service account and publisher group)
gcloud pubsub topics add-iam-policy-binding nest-events \
  --member="serviceAccount: [email protected] " \
  --role="roles/pubsub.publisher"

gcloud pubsub topics add-iam-policy-binding nest-events \
  --member="group: [email protected] " \
  --role="roles/pubsub.publisher"

3. Link Topic to Device Access

Go to console.nest.google.com/device-access → Your Project → Edit → Set Pub/Sub topic to:

projects/YOUR_GCP_PROJECT_ID/topics/nest-events

4. Set Up Cloudflare Tunnel

# Install cloudflared
curl -L -o ~/.local/bin/cloudflared https://github.com/cloudflare/cloudflared/releases/latest/download/cloudflared-linux-amd64
chmod +x ~/.local/bin/cloudflared

# Authenticate (opens browser)
~/.local/bin/cloudflared tunnel login

# Create named tunnel
~/.local/bin/cloudflared tunnel create nest-webhook

# Note the Tunnel ID (UUID) from output

Create ~/.cloudflared/config.yml:

tunnel: nest-webhook
credentials-file: /home/YOUR_USER/.cloudflared/TUNNEL_ID.json

ingress:
  - hostname: nest.yourdomain.com
    service: http://localhost:8420
  - service: http_status:404

Create DNS route:

~/.local/bin/cloudflared tunnel route dns nest-webhook nest.yourdomain.com

5. Create Systemd Services

Webhook server (/etc/systemd/system/nest-webhook.service):

[Unit]
Description=Nest Pub/Sub Webhook Server
After=network.target

[Service]
Type=simple
User=YOUR_USER
Environment=CLAWDBOT_GATEWAY_URL=http://localhost:18789
Environment=CLAWDBOT_HOOKS_TOKEN=your-hooks-token-here
ExecStart=/usr/bin/python3 /path/to/skills/nest-devices/scripts/nest-webhook.py
Restart=always
RestartSec=5

[Install]
WantedBy=multi-user.target

Cloudflare tunnel (/etc/systemd/system/cloudflared-nest.service):

[Unit]
Description=Cloudflare Tunnel for Nest Webhook
After=network-online.target
Wants=network-online.target

[Service]
Type=simple
User=YOUR_USER
ExecStart=/home/YOUR_USER/.local/bin/cloudflared tunnel run nest-webhook
Restart=always
RestartSec=5

[Install]
WantedBy=multi-user.target

Enable and start:

sudo systemctl daemon-reload
sudo systemctl enable --now nest-webhook cloudflared-nest

6. Create Pub/Sub Push Subscription

gcloud pubsub subscriptions create nest-events-sub \
  --topic=nest-events \
  --push-endpoint="https://nest.yourdomain.com/nest/events" \
  --ack-deadline=30

7. Test

# Test webhook endpoint
curl https://nest.yourdomain.com/health

# Simulate doorbell event
curl -X POST http://localhost:8420/nest/events \
  -H "Content-Type: application/json" \
  -d '{"message":{"data":"eyJyZXNvdXJjZVVwZGF0ZSI6eyJuYW1lIjoiZW50ZXJwcmlzZXMvdGVzdC9kZXZpY2VzL0RPT1JCRUxMLTAxIiwiZXZlbnRzIjp7InNkbS5kZXZpY2VzLmV2ZW50cy5Eb29yYmVsbENoaW1lLkNoaW1lIjp7ImV2ZW50SWQiOiJ0ZXN0In19fX0="}}'

Supported Events

EventBehaviour
DoorbellChime.Chime🔔 Alerts — sends photo to Telegram
CameraPerson.Person🚶 Alerts — sends photo to Telegram
CameraMotion.Motion📹 Logged only (no alert)
CameraSound.Sound🔊 Logged only (no alert)
CameraClipPreview.ClipPreview🎬 Logged only (no alert)
Staleness filter: Events older than 5 minutes are logged but never alerted. This prevents notification floods if queued Pub/Sub messages are delivered late.

Image Capture

When a doorbell or person event triggers an alert:

  1. Primary: SDM GenerateImage API — fast, event-specific snapshot
  2. Fallback: RTSP live stream frame capture via ffmpeg (requires ffmpeg installed)

Environment Variables

VariableRequiredDescription
CLAWDBOT_GATEWAY_URLNoGateway URL (default: http://localhost:18789)
CLAWDBOT_HOOKS_TOKENYesGateway hooks token for awareness notifications
OP_SVC_ACCT_TOKENYes1Password service account token for Nest API credentials
TELEGRAM_BOT_TOKENYesTelegram bot token for sending alerts
TELEGRAM_CHAT_IDYesTelegram chat ID to receive alerts
PORTNoWebhook server port (default: 8420)

Important Setup Notes

  • Verify the full Pub/Sub topic path in Device Access Console matches your GCP project exactly: projects/YOUR_GCP_PROJECT_ID/topics/nest-events
  • Use a push subscription, not pull — the webhook expects HTTP POST delivery
  • Test end-to-end after setup: ring the doorbell and confirm a photo arrives. Don't rely on simulated POST requests alone.

Limitations

  • Camera event images expire after ~5 minutes (RTSP fallback captures current frame instead)
  • Real-time events require Pub/Sub setup (see above)
  • Quick tunnels (without Cloudflare account) have no uptime guarantee
  • Some older Nest devices may not support all features
  • Motion and sound events are intentionally not alerted to avoid notification fatigue

平台分布

OpenCode

31.31%
按下载量换算1,369

windsurf

22.37%
按下载量换算978

clawdbot

17.56%
按下载量换算768

Codex

12.43%
按下载量换算543

Claude Code

8.13%
按下载量换算355

Antigravity

3.18%
按下载量换算139

安全审计

暂无安全审计结果可展示。

权限和风险

接触敏感数据

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

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills