360 Secure SkillHub
360 安全技能中心

Publish Guard

Publish Guard 是发布前的公开面审计技能:扫描仓库中的泄露模式(绝对路径、本地服务地址、凭据形态字符串),检查 README、SKILL.md、agent 元数据与工作区 launch 文档的受众适配问题,并为主 README 生成文案评分,最后合并成一份可决策的 Markdown 审计报告。

zack-dev-cm
zack-dev-cm
热度 65.90
最近更新 2026-05-11 17:41:54
分类:安全依赖:代码执行 / 读写文件应用场景:代码审查 / 报告撰写 / 校对润色 / 工作流

安装技能

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

执行命令安装此 skill: npx secure-skills-cli add public-surface-review
Metadata
name
public-surface-review
description
Publish Guard is a public ClawHub pre-release audit skill. Use it when the user says "publish guard", "release audit", "pre-release check", or wants to review a repo, README, SKILL.md, and public metadata before GitHub or ClawHub publish.
version
1.0.5
homepage
https://zack-dev-cm.github.io/
license
MIT-0
user-invocable
true
metadata
{"openclaw":{"homepage":"https://zack-dev-cm.github.io/","skillKey":"public-surface-review","requires":{"anyBins":["python3","python"]}}}

Publish Guard

Search intent: publish guard, public surface review, release audit, pre-release check, clawhub publish audit

Goal

Audit the public surface before release:

  • README
  • SKILL.md
  • agent metadata
  • launch docs in the working tree
  • obvious leak patterns

The output should answer one question clearly: publish now, or fix specific items first.

Use This Skill When

  • the user wants to publish a GitHub repo or ClawHub skill
  • the user wants a public-surface audit before a launch
  • the repo may contain internal launch docs, secret-shaped strings, or operator-only wording
  • the README or SKILL.md feels too insider-heavy or too long
  • the first-run path may be broken, vague, or buried

Quick Start

  1. Scan for obvious leak patterns.
    • python3 {baseDir}/scripts/scan_leaks.py --root <repo> --out <json>
  2. Scan the public surface for audience-fit problems.
    • python3 {baseDir}/scripts/scan_public_surface.py --root <repo> --out <json>
  3. Score the README or primary landing page.
    • python3 {baseDir}/scripts/score_launch_copy.py --readme <repo>/README.md --out <json>
  4. Render one decision-ready audit.
    • python3 {baseDir}/scripts/render_public_audit.py --repo <repo> --leaks <json> --surface <json> --copy <json> --out <md>

Operating Rules

  • Treat README.md, SKILL.md, agents/openai.yaml, and launch docs in the working tree as public.
  • Public copy should describe the user job before it explains the internal theory.
  • A public quick start should appear near the top and should be runnable without hidden context.
  • Keep public default prompts short. Move deeper operating rules into the skill body or scripts.
  • Flag internal launch docs in the repo unless they are intentionally private and excluded from the public package.
  • Prefer a small set of concrete findings over a broad essay.

What To Flag

  • absolute filesystem paths
  • localhost URLs and websocket endpoints
  • token-shaped strings and credential-like URLs
  • missing or buried quick starts
  • giant inventory sections or excessively long SKILL.md files
  • public prompts that read like internal control instructions
  • README intros that compare the repo to five other projects before explaining what it does

Bundled Scripts

  • scripts/scan_leaks.py
    • Search the repo for obvious leak patterns and secret-shaped strings.
  • scripts/scan_public_surface.py
    • Inspect README, SKILL.md, launch docs in the working tree, and public metadata for audience-fit issues.
  • scripts/score_launch_copy.py
    • Produce a simple launch-copy score for the primary README.
  • scripts/render_public_audit.py
    • Merge the JSON outputs into one concise markdown audit.