360 Secure SkillHub
360 安全技能中心

Api3 Feed Manager Readonly

核心功能:可发现最优Api3去中心化喂价、验证其活性与资金状态,生成浏览器/合约执行计划,审计跨链覆盖情况,仅输出精确执行细节,绝不持有签名材料或提交链上交易。典型场景:需安全查询喂价状态、生成交易详情但不想授予钱包权限、作为全执行版的安全配套工具。输入为指定命令,输出为喂价信息、执行方案或审计报告。

daav3
daav3
热度 29.32
最近更新 2026-05-11 17:47:52
分类:开发依赖:代码执行 / 联网浏览搜索 / 第三方 API / 读写文件应用场景:API 集成 / 数据处理 / 报告撰写 / 代码生成

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add api3-feed-manager-readonly
Metadata
name
api3-feed-manager-readonly
description
Read-only Api3 feed discovery, readiness, coverage, and purchase-planning skill for downstream agent projects. Use when an agent needs to discover or verify decentralized data feeds, inspect funding/runway state, prepare browser or contract plans, or produce exact transaction details without ever holding signer material or submitting onchain transactions.
metadata
{"clawdis":{"homepage":"https://github.com/daav3/agentic-lending-project","author":"daav3","requires":{"bins":["node"],"config":["request.ensure-feeds.json"]}}}

Api3 Feed Manager (Read-only)

This variant is for discovery, verification, readiness checks, and exact execution planning without signer-backed execution.

What it can do

  • discover the best Api3 feed for an asset or pair
  • verify whether a feed exists and appears active
  • inspect funding/runway state
  • classify whether activation is needed
  • generate browser-assisted funding plans
  • generate exact contract-call payloads for later human or executor use
  • audit coverage across chains

What it will not do

  • accept signer material
  • submit transactions
  • trigger browser purchase flows automatically
  • claim a feed was funded unless a fresh post-action check proves it

Use this when

  • you want a safer default package for general users
  • you need transaction details without giving the skill wallet authority
  • you want a companion to the full executor variant so users can choose

Operating rules

  1. Default to discovery and verification first.
  2. Return exact next-step details when execution would be required.
  3. Keep the distinction between not-needed, executable, browser-assisted, and unsupported.
  4. Treat any generated calldata or browser plan as review material for a separate executor or human operator.

Available commands

  • resolve
  • discover
  • ensure-active
  • prepare-activation
  • browser-plan
  • contract-plan
  • queue-plan
  • purchase-inputs
  • prepare-contract-call
  • coverage-audit
  • coverage-matrix
  • supported-chains

Notes

  • This package is intentionally split from the executor-capable variant to reduce false surprise in security review.
  • If a user wants real execution, direct them to the executor variant instead of expanding this package's authority.