运维写作
- 作者仓库星标 0
- 作者更新于 实时读取
- 作者仓库 skills-registry
- 领域
- 设计与多媒体
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @tomevault-io · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 即装即用
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- macOS · Linux · Windows
- 底层运行要求
- Python
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- 网络行为
- 允许外网请求
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
---
name: nostr-sdks-update
description: >- Use when this capability is needed. You are running a knowledge refresh for the Nostr SDK kno…
category: 设计与多媒体
runtime: Python
---
# nostr-sdks-update 输出预览
## PART A: 任务判断
- 适用问题：视觉内容、演示材料、信息图或设计交付。
- 输入要求：目标材料、限制条件、期望输出和验收方式。
- 证据边界：围绕“Knowledge Refresh Task / Refresh Procedure / 1. Fetch Latest from Library Repositories”读取原文规则，不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断：确认你的需求是否属于视觉内容、演示材料、信息图或设计交付，并标出输入、限制和预期结果。
- **02** 执行计划：优先按“Knowledge Refresh Task / Refresh Procedure / 1. Fetch Latest from Library Repositories”拆成步骤，说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果：给出可复制的命令、文件改动、检查清单或内容草稿，并说明如何继续迭代。
- **04** 风险边界：结合 读取文件、写入/修改文件、会按任务需要访问外部网络、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件；会按任务需要访问外部网络；通常不需要额外 API Key。
- 先小样例验证，再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。原文没有稳定的斜杠命令要求。安装验证后通常全局生效，直接在对话里点名这个 Skill 并描述任务即可。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是：读取文件、写入/修改文件。
先用一个小任务确认它会围绕“Knowledge Refresh Task / Refresh Procedure / 1. Fetch Latest from Library Repositories”工作；涉及文件或命令时，先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作；如果输出泛泛而谈，就补充输入、边界和验收标准后重跑。
---
name: nostr-sdks-update
description: >- Use when this capability is needed. You are running a knowledge refresh for the Nostr SDK kno…
category: 设计与多媒体
source: tomevault-io/skills-registry
---
# nostr-sdks-update
## 什么时候使用
- 把设计与视觉方向的常用动作沉淀成 Agent 可调用的技能 适合处理界面、视觉、封面、信息图或演示材料交付，核心价值是把输入、判断、执行、验证和交付边界固定下来，避免 Agent 泛泛回答。 把任务拆成可执行、可检查、可继续迭代的步骤…
- 面向视觉内容、演示材料、信息图或设计交付，优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「Knowledge Refresh Task / Refresh Procedure / 1. Fetch Latest from Library Repositories」组织步骤，不把推断写成作者事实。
- 读取文件、写入/修改文件；会按任务需要访问外部网络；通常不需要额外 API Key。
- 先跑小样例，确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown，不编造命令、平台或依赖。作者原文负责流程事实；仓库文件负责来源和命令；流狐只补充适用场景、限制和质量判断。
skill "nostr-sdks-update" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> Knowledge Refresh Task / Refresh Procedure / 1. Fetch Latest from Library Repositories
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> Python | 读取文件、写入/修改文件 | 会按任务需要访问外部网络
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
}Knowledge Refresh Task
You are running a knowledge refresh for the Nostr SDK knowledge base. This is a maintenance task — do NOT answer user questions, only update your agent memory.
Important: Write all findings to your agent memory directory ONLY. Never modify files in the plugin/skill directory — those are read-only artifacts managed by the plugin update mechanism.
If arguments were provided, focus on: $ARGUMENTS Otherwise, perform a full refresh.
Refresh Procedure
1. Fetch Latest from Library Repositories
Fetch README and recent release notes for each SDK:
| SDK | URL to fetch |
|---|---|
| nostr-tools | https://github.com/nbd-wtf/nostr-tools/releases |
| NDK | https://github.com/nostr-dev-kit/ndk/releases |
| rust-nostr | https://github.com/rust-nostr/nostr/blob/master/CHANGELOG.md |
| nostr-sdk-jvm (Maven) | https://central.sonatype.com/artifact/io.github.rust-nostr/nostr-sdk |
| nostr-sdk-swift (UniFFI) | https://github.com/rust-nostr/nostr-sdk-swift/releases |
| nostr-sdk-ios (native) | https://github.com/nostr-sdk/nostr-sdk-ios/releases |
| fiatjaf.com/nostr (Go) | https://pkg.go.dev/fiatjaf.com/nostr |
| go-nostr (archived legacy) | https://github.com/nbd-wtf/go-nostr |
| nostr-java | https://github.com/tcheeric/nostr-java/releases |
| nostr4j | https://github.com/NostrGameEngine/nostr4j |
| pynostr | https://pypi.org/project/pynostr/ |
| python-nostr (legacy) | https://github.com/jeffthibault/python-nostr |
| Rhodium | https://github.com/KotlinGeekDev/Rhodium |
| NostrKit | https://github.com/cnixbtc/NostrKit |
For each source, capture:
- Current version numbers (npm, JSR, crates.io, Maven Central, PyPI, SwiftPM)
- New or modified API surfaces
- Newly supported NIPs / dropped NIPs
- Breaking changes or deprecation notices
- Last commit timestamp; flag stale projects (>180 days inactive)
- Archive status changes
2. Search for Recent Developments
Use WebSearch for:
- "rust-nostr release" — version bumps, new bindings
- "nostr SDK new library" — emerging libraries to consider tracking
- "nostr-tools" / "NDK" major release notes
- "nostr go library" / "fiatjaf.com/nostr" — Go ecosystem updates
- "nostr Kotlin Swift" — JVM/Apple binding updates
3. Verify Project Status
For each tracked SDK:
- Is it still active? (commits in last 90 days)
- Has it been archived, renamed, or moved?
- Have new forks or successors emerged?
- Have new bindings appeared (UniFFI, FFI, JNI)?
If a new SDK is observed in the ecosystem, add it to the matrix in agent memory (not the shipped supporting docs) for inclusion in a future update release.
4. Update Agent Memory
Write all findings to your agent memory directory. Never modify plugin files.
MEMORY.md — update with:
last_fetch_date: <unix-timestamp>- Current version numbers for each tracked SDK
- Summary of what changed since last fetch
- Any newly archived / renamed / forked projects
Topic files — update or create as needed:
| File | What to record |
|---|---|
library-matrix.md |
Updated maturity / activity / NIP-support data per SDK |
new-libraries.md |
Newly observed Nostr SDKs not yet in shipped docs |
gotchas.md |
API quirks, name collisions, binding pitfalls discovered |
changelog.md |
Version bumps, breaking changes, archive notices |
corrections.md |
Anything that differs from shipped supporting documents — these corrections take precedence when answering |
5. Report
Output a concise summary of what was found:
- Key changes since last refresh
- New version numbers
- New or archived libraries
- Any corrections to the shipped supporting documents
- Issues encountered (404s, missing data, etc.)
Source: 941design/claude-plugins — distributed by TomeVault.
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核