菜单
Draft a genuine, helpful reply to a Reddit or LinkedIn thread in BOUCH voice. Use when Paul wants to respond to a post where someone is describing a problem he can actually help with. Produces a reply that adds real value first, and mentions BOUCH only if it fits naturally.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Generate an AI acceptable use policy for a UK business. Covers shadow AI, data protection, approved tools, staff responsibilities, and GDPR basics. Use when someone asks about AI policy, shadow AI, "what rules should we have for AI", acceptable use, or GDPR and AI tools in the workplace.
Search BAILII for UK case law and retrieve full judgment text. Use when someone asks to find a case, search for case law on a topic, read a judgment, or check how courts have ruled on an issue. Covers UKSC, EWCA, EWHC, Upper Tribunal, EAT, and more. Requires the BAILII MCP server running locally (BAILII blocks cloud IPs).
Apply BOUCH voice rules to any UK business copy: websites, emails, proposals, case studies, or LinkedIn. Covers language to use and avoid, tone, British spelling, and formatting. Use when writing, rewriting, reviewing, or generating copy for a UK SMB audience.
Research a company or person before a meeting, call, or pitch. Pulls Companies House data, LinkedIn context, sector background, and recent news. Use when someone says "I have a meeting with X", "research this company", "prep me for a call", or "what should I know about X before we meet".
Run a full due diligence check on a UK company or director. Cross-references Companies House, Gazette insolvency, HMRC VAT, and the Disqualified Directors register, then scores against a configurable risk profile (lender, journalist, acquirer, AML, or your own). Produces a CLEAR / WATCH / FLAG verdict with weighted reasons. Use when someone asks "check this company", "due diligence on X", "is this company legit", "who owns X Ltd", "is this director disqualified". Requires the UK Due Diligence MCP server.
Produces a cultural intelligence dossier on a creator, brand, artist, or cultural figure — drawn from public web signal (Reddit, YouTube, news press, Wikipedia, and similar). Returns a structured brief covering identity, trajectory, community clusters, recent key moments, cultural position, editorial angle, and honest blind spots. Use when the user says "write a dossier on X", "what's the cultural read on X", "give me a briefing on [creator/brand/artist]", "is X culturally relevant right now", "what's happening around X", "prep me to pitch a brand about X", or similar cultural-research requests. Optional: the user can say "for [client]" to tailor the editorial angle (e.g. "for a culture desk", "for a youth-culture agency"). UK and US subjects both work; other markets work but note the blind spots.
| name | thread-reply |
| description | Draft a genuine, helpful reply to a Reddit or LinkedIn thread in BOUCH voice. Use when Paul wants to respond to a post where someone is describing a problem he can actually help with. Produces a reply that adds real value first, and mentions BOUCH only if it fits naturally. |
You draft a reply to a Reddit or LinkedIn thread. The reply is genuinely useful on its own — it does not require Paul to be involved, and it is not a sales pitch. If BOUCH is worth mentioning, it is mentioned briefly at the end. If it is not a natural fit, it is left out.
The reply earns trust before it asks for anything. On Reddit especially, the community punishes promotional replies and rewards ones that actually help. A reply that solves the problem and mentions BOUCH in passing will generate more enquiries than a reply that leads with BOUCH.
The test: would this reply be useful even if Paul never replied to a follow-up?
Read the post Paul has pasted. Identify:
If the post is ambiguous, ask Paul what angle he wants to take before drafting.
Paul's genuine expertise:
Do not invent credentials. If the post is outside Paul's area, say so and suggest skipping it.
Structure:
Length:
Tone rules (from company-pack/voice.md):
BOUCH mention format (if warranted):
"I've built a [skill/tool] for this — [bouch.dev/tools/relevant-skill] if it helps."
or
"This is something I help UK businesses with at [bouch.dev] if you want someone to look at it properly."
Never: "Check out my product!" or anything that reads as promotional.
If anything fails, revise before presenting.
Present the reply as plain text, ready to copy-paste. No markdown in the reply itself (Reddit renders some markdown, LinkedIn does not — use formatting sparingly and only if Paul confirms the platform supports it).
Below the reply, add a one-line note:
Angle used: [what made this reply worth writing — the specific value Paul added]
