oss-product-selection
OSS Product Selection
A structured workflow for picking the next open-source product to build when the goal is personal brand growth rather than revenue. Most "what should I build next?" advice optimizes for monetization or product-market fit. That advice is wrong here. Brand-driven OSS has a different success function: stars, downloads, narrative coherence with prior work, audience fit, and signaling value. This skill bakes those criteria in and protects against the specific mistakes that derail brand-led product selection.
When this skill applies
Trigger this skill when the user is choosing among multiple possible OSS products to build, with brand-building (not revenue) as the dominant goal. The user usually has 1–3 products already shipped and is deciding what to ship next. Common framings: "what should I open-source next", "I have these three ideas, which one", "expanding my portfolio with X", "help me figure out my next side project for brand", "is <idea> a good thing to OSS".
When this skill does not apply
Skip this skill when:
- The user wants help building an already-chosen product (use coding skills instead).
- The user is choosing a startup or revenue-bearing product (different success function — use product-management or consulting-problem-solving).
- The user wants pure idea generation with no commitment to ship (this skill front-loads constraints because shipping is the assumed outcome).
- The user already shipped and wants growth/launch tactics, not selection (handoff territory).
Core principles
More from sfrangulov/skills
research-pipeline
Use when conducting research whose claims must be source-grounded, independently verifiable, and reproducible across sessions or machines — not a quick lookup. Explicit-invocation only.
5consulting-problem-solving-ru
**Русская версия Consulting Problem Solving Framework** — интерактивное решение бизнес- и организационных задач: ты ассоциат, пользователь — партнёр. 8 шагов с артефактами и явным утверждением: проблема, MECE-дерево, приоритизация, план работ, анализ, синтез, рекомендации, коммуникация по Strunk & White. Термины: стратегический консалтинг, дерево проблемы, issue tree, MECE, гипотезо-ориентированный подход, пирамида Минто, 80/20, case interview, структурное мышление. Роли: «я CEO/основатель/директор, у меня проблема с…», «готовлюсь к совету директоров», «нужна стратегическая сессия». Симптомы: падает выручка/маржа/LFL, теряем клиентов или долю рынка, не понимаем куда инвестировать, как приоритизировать инициативы, выходить ли в новый сегмент. Формулировки: «помоги структурно подумать», «разложи задачу», «как бы консультант подошёл», «нужен структурный подход к X». Используй на запросы, требующие структурного аналитического решения с артефактами — даже если фреймворк не назван явно.
3demo-video-pipeline
End-to-end automated pipeline for recording polished 30-90s demo videos of React or HTML web apps. Universal keyboard-driven zoom hook with cinematic scenes → Playwright headless recording → Remotion overlay graphics (intro, callouts, count-up numbers, pulse highlights) → ElevenLabs voiceover with frame-perfect timings → final mp4 with audio mixing and ducking. Use whenever the user wants to record a product walkthrough, marketing video, screencast with voiceover, demo for LinkedIn, YouTube or product launch, executive presentation, sales video, onboarding video, feature announcement, or any short polished video showing a web UI. Triggers on phrases like "record a demo", "make a screencast", "video for landing page", "product hunt video", "show this UI in a video", "walkthrough video", "demo with voiceover", "screen recording with zooms and callouts".
2