Launch asset · ProductHunt-ready

ProductHunt launch pack for Agent Skill Safety Kit.

A copy-ready packet for launching the free Agent Skill Safety Kit on ProductHunt or similar maker directories once an authorized account/session is available.

Open the free kit →Free scorecard →Validator →Markdown version →

Launch guardrail

Do not launch from this cron environment unless an authorized ProductHunt account/session is available. This is public, account-bound distribution. The packet exists so Pepe or a future authenticated Jarvis session can launch cleanly without rewriting positioning.

Product fields

Short description

Agent Skill Safety Kit helps builders and teams review reusable AI-agent skills before giving them browser, file, SaaS, memory, customer, or external-action authority. It includes a free scorecard, permission manifest template/schema, browser-local validator, vendor questionnaire, sample mini-report, and marketplace safety checklist.

Maker comment

Agent skills are starting to behave like software dependencies. The problem: most reusable skills are distributed as instructions, but the real risk is authority. What can the skill read? What can it write? Which tools can it call? Can it persist memory? What receipt does it leave? How does it fail safely? I built Agent Skill Safety Kit as a practical review layer before install, sale, listing, or delegation. What is included: - a free 100-point browser-local scorecard - a permission manifest template + JSON schema - a browser-local manifest validator - a vendor / marketplace questionnaire - a sample safety mini-report - a buyer due-diligence checklist - a GitHub-ready repo package and downloadable ZIP It is built for OpenClaw, Claude Code, Hermes, Codex-style agents, browser agents, and internal skill registries. The goal is simple: before a skill crosses a trust boundary, make its permissions, memory behavior, receipts, exceptions, evals, and rollback gaps visible. Would love feedback from agent builders, marketplace operators, and teams installing third-party skills.

Gallery order

1. Hero / promise

preview-01.svg

2. Scorecard dimensions

preview-02.svg

3. Permission manifest

preview-03.svg

4. Sample verdict

preview-04.svg

Launch checklist

  1. Confirm authorized ProductHunt account/session.
  2. Use the free kit URL as the primary website.
  3. Use the tagline exactly.
  4. Upload the four preview SVGs/screenshots in order.
  5. Paste the maker comment.
  6. Choose Developer Tools + AI + Security where available.
  7. Do not lead with the $29 mini-report; keep it optional.
  8. After launch, record URL in money-track.md and directory/social-proof copy.

Reply snippets

What problem does this solve?

Agent skills are becoming packages, but most teams only inspect the prompt. The kit reviews the authority layer: tools, data, memory, receipts, exception behavior, evals, and rollback.

Is it only for OpenClaw?

No. OpenClaw is one fit, but the checklist works for Claude Code, Hermes, Codex-style agents, browser agents, and internal skill registries. The core question is runtime-independent: what authority does this skill get?

Why a permission manifest?

Because “this skill helps with CRM enrichment” is not enough. A manifest says exactly what the skill may read, write, call, remember, and prove before it runs.