akash-joshi
- 21 skills
- 0 followers
- 2 hours ago last updated
- ▌ Discuss · akash-joshiIdentify 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.
- ▌ Grilling · akash-joshi bundleGrill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases. Covers multi-round decision analysis - external-model question formation, persistent decision logs, devil's-advocate checks, and standing values instruments (values card sort, Moving Motivators).
- ▌ LLM Wiki · akash-joshiBuild and maintain a persistent, compounding knowledge base as interlinked markdown files, based on Andrej Karpathy's LLM Wiki pattern. Unlike RAG (which rediscovers knowledge per query), the wiki compiles knowledge once and keeps it current - cross-references, contradiction flags, and synthesis are already there. Load when the user asks to create/build/start a wiki or knowledge base, ingest a source (URL, PDF, paste) into their wiki, query an existing wiki, or lint/audit/health-check it. Works as an Obsidian vault out of the box (wikilinks, graph view, Dataview).
- ▌ Playwright CLI · akash-joshi bundleAutomate browser interactions, test web pages and work with Playwright tests.
- ▌ Pr Description · akash-joshiWrite or revise a pull request or merge request description, or a commit message body. Load before drafting any PR/MR body, when rewriting one that reads as padded or unclear, and when a reviewer calls a description slop. Covers what to lead with, what to cut, and how to frame severity honestly. For voice (British English, no em-dashes, no bold-heading bullets) load writing-style as well.
- ▌ Voicenotes · akash-joshi bundleSearch, retrieve and create notes in Voicenotes — semantic search, full transcripts, tag/date filtering, and text note creation through natural conversation.
- ▌ Tiger Style Coding · akash-joshiApply 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.
- ▌ Context Engineering · akash-joshiThe new rules of context engineering for Claude 5 generation models. Anthropic removed ~80% of Claude Code's system prompt with no eval loss because judgement replaces rules. Load when writing or auditing system prompts, CLAUDE.md, AGENTS.md, or skills for a modern coding agent; when a prompt or skill feels bloated; when the agent seems to be waffling instead of acting; when you're tempted to add "ALWAYS do X" / "NEVER do Y" rules; or when consolidating scattered instructions into a coherent context tree.
- ▌ Cold Dm · akash-joshiWrite 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.
- ▌ Ship V1 · akash-joshiBuild and ship a first version of a validated startup idea. Use when the user has a validated idea and an entry angle and asks "how do I build this," "what should my MVP be," "how do I ship," "how do I start building," or mentions v1, MVP, or launching. This is the "Heat & Ship" stage of the B.R.O.T.H. framework. For choosing the entry angle first, see market-entry-strategies. For the demand mindset underneath it all, see demand-first-validation.
- ▌ Idea Scoring · akash-joshiScore and rank a shortlist of startup ideas to decide which one to build. Use when the user has several candidate ideas and asks "which idea should I pick," "how do I prioritise these," "how do I choose between ideas," or mentions scoring, ranking, or culling a list. This is the "Order & Cull" stage of the B.R.O.T.H. framework. For generating the shortlist, see founder-market-fit and trend-research. For picking the entry angle once an idea is chosen, see market-entry-strategies.
- ▌ Keyword Search · akash-joshiFind 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.
- ▌ Trend Research · akash-joshiResearch market demand and search traffic to find or validate startup ideas. Use when the user wants to find trends, check search volume, size a market, or asks "how do I research demand," "what's trending," "how big is this market," "how do I find competitors," or mentions tools like Google Trends, Ahrefs, Exploding Topics, or keyword research. This is the "Research Widely" stage of the B.R.O.T.H. framework. For generating the keywords to research, see founder-market-fit. For ranking what you find, see idea-scoring.
- ▌ Content Selling · akash-joshiUse 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.
- ▌ Discovery Calls · akash-joshiRun 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.
- ▌ Prospecting Lists · akash-joshiBuild 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.
- ▌ Founder Market Fit · akash-joshiGenerate candidate startup ideas grounded in the user's own skills, experience, and network. Use when the user asks "what should I build," "how do I find a startup idea," "what business is right for me," or mentions founder-market fit, ikigai, or not knowing where to start. This is the "Begin With Yourself" stage of the B.R.O.T.H. framework. For checking whether the resulting ideas have demand, see demand-first-validation and trend-research.
- ▌ Follow Up Sequences · akash-joshiBuild 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.
- ▌ Profile Optimization · akash-joshiOptimise 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.
- ▌ Demand First Validation · akash-joshiValidate that a startup idea has real market demand before building. Use when the user wants to check if an idea is worth pursuing, is worried a competitor already exists, or asks "is this a good idea," "should I build this," "someone already built my idea," "how do I validate an idea," or "how do I know if there's demand." Covers the demand-first mindset, the four failure modes that kill bootstrapped ideas, and the competitor reality check. For finding ideas from your own background, see founder-market-fit. For researching demand signals, see trend-research.
- ▌ Market Entry Strategies · akash-joshiChoose the angle to enter a proven, competitive market with a startup idea. Use when the user has picked an idea but a competitor already exists, or asks "how do I compete," "how do I differentiate," "someone already does this, what now," or mentions going downmarket, upmarket, or entering an adjacent market. This is the "Tactics Time" stage of the B.R.O.T.H. framework. For validating demand first, see demand-first-validation. For building once the angle is set, see ship-v1.