Token导航 LogoToken导航

Agent Skill · 研究检索

skill-inventory-auditor(技能清单审核员)

用于辅助安全审计、权限检查、凭据风险、认证流程和常见漏洞排查。它适合让 Agent 梳理敏感配置、检查依赖风险、分析鉴权逻辑或生成安全复核清单。使用时不能把工具输出直接当最终结论,涉及密钥、令牌、用户数据或生产系统时,应先确认最小权限、脱敏方式和操作边界。

skill-inventory-auditor 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为需要联网;许可证信息还不明确,第三方扫描已通过,按安装量在研究检索类的 73,674 个 Skill 里排第 54,843。

总安装 494周安装 21GitHub Stars 68下载 173核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:skill-inventory-auditor(技能清单审核员)
来源仓库:https://github.com/luongnv89/skills
仓库路径:skills/skill-inventory-auditor
安装命令:
npx skills add https://github.com/luongnv89/skills --skill skill-inventory-auditor
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/luongnv89/skills --skill skill-inventory-auditor

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

skill-inventory-auditor 用于辅助安全审计、权限检查和常见漏洞排查,适合梳理敏感配置与依赖风险。可分析鉴权逻辑、生成安全复核清单或识别凭据暴露问题,提升系统安全性。通过 npx skills add 命令从指定仓库安装,需确认来源仓库的有效性与访问权限。

使用时不能将工具输出直接当作最终结论,需人工复核关键发现。涉及密钥、令牌或用户数据时,应先确认最小权限与脱敏方式。

来源仓库内路径:skills/skill-inventory-auditor

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/luongnv89/skills --skill skill-inventory-audit…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

skill-inventory-auditor 怎么安装?

在终端执行 npx skills add https://github.com/luongnv89/skills --skill skill-inventory-auditor。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

skill-inventory-auditor 支持哪些 AI 工具?

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

skill-inventory-auditor 需要什么权限?

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

skill-inventory-auditor 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

skill-inventory-auditor 用的人多吗?

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

skill-inventory-auditor 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

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

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

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

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
skill-inventory-auditor

技能清单审核员 · 本页

49468需要联网未明确通过

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

SKILL.md 原文

Skill Inventory Auditor

Find and remove duplicate skills across installed skill directories.

Repo Sync Before Edits (mandatory)

Before removing skills from git-tracked directories, sync the current branch with remote:

branch="$(git rev-parse --abbrev-ref HEAD)"
git fetch origin
git pull --rebase origin "$branch"

If the working tree is not clean, stash first, sync, then restore:

git stash push -u -m "pre-sync"
branch="$(git rev-parse --abbrev-ref HEAD)"
git fetch origin && git pull --rebase origin "$branch"
git stash pop

If origin is missing, pull is unavailable, or rebase/stash conflicts occur, stop and ask the user before continuing.

Workflow

Phase 1: Scan

Run the duplicate scanner with scope both (default) unless the user specifies otherwise:

python3 {SKILL_DIR}/scripts/scan_inventory.py --scope both --project-dir {cwd}

Scopes: global (~/.claude/skills/, ~/.agents/skills/), project (.claude/skills/), or both.

Parse the JSON output. If the script fails, report the error and stop.

Phase 2: Report Duplicates

If no duplicates are found, say so and stop.

For each duplicate group:

  1. Present a table with skill name, location, version, and description excerpt
  2. Show the similarity score between descriptions
  3. Explain why they were flagged (same name or similar description)
  4. Recommend which to keep based on:

- Higher version number - More descriptive name - Richer feature set (more scripts/files) - Location preference (project-local skills may override global)

Ask the user which skills to keep/remove for each group. Wait for confirmation.

Phase 3: Remove Duplicates

Present a summary of planned removals, then ask for confirmation.

Symlink removal (preserves the source):

rm {symlink_path}

Directory removal:

rm -rf {directory_path}

Safety rules:

  • Always confirm before executing removals
  • Print exactly what will be deleted
  • Never remove skills from the project source repository (e.g., skills/ in a git repo)
  • When removing a symlink, only the link is deleted — the source remains intact

