Agent同步
- 作者仓库星标 0
- 作者更新于 实时读取
- 作者仓库 skills-registry
- 领域
- 通用
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @tomevault-io · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- macOS · Linux · Windows
- 底层运行要求
- Node.js
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- 网络行为
- 仅限本地
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生,可能与作者实际意图存在差异。
需要注意: 未限定 allowed-tools,默认拥有全部工具权限。
---
name: lightning-ldk
description: | Use when this capability is needed. LDK is a library, not a daemon. Provides Rust crates with…
category: 通用
runtime: Node.js
---
# lightning-ldk 输出预览
## PART A: 任务判断
- 适用问题:通用任务拆解、检查和交付。
- 输入要求:目标材料、限制条件、期望输出和验收方式。
- 证据边界:围绕“Crates (selected) / Core primitives / ldk-node (quick-start)”读取原文规则,不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断:确认你的需求是否属于通用任务拆解、检查和交付,并标出输入、限制和预期结果。
- **02** 执行计划:优先按“Crates (selected) / Core primitives / ldk-node (quick-start)”拆成步骤,说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果:给出可复制的命令、文件改动、检查清单或内容草稿,并说明如何继续迭代。
- **04** 风险边界:结合 读取文件、写入/修改文件、主要在本地完成、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件;主要在本地完成;通常不需要额外 API Key。
- 先小样例验证,再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。 原文没有稳定的斜杠命令要求。安装验证后通常全局生效,直接在对话里点名这个 Skill 并描述任务即可。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是:读取文件、写入/修改文件。
先用一个小任务确认它会围绕“Crates (selected) / Core primitives / ldk-node (quick-start)”工作;涉及文件或命令时,先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作;如果输出泛泛而谈,就补充输入、边界和验收标准后重跑。
---
name: lightning-ldk
description: | Use when this capability is needed. LDK is a library, not a daemon. Provides Rust crates with…
category: 通用
source: tomevault-io/skills-registry
---
# lightning-ldk
## 什么时候使用
- 把通用方向的常用动作沉淀成 Agent 可调用的技能 适合处理通用任务拆解、检查、交付和复盘,核心价值是把输入、判断、执行、验证和交付边界固定下来,避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭代的步骤;通常不需要额外…
- 面向通用任务拆解、检查和交付,优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「Crates (selected) / Core primitives / ldk-node (quick-start)」组织步骤,不把推断写成作者事实。
- 读取文件、写入/修改文件;主要在本地完成;通常不需要额外 API Key。
- 先跑小样例,确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown,不编造命令、平台或依赖。 作者原文负责流程事实;仓库文件负责来源和命令;流狐只补充适用场景、限制和质量判断。
skill "lightning-ldk" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> Crates (selected) / Core primitives / ldk-node (quick-start)
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> Node.js | 读取文件、写入/修改文件 | 主要在本地完成
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
} LDK (Lightning Dev Kit)
LDK is a library, not a daemon. Provides Rust crates with C/Swift/ Kotlin/JS bindings. Used by Mutiny Wallet, Cash App, Casa, ldk-node, Phoenix (parts), etc.
Crates (selected)
lightning— core protocol logic.lightning-net-tokio— async TCP transport.lightning-persister— file-based persistence.lightning-background-processor— background task driver.lightning-block-sync— chain sync.lightning-transaction-sync— alternative tx-only sync.lightning-rapid-gossip-sync— fast gossip via signed snapshot.lightning-invoice— BOLT11 invoice handling.ldk-node— opinionated bundling for quick-start.lightning-liquidity— LSP client/server primitives.bdkintegration crates.
Core primitives
// Persistence trait
trait Persist<ChannelSigner> { ... }
// Channel manager — owns all channels
let chan_mgr = ChannelManager::new(...);
// Chain monitoring — watches outputs, force-close events
let chain_mon = ChainMonitor::new(...);
// Router — pathfinding
let router = DefaultRouter::new(...);
// Background processor — drives async tasks
BackgroundProcessor::start(...);
User code provides:
- KeysManager — produces/derives keys.
- NetworkGraph — channel graph storage.
- EventHandler — react to events (payment received, channel opened).
- Persister — save state to disk / DB.
- FeeEstimator — fee rate source.
- BroadcasterInterface — broadcast txs.
ldk-node (quick-start)
use ldk_node::{Builder, Network};
let builder = Builder::new()
.set_network(Network::Bitcoin)
.set_chain_source_esplora("https://blockstream.info/api".into())
.set_storage_dir_path("/path/to/data".into());
let node = builder.build().unwrap();
node.start().unwrap();
// Use the node
let address = node.onchain_payment().new_address().unwrap();
let invoice = node.bolt11_payment().receive(amount_msat, "desc", 3600).unwrap();
node.bolt11_payment().send(&invoice, None).unwrap();
ldk-node exposes a single API surface across Rust + Swift/Kotlin/JS
bindings.
Async signer
For hardware wallets / remote signers:
trait NodeSigner { fn ecdh(&self, ...) -> Result<...>; ... }
trait ChannelSigner { fn sign_counterparty_commitment(&self, ...) -> ...; ... }
trait SignerProvider { fn derive_channel_signer(&self, ...) -> ChannelSigner; ... }
LDK supports async signing via EventHandler::handle_event returning
deferred sigs. Useful for hardware-wallet-backed Lightning.
Persistence model
LDK doesn't dictate storage. Common backends:
- File:
lightning-persisterwrites channel state to disk. - Database: SQLite, PostgreSQL — implement
Persisttrait. - Cloud: persist channel state encrypted to cloud storage (Mutiny does this).
- Trustless replication: VSS (Versioned Storage Service) — Lightning Labs' encrypted cloud storage protocol.
Chain sync options
- bitcoind RPC —
lightning-block-syncpolls / ZMQs. - Esplora API —
lightning-transaction-syncvia Esplora REST. - Electrum — same crate, via Electrum protocol.
- Neutrino (BIP157/158) — light-client; for mobile.
Mobile uses Neutrino: lightning-block-sync downloads filters, scans locally for UTXO matches, downloads only relevant blocks.
Bindings
LDK provides:
- Rust native crates.
- C via
lightning-c-bindings. - Swift / iOS via
LDKSwiftandLDKNode. - Kotlin / Android via
LDKKotlinandldk-node-kotlin. - JS / WASM via
ldk-node-js(experimental).
ldk-node specifically targets Swift/Kotlin/JS so mobile devs get a single API.
Use cases
- Mutiny Wallet — browser-based LN via WASM + LDK.
- Cash App — backend LN.
- Casa — vault + LN integration.
- Phoenix (partial) — uses LDK components.
- Greenlight (Blockstream) — alternative; CLN-based.
Memory footprint
LDK is light: ~10-20 MB RAM for a typical mobile node. Bitcoin Core
- LND can use 1+ GB. This is the main reason LDK dominates mobile.
Comparing LDK to LND/CLN
| Aspect | LND/CLN | LDK |
|---|---|---|
| Deployment | daemon | library, embedded |
| Mobile | no | yes (primary use) |
| Custom UI/logic | hard | easy (you own everything) |
| Default features | full | you choose |
| Memory | 200 MB+ | 10-20 MB |
Common issues
Persisttrait misimplementation: missed updates → state corruption on restart.- Async signer race conditions: signing requests racing with channel updates.
- Chain sync gaps: skipped blocks → channel state diverges.
- ldk-node migration: upgrading minor versions sometimes requires state migration; back up first.
See also
Source: claude-dev-suite/claude-dev-suite — distributed by TomeVault.
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核