Skip to content
orbitant-os

orbitant-marketing v1.6.0

· Orbitant Team · v1.6.0
releasemarketing
📦 Release for orbitant-marketing

Adds x-thread, a skill that turns a published blog post or native material into an X thread ready to post. It has been exercised end to end through Mercuria, not only linted: the orchestrator picks it up from the discovered catalogue with no code change on the consumer side, and the draft lands on the Notion review surface as a row of its own.

✨ Features

  • New skill orbitant-x-thread (#49)
- Takes a published blog post or native material — a Knowledge Sharing transcript, a Slack thread, a feature just shipped, a build-in-public moment — and produces an opening post that stands alone, body posts of one idea each, and a closing post, every one annotated with its character count against X's 280 limit

- Written on X's own terms rather than as a variation of another channel: no link in the opening post because links cost reach, the line break as the only formatting because X renders no markdown, and code as an image because indentation is stripped

- No hashtags at all. This is a deliberate deviation from linkedin-post and yt-description, which both make #Orbitant mandatory. Those rules are right for LinkedIn and YouTube, where hashtags still work as category signals, and wrong for X, where they have lost their discovery function. The skill carries a section saying so, to stop anyone aligning it back for consistency. On X the brand appears as the @WeOrbitant mention

- Language follows the source material, and the voice follows the account: the company account writes "we" and never mentions itself, a personal account writes "I" and carries one @WeOrbitant mention in the closing post

- The POST n — c/280 header is a delimiter contract, so a scheduler or an n8n step can split the thread deterministically. A length-based auto-splitter is the wrong tool and the skill says why: it cuts wherever 280 falls and undoes one idea per post

📝 Documentation

  • Fixed two stale spots in .claude/CLAUDE.md (#49)
- The "When Adding a New Skill" steps told you to add the skill path to a skills array in marketplace.json. That array does not exist — the file lists plugins only. The steps now describe the real procedure, including the meta package bump and the fact that the npm vertical version is derived from plugin.json

- The repo-structure line and the Current State row for marketing were still on v1.4.0 and missing already-shipped skills

Full Changelog: orbitant-marketing-v1.5.1...orbitant-marketing-v1.6.0

← Back to Blog