Agent安装
- 作者仓库星标 236
- 作者更新于 实时读取
- 作者仓库 armory
- 领域
- AI 智能
- 兼容 Agent
-
- Claude Code
- Cursor
- Cline
- Codex
- Windsurf
- Gemini CLI
- +20
- 信任分
- 88 / 100 · 社区维护
- 作者 / 版本 / 许可
- @Mathews-Tom · 未声明 license
- Token 消耗评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部 API Key
- 不需要
- 兼容的系统
- 未声明（默认跨平台）
- 底层运行要求
- 无特殊要求
- 文件与系统权限
-
- 只读
- 允许写入 / 修改
- Shell 执行
- 网络行为
- 允许外网请求
- 安装命令数
- 26 条
档案由构建时根据 SKILL.md 与安装命令自动衍生，可能与作者实际意图存在差异。
需要注意： 未限定 allowed-tools，默认拥有全部工具权限。
---
name: skill-library
description: Agent-native catalog and installer for armory packages across all 7 types. Browse, search, insta…
category: AI 智能
runtime: 无特殊运行时
---
# skill-library 输出预览
## PART A: 任务判断
- 适用问题：提示词、Agent 工作流、模型评估或自动化推理。
- 输入要求：目标材料、限制条件、期望输出和验收方式。
- 证据边界：围绕“Variables / Supported Package Types / Command Reference”读取原文规则，不把推断写成作者承诺。
## PART B: 执行结果
- **01** 任务判断：确认你的需求是否属于提示词、Agent 工作流、模型评估或自动化推理，并标出输入、限制和预期结果。
- **02** 执行计划：优先按“Variables / Supported Package Types / Command Reference”拆成步骤，说明每一步会读取什么、修改什么、产出什么。
- **03** 交付结果：给出可复制的命令、文件改动、检查清单或内容草稿，并说明如何继续迭代。
- **04** 风险边界：结合 读取文件、写入/修改文件、执行终端命令、会按任务需要访问外部网络、通常不需要额外 API Key 给出执行前确认项。
## Running Rules
- 读取文件、写入/修改文件、执行终端命令；会按任务需要访问外部网络；通常不需要额外 API Key。
- 先小样例验证，再放大到真实任务。
- 交付时同时给结果、检查口径和下一步迭代建议。原文出现了 `/tmp`、`/library` 这类斜杠命令；如果你的 Agent 支持命令触发，优先用命令开场，再补充目标和边界。
告诉 Agent 目标文件或材料、期望结果、不可改范围、是否允许联网或执行命令。本 Skill 的权限画像是：读取文件、写入/修改文件、执行终端命令。
先用一个小任务确认它会围绕“Variables / Supported Package Types / Command Reference”工作；涉及文件或命令时，先看 diff、日志、预览或测试结果。
检查最终产物是否包含明确结果、必要证据和下一步动作；如果输出泛泛而谈，就补充输入、边界和验收标准后重跑。
---
name: skill-library
description: Agent-native catalog and installer for armory packages across all 7 types. Browse, search, insta…
category: AI 智能
source: Mathews-Tom/armory
---
# skill-library
## 什么时候使用
- 把 AI / Agent方向的常用动作沉淀成 Agent 可调用的技能 适合处理AI Agent、提示词、模型评估与自动化推理，核心价值是把输入、判断、执行、验证和交付边界固定下来，避免 Agent 泛泛回答。 把任务拆成可执行、可检查…
- 面向提示词、Agent 工作流、模型评估或自动化推理，优先处理能明确输入、步骤和验收标准的工作。
## 需要提供什么
- 目标材料、目录范围、期望结果和不可改动内容。
- 是否允许联网、执行命令、读写文件或调用外部服务。
## 执行规则
- 围绕「Variables / Supported Package Types / Command Reference」组织步骤，不把推断写成作者事实。
- 读取文件、写入/修改文件、执行终端命令；会按任务需要访问外部网络；通常不需要额外 API Key。
- 先跑小样例，确认结果可检查后再扩大任务范围。
## 输出要求
- 给出最终产物、关键证据、验证方式和下一步动作。
- 信息不足时标记 unknown，不编造命令、平台或依赖。作者原文负责流程事实；仓库文件负责来源和命令；流狐只补充适用场景、限制和质量判断。
skill "skill-library" {
输入层 -> 用户目标 + 目标文件 + 禁止范围 + 验收标准
上下文层 -> Variables / Supported Package Types / Command Reference
规则层 -> SKILL.md 触发条件 / 执行顺序 / 输出格式
运行层 -> 无特殊运行时 | 读取文件、写入/修改文件、执行终端命令 | 会按任务需要访问外部网络
安全层 -> 通常不需要额外 API Key + 小任务验证 + diff / 日志复核
输出层 -> 可复制结果 + 检查清单 + 下一步迭代
}Package Library
Agent-native catalog and installer for all armory package types. Provides browsing, searching, installing, updating, syncing, and removing packages directly within an agent session.
Variables
- ARMORY_REPO:
Mathews-Tom/armory - ARMORY_BRANCH:
main - ARMORY_CATALOG_URL:
https://raw.githubusercontent.com/{ARMORY_REPO}/{ARMORY_BRANCH}/manifest.yaml - DEFAULT_INSTALL_DIR:
~/.claude/ - CATALOG_CACHE_PATH:
/tmp/armory-manifest.yaml - CATALOG_CACHE_TTL:
600(seconds)
Supported Package Types
| Type | Install Target | Method |
|---|---|---|
| skill | ~/.claude/skills/ |
Copy directory |
| agent | ~/.claude/agents/ |
Copy directory |
| hook | ~/.claude/hooks/ |
Copy directory |
| rule | ~/.claude/rules/ |
Body-only file |
| command | ~/.claude/commands/ |
Body-only file |
| utility | ~/.claude/utilities/ |
Copy + chmod +x |
| preset | ~/.claude/presets/ |
Copy directory |
Command Reference
| Command | Cookbook | Purpose |
|---|---|---|
/library list |
cookbook/list.md |
Show all packages with type, version, installed status, update available |
/library list --type <type> |
cookbook/list.md |
Filter listing by package type (skill, agent, hook, rule, etc.) |
/library use <name> |
cookbook/use.md |
Pull a package from armory (auto-detects type from manifest) |
/library search <keyword> |
cookbook/search.md |
Keyword search across all package types, names, and descriptions |
/library search --category <name> |
cookbook/search.md |
Filter search by category (development, review, security, etc.) |
/library sync |
cookbook/sync.md |
Re-pull all installed packages that have updates |
/library info <name> |
cookbook/info.md |
Show full detail for a package (type, version, tags, category) |
/library update |
cookbook/update.md |
Check all installed packages for version bumps (dry-run sync) |
/library remove <name> |
cookbook/remove.md |
Remove an installed package |
/library profiles |
cookbook/profiles.md |
Show available install profiles with package counts |
Cookbook Dispatch
User commands are routed to the corresponding cookbook file based on the subcommand. When a /library command is received, extract the subcommand (the first token after /library) and load the matching cookbook file from the cookbook/ directory relative to this skill. The cookbook file contains the full execution procedure for that operation.
For example, /library use commit-standards dispatches to cookbook/use.md with commit-standards as the package name argument. /library list --type agent dispatches to cookbook/list.md with --type agent as the filter.
If the subcommand does not match any known cookbook, report the error and list the valid subcommands from the table above.
Type Detection
When /library use <name> is called, determine the package type by searching all sections of the manifest (packages.skills, packages.agents, packages.hooks, etc.). The first section containing a matching name entry determines the type. Use the type to:
- Resolve the correct source path:
{type_dir}/{name}/ - Determine the install target:
~/.claude/{install_subdir}/ - Choose the install method: directory copy or body-only extraction
Behavioral Notes
- All bash operations must use absolute paths. Never
cdinto temp dirs. - Fetch uses a 3-tier fallback chain: sparse checkout, then
gh api, thencurl. Attempt each in order; proceed to the next only on failure. - Cache lives in
/tmp/with a 10-minute TTL. A missing cache file is treated as expired (triggers a re-fetch), not as an error. - The catalog is read from
manifest.yamlon GitHub (atARMORY_CATALOG_URL), not from a separate catalog file. This is the same manifest format used by the armory repository. - All package type sections share the same entry format:
name,version,description,path,source, plus optionaltags,category,difficulty.
先判断是否适合
作者设计意图
作者的方法与取舍
边界和复核