市场健康检查
- 作者仓库星标 0
- 作者更新于 2026年8月24日 07:33
- 作者仓库 claude-code-skills
- 领域
- 通用
- 作者声明的智能体
- 未找到明确声明;不据此推断已兼容或已测试
- 静态检查
- 88 / 100 · 启发式扫描,不代表运行安全
- 运行环境证据
- 未执行;当前没有隔离运行测试证据
- 作者 / 版本 / 许可证
- @daymade · 未声明许可证
- 上下文用量评级
- 低消耗
- 接入复杂程度
- 需简单配置
- 是否需要外部接口密钥
- 不需要
- 兼容的系统
- 未声明(默认跨平台)
- 运行环境要求
- 未检出明确要求
- 检测到的文件与系统行为
-
- 只读
- 允许写入 / 修改
- 命令执行
- 网络行为
- 仅限本地
- 安装命令数
- 无(仅作为资料)
需要注意: 未声明工具权限范围;实际权限由运行环境决定。
第 1 步 — 侦察当前规模(一次快速通过,由所有六名特工共享)
工作流程脚本采用一个`args`对象,因此所有代理共享一个准确的快照,而不是每个代理都重新发现它。收集:在将 PII 视为发布风险之前确认`isPrivate: false` - 重点是这是一个公共存储库。
第 2 步 — 启动工作流程
读取捆绑的脚本并通过 `script` 参数内联启动它(传递其内容,因此不依赖于技能的安装位置):它并行运行六个检查器(约 15-20 分钟,约 400-500k 输出令牌 - 预先告诉用户成本)并返回 `{ checks: [...] }`,每个维度一个结构化结果:`health` + `summary` + `findings[]`(每个都有严重性/标题/详细信息/位置/建议)+ `stats`。
第 3 步 — 在报告之前对严重的调查结果进行反审核
代理人的发现是假设,而不是结论。切勿逐字转述。对于每个`high`/`critical`发现,请使用快速命令自行验证 - grep 泄漏的值,`sed -n`虚线,`gh repo view`声明的状态 - 确认它是(a)真实的,(b)位于代理所说的位置,并且(c)没有超出范围。这可以捕获误报,并且同样重要的是,代理“建议”实际上是错误的。 (在该技能的提炼中,安全检查员建议将真正的私有域添加到公共领域`.gitleaks.toml`——这是必须拒绝的反目标举措;请参阅方法参考。)
# Marketplace Health Check
Run a comprehensive, evidence-based health check of this Claude Code skills marketplace repo using a parallel fan-out Dynamic Workflow. Six independent inspectors cover, in parallel:
1. **Code & script safety** — dangerous deletes, NO-FALLBACK secret leaks, hardcoded real paths, bare `except`, injection, missing shebangs
2. **Documentation / SSOT consistency** — version coherence across marketplace.json / README×2 / CHANGELOG / git release, skill & plugin counts, broken references, derived-value drift
3. **Security / PII** — keyword-free leaks gitleaks can't catch (real names, private domains), the `.security-scan-passed` marker gap, case-file audits
4. **Open-PR triage** — classify every PR (worth-merging / needs-changes / decline-as-promotion)
5. **Open-issue triage** — real bugs vs skill-requests vs promotion, plus the broken-install-command bug class
6. **Marketplace-manifest integrity** — `check_marketplace.sh` + `check_doc_skill_lists.py`, orphans, suite registration
Then YOU verify the serious findings and report by priority. The bundled script (`scripts/repo-health-check.workflow.js`) is the proven, ready-to-run workflow; this file is how to run and interpret it.
## Why a workflow — and why it MUST run inline
The six dimensions are independent, so fanning them out across six parallel agents is far faster than one agent sweeping serially, and each inspector stays focused on one concern with its own structured output.
**This skill must run inline (no `context: fork`).** It orchestrates parallel agents through the Workflow tool, and a forked subagent cannot spawn subagents or launch a workflow — running it forked would silently break the fan-out. The Workflow tool also requires explicit user opt-in; a user asking to "run the health check" IS that opt-in, so proceed.
## How to run
### Step 1 — Scout the current scale (one quick pass, shared by all six agents)
The workflow script takes an `args` object so all agents share one accurate snapshot instead of each re-discovering it. Gather:
```bash
gh repo view --json nameWithOwner,stargazerCount,isPrivate | jq -c .
echo "skills: $(find . -name SKILL.md -not -path '*-workspace/*' | wc -l | tr -d ' ')"
echo "open PRs: $(gh pr list --state open --json number | jq length)"
echo "open issues: $(gh issue list --state open --json number | jq length)"
grep -A1 '"metadata"' .claude-plugin/marketplace.json | grep -oE '"version": "[^"]*"' | head -1
git rev-parse --short HEAD; gh release view --json tagName -q .tagName 2>/dev/null
```
Confirm `isPrivate: false` before treating PII as a publishing risk — the whole point is that this is a PUBLIC repo.
### Step 2 — Launch the workflow
Read the bundled script and launch it **inline via the `script` parameter** (pass its contents, so there's no dependency on where the skill is installed):
```
Workflow({
script: <full contents of scripts/repo-health-check.workflow.js>,
args: { repo: "<owner/name>", scale: "<one-line summary from Step 1>" }
})
```
It runs the six inspectors in parallel (~15-20 min, ~400-500k output tokens — tell the user the cost up front) and returns `{ checks: [...] }`, one structured result per dimension: `health` + `summary` + `findings[]` (each with severity / title / detail / location / recommendation) + `stats`.
While it runs you can do other useful prep, but don't start editing files the inspectors are reading.
### Step 3 — Counter-Review the serious findings BEFORE reporting
**Agent findings are HYPOTHESES, not conclusions. Never relay them verbatim.** For every `high`/`critical` finding, verify it yourself with a quick command — grep the leaked value, `sed -n` the broken line, `gh repo view` the claimed state — confirming it's (a) real, (b) located where the agent says, and (c) not over-reach. This catches false alarms AND, just as important, agent *recommendations* that are actively wrong. (In the session this skill was distilled from, a security inspector recommended adding the real private domains into the public `.gitleaks.toml` — an anti-target move that had to be rejected; see the methodology reference.)
Filter every finding through four questions: **probability** (does it really happen?), **cost** (fix vs ignore), **real scenario** (does it bite in practice?), **verifiable** (can a 1-line command confirm or refute it?).
## Report format
Lead with the table, then layer by priority. Classify — don't dump:
- **One-line verdict + a 6-dimension health table** (good / minor-issues / needs-attention / critical per dimension)
- **🔴 Must-fix** — each VERIFIED high/critical, with exact location + a concrete fix
- **🟠 Backlog** — PR/issue triage outcomes, scan-marker gaps (decisions, often outward-facing — flag that they affect external contributors)
- **🟢 Optional** — low/info nits, one line each
- **💡 Key insights** — the meta-findings worth surfacing (a structural blind spot in tooling, a recurring bug class)
Tag each surfaced item ✅ real / ⚠️ partly / ❌ false-alarm. Most raw agent output is noise; your job is to surface the real risks the owner didn't already know, not to forward 25 findings for them to sift.
## Judgment principles
Apply these when interpreting findings and proposing fixes. Full reasoning + the real failure cases behind each are in [references/health-check-methodology.md](references/health-check-methodology.md) — read it before acting on PII or PR/issue findings.
- **Anti-target**: never "fix" a PII leak by listing the real value in a public allowlist (e.g. the repo's own `.gitleaks.toml`) — a public list enumerating real assets is itself a leak. Sanitize the value in place; detection rules for real private values belong in the owner's private global guard, not in this public repo.
- **History note**: sanitizing the working copy cleans the *current* version, but a pre-existing leak still sits in git history. Flag the history exposure honestly; a history rewrite (force-push) is a separate high-risk decision that affects every fork — never do it unprompted.
- **Scan marker = necessary-not-sufficient**: a `.security-scan-passed` marker means "no known-format secret was found", NOT "sanitized". It is blind to keyword-free leaks, so pair it with a human/semantic read of any skill shipping real-data examples.
- **Mandatory version bump**: any change to a skill's files requires bumping that skill's `version` in marketplace.json (and a CHANGELOG entry). External-contributor PRs almost always miss this — flag it, don't merge without it.
- **Promotion is declined by default**: third-party directory / tool / marketplace promotion PRs and issues are declined — the repo is a personal curated marketplace, not an ecosystem directory. The decline-policy template is a reference doc at the repo root (outside this skill's bundle).
## Bundled resources
- `scripts/repo-health-check.workflow.js` — the six-inspector Dynamic Workflow. Run it via the Workflow tool's `script` param (Step 2). Edit it when you add/retire an inspector dimension.
- `references/health-check-methodology.md` — the Counter-Review filter, reporting discipline, and the anti-target / history / scan-marker / decline rules, each with the real failure case that motivated it.
## Next step
After delivering the report, the typical follow-ups are owner decisions, not automated actions — fixing the verified HIGHs (sanitize PII, correct broken commands), or triaging the PR/issue backlog. Surface them as options; don't auto-fix or auto-comment on PRs/issues without the user's go-ahead, since those are outward-facing and affect external contributors.
章节与文件索引
按说明文件中的顺序排列。
为什么工作流程——以及为什么它必须内联运行
第 1 步 — 侦察当前规模(一次快速通行证,由所有六名特工共享)
第 2 步 — 启动工作流程
第 3 步 — 在报告之前对严重的调查结果进行反审核
报告格式
文件/命令 -> except · .security-scan-passed · check_marketplace.sh · check_doc_skill_lists.py · scripts/repo-health-check.workflow.js · context: fork · args · isPrivate: false
内容校验值 -> d40bfc9793ec
当前原文的自动摘译,尚未人工审校。
为什么工作流程——以及为什么它必须内联运行
六个维度是独立的,因此将它们分散到六个并行代理中比一个代理串行扫描要快得多,并且每个检查员都通过自己的结构化输出专注于一个问题。该技能必须内联运行(无
context: fork)。它通过工作流工具编排并行代理,分叉的子代理无法生成子代理或启动工作流 - 分叉运行它会默默地破坏扇出。工作流程工具还需要明确的用户选择加入;要求“运行健康检查”的用户即表示选择加入,因此请继续。第 2 步 — 启动工作流程
读取捆绑的脚本并通过
script参数内联启动它(传递其内容,因此不依赖于技能的安装位置):它并行运行六个检查器(约 15-20 分钟,约 400-500k 输出令牌 - 预先告诉用户成本)并返回{ checks: [...] },每个维度一个结构化结果:health+summary+findings[](每个都有严重性/标题/详细信息/位置/建议)+stats。第 3 步 — 在报告之前对严重的调查结果进行反审核
代理人的发现是假设,而不是结论。切勿逐字转述。对于每个
high/critical发现,请使用快速命令自行验证 - grep 泄漏的值,sed -n虚线,gh repo view声明的状态 - 确认它是(a)真实的,(b)位于代理所说的位置,并且(c)没有超出范围。这可以捕获误报,并且同样重要的是,代理“建议”实际上是错误的。 (在会议上,这项技能被提炼出来,一位安全检查员建议将真正的私有域添加到公共域中.gitleaks.toml——这是一个必须拒绝的反目标举措;请参阅方法参考。)报告格式
以表格为主导,然后按优先级分层。分类 — 不要转储:一行判决 + 6 维健康表(每个维度良好/次要问题/需要注意/关键) 🔴 必须修复 — 每个已验证的高/关键,具有确切位置 + 具体修复 🟠 待办事项 — PR/问题分类结果,扫描标记差距(决策,通常是面向外的 — 标记它们影响外部贡献者) 🟢 可选 — 低/信息尼特,每行一行