来自 Mihir-Bhargav/OmniSkill 的 Skills

Build an M&A investment case with stress-tested valuation and a narrative that survives board scrutiny — not just a number with a multiple attached.

Run a structured 30-minute angel diligence session that catches the red flags gut feeling reliably misses.

Synthesize turnover data and culture signals to find the root causes of attrition — not the exit survey answers, which are almost always sanitized.

Build a brand positioning framework with competitive differentiation that's actually true, ownable, and impossible for competitors to copy.

Uncover a candidate's actual career priorities and structure an offer that lands — moves beyond resume recitation to the motivations that determine yes or no.

Build a collaborative case formulation that maps the maintaining loop, gives the client a usable map, and makes session work translate to real-world behavior c…

Design a cloud architecture for a specific workload with explicit cost, operational burden, and tradeoff analysis — so you ship the right system, not the fashi…

Diagnose the repeating pattern beneath a leader's stated problem, find the belief driving it, and design a coaching engagement around the shift that changes be…

Craft a personalized 5-touch cold outreach sequence for a specific prospect — forces positioning work that separates 1% reply rates from 3-5%.

Design community guidelines and an enforcement framework that makes moderation decisions consistent, defensible, and 80% faster.

Develop positioning that changes the buyer's economics — not a feature list that's indistinguishable from every competitor's one-pager.

Design a content topic and series targeting a specific buyer stage with pipeline metrics attached — so content investment produces revenue, not just traffic.

Extract real financial and operational risks from a contract and produce a prioritized negotiation brief — so you walk in knowing what to fight for and what to…

Analyze a real estate deal with a stress-tested pro forma that surfaces the assumption that breaks it and enables a fast, defensible yes/no.

Convert raw user research into an actionable design brief that forces signal from noise and drives product priority decisions.

Scope a consulting engagement from initial conversation to proposal-ready SOW, with scope creep and unprofitable assumptions killed before signing.

Build a technical strategy and multi-quarter roadmap that translates tech debt into product velocity cost — so it actually gets funded.

Transform a raw recorded episode into a structured show asset with narrative momentum, chapter markers, and the one moment that drives shares.

Synthesize a week of cross-functional inputs into a 2-page CEO brief — surfaces real issues and stuck decisions, not status theater.

Diagnose why a team member is underperforming and structure a conversation that produces behavioral change — not defensiveness, not vague discomfort.

Build a forecast that documents key assumptions, stress-tests them, and surfaces what must be true — so the model survives board scrutiny instead of collapsing…

Writes an Architecture Decision Record — captures the decision, the context, the alternatives, and the consequences.

Designs an API with explicit decisions on contracts, versioning, errors, and the mistakes that are hard to undo.

Audits a diff or change for everything that could break callers, dependents, consumers, or existing data.

Reviews code systematically — logic, security, performance, edge cases, and maintainability.

Reviews a database migration for safety — data loss risk, lock contention, rollback path, and deployment order.

Audits project dependencies for security vulnerabilities, abandonment, and hidden upgrade risk.

Designs a feature flag rollout plan — targeting, graduation criteria, and the cleanup you'll actually do.

Turns an incident into a structured postmortem that finds the real cause and prevents recurrence.

Writes the onboarding documentation a new engineer actually needs to be productive — not a list of tools to install.

Finds the performance problems in code that will only appear at scale — before they appear in production.

Writes a PR description that actually tells reviewers what changed, why, and what to watch out for.

Produces a structured plan for refactoring a file, module, or system before touching a line of code.

Writes release notes that tell users what changed and why they should care — not a git log summary.

Goes beyond finding bugs — produces a hardening plan that raises the baseline security posture of a system.

Audits a codebase area for tech debt, prioritises it by real cost, and produces a paydown plan.

Identifies the test cases that are missing and would actually catch real bugs — not just increase coverage numbers.

Identify the true conversion bottleneck and design an experiment that addresses root cause — the difference between a 2% button-color lift and a 10x funnel fix.

Run a customer health diagnostic that surfaces churn risk 90 days before renewal — so you're saving accounts, not watching them leave.

Identify the assumption that kills your idea if wrong, design 3-4 tests that produce real signal, and build a 2-week go/no-go playbook — before writing a line …

Synthesize diligence on a startup into a go/no-go investment memo — forces the uncomfortable questions that separate conviction from vibes.

Mid-build health check — tells you what's working, what's silently broken, and whether it's safe to keep building.

Refactors the codebase before it gets too messy for Lovable to work with effectively.

Generates an Awwwards-level Lovable prompt — the exact ingredients that separate a stunning website from a generic AI-generated one.

Turns your app idea into a structured plan before you write your first Lovable prompt.

Rewrites what you want to say into a precise, safe Lovable prompt that won't break what's working.

Audits your Lovable app for the security vulnerabilities that vibe-coded apps almost always ship with.

Pre-ship checklist — finds everything that would embarrass you when real users try your app.