North Star Selection logo

North Star Selection

Community
Productfculty-aipm
north-star-selection

Use this skill when the user asks "which metric should we focus on", "how do I choose between these metrics", "what's the best metric to track", "help me select our primary metric", "our metrics are confusing", "we have too many metrics", or wants to select a primary North Star from a set of competing metrics. This is the selection and evaluation skill; for defining and setting a North Star from scratch, use strategy/north-star.

Overview

PublisherProductfculty-aipm
RepositoryPM-Copilot-by-Product-Faculty
Skill namenorth-star-selection
Stars
80
Forks
34
Bundled files
Instructions only
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.

  • Self-contained

    Everything the model needs lives in the instructions — no extra files to sync.

  • Open source

    Published by Productfculty-aipm on GitHub. Read the source before you install it.

Installation

Install the North Star Selection 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.
    https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty/tree/main/skills/north-star-selection
  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/Productfculty-aipm/PM-Copilot-by-Product-Faculty.git /tmp/PM-Copilot-by-Product-Faculty
mkdir -p .claude/skills
cp -r /tmp/PM-Copilot-by-Product-Faculty/skills/north-star-selection .claude/skills/north-star-selection
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable North Star Selection 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 North Star Selection 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 North Star Selection 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.

North Star Selection

You are helping the user choose the right North Star Metric from a set of candidates. This is different from defining a North Star from scratch — here, the user has options and needs a framework for deciding.

Framework: Lenny Rachitsky (North Star guide, survey of 40+ top companies), Sean Ellis (North Star selection criteria), Dan Olsen (prioritizing metrics).

Step 1 — Load Context

Read memory/user-profile.md for product stage, business model, and current metrics. Read context/company/analytics-baseline.md for available metrics.

Step 2 — Gather the Candidates

Ask: what metrics are being considered? For each candidate metric, capture:

  • Name and definition
  • How it's currently measured
  • Who has access to this data

Step 3 — Evaluate Against NSM Criteria

Score each candidate on the 5 NSM criteria (1–5 each):

1. Represents value: Does it go up when users genuinely get value, not just when they're active?

2. Predicts revenue: Is it a leading indicator of long-term revenue or retention? (Revenue itself is a lagging indicator — avoid as a primary NSM)

3. Measurable: Can you track it accurately with current infrastructure? Any data quality concerns?

4. Actionable: Can the product team run experiments that meaningfully move this metric?

5. Understandable: Can any team member immediately understand what this metric means? (Avoid complex composite metrics as NSM)

Score each candidate across all 5. The highest total score is the strongest candidate.

Step 4 — The Vanity vs. Value Test

Apply the most important filter: does this metric go up even when users aren't getting value?

  • Total signups: Goes up with any acquisition — users could sign up and never use the product
  • Total sessions: Goes up if users open the app and immediately give up
  • Total pageviews: Goes up with any traffic, regardless of engagement

Eliminate vanity metrics from consideration.

Step 5 — North Star for Your Business Model

Cross-reference with the known best-practice NSM by business model (from memory context):

SaaS: "Weekly active users who complete [core action]" — captures genuine engagement, not just logins Marketplace: "Completed transactions with positive outcome for both sides" — prevents optimizing for volume at the expense of quality Consumer: "DAU/MAU ratio" — measures habit formation, not just reach Usage-based: "Value-generating actions per period" — not all usage, specifically value-generating Freemium: "Users who hit the activation threshold" — the specific action that predicts conversion

Step 6 — Recommendation

Present:

  • Ranked candidates with scores and rationale
  • Recommendation with explanation
  • Why the top alternative was rejected
  • Any supporting metrics that should be tracked alongside the NSM
  • One metric to explicitly exclude (and why — prevents gaming)

Step 7 — Output

Produce:

  • Evaluation table (all candidates × 5 criteria × scores)
  • Final recommendation with rationale
  • Supporting metric suite (3–4 metrics that indicate whether the NSM will move)
  • Implementation note: if the recommended NSM isn't currently being tracked, what would it take to start?

Frequently asked questions

What does the North Star Selection AI skill do?

Use this skill when the user asks "which metric should we focus on", "how do I choose between these metrics", "what's the best metric to track", "help me select our primary metric", "our metrics are confusing", "we have too many metrics", or wants to select a primary North Star from a set of competing metrics. This is the selection and evaluation skill; for defining and setting a North Star from scratch, use strategy/north-star.

Why use North Star Selection on TypingMind?

Because you install it once and use it with any model. North Star Selection 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 North Star Selection in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Productfculty-aipm/PM-Copilot-by-Product-Faculty/tree/main/skills/north-star-selection. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use North Star Selection?

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 North Star Selection?

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

Is the North Star Selection AI skill free?

It is published on GitHub by Productfculty-aipm. Check the repository for licensing terms. 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 👇