Loading...
Loading...
Found 10,837 Skills
Your startup isn't just your team - it's an ecosystem of people who have a stake in your success. Investors, board members, advisors, partners, vendors. Each group has different needs, different communication rhythms, and different expectations. Get it wrong, and you lose credibility. Get it right, and you have an army of advocates multiplying your reach. This skill covers investor updates, board communications, partner management, advisor engagement, and vendor relationships. It's about building trust through consistent, thoughtful communication that treats stakeholders as partners in your mission, not just audiences to manage. Use when "stakeholder, investor update, board meeting, board deck, advisor, partner, vendor, monthly update, quarterly update, keep stakeholders informed, investor relations, stakeholder, investor, board, advisor, partner, vendor, updates, communications, relationship, engagement" mentioned.
Design predictive maintenance strategies using sensor data, ML models for remaining useful life (RUL), and the P-F curve framework. Use this skill when the user needs to reduce unplanned downtime, transition from reactive to predictive maintenance, evaluate sensor/IoT investments, or estimate equipment failure probability — even if they say 'machines keep breaking down', 'when will this equipment fail', 'should we invest in IoT sensors', or 'reduce unplanned downtime'.
Apply the Elaboration Likelihood Model to design persuasion strategies by matching message type to audience elaboration level. Use this skill when the user needs to craft persuasive communications, choose between argument-based and cue-based messaging, predict attitude durability after a campaign, or when they ask 'why did the message fail to persuade', 'how to change resistant attitudes', or 'should we use data or endorsements'.
Application performance profiling and bottleneck identification — Node.js profiling, Chrome DevTools, flame graphs, memory leak detection, CPU profiling, React rendering performance. Activate on "profiling", "performance bottleneck", "flame graph", "memory leak", "slow app", "CPU profiling", "heap snapshot", "React re-renders", "EXPLAIN ANALYZE", "event loop lag", "clinic.js", "Core Web Vitals". NOT for infrastructure monitoring or observability (use logging-observability), load testing (use a load-testing skill), or database schema optimization.
Port phone numbers into Telnyx. Check portability, create port orders, upload LOA documents, and track porting status. This skill provides JavaScript SDK examples.
Cross-protocol DeFi position aggregator for Stacks wallets — 5 parallel scanners covering Bitflow HODLMM LP bins, Zest lending/borrowing (V2 pool-borrow-v2-3), ALEX pool shares, Styx bridge deposits, and Hiro wallet balances. Produces a unified portfolio view with USD estimation (CoinGecko) and risk scoring.
Meta-skill for combining Three.js, GSAP ScrollTrigger, React Three Fiber, Motion, and React Spring for complex 3D web experiences. Use when building applications that integrate multiple 3D and animation libraries, requiring architecture patterns, state management, and performance optimization across the stack. Triggers on tasks involving library integration, multi-library architectures, scroll-driven 3D experiences, physics-based 3D animations, or complex interactive 3D applications.
When the user wants to model inventory systems with uncertain demand, optimize safety stock levels, implement (s,S) or (Q,r) policies, or analyze service levels under uncertainty. Also use when the user mentions "stochastic inventory," "probabilistic inventory," "(Q,r) policy," "(s,S) policy," "base stock policy," "safety stock optimization," "service level constraints," "lead time demand distribution," "fill rate calculation," or "inventory with demand uncertainty." For deterministic models, see economic-order-quantity or lot-sizing-problems. For single-period uncertainty, see newsvendor-problem.
Grassroots-first campaign design for anyone being outspent — startups vs. incumbents, NGOs vs. corporate comms, movements vs. state-backed machines, solo brands vs. big-budget competitors. Ideates awareness, launch, fundraising, mobilization, community-build, counter-narrative, referral, founder-story, and coalition campaigns. Triggers on "campaign plan", "marketing strategy", "ad budget", "should I advertise", "paid vs organic", "launch plan", "grassroots", "low budget marketing", "NGO campaign", "outspent", "competitor has bigger budget", "how do I compete without money". Also trigger on any spend asymmetry, collapsing organic reach, rising CPAs, or a trust/credibility problem — even without the word "campaign". Nudge activation when the user debates buying ads, boosting posts, or hiring influencers; they are likely about to burn money on a channel that will not persuade.
When the user wants help setting up or auditing Google Ads conversion tracking, Google Tag, Google Tag Manager, enhanced conversions, conversion actions, attribution models, cross-channel attribution, GA4 import, phone call tracking, or troubleshooting conversion data issues. Triggers on 'conversion tracking', 'Google tag', 'gtag', 'GTM', 'Tag Manager', 'conversion action', 'enhanced conversions', 'attribution model', 'conversion window', 'tracking not firing', 'missing conversions', 'GA4 import', or 'phone call tracking'. This skill is a prerequisite for google-ads-bidding Smart Bidding and google-ads-audiences remarketing.
Architecture patterns and best practices for giving AI agents email capabilities. Use when designing how agents send, receive, and manage email conversations, building two-way communication loops, implementing human-in-the-loop approval with drafts, choosing between WebSockets and webhooks, setting up multi-agent email topologies, handling OTP and verification flows, or securing agent email against prompt injection.
Issue Workflow Stage 1 — Convert the user's problem into a reproducible, traceable {slug}-report.md through conversation. The AI only asks "what you saw, how to reproduce it, what should happen" here, and does not guess the root cause for the user (that's Stage 2's responsibility). Meanwhile, this stage is the only official decision point for choosing between the fast track and standard path: Based on the user's description, first review the relevant code; if the root cause can be identified at a glance and the required changes are minor, directly inform the user to take the fast track. Trigger scenarios: The user says "file an issue", "record this bug", "I found a problem". This is the starting point of the issue workflow with no pre-dependencies.