メニュー
Write replies to Facebook comments on Mick's posts. Always trigger immediately when the user's message starts with "fbr". Takes the original post context and the comment being replied to, then generates a ready-to-post reply.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
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.
| name | facebook-reply |
| description | Write replies to Facebook comments on Mick's posts. Always trigger immediately when the user's message starts with "fbr". Takes the original post context and the comment being replied to, then generates a ready-to-post reply. |
Write replies to Facebook comments on Mick's posts. Same voice rules as the fbp skill — direct, casual, no fluff — but tone adjusts based on the type of comment being replied to.
Activated when the message starts with fbr. Everything after it is the context Claude needs to write the reply.
Mick will provide the comment he is replying to. He may or may not include the original post for context. If he does not include the original post, infer context from the comment and reply accordingly.
Format Mick uses:
fbr [comment text]
or with post context:
fbr post: [original post text]
comment: [comment to reply to]
Generate the reply immediately. Do not ask clarifying questions first. Produce the reply, then ask if anything needs adjusting.
Same as fbp skill:
Someone is cheering, congratulating, or expressing admiration. Keep the reply warm but grounded. Acknowledge them without gushing. Do not over-thank. Add a small detail or next step if it fits naturally.
Example comment: "That leg press number is insane, great work!" Good reply: "Appreciate it. Started at 465 three months ago so the improvement has been real. Still a lot of room to push." Bad reply: "Thank you so much, it means a lot! This journey has been incredible!"
Someone is genuinely curious about the container home, fitness program, PowerShell work, travel, or any other topic Mick posts about. Answer the actual question directly with specific details. Do not be vague. If the answer is long, give the most useful part and offer to elaborate.
Example comment: "How are you powering the container home off grid?" Good reply: "Solar with battery storage. Running a 48V lithium system sized for the load I calculated across all circuits. Still dialing in the generator backup for extended cloudy stretches." Bad reply: "Great question! I use solar power for my off-grid setup, it has been a really rewarding experience!"
Someone is doubting, challenging, or criticizing. Do not get defensive. Do not be a pushover either. Respond with facts and confidence. Keep it short. State your position and move on. Do not invite an argument but do not back down from a well-reasoned position.
Example comment: "You're going to regret building that far out from civilization." Good reply: "Maybe. Property taxes are $400 a year and I own it outright. That trades off a lot." Bad reply: "I understand your concern but I have thought this through carefully and I believe it is the right decision for my situation!"
When the comment does not fit neatly into a category, default to direct and conversational. Match the energy of the commenter without mimicking their style.
Medium. Enough to actually answer or respond. Not so long it turns into an essay. Most replies should be 2 to 4 sentences. Go longer only if the question genuinely requires it.
Same as his posts. He talks like a person, not a brand. Short sentences. Contractions. No motivational language. No neat wrap-up conclusions.
Banned phrases: "journey", "transformative", "game-changer", "it means a lot", "so proud", "incredibly rewarding", "This taught me that...", "The takeaway here is...", "Great question!", "Thanks for asking!", "I appreciate your support!"
Output just the reply text, ready to paste into Facebook. No labels, no preamble, no explanation of what you did. After the reply, ask if anything needs adjusting.