cold-email
Write cold emails that get replies using proven frameworks (AIDA, PAS, BAB). Enforces best practices like 50-125 word limit and personalized openers.
detect-ai
Analyze text to detect if it was written by AI. Returns a score from 0-100 with detailed metrics. Use when checking content before publishing or submitting.
php-modernization
Use when working with ANY PHP modernization task: upgrading PHP 8.1+, adding strict types, configuring PHPStan/Rector/PHP-CS-Fixer, refactoring to enums/DTOs/readonly, improving type safety, or reviewing PHP code quality. Triggers on: PHP upgrade, modernize, type safety, PHPStan, Rector, PHP-CS-Fixer, enum, DTO, readonly, strict_types.
android
Use when working with Android devices via ADB - connecting devices, running shell commands, installing apps, debugging, taking screenshots, UI automation, viewing logs, analyzing crashes, or exploring system internals. Triggers on "adb", "logcat", "install apk", "debug android", "android device", "shell command", "screenshot", "dumpsys", "crash", "ANR".
android-fastboot
Use for fastboot operations, flashing partitions, bootloader unlocking, recovery mode, or partition management. Triggers on "fastboot", "flash boot.img", "unlock bootloader", "recovery mode", "TWRP", "Magisk", "partition", "sideload", "A/B slots". WARNING - These operations can brick devices if done incorrectly.
lineageos
Use when working with LineageOS custom ROM development, including syncing sources, building, device trees, repopick, Gerrit contributions, or LineageOS-specific features. Triggers on "LineageOS", "lineage-sdk", "breakfast", "brunch", "repopick", "vendor/lineage", "lineage.dependencies", "mka bacon".
android-build
Use when building Android apps (Gradle CLI) or ROMs (AOSP, LineageOS). Triggers on "gradle build", "assemble", "AOSP", "LineageOS", "lunch", "mka", "breakfast", "brunch", "compile android", "device tree", "kernel build".
signup-flow-cro
When the user wants to optimize a signup or registration flow -- including field selection, social auth, single-step vs multi-step forms, or mobile signup. Also use when the user says "signup conversion," "registration form," "reduce signup friction," "signup A/B test," or "signup drop-off." For post-signup onboarding, see product-onboarding. For activation measurement, see activation-metrics.
self-serve-motion
When the user wants to reduce friction in the self-serve buying experience, optimize in-product checkout, remove "contact sales" gates, or design self-serve onboarding and support. Also use when the user says "frictionless," "self-service," "remove sales gates," "no-demo experience," or "friction audit." For signup flow optimization, see signup-flow-cro. For pricing page design, see pricing-strategy.
retention-analysis
When the user wants to analyze, diagnose, or improve user retention -- including cohort analysis, churn prediction, engagement scoring, or resurrection campaigns. Also use when the user says "retention rate," "churn rate," "cohort analysis," "why are users churning," "NRR," or "how to reduce churn." For engagement loops, see engagement-loops. For activation, see activation-metrics.
referral-program
When the user wants to design a referral or affiliate program -- including reward structures, referral mechanics, two-sided incentives, or partner programs. Also use when the user says "refer a friend," "referral reward," "affiliate program," "ambassador program," or "referral ROI." For viral loop design, see viral-loops. For growth loops, see growth-loops.
trial-optimization
When the user wants to optimize free trial conversion -- including trial length, trial type selection, expiry flows, or trial email sequences. Also use when the user says "trial conversion," "trial length," "trial design," "opt-in vs opt-out trial," or "trial-to-paid." For activation, see activation-metrics. For feature gating, see feature-gating.
usage-based-pricing
When the user wants to design or implement usage-based, consumption, or metered pricing -- including credit systems, overage handling, or billing infrastructure. Also use when the user says "pay per use," "metered billing," "credit system," "usage pricing," or "consumption pricing." For broader pricing strategy, see pricing-strategy. For expansion, see expansion-revenue.
user-segmentation
When the user wants to segment users for personalized experiences -- including behavioral cohorts, engagement scoring, churn risk scoring, or ICP refinement. Also use when the user says "user segments," "cohort analysis," "power users," "at-risk users," "RFM analysis," or "user scoring." For product-led sales, see product-led-sales. For retention, see retention-analysis.
viral-loops
When the user wants to design product-driven viral growth -- including invite mechanics, collaboration loops, embedding loops, or network effects. Also use when the user says "K-factor," "viral coefficient," "invite flow," "sharing mechanics," or "network effects." For structured referral programs, see referral-program. For growth loop design, see growth-loops.
product-analytics
When the user wants to set up product analytics -- including event taxonomy, tracking plans, funnel analysis, or tool selection (Mixpanel, Amplitude, PostHog). Also use when the user says "event tracking," "analytics setup," "tracking plan," "analytics implementation," or "user identification." For PLG metrics, see plg-metrics. For experimentation, see growth-experimentation.
pricing-strategy
When the user wants to design or optimize pricing, packaging, or monetization -- including tier structure, freemium design, value metrics, or price research. Also use when the user says "pricing page," "how to price," "freemium vs free trial," "Good-Better-Best tiers," or "value-based pricing." For feature gating, see feature-gating. For trial optimization, see trial-optimization. For usage-based models, see usage-based-pricing.
plg-strategy
When the user wants to assess PLG readiness, design a product-led growth strategy, choose between freemium and free trial, evaluate PLG maturity, or plan a hybrid PLG + sales model. Also use when the user says "should we do PLG," "PLG vs sales-led," "growth motions," "PLG audit," or "go-to-market strategy." For specific mental models, see plg-mental-models. For growth loop design, see growth-loops.
plg-metrics
When the user wants to define PLG metrics, build a growth dashboard, or set KPI targets -- including activation rate, free-to-paid conversion, NRR, or North Star metric. Also use when the user says "PLG dashboard," "growth KPIs," "metric definitions," or "PLG benchmarks." For activation-specific metrics, see activation-metrics. For analytics setup, see product-analytics.
plg-mental-models
When the user needs mental models or frameworks for PLG decisions -- including product-channel fit, time-to-value, network effects, habit loops, or pricing psychology. Also use when the user asks "what framework should I use," "how should I think about this," or references a specific model like "adjacent user theory" or "bowling alley framework." For comprehensive PLG strategy, see plg-strategy. For growth loops, see growth-loops.
plg-ideas
When the user wants PLG ideas, tactics, or inspiration -- a mega-reference of 100+ product-led growth strategies organized by category. Also use when the user says "growth ideas," "PLG playbook," "growth tactics," "what should we try," or "growth brainstorm." For PLG strategy, see plg-strategy. For experimentation, see growth-experimentation.
paywall-upgrade-cro
When the user wants to optimize in-app paywalls, upgrade screens, or upgrade prompts -- including feature locks, usage limit walls, trial expiration screens, or context-triggered upsells. Also use when the user says "paywall design," "upgrade conversion," "upgrade modal," or "upsell prompt." For feature gating strategy, see feature-gating. For in-product messaging, see in-product-messaging.
in-product-messaging
When the user wants to design in-product messages -- including tooltips, banners, modals, slideouts, or notification bells -- without annoying users. Also use when the user says "in-app messages," "product announcements," "nudges," "contextual help," or "message frequency." For upgrade prompts specifically, see paywall-upgrade-cro. For feature launches, see feature-adoption.
growth-modeling
When the user wants to build quantitative growth models -- including loop-based models, sensitivity analysis, revenue forecasting, or unit economics. Also use when the user says "growth forecast," "revenue model," "CAC LTV," "growth projections," or "financial model." For growth loops, see growth-loops. For PLG metrics, see plg-metrics.
growth-loops
When the user wants to design, map, or quantitatively model growth loops -- including viral, content, paid, or sales loops. Also use when the user says "growth flywheel," "compounding growth," "loop modeling," "S-curve sequencing," or "growth engine." For viral-specific loop design, see viral-loops. For quantitative forecasting, see growth-modeling.
growth-experimentation
When the user wants to design, prioritize, or analyze growth experiments -- including A/B tests, hypothesis frameworks, ICE/RICE scoring, or growth sprints. Also use when the user says "A/B test," "experiment design," "growth sprint," "experiment prioritization," or "statistical significance." For analytics setup, see product-analytics. For growth modeling, see growth-modeling.
free-tool-strategy
When the user wants to plan a free tool for acquisition -- including calculators, analyzers, generators, or interactive resources as an engineering-as-marketing strategy. Also use when the user says "free tool," "engineering as marketing," "lead magnet tool," "free calculator," or "SEO tool." For viral growth, see viral-loops. For PLG strategy, see plg-strategy.
feature-adoption
When the user wants to drive adoption of a specific feature -- including launch planning, discovery mechanisms, adoption funnels, or feature deprecation. Also use when the user says "feature launch," "feature rollout," "underused features," "feature stickiness," or "how to get users to use a feature." For in-product messaging, see in-product-messaging. For onboarding, see product-onboarding.
expansion-revenue
When the user wants to grow revenue from existing customers -- including seat expansion, plan upgrades, usage upsells, or cross-sell strategies. Also use when the user says "NRR," "net revenue retention," "upsell," "expansion MRR," or "how to increase revenue from existing customers." For pricing, see pricing-strategy. For upgrade screens, see paywall-upgrade-cro.
engagement-loops
When the user wants to design engagement loops that drive repeated product usage -- including notification strategy, habit formation, or re-engagement triggers. Also use when the user says "DAU/MAU," "habit loop," "trigger action reward," "engagement framework," or "how to bring users back." For retention analysis, see retention-analysis. For feature adoption, see feature-adoption.
activation-metrics
When the user wants to define, measure, or optimize user activation -- including identifying the aha moment, measuring time-to-value, or building an activation funnel. Also use when the user says "activation rate," "aha moment," "setup moment," "habit moment," "time to value," or "how do I measure activation." For onboarding design, see product-onboarding. For retention, see retention-analysis.
product-onboarding
When the user wants to design or improve new user onboarding -- including product tours, checklists, empty states, welcome flows, or progressive disclosure. Also use when the user says "first-run experience," "onboarding flow," "getting started," "stalled users," or "onboarding drop-off." For activation metrics, see activation-metrics. For signup optimization, see signup-flow-cro.
product-led-sales
When the user wants to layer sales onto a PLG motion, build PQL scoring, design sales handoffs from product usage signals, or plan a hybrid PLG + sales model. Also use when the user says "product-led sales," "PQL," "PQA," "when to add sales to PLG," or "enterprise PLG." For broader PLG strategy, see plg-strategy. For expansion revenue, see expansion-revenue.
feature-gating
When the user wants to decide what features to gate vs keep free, design usage limits, implement reverse trials, or plan a free tier. Also use when the user says "what should be free," "feature gate," "paywall placement," "usage limits," or "reverse trial." For pricing strategy, see pricing-strategy. For upgrade screens, see paywall-upgrade-cro.
coordinate
Task-based multi-agent coordination (includes Issue Remediation Loop)
Financial Data Fetcher
Fetches real-time and historical market data, financial news, and fundamental data for trading decisions
debug
Structured bug diagnosis and fix — Root cause analysis, pattern scanning, regression tests
oma-commit
Create git commits following Conventional Commits specification with project-specific branch naming rules. Use for commit message generation, changelog, and versioning.
oma-brainstorm
Design-first ideation that explores user intent, constraints, and approaches before any planning or implementation. Use for brainstorming, ideation, exploring concepts, and evaluating approaches.
backtesting-trading-strategies
|
oma-backend
Backend specialist for APIs, databases, authentication with clean architecture (Repository/Service/Router pattern). Use for API, endpoint, REST, database, server, migration, and auth work.
stock-analysis
Analyze stocks and cryptocurrencies using Yahoo Finance data. Supports portfolio management (create, add, remove assets), crypto analysis (Top 20 by market cap), and periodic performance reports (daily/weekly/monthly/quarterly/yearly). 8 analysis dimensions for stocks, 3 for crypto. Use for stock analysis, portfolio tracking, earnings reactions, or crypto monitoring.
oma-translator
Context-aware translation that preserves tone, style, and natural word order. Use when translating UI strings, documentation, marketing copy, or any multilingual content. Infers register, domain, and style from the source text and surrounding codebase context.
ultrawork
5-phase 17-step Phase Gate orchestration
oma-pm
Product manager that decomposes requirements into actionable tasks with priorities and dependencies. Use for planning, requirements, specification, scope, prioritization, task breakdown, and ISO 21500, ISO 31000, or ISO 38500-aligned planning recommendations.
tools
Show available skills, agents, and their status
stack-set
Auto-detect project tech stack and configure language-specific references
oma-coordination
Guide for coordinating PM, Frontend, Backend, Mobile, and QA agents on complex projects via CLI. Use for manual step-by-step coordination and workflow guidance.
setup
oh-my-agent project setup verification and configuration
review
OWASP security, performance, accessibility, code quality review (includes Fix-Verify Loop)
Page 1046 of 1678 · 83894 results
