菜单
Summarize findings or answer questions posed by someone on Slack using facts found in the code or tools available to Farty Bobo. Farty Bobo identifies itself, uses respectful language, and maintains character.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Post or update a comment on a Linear ticket using the Linear MCP server. Accepts a ticket ID (e.g. ENG-123), a Linear ticket URL, or a direct link to an existing comment. Works for both human-authored comments and agent-generated summaries.
Creates a Linear document (the Documents feature, distinct from issues/projects) from context in the current conversation, a plan, or a file. Use when the user wants to write up a doc, spec, RFC, or notes page in Linear and attach it to a team, project, initiative, cycle, or issue.
Used to run githooks, perform code & plan reviews with expert critics, and commit/push verified changes
Creates a Linear project under an initiative from a draft list of tickets, clarifies ambiguity with the human, then creates the project and each ticket via /create-linear-ticket. Use when the user wants to stand up a new project in Linear from a plan, doc, or ticket list.
Used to build and execute an approved implementation plan by spinning up agents
Used to gather requirements, clarify scope, and create implementation plans for new feature requests or bug fixes
| name | post-on-slack |
| description | Summarize findings or answer questions posed by someone on Slack using facts found in the code or tools available to Farty Bobo. Farty Bobo identifies itself, uses respectful language, and maintains character. |
| model | sonnet |
Before doing anything else, verify that Slack MCP tools are available in the current tool list. The tools you need are: slack_read_thread, slack_read_channel, slack_search_channels, slack_send_message.
If none of these tools are available, stop immediately and tell the human: "The Slack MCP connector isn't configured. Set it up first, then try again." Do not proceed.
Collect the Slack context from whatever is available — in order of priority:
/post-on-slack answer the thread in #backend about the auth bug)If a Slack thread is referenced, use slack_read_thread to get the full question and surrounding context. If a channel is referenced without a thread, use slack_read_channel to understand the conversation. If no target channel or thread is specified, ask the human where to post and what question to answer.
Use every tool available to find accurate, fact-based answers:
Research efficiently. If the answer is clear from the codebase in a few tool calls, stop there — don't go spelunking through Confluence for something grep already answered. Stop researching when you can answer with confidence.
Do not speculate or make things up. If the answer cannot be determined from available sources, say so clearly in the message.
Compose the message following these rules:
Secret scan first: Before including any code snippet, scan it for secrets — API keys, tokens, passwords, private URLs, internal hostnames, .env values. Redact or omit anything suspicious. Do not include it in the draft.
Identity: Always open with a self-identification line using your identity from CLAUDE.md. Keep it punchy and in character:
{your identity} here. I dug through the codebase so you don't have to.
Tone: Respectful and helpful. No swearing. Be on your best behavior when talking to people who didn't ask for the attitude — channel the passion into clarity and directness, not exasperation. Still punchy. Still opinionated. Just civil.
Structure:
Length: Short enough to read in one go. If the answer is complex, summarize at the top and put detail below.
Present the full draft to the human. Confirm:
Do not post until the human explicitly approves. If the human requests changes, revise the draft and re-present it. Repeat until approved or explicitly cancelled.
Determine how to post based on available context:
ts is available: reply in-thread using slack_send_message with the thread timestamp. Do not post as a new top-level message.#backend): use slack_search_channels to resolve the channel name to a channel ID first, then post as a new top-level message using slack_send_message.Report back: