--- name: unified_hand_posted_pack title: "Unified Hand-Posted Pack" description: "Corrects social publishing for pieces the user posts by hand, producing one identical post that works on X, LinkedIn and Threads instead of separate per-channel blocks." version: 1.0.0 author: Script Master Labs LLC license: MIT source: https://scriptmasterlabs.com/hive402-skills/unified_hand_posted_pack/SKILL.md registry: HIVE402 Skills (https://scriptmasterlabs.com/hive402-skills) --- # Unified Hand-Posted Pack ## When this correction applies - Apply this correction whenever the user will post a piece by hand to X, LinkedIn and Threads himself. - Keep the base skill unchanged for channels the agent posts automatically, since those routes keep their native formats and approvals. - Treat any older instruction to adapt a hand-posted piece into a separate version per network as superseded for this case. ## Build one post for all three networks - Write one single post that works identically on X, LinkedIn and Threads, so the user copies one text and posts it three times. - Open with the hook and put the answer in the first two sentences, led by the first-party number the piece is built on. - Add the canonical link once with utm_source=social on it. - Bake the tags into the post itself, with hashtags and mentions always present and cashtags where they genuinely fit the product. - Keep the post at or under 280 effective characters, counting the URL as 23 characters. - Ship every pack with a cover image or a video, because a text-only pack is incomplete under the standing cover rule. ## Apply the LinkedIn tag exception - Run a pack on LinkedIn with its honest tag set when it fails only the cashtag floor, because the tag floor is waived on LinkedIn only. - Keep the tag floor hard on X and Threads, where a pack below the floor still fails the pre-delivery check. - Never use the LinkedIn waiver to excuse a missing cover, a missing canonical link or a missing comparison to your own comparable product in the body. ## Check the post before delivery - Count the effective characters with the URL counted as 23 before the post leaves your hands. - Read the finished post text and confirm the hashtags, mentions and fitting cashtags are actually in it, not just planned. - Fix a post that fails either check before delivery instead of handing the user a pack he has to repair. ## Deliver it in the unified shape - Deliver a short brief that says what the piece is, where it goes and why, then one copy-paste code block holding the single post. - Never deliver separate X, LinkedIn and Threads blocks for a hand-posted piece, and never split it into a multi-post thread. - Convert older queued packs to this format before handing them over, and name any stale-format files you leave behind instead of passing them off as ready. ## Alternatives for better results - Shrink the supporting line before touching the hook, the first-party number or the tags when a draft runs over the character limit. - Reuse the same unified text for the launch post a scheduled piece hands to the user when it ships, so no second format is created downstream. --- ## From Script Master Labs This skill is listed in [HIVE402 Skills](https://scriptmasterlabs.com/hive402-skills) — every skill there passed a verification gate before listing: parsed, safety-scanned, provenance recorded, self-contained. Skills, probed before listed. Script Master Labs also runs [HIVE402](https://hive402.scriptmasterlabs.com), the payability-probed catalog of 132 paid agent APIs, [OMNIGATE](https://scriptmasterlabs.com/omnigate-facilitator), the x402 gateway those payments settle through, and the free [x402 Starter Kit](https://scriptmasterlabs.com/x402-kit).