Ejecuta cualquier Skill en Manus
con un clic

Ejecuta cualquier Skill en Manus con un clic

metrics-definition-skill

Estrellas1

Forks0

Actualizado28 de abril de 2026 a las 21:47

Define KPIs, events, and reporting views for a project or feature. Use for success metrics, tracking plans, measurement frameworks, or analytics dashboards.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Ejecutar en Manus

Fuente

Nickolai-Brennan

Nickolai-Brennan/__Campaign

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ejecutar en Manus

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Analistas de investigación de mercados y especialistas en marketingOperaciones empresariales y financieras·SOC 13-1161

Explorador de archivos

3 archivos

SKILL.md

readonly

name	metrics-definition-skill
description	Define KPIs, events, and reporting views for a project or feature. Use for success metrics, tracking plans, measurement frameworks, or analytics dashboards.
category	analytics
version	v1.0
inputs	["project or feature description","business goals"]
outputs	["metrics definition doc","KPI list","event tracking plan"]

Metrics Definition Skill

Purpose

Define clear, measurable KPIs, tracking events, reporting dimensions, and success criteria so the team can measure and improve performance.

When To Use

Use this skill when the user asks to:

Define success metrics for a feature or product
Create a KPI dashboard plan
Set up event tracking and analytics
Map business goals to measurable outcomes
Produce a measurement framework

Inputs

Project or feature description
Business goals and success criteria
Reporting tool in use (e.g., Mixpanel, Amplitude, Datadog, custom)

Workflow

Clarify business goals and what "success" looks like
Identify primary KPIs (the 3–5 numbers that matter most)
Define supporting metrics and dimensions
Map user actions to trackable events
Specify reporting views (dashboards, charts, alerts)
Document the full metrics plan

Output Format

# Metrics Plan: [Feature/Project Name]
## Primary KPIs
| Metric | Definition | Target | Owner |
## Supporting Metrics
## Events
| Event Name | Trigger | Properties |
## Reporting Views
## Measurement Notes

Quality Checklist

At least 3 primary KPIs defined with clear definitions
Each KPI has a target value or trend direction
Events mapped to user actions
Reporting views identified
Metrics owner assigned

References

Más de este repositorio

mismo repositorio

project-planning-agent

Nickolai-Brennan/__Campaign

Full end-to-end project planning agent that takes a rough idea all the way through research, planning, organization, and validation before any code is written. Use this skill whenever a user has a new project idea and wants structured, phase-by-phase help turning it into a complete, research-backed, approved plan — even if they don't explicitly say "project planning". This is the right skill any time someone wants to think before they build. Always trigger this skill for phrases like: "I have a project idea", "help me plan my project", "let's plan this before we build", "what should I figure out before starting", "turn my idea into a project plan", "help me go from idea to plan", "project planning", "create a project brief", "I want to build a SaaS / app / tool / website — where do I start?", "I have an idea but don't know where to begin", "help me think through this idea", "should I build this?", "help me scope this project", "I need a PRD and roadmap before we code anything", "let's research this idea first

2026-04-281

api-agent

Nickolai-Brennan/__Campaign

Designs and documents REST and GraphQL APIs, OpenAPI specifications, service boundaries, and integration contracts. Use this skill when a user asks to design an API, define endpoints, create a REST or GraphQL schema, write an OpenAPI or Swagger spec, establish a service contract, map integration points between services, or document an existing API. Common phrasings: "design an API for my app", "write an OpenAPI spec", "define REST endpoints", "create a GraphQL schema", "document this service's interface", "what endpoints do I need?", "help me plan my API surface". Do NOT use for implementing API server code, writing client SDK code, or running/testing live API requests — those require execution environments beyond this skill's scope.

2026-04-281

api-design-skill

Nickolai-Brennan/__Campaign

Designs REST and GraphQL APIs including endpoint definitions, request/response schemas, authentication patterns, error-handling conventions, and OpenAPI documentation. Use this skill when a user asks to design an API, create API specs, define endpoints, document a service interface, plan an API surface, or establish request/response contracts. Common phrasings: "design an API for X", "create an OpenAPI spec", "what endpoints should I have?", "define my REST routes", "write a Swagger file", "document my service interface", "help me plan my API". Do NOT use when the user wants to implement handler code, test a live API, write client SDKs, or when the request is about database schema design (use database-schema-skill) or service orchestration architecture.

2026-04-281

code-review-skill

Nickolai-Brennan/__Campaign

Reviews code for correctness, security vulnerabilities, performance issues, readability, and adherence to best practices and team conventions. Use this skill when a user asks for a code review, PR review, feedback on code quality, a security audit of code, style or pattern improvements, or a second opinion on an implementation. Common phrasings: "review this code", "check my PR", "look at this function", "is this secure?", "any issues with this?", "code feedback please", "audit this module", "does this follow best practices?". Do NOT use when the user wants code written from scratch (no existing code to review), or when the request is purely about running/executing code, deploying, or testing infrastructure — this skill reads and critiques existing code only.

2026-04-281

dashboard-design-skill

Nickolai-Brennan/__Campaign

Designs analytics and operational dashboards including layout, chart types, KPI cards, filters, drill-downs, and data visualizations. Use this skill when a user asks to design a dashboard, create data visualizations, build a metrics view, display charts or graphs, plan a reporting interface, or structure an analytics page. Common phrasings: "design a dashboard for X", "what charts should I use?", "help me visualize this data", "create a metrics view", "build a reporting page", "I need a KPI dashboard", "show me how to display this data visually". Do NOT use when the user wants to write the actual frontend code for a dashboard (use a code-generation skill), query the underlying data (use notebook-query-skill), or set up a BI tool like Tableau or Looker.

2026-04-281

data-cleaning-skill

Nickolai-Brennan/__Campaign

Cleans, normalizes, and validates datasets: fixes formatting inconsistencies, handles null/missing values, deduplicates records, standardizes field values, validates data types, and prepares data for downstream analysis or import. Use this skill when a user has messy data to fix, needs to normalize a CSV or table, wants data preparation before analysis or loading, or needs a cleaning plan for a dataset. Common phrasings: "clean this data", "fix my CSV", "normalize these fields", "deduplicate this table", "my data has inconsistencies", "prepare this for analysis", "standardize these values", "handle nulls in my dataset". Do NOT use when the user wants to analyze or visualize already-clean data (use notebook-query-skill), design a database schema (use database-schema-skill), or build an ETL pipeline (beyond cleaning rules, into full pipeline architecture).

2026-04-281