agent-skills

Apply TigerBeetle's Tiger-Style rules to any codebase. Load when writing, reviewing, or refactoring code — or when instructing AI coding agents (Claude Code, Codex, subagents) on style. Enforces safety > performance > developer experience priority order, function-length caps, runtime assertions, bounded loops, and dependency discipline. Works across TypeScript, JavaScript, Python, Go, Rust, and any language with runtime assertions.

Write cold DMs on Twitter/X, LinkedIn, and Telegram that get replies. Use when the user wants to write outreach messages, cold DMs, prospecting messages, or direct messages to potential clients. Also use when the user mentions "cold outreach," "DM script," "outreach template," "how to reach out," "nobody's replying," or "write a DM." Covers message structure, personalisation, platform-specific formatting, and volume targets. For finding prospects to DM, see keyword-search. For what to do after the first message, see follow-up-sequences. For handling the call after they reply, see discovery-calls.

Use content to attract inbound clients without direct selling. Use when the user wants to build a content strategy for client acquisition, create "show don't tell" content, build in public, or use social media for lead generation. Also use when the user mentions "content marketing," "build in public," "inbound leads," "show my work," "social selling," "posting strategy," or "content for clients." This is the long-term compounding play — layer it on top of outreach once you have recurring revenue. For direct outreach, see cold-dm. For profile setup, see profile-optimization.

Run discovery calls that close deals. Use when the user has a call booked with a prospect and needs to prepare, or wants to improve their close rate. Also use when the user mentions "discovery call," "sales call," "client call," "how to close," "call prep," "pricing conversation," or "they want to get on a call." The goal of a discovery call is to understand the problem deeply, show relevant proof, propose a clear scope, and close. For getting to the call, see cold-dm and follow-up-sequences.

Build multi-channel follow-up sequences that close deals. Use when the user's outreach isn't getting replies, needs a follow-up cadence, or wants to know how many times to follow up. Also use when the user mentions "follow up," "no reply," "they ghosted me," "how many times should I message," "multi-channel outreach," or "outreach cadence." Most deals close on the 3rd-5th touch, not the first. For writing the initial DM, see cold-dm.

Find people actively looking for your service right now using platform search. Use when the user wants to find clients on Twitter/X, LinkedIn, or Telegram by searching for hiring posts, help requests, or project announcements. Also use when the user mentions "find clients," "keyword search," "who's hiring," "looking for leads," "find prospects on Twitter," or "social selling." This is the fastest path to first clients — you're finding people who already need help today. For writing the outreach message after finding them, see cold-dm. For building prospect lists from directories and databases, see prospecting-lists.

Optimise your social profiles to convert visitors into clients. Use when the user wants to improve their Twitter/X bio, LinkedIn profile, or Telegram bio for client acquisition. Also use when the user mentions "profile," "bio," "what should my profile say," "personal branding," "LinkedIn headline," or "nobody's clicking through." Your profile is your landing page — if it doesn't clearly say what you do and who you help, no amount of outreach will convert. For writing the outreach itself, see cold-dm.

Build qualified prospect lists from directories, databases, and community research. Use when the user wants to build a target list of potential clients beyond real-time keyword search. Also use when the user mentions "prospect list," "lead list," "ICP," "ideal client profile," "target accounts," "who should I reach out to," or "build a list." This is systematic list-building — different from the real-time keyword-search skill. For writing outreach after building the list, see cold-dm.

Identify gray areas in proposed work and capture decisions before planning. Use at the start of a new feature or piece of work to clarify HOW (not what) to build — surface implementation choices the user cares about, walk through them with concrete options, and produce a context file that plan mode or downstream agents can consume. Lightweight extraction of gsd-discuss-phase, no .planning/ scaffold required.