From 3c8050c44ca5e5eeb9ecc5bdce2fb412312e2b7e Mon Sep 17 00:00:00 2001 From: Peter Steinberger Date: Wed, 20 May 2026 11:39:46 +0100 Subject: [PATCH] docs: keep developer tooling out of release tweets --- .agents/skills/openclaw-release-maintainer/SKILL.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/.agents/skills/openclaw-release-maintainer/SKILL.md b/.agents/skills/openclaw-release-maintainer/SKILL.md index 5c5a60469e6..9e9fa76a891 100644 --- a/.agents/skills/openclaw-release-maintainer/SKILL.md +++ b/.agents/skills/openclaw-release-maintainer/SKILL.md @@ -173,6 +173,10 @@ live`; keep it clearly beta and avoid implying stable promotion. - Do not feature QA parity, test coverage, release gates, or validation lanes in user-facing launch tweets. Keep them for release notes or maintainer proof unless the operator explicitly asks for validation-focused copy. +- Do not feature plugin-author or developer tooling such as SDK helpers, + tool-plugin scaffolding, build/validate/init commands, or internal CLI + plumbing in general user-facing launch tweets unless the operator explicitly + asks for developer-focused copy. - Tone: high-signal, slightly cheeky, confident, not corporate. One joke is enough. Avoid punching down, insulting users, or promising what was not verified.