Product Tool Stack logo

Product Tool Stack

OrganizationPopular
RefoundAI
product-tool-stack

Help users select, implement, and optimize a modern product tool stack that reduces operational friction and accelerates delivery cycles.

Overview

PublisherRefoundAI
Repositorylenny-skills
Skill nameproduct-tool-stack
Stars
1.3K
Forks
170
Bundled files
2
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 2 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by RefoundAI on GitHub. Read the source before you install it.

Installation

Install the Product Tool Stack AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/RefoundAI/lenny-skills.git /tmp/lenny-skills
mkdir -p .claude/skills
cp -r /tmp/lenny-skills/skills/product-tool-stack .claude/skills/product-tool-stack
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Product Tool Stack in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Product Tool Stack on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Product Tool Stack is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Product Stack Strategy

Build a high-performance product toolkit by balancing established standards with AI-native speed.

Help the user with product stack strategy using insights from 6 guests and posts across Lenny's Podcast and Newsletter.

How to Help

  1. Audit and Consolidate - Review current software spending and identifying opportunities to move toward all-in-one platforms that reduce workflow friction.
  2. Define the Foundation - Establish the core data and communication layers required for early-stage stability and cross-functional alignment.
  3. Apply Selection Frameworks - Distinguish between 'safe bet' industry standards for stability and 'early-adopter' tools for competitive productivity gains.
  4. Integrate AI-Native Workflows - Identify specific opportunities to automate administrative tasks, ticket drafting, and video editing with agentic tools.

Core Principles

Consolidate for seamless workflows

From "A year free of PostHog ($16,500 value): The all-in-one analytics, experimentation, feature flag, surveys, session replay, error tracking, data warehouse, LLM analytics platform": "Being able to follow an issue from a session recording, to its impact in analytics, to shipping a fix as a feature flag, to testing a variant, to collecting feedback with surveys—that’s the holy grail."

Moving toward all-in-one platforms reduces the technical and operational friction of managing multiple point solutions, enabling better integration between discovery and shipping.

Commit to engineering-backed data

From "Five steps to starting your product-led growth motion, part 2": "Tools such as Amplitude and Mixpanel are commonly used here, but, as the saying goes, “garbage in, garbage out.” Companies need to dedicate engineering resources to instrument tracking properly. Many B2B companies are significantly lacking in product analytics—watching product usage closely is less important when you sell via human touch—but without a strong foundation of product analytics, PLG will never work."

Product analytics requires dedicated engineering resources for proper instrumentation; successful PLG is impossible without a robust data foundation.

Buy instead of build experimentation

From "Five steps to starting your product-led growth motion, part 2": "The most common mistake I see is that companies skip buying and jump right into building. In other words, they bypass the option of using a third-party experimentation tool, often because the engineering and product teams feel like they can build anything. But building an experimentation platform requires not only engineering resources but also data science and statistical expertise."

Small teams should choose third-party experimentation tools over homegrown platforms to avoid massive engineering and statistical overhead.

Questions to Help Users

  • "Which tools in your current stack are creating the most manual data transfer work between teams?"
  • "Are you currently using a 'safe bet' for your mission-critical data, or are you over-extended on unproven tools?"
  • "What percentage of your PMs' time is spent on administrative tasks like ticket drafting that could be handled by AI agents?"
  • "Is your product instrumentation handled by a dedicated engineering resource or as an afterthought?"
  • "Do you have a single source of truth for user behavioral data that bridges into your CRM?"

Common Mistakes to Flag

  • Building homegrown experimentation platforms - Small teams often underestimate the statistical and engineering maintenance required compared to buying a specialized third-party tool.
  • Over-complicating early-stage process - Using heavy tools like long-term backlogs and story points early on can kill velocity and distract from immediate shipping.
  • Failing to instrument granular data - Without engineering-backed tracking of specific feature interactions, you cannot identify the 'aha moments' that drive growth.
  • Neglecting the data warehouse connection - Failing to sync product usage data with sales and marketing tools prevents the cross-functional intelligence needed for effective scaling.

Deep Dive

For all 25 sourced insights from 6 guests, see references/guest-insights.md

Related Skills

  • Writing Prds
  • Shipping Velocity
  • Ai Assisted Prototyping
  • Building With Ai Agents

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Product Tool Stack AI skill do?

Help users select, implement, and optimize a modern product tool stack that reduces operational friction and accelerates delivery cycles.

Why use Product Tool Stack on TypingMind?

Because you install it once and use it with any model. Product Tool Stack is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Product Tool Stack in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/RefoundAI/lenny-skills/tree/main/skills/product-tool-stack. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Product Tool Stack?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Product Tool Stack?

As many as you like. As long as a model supports skills, you can use Product Tool Stack with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Product Tool Stack AI skill free?

Yes. It is published on GitHub by RefoundAI under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