メニュー
Use when new RAPS features ship and LinkedIn content is needed — adds posts to the raps-smm post bank following established tone, format, and hashtag conventions.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use when adding a new MCP tool to the RAPS MCP server — covers tool schema definition, handler implementation, dispatch registration, and the client accessor pattern.
Use when adding a new CLI command or subcommand to RAPS — covers the clap struct pattern, module wiring, output formatting, and test structure across the 10-crate workspace.
Use when bumping the RAPS version for a new release — updates Cargo.toml workspace version, 9 internal crate dependencies, 6 npm package.json files, creates git tag, and triggers the release workflow.
Use when adding or updating CI/CD integrations in the raps-actions repo — GitHub Actions composite actions, GitLab CI include templates, test workflows, and floating tag management.
Use before releases or after dependency updates to run security checks — cargo-audit, ASVS compliance matrix review, clippy security lints, redaction pattern verification.
Use when you need to create a shortened URL at go.rapscli.xyz — for long Cloudflare OAuth links, wrangler login URLs, or any URL that's unwieldy in the terminal.
| name | composing-raps-linkedin-posts |
| version | 1.0 |
| description | Use when new RAPS features ship and LinkedIn content is needed — adds posts to the raps-smm post bank following established tone, format, and hashtag conventions. |
Add LinkedIn posts to the raps-smm post bank for new features and releases.
Repo: /root/github/raps/raps-smm
File: content/linkedin/post-bank.md
Posts are numbered sequentially and wrapped in fenced code blocks:
### Post N: Title
` ` `
Post body here.
Lines starting with -> are bullet points.
-> First point
-> Second point
Question at the end for engagement?
#Tag1 #Tag2 #Tag3 #Tag4
` ` `
**firstComment:** github.com/dmytro-yemelianov/raps
The firstComment line (outside the code block) is optional — use for link-heavy posts to avoid LinkedIn's algorithm penalty.
Posts are organized under themed H2 headers:
| Section | Content |
|---|---|
| Launch & Announcements | Major version launches |
| Educational Content | OAuth, CI/CD, DA tutorials |
| Quick Tips & Engagement | Short tips, polls |
| Tutorials & How-To | Step-by-step guides |
| MCP & AI Integration | MCP tools, AI workflows |
| Data-Driven Posts | Research-backed insights |
| New Feature Posts | Per-version feature highlights |
- or *).| Category | Tags |
|---|---|
| Primary | #AutodeskPlatformServices #APS #Automation |
| DevOps | #CICD #DevOps #GitHubActions #GitLabCI |
| AEC | #BIM #AEC #DigitalConstruction |
| Tech | #Rust #CLI #OpenSource |
| AI/MCP | #AI #MCP #ClaudeAI #CursorIDE #VibeCoding |
| Personal | #BuildInPublic #SoftwareDevelopment |
Always use 3-5 total. Mix primary + specific category.
Update the version reference at the top of the file when stats change:
> **Source of truth:** Feature counts reference [`raps/MANIFEST.md`](...) (v4.16.0: 95+ commands, 101 MCP tools, 10 crates, 7 modes).