360 Secure SkillHub
360 安全技能中心

Skill Package Doctor

面向 Claude、Codex、OpenClaw 等技能包发布前的本地审查:定位技能目录后运行随包提供的 Python 脚本,生成评分、错误、警告与修复清单,检查 frontmatter 契约、说明清晰度与安全风险,迭代修改后复评;分数达 80 且无阻断错误才建议发布,可输出 JSON、Markdown 与 SVG 证明卡片。

zack-dev-cm
zack-dev-cm
热度 16.78
最近更新 2026-05-23 16:28:02
分类:开发依赖:代码执行 / 读写文件应用场景:代码审查 / 调试排错 / 报告撰写

安装技能

复制下面的话术发给你的 Agent,它会通过 secure-skills 检索并安装该技能。

执行命令安装此 skill: npx secure-skills-cli add skill-package-doctor
Metadata
name
skill-package-doctor
description
Audit Claude, Codex, OpenClaw, and ClawHub skill packages before publishing; produce concrete fix lists, trust scores, and shareable proof cards.
version
0.1.1
homepage
https://clawhub.getgeofix.xyz/
license
MIT
user-invocable
true
metadata
{"openclaw":{"skillKey":"skill-package-doctor","requires":{"anyBins":["python3","python"]}}}

Skill Package Doctor

Use this skill when the user wants to review, debug, score, publish, or improve an agent skill package.

When To Use

  • A skill folder needs a publish gate before ClawHub, Codex, Claude, or OpenClaw distribution.
  • A generated SKILL.md feels generic, unsafe, too broad, or hard to trust.
  • A builder wants a concrete fix list and a proof card they can share.
  • A marketplace listing needs evidence that the package was checked locally.

Workflow

  1. Locate the target skill folder or SKILL.md.
  2. Run the bundled doctor script when possible:
python3 scripts/skill_doctor.py /path/to/skill \
  --json-out skill-doctor.json \
  --markdown-out skill-doctor.md \
  --svg-out skill-doctor.svg
  1. Read the score, errors, warnings, and fixes.
  2. Patch only the specific issues found. Do not rewrite the skill from scratch unless it is empty or unsafe.
  3. Run the doctor again and compare the score.
  4. Before publish, make sure there are no errors and the score is at least 80.
  5. Read references/source-manifest.json only when you need package provenance or release-surface context.

Review Rules

  • Treat SKILL.md frontmatter as the registry contract.
  • A good description says the task, input, and output in plain words.
  • A useful skill has a clear When To Use trigger, an operating order, and a validation step.
  • Bundled scripts/ and references/ must be mentioned in SKILL.md.
  • Do not allow skill instructions that ask agents to reveal secrets, ignore system instructions, disable safety, or run destructive shell commands.
  • Replace vague wording with concrete inputs, outputs, failure modes, and test commands.
  • Prefer small edits that preserve the builder's intent.

Output

Return:

  • publish decision: publish-ready, ship-after-small-fixes, needs-work, or do-not-publish
  • score out of 100
  • blocking errors first
  • warnings and quick fixes
  • exact files changed
  • proof-card path when generated

Stop Conditions

Do not recommend publishing when:

  • SKILL.md is missing frontmatter, name, or description
  • the body is too short to guide an agent
  • the package contains unexplained scripts
  • the skill asks for secrets, destructive commands, or safety bypasses
  • the stated capability is broader than the files and instructions support