rt-andreessen

Frame technology and strategy questions through Marc Andreessen's techno-optimist lens.

28|11|Updated Apr 11, 2026
One-click install
npx skills add https://github.com/risingdream/roundtable --skill rt-andreessen
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rt-andreessen
Source: https://github.com/risingdream/roundtable/tree/main/skills/vc/rt-andreessen
Command: npx skills add https://github.com/risingdream/roundtable --skill rt-andreessen

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Technology-focused debates stall when the user can’t get a compelling builder’s frame for priorities, tradeoffs, and what to bet on; this skill lets users channel Marc Andreessen’s techno-optimist, software-eats-everything stance to push toward ambitious execution.

Core Features & Use Cases

  • Software-eats-everything reframing: Converts the user’s topic into “which industry layer gets eaten by software next,” prioritizing where speed and leverage matter.
  • Techno-optimist argumentation: Challenges stagnation narratives with growth, competition, and “permissionless innovation” logic to re-open decision space.
  • Concrete frontier lens: Uses AI/frontier evaluation themes, markets-as-information, and founder-quality heuristics to turn vague questions into actionable bets and calls to action.
  • Use case example: If you’re unsure whether to invest in an AI product vs. an incumbent workaround, use this skill to pressure-test the plan through a pro-building, anti-stagnation lens and produce a clear “what to build now” direction.

Quick Start

Ask for a debate stance: “Answer as Marc Andreessen to evaluate my product idea: where is software eating this industry, what’s the biggest risk of stagnation, and what should we build first?”

Frequently Asked Questions about rt-andreessen

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

FAQPage Schema
How do I evaluate if software will disrupt my industry sector?

To evaluate industry disruption, frame your sector through a techno-optimist lens to identify where speed and leverage matter, determining which industry layer gets eaten by software next to prioritize builder-first execution.

What is the best way to pressure-test an AI product strategy against stagnation risks?

Pressure-test AI product strategy by challenging stagnation narratives with growth and permissionless innovation logic, applying founder-quality heuristics and markets-as-information concepts to turn vague AI bets into actionable directions.

How do I prioritize frontier technology bets for venture capital decisions?

Prioritize frontier technology bets by applying a concrete frontier lens that uses AI evaluation themes and decisive calls to action, converting ambiguous investment questions into clear, builder-first priorities.

Can I use techno-optimist argumentation to overcome regulatory objections in product development?

Yes, you can overcome regulatory objections by challenging them with pro-building, anti-stagnation logic, reframing regulatory constraints as opportunities for permissionless innovation to re-open decision space.

When should I use a builder mindset approach for technology strategy debates?

Use a builder mindset approach when technology-focused debates stall and you need a compelling frame for priorities, tradeoffs, and what to bet on to push your team toward ambitious execution.