vultr/openclaw
1
0
Fork 0
mirror of https://github.com/openclaw/openclaw.git synced 2026-05-21 02:34:54 +00:00
Code Issues Packages Projects Releases Wiki Activity

docs: keep developer tooling out of release tweets

Browse Source
This commit is contained in:
Peter Steinberger
2026-05-20 11:39:46 +01:00
parent 45930457ca
commit 3c8050c44c
1 changed files with 4 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

4
.agents/skills/openclaw-release-maintainer/SKILL.md
View File

@@ -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.