skill releaser

Security Community v1.5.0

Skill notes

When to Use

User says "release {skill}" or "publish {skill} to clawhub" User says "prepare {skill} for release" or "check release readiness" User says "review {skill} for publication" Cron-triggered release check during refactory pipeline

Assumptions

How OpenClaw and user interact during release: Agent runs on a machine with shell access (exec tool) for git and CLI operations User communicates via messaging channel (Telegram, Discord, Signal, etc.) — likely on a phone User reviews the private GitHub repo directly in their browser/phone — the repo IS the review artifact, not a text summary User approves or rejects by replying to the agent's message (natural language: "approve", "revise: fix the readme", "reject")

Prerequisites

gh CLI authenticated (for repo creation and visibility changes) clawhub CLI installed (for ClawhHub publishing) A skill directory with at least a SKILL.md file

Scope & Boundaries

This skill handles: The full release pipeline — structure scaffolding, OPSEC scanning, review, publishing. This skill does NOT handle: Skill content creation or design. The SKILL.md must already describe what the skill does. Everything else (boilerplate, structure, scaffolding) is this pipeline's job. A user with a finished SKILL.md should be able to say "release this skill" and this skill handles everything from there — including generating all missing structure files.

Automation Model

The pipeline has two fully automated phases separated by one human gate. Both single and batch releases follow the same model.

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Security
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
92 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@LeoYeAI · v1.5.0 · no license declared
Token usage
Heavy
Setup complexity
Guided setup
External API key
Not required
Operating systems
macOS · Linux · Windows
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
  • Shell exec
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview skill-releaser.preview
# OPSEC Scan Output

{paste scan output}

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.