Documents

Proof Card Forge

Try it

Create SVG and Markdown trust cards from skill audits or release metadata

What it does

Create SVG and Markdown trust cards from skill audits or release metadata

The skill document

Proof Card Forge

Use this skill when a builder wants a small trust badge that shows a skill was checked before publish.

When To Use

  • A skill audit JSON exists and needs a clean proof card.
  • A GitHub README, landing page, or ClawHub listing needs a visual trust signal.
  • A release needs a stable score, grade, status, and install link in one asset.
  • A builder wants a proof card without hand-editing SVG.

Workflow

  1. Locate the audit JSON from Skill Package Doctor, or collect the skill name, score, grade, and URL.
  2. Run the bundled script:
python3 scripts/proof_card.py \
  --audit skill-doctor.json \
  --out-svg proof-card.svg \
  --out-md proof-card.md \
  --out-json proof-card.json
  1. If there is no audit file, pass --name, --score, --grade, and --url.
  2. If you intentionally replace existing artifacts, add --force.
  3. Review the generated SVG text, score, and link before sharing.
  4. Use the Markdown snippet in GitHub and the raw SVG in landing pages.
  5. Keep the card honest: refresh it after every material skill change.
  6. Read references/source-manifest.json only when you need package provenance.

Review Rules

  • Do not show publish-ready unless the latest audit supports it.
  • Escape all names, descriptions, and links before rendering SVG or Markdown.
  • Keep proof cards small, legible, and embeddable.
  • Use plain labels: score, status, grade, version, and checked date.
  • Link the card to the skill page, release page, or public audit artifact when available.
  • If the score is missing, ask for the audit or mark the status as unchecked.
  • Refuse accidental overwrites unless the user explicitly chooses --force.

Output

Return:

  • proof-card SVG path
  • Markdown badge snippet
  • JSON summary path when generated
  • any missing inputs or honesty warnings
  • suggested placement for README, landing page, and listing

Stop Conditions

Do not create or recommend a proof card when:

  • the audit says do-not-publish
  • the user asks to hide known errors
  • the source score or status cannot be verified and the card would imply a completed audit

Related skills

Skill Package Doctor

Audit skill packages before publishing, then generate concrete fixes and a shareable proof card

11 installs

Skill Vetter V2 0.0.6

Get a structured risk report on a skill package before installing or publishing it.

129 installs

skill-trust-auditor

Audit a named ClawHub skill or skill URL before installation by combining OpenClaw verification with bounded static analysis. Use when the user explicitly asks whether a skill is safe or requests a pre-install review; report evidence and uncertainty instead of treating a score as proof.

39 installs

secure-skill

Scan skills in a project directory for security issues and generate a markdown table report, then install skills from a local registry. Combines static analysis of code and markdown files with supply chain checks. Use when auditing a skills directory, generating a security summary table, or installi

Skill Checker

Audit a target SKILL.md against the Agent Skills specification and generate a Chinese HTML report. Use when the user asks to check, audit, review, or optimiz...

21 installs

SkillHub Publish Auditor

Use when preparing a Skill folder for public release to SkillHub, ClawHub, or another agent-skill marketplace, especially before publishing third-party insta...

5 installs