oss-product-selection

Run a gated 7-phase workflow to select the next open-source product.

2|Updated May 4, 2026
One-click install
npx skills add https://github.com/sfrangulov/skills --skill oss-product-selection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: oss-product-selection
Source: https://github.com/sfrangulov/skills/tree/main/oss-product-selection
Command: npx skills add https://github.com/sfrangulov/skills --skill oss-product-selection

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve?

Helps you choose the next open-source product to build for personal brand growth by enforcing constraints, validating competitive saturation, checking platform obsolescence risk, and committing to a buildable spec.

Core Features & Use Cases

  • 7-phase selection workflow with hard gates: guides you from brand goals and constraints through options, research scans, scoring, naming validation, and a reality-check commit.
  • Brand-vs-product independent evaluation: scores narrative coherence and user value separately so you can weigh them intentionally.
  • Mandatory landscape protection: performs niche, platform, pain, and hype scans to avoid saturated, obsolete, or weak-demand ideas.
  • Naming safety checks: checks availability across npm/GitHub/domains/social and reduces negative-SEO risk before you commit.

Quick Start

Use oss-product-selection when you are deciding which OSS tool, npm CLI, dev utility, or side project to open-source next for brand growth (not revenue), and answer the first gate questions about your brand goal, hard constraints, and measurable success criteria.

Frequently Asked Questions about oss-product-selection

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I choose an open-source project to build for personal brand growth?

Validating OSS naming requires checking availability across npm, GitHub, domains, and social platforms to reduce negative-SEO risk before committing. This ensures your open-source project name is legally accessible and discoverable across your developer ecosystem.

What is competitive saturation research for side projects?

Competitive saturation research evaluates niche, platform, pain, and hype scans to avoid building open-source tools in obsolete or weak-demand markets. It prevents launching products into ecosystems that already have too many similar solutions competing for attention.

How do I score multiple side project ideas against my existing portfolio?

Score multiple side project ideas using a two-axis evaluation that rates narrative coherence and user value separately. This brand-versus-product independent evaluation lets you intentionally weigh how well an open-source tool extends your portfolio against its standalone utility.

Can I use this approach to select npm CLI tools specifically?

Yes, you can use this approach to select npm CLI tools, dev utilities, or side projects. The workflow applies specifically to comparing open-source ideas for brand growth rather than revenue, requiring constraint locking and a reality-check that results in a committed buildable spec.