تشغيل أي مهارة في Manus بنقرة واحدة

release-tweets

النجوم٠

التفرعات٠

آخر تحديث١٢ يوليو ٢٠٢٦ في ٠١:٥٤

Draft, validate, copy, or post concise X/Twitter or Threads release announcements from changelogs, tags, release notes, npm/appcast state, and shipped artifacts.

التثبيت

التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.

تشغيل في Manus

المصدر

2lab-ai

2lab-ai/skills

فتح مستودع GitHub عرض مستودعات المنشئ

تنزيل

تشغيل في Manus

المهن ذات الصلةSOC

استنادا إلى تصنيف SOC المهني

محللو أبحاث السوق ومتخصصو التسويقمهن الأعمال والعمليات المالية·SOC 13-1161

SKILL.md

readonly

name	release-tweets
description	Draft, validate, copy, or post concise X/Twitter or Threads release announcements from changelogs, tags, release notes, npm/appcast state, and shipped artifacts.

Source: https://github.com/steipete/agent-scripts/tree/main/skills/release-tweets (adopted 2026-05-16) 적용 대상: soma/p9 릴리즈 트윗, 블로그 shortform 헤드라인, 텔레그램 알림 카피. Peter의 X 계정 인프라(bird/xurl) 의존성 제거. 카피라이팅 룰만 유지. 한국어 출력 허용.

Release Tweets

Use when 지혁 asks for a release tweet, launch tweet, X/Threads announcement, release thread, changelog-to-tweet rewrite, or social copy for a shipped version. This skill is about release copy, not cutting the release.

Ground The Copy

Verify the release target before writing confident copy:
- read the relevant CHANGELOG.md section or GitHub release notes
- check the tag/release/npm/appcast/artifact state that applies to the project
- distinguish Unreleased, beta/prerelease, stable, hotfix, and correction releases
Do not say a feature shipped only because it is in the top changelog block. Confirm the tag/release/package evidence when available.
Lead with user-visible wins: features, integrations, workflow improvements, install/update reliability, security fixes.
Avoid leading with CI, coverage, validation, refactors, internal migrations, or release mechanics unless that is the actual story.
If evidence is incomplete, say what is unverified and draft with softer wording.

Launch Tweet Shape

One standard tweet under 280 characters (X/Twitter) or 500 자 (Threads).
한국어 트윗: 한글 280자 한도 (X는 한글은 1자=2바이트 카운트 아니라 1자=1자임).
Typical format:
- product + version
- blank line
- 3-4 compact emoji-led feature bullets
- blank line
- one short punchline
- release/changelog URL
Use emoji bullets by default for launch tweets. Pick clear, low-noise emoji that match the feature or product; skip only when the user asks for plain text or the release is incident-style.
Tone: high-signal, compact, confident, a little dry when earned. Not corporate.
One joke max. Let the feature bullets do the work.
Put the release/changelog URL at the end.
Count final raw characters before presenting it as ready to post.

Beta, Hotfix, Correction

Beta/prerelease:
- make beta status explicit
- avoid implying stable promotion
- phrase as "beta N", VERSION-beta.N, or "preview" as appropriate
Hotfix/correction:
- be direct and accountable
- state what slipped, what is fixed, and the new version
- skip jokes unless the user asks for a lighter tone

Threads (X/Twitter thread sense, not Meta Threads)

First agree on the generic launch tweet.
Then write follow-ups one at a time. When 지혁 says next, provide only the next reply.
Each follow-up should focus on one feature or user workflow.
Include a docs/release URL for the specific feature when available.
Avoid repeating the version in every reply when the thread context already has it.
Good follow-up length: 160-220 raw characters. Hard cap: 280.

Posting And Clipboard

Draft by default. Do not post unless 지혁 explicitly asks.
카피 결과를 텔레그램으로 전달: mcp__send-file__send_document 또는 직접 텍스트로 답.
Never invent media. If 지혁 wants media, use an existing release screenshot/asset or generate one via image-gen / nano-banana-pro separately.

Quality Pass

Before final:

Character count under 280 for each tweet (영어) / 500 (Threads).
Exact version string and channel.
Release URL included when requested or expected.
No unverified claims.
No more than 3-4 emoji-led bullets in the launch tweet.
지혁 style: 간결, 직설, 광고 톤 회피.

Examples

soma v0.4.2 released

🧠 Memory restoration on restart fixed
⚡ Codex MCP latency -40%
🔧 bd-verify enforcement
🐛 Context crash at 62% (soma-u63c) closed

Brittle beta, finally less brittle.
https://github.com/icedac/soma/releases/tag/v0.4.2

p9 daily memory update — 2026-05-16

📝 ZETTEL/000_index refreshed
🛠️ cron.yaml: link-summary every 30min
🧹 67 stale bd issues cleared (last spring)

Cleaner queue, faster wake.

릴리즈 깨졌습니다. v0.4.2-beta.1

v0.4.2-beta.2에서 install/update 검증 수정. 태그 재작성 없음, 베타는 그대로 전진.

المزيد من هذا المستودع

نفس المستودع

beautiful-pdf

2lab-ai/skills

