How do I install the Set Goals Okrs Kpis skill?

Run npx skillmds@latest add alexe-ev/set-goals-okrs-kpis in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Set Goals Okrs Kpis safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Set Goals Okrs Kpis?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Set Goals Okrs Kpis free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Set Goals Okrs Kpis?

alexe-ev (@alexe-ev) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Set Goals Okrs Kpis by alexe-ev — Agent Skill

Name: Set Goals Okrs Kpis
Author: alexe-ev

File contents

Set Goals: OKRs & KPIs

Purpose

Help teams define well-structured, measurable goals that connect product work to business outcomes.

Skill type

Conceptual skill

Use this skill when

A team is starting a planning cycle and needs to define goals
Existing OKRs are vague, unmeasurable, or disconnected from strategy
KPIs are undefined or not connected to product decisions
There is confusion between outputs (features shipped) and outcomes (user/business impact)

Do not use this skill when

Goals are already defined and the team needs roadmap prioritization
The goal is experiment design (use experimentation skills)

Required inputs

Business or product area
Strategic priority or direction (even rough)

Optional inputs

Company-level OKRs
Current metrics baseline
Time horizon (quarter, half-year)
Prior OKR performance

Upstream context

Works best when:

Product vision and strategy are defined
Product-market fit assessment exists

If upstream context is missing

Produce provisional OKR structure. Flag that without strategic direction, goals may not align with the business.

Downstream handoff

Output can feed:

build-roadmap-prioritization
define-success-metrics (experiment metrics derived from KPIs)
build-decision-dashboard

Instructions

Identify the strategic priority being addressed.
Define 1–3 Objectives: qualitative, inspiring, directional.
For each Objective, define 2–4 Key Results: specific, measurable, time-bound.
Separate leading indicators (KRs) from lagging outcomes.
Identify 3–5 KPIs for ongoing product health monitoring.
Confirm that KRs are outcomes, not output metrics.
Flag dependencies and risks to achieving the goals.

Output

Provide:

Objectives (1–3)
Key Results per Objective (2–4 each)
KPIs for ongoing monitoring
Baseline values where known
Assumptions behind each KR
Risks to goal achievement
Confidence level: provisional / context-informed / ready-to-commit

Risks / caveats

Do not write KRs that measure activity instead of outcomes
Do not set too many OKRs — focus is more important than coverage
OKRs should stretch but remain achievable; flag if targets are arbitrary

---name: set-goals-okrs-kpisdescription: Help teams define and structure goals using OKRs, KPIs, and related frameworks. Use this skill when a team needs to set clear, measurable goals aligned with business strategy.---# Set Goals: OKRs & KPIs## PurposeHelp teams define well-structured, measurable goals that connect product work to business outcomes.## Skill typeConceptual skill## Use this skill when- A team is starting a planning cycle and needs to define goals- Existing OKRs are vague, unmeasurable, or disconnected from strategy- KPIs are undefined or not connected to product decisions- There is confusion between outputs (features shipped) and outcomes (user/business impact)## Do not use this skill when- Goals are already defined and the team needs roadmap prioritization- The goal is experiment design (use experimentation skills)## Required inputs- Business or product area- Strategic priority or direction (even rough)## Optional inputs- Company-level OKRs- Current metrics baseline- Time horizon (quarter, half-year)- Prior OKR performance## Upstream contextWorks best when:- Product vision and strategy are defined- Product-market fit assessment exists## If upstream context is missingProduce provisional OKR structure. Flag that without strategic direction, goals may not align with the business.## Downstream handoffOutput can feed:- build-roadmap-prioritization- define-success-metrics (experiment metrics derived from KPIs)- build-decision-dashboard## Instructions1. Identify the strategic priority being addressed.2. Define 1–3 Objectives: qualitative, inspiring, directional.3. For each Objective, define 2–4 Key Results: specific, measurable, time-bound.4. Separate leading indicators (KRs) from lagging outcomes.5. Identify 3–5 KPIs for ongoing product health monitoring.6. Confirm that KRs are outcomes, not output metrics.7. Flag dependencies and risks to achieving the goals.## OutputProvide:- Objectives (1–3)- Key Results per Objective (2–4 each)- KPIs for ongoing monitoring- Baseline values where known- Assumptions behind each KR- Risks to goal achievement- Confidence level: provisional / context-informed / ready-to-commit## Risks / caveats- Do not write KRs that measure activity instead of outcomes- Do not set too many OKRs — focus is more important than coverage- OKRs should stretch but remain achievable; flag if targets are arbitrary

Frequently asked questions

Set Goals Okrs Kpis