Run any Skill in Manus with one click

instrument-the-truth

Stars0

Forks0

UpdatedJuly 2, 2026 at 09:03

Wire minimal, consent-first instrumentation into a codebase — an event schema for the keystone path, cohort queries, and experiment scaffolding on whatever stack exists. Use when GROWTH.md has an Aha but no verified instrumentation, when find-the-keystone stalls for lack of data, when a team is flying on vibes, or when an analytics setup has grown into an unusable event swamp and needs cutting back to the path that matters.

Installation

Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.

Run Skill in Manus

Source

zakelfassi

zakelfassi/skdd-commons

View GitHub Repository View Creator Repositories

Download

Run Skill in Manus

Related occupationsSOC

Based on SOC occupation classification

Software DevelopersComputer and Mathematical Occupations·SOC 15-1252

SKILL.md

readonly

name	instrument-the-truth
description	Wire minimal, consent-first instrumentation into a codebase — an event schema for the keystone path, cohort queries, and experiment scaffolding on whatever stack exists. Use when GROWTH.md has an Aha but no verified instrumentation, when find-the-keystone stalls for lack of data, when a team is flying on vibes, or when an analytics setup has grown into an unusable event swamp and needs cutting back to the path that matters.
metadata	{"pack":"2026-07-growth-circle","forged-by":"claude-fable-5","forged-from":"session-2026-07-02-growth-circle — the Growth Circle protocol (github.com/zakelfassi/growth-circle)","forged-reason":"The circle replaces lore with instruments, and instruments are code. This is the skill that does the wiring — with taste (≤10 events) and a consent posture that treats tracking a user like borrowing from them.","usage-count":"0"}

Instrument the Truth

Instrument the keystone path — and almost nothing else. Verify with your own eyes that one real event flows end-to-end before calling it done.

Gate

Requires gate: aha = open in GROWTH.md. A keystone spec is ideal but not required — this skill often runs before find-the-keystone to give it data. Without even an aha, there is no path to instrument; run name-the-aha first.

Inputs

The codebase, GROWTH.md, and whatever analytics/experimentation stack already exists (PostHog, GrowthBook, Statsig, Amplitude, plain SQL + a table — all fine). Prefer what's installed; never add a paid dependency uninvited.

Steps

Draw the path first. From ## Aha (and ## Keystone if present), list the signup → aha → repeat-value sequence as concrete user actions. The event schema is this list and nothing else. Taste target: ≤10 events.
Design the schema. Per event: name (verb-first, keystone-path vocabulary), properties (minimum viable — cohort keys, timing, context), and an explicit no-PII check per property. Distinguish agent traffic by declared user-agent, never by fingerprinting.
Check the consent posture. Read the app's existing consent framework, privacy policy, and applicable defaults. Instrumentation must fit inside what users have actually agreed to. Collect under the stated basis or don't collect. Refuse dark patterns (consent walls, pre-checked boxes, tracking disguised as functionality) in writing, in the PR.
Wire it. Implement events in code, matching the repo's conventions. Add the cohort queries the keystone derivation needs (engaged cross-section, first-N-days paths, matched dead cohort) wherever queries live in this project.
Verify first light. Run the product, perform the aha path yourself, and watch the events arrive end-to-end — dashboard, table, or log. "The code merged" is not done; "I watched the event land" is done.
Record. Write to GROWTH.md ## Instrumentation: schema, query locations, consent posture, first-light date. Set gate: instrumented = open.

Conventions

Every event traces to a ring; if you can't say which growth question an event answers, delete it.
Experiment scaffolding (flags, assignment, exposure logging) counts as instrumentation — add the minimal version if run-the-loop is next.
When cutting an event swamp: keep the keystone path, archive the rest, and log the cut in the lore ledger (swamps encode dead beliefs).

Edge Cases

No analytics stack at all. Plain append-only table + three SQL queries beats installing a platform mid-skill. Note the upgrade path.
Consent posture is undefined. Stop at step 3, draft the posture, and flag it for human decision — consent posture is non-delegable to agents.
Client-side only, privacy-sensitive product. Count events without identifying users (anonymous aggregates, local-first counters). A cruder honest instrument beats a sharper invasive one.
First light won't verify. Do not open the gate. A broken pipeline recorded as working poisons every downstream verdict.

More from this repository

same repository

name-the-aha

zakelfassi/skdd-commons

Interrogate a product for its core value — name the observable aha moment, measure time-to-aha, or honestly conclude there is none yet. Use when starting Growth Circle work on any repo, when someone asks "how do we grow this", when GROWTH.md is missing or its Aha section is empty, or before any activation/retention/distribution work is proposed. This is the gatekeeper skill — every other growth skill depends on its output.

2026-07-020

prove-the-value

zakelfassi/skdd-commons

Compile a product's earned, evidence-backed claims from GROWTH.md into a public VALUE.md — the proof-of-value surface that agent-mediated discovery reads — with attestation levels, expiry dates, and honest retractions. Use when creating or refreshing a VALUE.md, when marketing copy needs grounding in evidence, when preparing a product to be evaluated by assistants and their principals' agents, or when a published claim has gone stale.

2026-07-020

run-the-loop

zakelfassi/skdd-commons

Run the growth experiment cadence — propose ranked by keystone impact, pre-register before launch, evaluate by the committed rule, keep/kill without relitigating, log everything. Enforces the virality gate (get-users-to-get-users proposals are parked until activation and retention run green) and the alienation test (auto-kill anything a fully-informed user would resent). Use when the growth cadence comes due (weekly/biweekly), when someone proposes "a growth hack", or when experiment results need an honest verdict.

2026-07-020

forge-the-local-circle

zakelfassi/skdd-commons

Use SkDD to forge project-specialized adaptations of the Growth Circle skills — local skills that carry this product's keystone, event names, query paths, contexts, and cadence baked in, so future sessions (and cheaper models) run the circle without rediscovering it. Use when the generic pack has run against a project a few times and keeps re-deriving the same context, when handing growth work to scheduled or lighter-weight agents, or when a project's circle has stabilized enough to be worth freezing as skills.

2026-07-020

wind-the-clock

zakelfassi/skdd-commons

Make the growth circle self-running — schedule its recurring checks (loop cadence, keystone sunset, first-light freshness, AEO probes, trust-ledger review) using whatever scheduling primitive the current harness offers, and record every schedule in GROWTH.md so it survives harness changes. Use when the circle's gates are open but nothing recurs, when a keystone sunset or instrumentation check exists only as a date nobody watches, after run-the-loop establishes a cadence, or when growth work keeps happening "whenever someone remembers".

2026-07-020

hire-the-circle

zakelfassi/skdd-commons

Turn growth-team values into working artifacts — role scorecards, interview kits with listen-fors — and map which rings of the growth circle run on agents versus humans, with explicit approval boundaries. Use when hiring a first growth person, when staffing growth work across a human/agent team, when a growth hire is failing and nobody can say why, or when deciding what an autonomous agent may and may not do to users.

2026-07-020