Token导航 LogoToken导航

Agent Skill · 开发

structs-economy(结构经济)

structs-economy 用于辅助前端页面、组件、样式和交互逻辑开发,适合在 OpenClaw 中需要维护前端项目、生成组件或检查界面实现时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

structs-economy 是开发类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描有提醒项,按安装量在开发类的 21,746 个 Skill 里排第 3,013。

总安装 13,218周安装 562GitHub Stars 公开资料未说明下载 4,631核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:structs-economy(结构经济)
来源仓库:https://github.com/abstrct/structs-economy
安装命令:
openclaw skills install structs-economy
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install structs-economy

这个 Skill 是做什么的

开发类 Skill 面向写代码、改代码和排查问题,一般会读写仓库文件,部分还会执行构建或测试命令。

管理结构中的经济运营,涵盖反应堆质押、能源供应商和代币流转。适用于 OpenClaw 中维护前端项目、生成组件或检查界面实现时。通过 clawhub 安装,结合来源仓库和 README 核验具体用法。使用前需确认权限范围、维护状态及是否触发联网或文件读写操作。建议在安装前评估是否会执行命令或访问外部资源。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install structs-economy;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要需要联网,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

structs-economy 怎么安装?

在终端执行 openclaw skills install structs-economy。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

structs-economy 支持哪些 AI 工具?

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

structs-economy 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

structs-economy 是免费的吗?

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

structs-economy 用的人多吗?

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

structs-economy 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

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

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。

先想清楚的地方

  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

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

不太适合

  • 需要厂商级技术支持和 SLA 的生产系统。

开发类 Skill 对比

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

技能审查员 · OpenClaw

8,779,018986操作浏览器MIT-0通过
ontology

本体论 · OpenClaw

6,636,960576只读MIT-0通过
entra-app-registration

内部应用程序注册 · Codex、Claude

6,631,872764接触敏感数据未明确通过
entra-app-registration

内部应用程序注册 · Codex、Claude

3,757,680201接触敏感数据未明确通过
nano-banana-pro

纳米香蕉专业版 · OpenClaw

3,526,898364接触敏感数据MIT-0有提醒
structs-economy

结构经济 · 本页

13,218—需要联网MIT-0有提醒

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

SKILL.md 原文

name
structs-economy
description
Manages economic operations in Structs. Covers reactor staking, energy providers, agreements, allocations, generator infusion, and token transfers. Use when staking Alpha Matter in reactors, creating or managing energy providers, negotiating agreements, allocating energy, infusing generators, transferring tokens, or managing economic infrastructure.

Structs Economy

Procedure

  1. Assess position — Query player, reactor, provider, agreement state via structsd query structs player/reactor/provider/agreement [id].
  2. Reactor staking — Stake Alpha Matter: structsd tx structs reactor-infuse [player-address] [reactor-address] [amount] TX_FLAGS. The amount must include the denomination, e.g. 60000000ualpha (not just 60000000). This automatically increases the player's capacity — no allocation setup needed. The reactor's commission rate determines the split: player receives power * (1 - commission), reactor keeps the rest. Unstake: reactor-defuse [reactor-id] (cooldown applies). Cancel cooldown: reactor-cancel-defusion [reactor-id]. Migrate: reactor-begin-migration [player-address] [source-validator-address] [dest-validator-address] [amount].
  3. Generator infusion — structsd tx structs struct-generator-infuse [struct-id] [amount] TX_FLAGS. IRREVERSIBLE — Alpha cannot be recovered. Higher conversion rates than reactors (2-10x) but generator is vulnerable to raids.
  4. Provider lifecycle — Create: provider-create [substation-id] [rate] [access-policy] [provider-penalty] [consumer-penalty] [cap-min] [cap-max] [dur-min] [dur-max] TX_FLAGS. Valid access-policy values: open-market (anyone can buy), guild-market (guild members with sufficient rank can buy -- managed via guild rank permissions on the provider), closed-market (only players with explicit PermProviderOpen on the provider). Update capacity/duration/access via provider-update-capacity-maximum, provider-update-duration-minimum, etc. Delete: provider-delete [provider-id]. Withdraw earnings: provider-withdraw-balance [provider-id]. To grant guild members access to a guild-market provider: permission-guild-rank-set [provider-id] [guild-id] 262144 [rank] (PermProviderOpen).
  5. Agreements — Open: agreement-open [provider-id] [duration] [capacity] TX_FLAGS. Close: agreement-close [agreement-id]. Adjust: agreement-capacity-increase/decrease, agreement-duration-increase.
  6. Allocations — Create: allocation-create [source-id] [power] --allocation-type static|dynamic|automated TX_FLAGS. The --controller flag accepts a PlayerId (e.g., 1-42). If omitted, the creating player is the default controller. Update: allocation-update [allocation-id] [new-power]. Delete: allocation-delete [allocation-id] — only the controlling player can delete an allocation. Transfer: allocation-transfer [allocation-id] [new-controller].

