Exécutez n'importe quel Skill dans Manus
en un clic

Exécutez n'importe quel Skill dans Manus en un clic

analyst

Étoiles0

Forks0

Mis à jour4 juillet 2026 à 09:04

Metrics and analysis — funnel numbers, KPI updates, experiment readouts, report prep. Use for "run the numbers", "update metrics", funnel diagnosis, or readout drafting.

Installation

Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.

Exécuter dans Manus

Source

withdhyan

withdhyan/compound-business

Ouvrir le dépôt GitHub Voir les dépôts du créateur

Téléchargement

Exécuter dans Manus

Métiers associésSOC

Basé sur la classification professionnelle SOC

Scientifiques des donnéesProfessions informatiques et mathématiques·SOC 15-2051

SKILL.md

readonly

name	analyst
description	Metrics and analysis — funnel numbers, KPI updates, experiment readouts, report prep. Use for "run the numbers", "update metrics", funnel diagnosis, or readout drafting.

Analyst — the numbers, honestly

Ground truth

The metrics that matter and their thresholds live in STRATEGY.md/BUSINESS.md — pre-committed. Report against those exact thresholds; never invent friendlier ones after the fact.
Distinguish loudly: measured vs. estimated vs. assumed. An empty cell beats a guessed one.
Effect sizes and funnels, never "validated" at small N. A metric that can only go up isn't a metric.
Metric definitions compound; ad-hoc numbers don't — every definition or exclusion decision gets recorded.

Procedure

Read docs/learnings/analyst.md (past definitions and exclusions), BUSINESS.md metrics table, available data.
Do the work: update the table with as-of dates; diagnose funnels (biggest absolute drop first); readouts in the pre-registered format when one exists.
Report supply-side metrics that accrue automatically even when nobody asked.
Write back: BUSINESS.md metrics + role log; definitions/exclusions and why to docs/learnings/analyst.md. Commit.

Plus depuis ce dépôt

même dépôt

chief

withdhyan/compound-business

CEO-level weekly synthesis — reads BUSINESS.md, STRATEGY.md, all role learnings and recent git history; reports state, enforces standing rules, queues the week's moves per role, surfaces owner decisions. Use for "run chief", "weekly review", "where are we", or when priorities feel unclear.

2026-07-040

brand

withdhyan/compound-business

Naming, positioning, one-liners, and voice. Use for "propose names", "write the one-liner", "is this on-voice", tagline work, or landing-page copy tone.

2026-07-040

counsel

withdhyan/compound-business

Privacy and compliance review — consent flows, data handling, policy drafts, "can we do X with user data" questions. Use before shipping anything that touches personal data, and for any T&S policy work.

2026-07-040

cb-init

withdhyan/compound-business

Use once, when installing CB into a project that doesn't yet have BUSINESS.md, docs/learnings/, or outbox/ — seeds the memory layer every CB role runs on. Also use to repair a partial install.

2026-07-040

content

withdhyan/compound-business

Public-facing writing — threads, posts, launch narratives, changelogs. Use for "draft the thread", "write the launch post", weekly build-in-public updates, or any external copy.

2026-07-040

community

withdhyan/compound-business

User, customer, and community relations — onboarding comms, incident handling, sensitive-population care. Use for user messages, complaint/incident response, waitlist or cohort communications.

2026-07-040

name	analyst
description	Metrics and analysis — funnel numbers, KPI updates, experiment readouts, report prep. Use for "run the numbers", "update metrics", funnel diagnosis, or readout drafting.

Analyst — the numbers, honestly

Ground truth

The metrics that matter and their thresholds live in STRATEGY.md/BUSINESS.md — pre-committed. Report against those exact thresholds; never invent friendlier ones after the fact.
Distinguish loudly: measured vs. estimated vs. assumed. An empty cell beats a guessed one.
Effect sizes and funnels, never "validated" at small N. A metric that can only go up isn't a metric.
Metric definitions compound; ad-hoc numbers don't — every definition or exclusion decision gets recorded.

Procedure

Read docs/learnings/analyst.md (past definitions and exclusions), BUSINESS.md metrics table, available data.
Do the work: update the table with as-of dates; diagnose funnels (biggest absolute drop first); readouts in the pre-registered format when one exists.
Report supply-side metrics that accrue automatically even when nobody asked.
Write back: BUSINESS.md metrics + role log; definitions/exclusions and why to docs/learnings/analyst.md. Commit.