菜单
Write replies to Facebook comments on Mick's posts. Trigger on requests to reply to a Facebook comment, especially when the user starts with `fbr`.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Extract trip logistics from pasted travel emails, booking confirmations, forwarded messages, reservation notes, or raw itinerary text and generate one polished, self-contained offline HTML itinerary file for sharing with family or other travelers. Trigger when the user asks to turn trip emails into an HTML itinerary, travel handoff page, shareable trip page, family trip summary, booking-reference page, or offline travel document.
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.
Write or draft a blog post for Mick's IT blog at mickitblog.blogspot.com. Trigger when Mick asks for a blog post or wants to document a technical solution, project, or finding in post format. Match Mick's writing style with plain first-person prose, practical focus, honest status notes, code blocks where relevant, and GitHub links when applicable.
Convert a finished blog post into three ready-to-post social media versions in one pass for Facebook, X, and LinkedIn. Always trigger immediately when the user's message starts with "bts". Also trigger on "blog to social", "social posts for this", "promote this post", or when the user pastes or links a blog post and asks to share it, promote it, or turn it into social content.
Answer questions, assist with planning, and help with design decisions for Mick's off-grid shipping container lake home project. Trigger when the user mentions the container home, lake home, Stewart County, LBL, the expansion, solar system, septic permitting, or retirement property.
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", or asks what cryptos just launched or are launching soon. Always verify current listings data before responding; never answer from memory.
| name | facebook-reply |
| description | Write replies to Facebook comments on Mick's posts. Trigger on requests to reply to a Facebook comment, especially when the user starts with `fbr`. |
| version | 1.2.0 |
Write practical Facebook replies that match Mick's tone and respond to the actual comment context.
Write replies to Facebook comments in Mick's direct, casual voice. Adjust the tone based on the comment type, sentiment, reply goal, and the context of the original post.
fbrfbr as the reply context.Great question! or Thanks for asking!Infer one of these modes unless the user explicitly asks for a different one:
appreciative: supportive comments, encouragement, or praiseclarifying: direct questions, confusion, or requests for more detailhumorous: light friendly comments where a short joke or playful line fits naturallyboundary setting: criticism, bad-faith pokes, repeated off-topic comments, or replies that need a clean limitappreciative: warm but grounded. Thank them without overdoing it.clarifying: answer directly and keep the explanation tight.humorous: keep it dry or light. Do not get corny.boundary setting: stay calm, clear, and brief. Do not escalate.Infer one of these unless the user asks for a specific depth:
concise: 1 to 2 short sentencesfuller: 2 to 4 short sentencesUse concise for quick praise, obvious answers, or mild pushback. Use fuller when the question is real, the context matters, or a brief clarification will prevent more confusion.
Classify the incoming comment before writing the reply:
supportiveneutralskepticalcriticaloff topichostileUse the tag to decide how much warmth, detail, humor, or distance the reply should carry. Do not echo hostility back.
Mick's replies should sound like a person, not a brand. Short sentences. Contractions. No motivational language. No canned gratitude phrases.
Avoid phrases such as:
journeytransformativegame-changerit means a lotso proudincredibly rewardingThis taught me thatThe takeaway here isGreat question!Thanks for asking!I appreciate your support!When context is available, account for:
Use that context to make the reply feel like part of the real conversation instead of a generic standalone answer.
For skepticism, criticism, and off-topic comments:
If the user provides multiple comments from the same post:
If several comments are repeating the same question or misunderstanding:
When the conversation should move somewhere more useful than the comment thread:
move to DM: when the answer needs personal detail, back and forth, or anything not worth airing publicly. Close with a natural invitation such as offering to message them directly, not a canned "DM me".point to the blog: when a post already answers the question in depth. Give the one-line answer first, then mention the writeup exists. Never reply with only a link.tease a follow-up post: when the question deserves a full post. Answer briefly and note that a longer update is coming. Only do this when the user actually plans one.Default to answering in place. Use a CTA only when staying in the thread would shortchange the answer.
When the comment is high stakes (public criticism, a sensitive topic, a person who matters to Mick) or the user asks for options, return 2 to 3 distinct replies that take genuinely different approaches, such as direct answer, brief boundary, or warm redirect. Label them simply and note in one short line when one option carries more risk. Otherwise return a single reply as usual.
If Mick has already replied once in the thread and the commenter responded again:
Reply 1, Reply 2, and Pinned reply when neededSupportive 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.
Question:
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.
Pushback:
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.
Output only the reply text, ready to paste into Facebook. No labels, no explanation, and no extra commentary around the reply.
If the user is not sure how to use this skill, asks what it needs, or asks for examples:
Minimum useful input:
Example prompts:
Use facebook-reply to answer this comment in a friendly but direct way.Write three reply options to this Facebook comment, one warm, one short, and one more technical.Show me how to use this skill when I have a full thread and need several replies.