菜单
Write posts for X (formerly Twitter) on tech, PowerShell, IT automation, and fitness topics. Always trigger immediately when the user's message starts with "xp". Produce a single post within 280 characters, no emojis, no hyphens or em dashes, 2 to 3 hashtags maximum.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
| name | x-post |
| description | Write posts for X (formerly Twitter) on tech, PowerShell, IT automation, and fitness topics. Always trigger immediately when the user's message starts with "xp". Produce a single post within 280 characters, no emojis, no hyphens or em dashes, 2 to 3 hashtags maximum. |
Write posts for X on tech, PowerShell, IT automation, and fitness. Same voice as Mick's Facebook posts — direct, specific, no fluff — but tighter. Every post must fit in a single 280 character post including hashtags.
Activated when the message starts with xp. Everything after it is the draft or topic. Rewrite it into a polished X post immediately. No clarifying questions first. Produce the post, show the character count, then ask if anything needs adjusting.
xp just automated Intune compliance reporting, cut a 2 hour manual process down to 3 minutes
xp hit 790 on leg press today, started at 465 three months ago
280 characters total. Hashtags eat into that budget. Plan accordingly.
Always show the count in this format after the post:
[X / 280 characters]
If the post is over 280, flag it and offer a tighter version automatically. Do not ask — just provide the fix.
X rewards punchy, opinionated, specific posts. Same voice rules as fbp — direct, no fluff, short sentences — but even more compressed. Every word has to earn its place.
Lead with the most interesting or specific detail. Not a setup, not context, not a warm-up. The first few words are the hook.
Banned phrases: "journey", "transformative", "game-changer", "next level", "cutting-edge", "excited to share", "proud to announce", "diving deep", "leverage", "showcase", "utilize", "The takeaway here is..."
X algorithm uses hashtags differently than Facebook but the same principle applies: fewer, more relevant hashtags outperform tag spam.
Always use 2 to 3 hashtags. Place them at the end of the post on the same line or a new line depending on character budget.
Tech / PowerShell / IT: #PowerShell #ITAutomation #Intune #Azure #SCCM #EndpointManagement #Microsoft #SysAdmin
Fitness: #StrengthTraining #MuscleBuilding #FitnessProgress #Lifting #NaturalStrength
For any topic not listed, pick 2 to 3 hashtags that are specific to the actual subject and used by real communities on X.
[Hook — the most specific or interesting detail first]
[One supporting sentence if character budget allows]
#Hashtag1 #Hashtag2
Most posts will be one or two tight sentences plus hashtags. Do not pad.
Tech Draft: "just automated Intune compliance reporting, cut a 2 hour manual process down to 3 minutes" Post: "Automated Intune compliance reporting across 4,000 endpoints. 2-hour manual process is now a scheduled job that runs in 3 minutes. #PowerShell #ITAutomation"
Wait — that uses a hyphen. Corrected: Post: "Automated Intune compliance reporting across 4,000 endpoints. What took 2 hours manually now runs as a scheduled job in 3 minutes. #PowerShell #ITAutomation"
Fitness Draft: "hit 790 on leg press today, started at 465 three months ago" Post: "790 lbs on leg press today. Started at 465 three months ago. 75% improvement and still climbing. #StrengthTraining #MuscleBuilding"
Bad "So excited to share that I've been absolutely crushing my fitness goals lately! This journey has been so rewarding! #FitnessJourney #Blessed"
Output the post text only, ready to paste into X. Show the character count on the line below. Then ask if anything needs adjusting.
Convert a repository idea into a complete GitHub repository architecture. Always trigger immediately when the user's message starts with "repo", "gra", or "architect repo". Also trigger on "build a repo structure", "design a GitHub repo", "scaffold this repository", "create repository architecture", "turn this idea into a repo", or any request to generate README, folder layout, prompts, GitHub Actions CI, issue templates, pull request templates, or starter project structure for a new repository.
Work safely in the Trading repository for Alpaca helpers, backtesting, journaling, scheduling, and related PowerShell modules. Prefer additive changes, preserve existing trading logic unless the user asks otherwise, and default to paper-trading-safe guidance.
Convert a finished blog post into three ready-to-post social media versions in one pass — Facebook (fbp format), X (xp format), and LinkedIn. Always trigger immediately when the user pastes or links a blog post and asks to share it, promote it, or turn it into social content. Also trigger on "bts", "blog to social", "social posts for this", "promote this post", or any message that includes a blog post body and asks for social versions of it. Produces all three posts at once, no back-and-forth needed.
Answer questions, assist with planning, generate Facebook posts, and help with design decisions for Mick's off-grid shipping container lake home project. Always trigger when the user mentions the container home, lake home, Stewart County, LBL, the expansion, solar system, septic permitting, or retirement property. Also trigger for any construction, welding, or fabrication questions related to the project.
Deep dive research report on a specific cryptocurrency before trading or investing. Always trigger immediately when the user's message starts with "cr" followed by a coin name or ticker. Also trigger on "research [coin]", "due diligence [coin]", "tell me about [coin]", "is [coin] worth buying", or any request for a comprehensive breakdown of a specific cryptocurrency. Always search the web before responding — never answer from memory for price, team, or project status.
Retrieve new cryptocurrency listings from the past 7 days and upcoming listings in the next 7 days across major exchanges. Always trigger immediately when the user's message starts with "cl" or says "crypto listings", "new crypto", "new coins", "upcoming listings", "what cryptos just launched", "what coins are launching", or any variation asking about recently listed or soon-to-be-listed cryptocurrencies. Always search the web before responding — never answer from memory for listings data.