Allocation Type Comparison

TypeUpdatableDeletableAuto-growsLimitUse Case
staticNoNo (while connected)NoUnlimitedFixed capacity routing
dynamicYesYesNoUnlimitedFlexible, managed routing
automatedYesNoYes (scales with source capacity)One per sourceEnergy commerce (recommended)
provider-agreementSystem-managedSystem-managedSystem-managedSystem-createdAuto-created when agreements open; never create manually

Automated allocation limit: Only one automated allocation per source is allowed. Attempting to create a second from the same source will error. Use dynamic type if you need multiple allocations from one source.

Recommended for energy sales: Use automated allocations. When you infuse more alpha into a reactor, your capacity grows, and automated allocations proportionally increase energy flowing to your substations with no manual intervention.

  1. Token transfer — player-send [from-address] [to-address] [amount] TX_FLAGS.

Commands Reference

ActionCommand
Reactor infusestructsd tx structs reactor-infuse [player-addr] [validator-addr] [amount] (validator = structsvaloper1..., NOT reactor ID)
Reactor defusestructsd tx structs reactor-defuse [reactor-id]
Reactor migratestructsd tx structs reactor-begin-migration [player-addr] [src-validator-addr] [dest-validator-addr] [amount]
Reactor cancel defusionstructsd tx structs reactor-cancel-defusion [reactor-id]
Generator infusestructsd tx structs struct-generator-infuse [struct-id] [amount]
Provider createstructsd tx structs provider-create [substation-id] [rate] [access] [prov-penalty] [cons-penalty] [cap-min] [cap-max] [dur-min] [dur-max]
Provider deletestructsd tx structs provider-delete [provider-id]
Provider withdrawstructsd tx structs provider-withdraw-balance [provider-id]
Agreement openstructsd tx structs agreement-open [provider-id] [duration] [capacity]
Agreement closestructsd tx structs agreement-close [agreement-id]
Allocation createstructsd tx structs allocation-create [source-id] [power] --allocation-type [type]
Allocation updatestructsd tx structs allocation-update [allocation-id] [power]
Allocation deletestructsd tx structs allocation-delete [allocation-id]
Player sendstructsd tx structs player-send [from] [to] [amount]

TX_FLAGS: --from [key-name] --gas auto --gas-adjustment 1.5 -y

Important: Entity IDs containing dashes (like 3-1, 4-5) are misinterpreted as flags by the CLI parser. Always place -- between flags and positional args: structsd tx structs command TX_FLAGS -- [entity-id] [other-args]

Verification

  • Reactor: structsd query structs reactor [id] — check infusedAmount, defusionCooldown.
  • Provider: structsd query structs provider [id] — verify capacity, rate, active agreements.
  • Agreement: structsd query structs agreement [id] — check status, capacity, duration.
  • Allocation: structsd query structs allocation [id] — confirm power, source, destination.
  • Player balance: structsd query structs player [id] — verify Alpha Matter after transfers.

Error Handling

  • Insufficient balance: Check player Alpha Matter before infuse/send. Refine ore first.
  • Provider capacity exceeded: Query provider capacityMaximum; reduce agreement capacity or create new provider.
  • Defusion cooldown: Use reactor-cancel-defusion to re-stake during cooldown, or wait.
  • Generator infuse failed: Cannot undo. Verify struct is a generator type and amount is correct before submitting.

See Also

平台分布

OpenClaw

96.87%
按下载量换算4,486

安全审计

VirusTotal

通过

ClawScan

可疑

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

继续浏览同类 Skills