Convert markdown to a beautifully designed editorial-style PDF report. Uses Pretendard variable font, Swiss-Coffee + Cool-Blue palette, minimalist-maximalism layout, cover page, table of contents, section dividers, page numbers. Optimized for Korean+English mixed reports. Use when user asks for "report PDF", "보고서 PDF", "아름다운 PDF", "예쁜 PDF", or wants to publish a markdown document as a polished document.

2026-07-120

blog-shortform

2lab-ai/skills

블로그 URL 1개를 받아 60초 9:16 숏폼 영상(mp4)을 자동 생성하는 파이프라인. 한국 블로그 4종(티스토리/네이버/벨로그/브런치)에서 본문·이미지를 추출하고, 2인 대화 대본을 만든 뒤 로컬 fish-tts(soma-voice HTTP)와 GPT Image 2(gpt-image-2)로 음성·이미지를 생성해 Remotion v4로 합성한다. "블로그 URL로 숏폼 만들어줘", "이 글로 릴스 영상 만들어줘", "blog to shortform", "blog-shortform", "blog-url-to-shortform" 같은 요청에서 발동한다.

2026-07-120

cohere-stt

2lab-ai/skills

Speech-to-Text using Cohere Transcribe (2B, Apache 2.0)

2026-07-120

create-cli

2lab-ai/skills

CLI UX/spec: args, flags, help, output, errors, config, dry-run.

2026-07-120

dialogue-archive

2lab-ai/skills

Use when 지혁 asks to record/save/archive a conversation between him and Elon — produces (1) verbatim RAW markdown, (2) cleaned-up EDITED markdown with nothing removed, and (3) a messenger-style HTML blog post. Triggers on "대화 기록해줘", "이거 저장해서 보내줘", "블로그에 올리게 html로", "원문 그대로 + 교정본 + 포스트".

2026-07-120

frontend-design

2lab-ai/skills

Production frontend UI: pages, apps, components, polished non-generic design.

2026-07-120

Release Tweets

Ground The Copy

Verify the release target before writing confident copy:

read the relevant CHANGELOG.md section or GitHub release notes
check the tag/release/npm/appcast/artifact state that applies to the project
distinguish Unreleased, beta/prerelease, stable, hotfix, and correction releases

Do not say a feature shipped only because it is in the top changelog block. Confirm the tag/release/package evidence when available.

Lead with user-visible wins: features, integrations, workflow improvements, install/update reliability, security fixes.

Avoid leading with CI, coverage, validation, refactors, internal migrations, or release mechanics unless that is the actual story.

If evidence is incomplete, say what is unverified and draft with softer wording.

Launch Tweet Shape

One standard tweet under 280 characters (X/Twitter) or 500 자 (Threads).

한국어 트윗: 한글 280자 한도 (X는 한글은 1자=2바이트 카운트 아니라 1자=1자임).

Typical format:

product + version
blank line
3-4 compact emoji-led feature bullets
blank line
one short punchline
release/changelog URL

Use emoji bullets by default for launch tweets. Pick clear, low-noise emoji that match the feature or product; skip only when the user asks for plain text or the release is incident-style.

Tone: high-signal, compact, confident, a little dry when earned. Not corporate.

One joke max. Let the feature bullets do the work.

Put the release/changelog URL at the end.

Count final raw characters before presenting it as ready to post.

Beta, Hotfix, Correction

Beta/prerelease:

make beta status explicit
avoid implying stable promotion
phrase as "beta N", VERSION-beta.N, or "preview" as appropriate

Hotfix/correction:

be direct and accountable
state what slipped, what is fixed, and the new version
skip jokes unless the user asks for a lighter tone

Threads (X/Twitter thread sense, not Meta Threads)

First agree on the generic launch tweet.

Then write follow-ups one at a time. When 지혁 says next, provide only the next reply.

Each follow-up should focus on one feature or user workflow.

Include a docs/release URL for the specific feature when available.

Avoid repeating the version in every reply when the thread context already has it.

Good follow-up length: 160-220 raw characters. Hard cap: 280.

Posting And Clipboard

Draft by default. Do not post unless 지혁 explicitly asks.

카피 결과를 텔레그램으로 전달: mcp__send-file__send_document 또는 직접 텍스트로 답.

Never invent media. If 지혁 wants media, use an existing release screenshot/asset or generate one via image-gen / nano-banana-pro separately.

Quality Pass

Before final:

Character count under 280 for each tweet (영어) / 500 (Threads).

Exact version string and channel.

Release URL included when requested or expected.

No unverified claims.

No more than 3-4 emoji-led bullets in the launch tweet.

지혁 style: 간결, 직설, 광고 톤 회피.

Examples

soma v0.4.2 released 🧠 Memory restoration on restart fixed ⚡ Codex MCP latency -40% 🔧 bd-verify enforcement 🐛 Context crash at 62% (soma-u63c) closed Brittle beta, finally less brittle. https://github.com/icedac/soma/releases/tag/v0.4.2

p9 daily memory update — 2026-05-16 📝 ZETTEL/000_index refreshed 🛠️ cron.yaml: link-summary every 30min 🧹 67 stale bd issues cleared (last spring) Cleaner queue, faster wake.

릴리즈 깨졌습니다. v0.4.2-beta.1 v0.4.2-beta.2에서 install/update 검증 수정. 태그 재작성 없음, 베타는 그대로 전진.