After removals, rerun the scanner to verify no duplicates remain.

Expected Output

After the audit completes, the skill presents:

Skill Inventory Audit — 2 duplicate group(s) found

Group 1: "release-manager"
| Location                          | Version | Description excerpt              |
|-----------------------------------|---------|----------------------------------|
| ~/.claude/skills/release-manager  | 2.3.1   | Automate the full release...     |
| .claude/skills/release-manager    | 2.1.0   | Complete release automation...   |
Recommendation: keep ~/.claude/skills/release-manager (higher version)
Similarity: exact name match

Removed: .claude/skills/release-manager
Rescan: 0 duplicates remaining.

Edge Cases

  • Symlink pointing to the same source as another entry: Do not flag as a duplicate. The scanner excludes cross-linked entries that resolve to the same path; treat them as a single shared installation.
  • Skill with no skill.md file: If a directory in a skills folder lacks a skill.md, skip it during scanning and report it separately as an unrecognized entry. Do not attempt to remove it automatically.
  • Scanner script not found: If scripts/scan_inventory.py is missing (e.g., the skill was installed without its scripts), report the missing dependency and stop. Do not attempt to scan manually.

Acceptance Criteria

  • All configured skill directories (global and project) are scanned
  • Each duplicate group is presented with a table showing location, version, and description excerpt
  • A keep/remove recommendation is provided for each group based on version and feature richness
  • No skills are removed without explicit user confirmation
  • Source repositories are never touched — only installed copies in ~/.claude/skills/, ~/.agents/skills/, or .claude/skills/ are eligible for removal
  • A rescan is run after removals to confirm zero duplicates remain

Step Completion Reports

After completing each major step, output a status report in this format:

◆ [Step Name] ([step N of M] — [context])
··································································
  [Check 1]:          √ pass
  [Check 2]:          √ pass (note if relevant)
  [Check 3]:          × fail — [reason]
  [Check 4]:          √ pass
  [Criteria]:         √ N/M met
  ____________________________
  Result:             PASS | FAIL | PARTIAL

Adapt the check names to match what the step actually validates. Use √ for pass, × for fail, and — to add brief context. The "Criteria" line summarizes how many acceptance criteria were met. The "Result" line gives the overall verdict.

Phase-specific checks

Phase 1 — Scan

◆ Scan (step 1 of 3 — inventory collection)
··································································
  Global skills scanned:    √ pass (~/.claude/skills/, ~/.agents/skills/)
  Project skills scanned:   √ pass (.claude/skills/)
  Duplicates identified:    √ pass (N duplicate groups found)
  ____________________________
  Result:             PASS | FAIL | PARTIAL

Phase 2 — Report

◆ Report (step 2 of 3 — findings presentation)
··································································
  Findings presented:       √ pass (table shown per duplicate group)
  Severity classified:      √ pass (exact name match | similar description)
  Removal plan ready:       √ pass (keep/remove recommendations made)
  ____________________________
  Result:             PASS | FAIL | PARTIAL

Phase 3 — Cleanup

◆ Cleanup (step 3 of 3 — duplicate removal)
··································································
  Duplicates removed:       √ pass (N skills removed)
  No side effects:          √ pass (source repos untouched)
  Inventory verified:       √ pass (rescan: 0 duplicates remaining)
  ____________________________
  Result:             PASS | FAIL | PARTIAL

Important Notes

  • This skill only removes installed copies (in ~/.claude/skills/, ~/.agents/skills/, or .claude/skills/). It never touches source repositories.
  • Symlinks between ~/.claude/skills/ and ~/.agents/skills/ pointing to the same target are shared installations, NOT duplicates. The scanner excludes these automatically.

平台分布

Codex

33.1%
按下载量换算57

Claude

28.84%
按下载量换算50

Cursor

19.59%
按下载量换算34

Gemini CLI

10.69%
按下载量换算18

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

需要联网

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

安装前确认

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

继续浏览同类 Skills