drop another .md file to compare - side-by-side diff against analytics

analytics

Brings your key numbers together so you can see how things are tracking.

description: "Triggers on prompt mention of 'analytics'."

personal 2 files 10 recent evals

Export

What it does for you

Brings your key numbers together so you can see how things are tracking.

What it produces

A recent result, so you can see the kind of work it returns.

loading…

How to get it

These run inside the Snappy workspace. Want this working in your business? I set skills like this up with you, in one focused week.

Work with me

For developers how this skill is built, graded, and how it runs

at a glance- the short version

actorExported functions in state/lib/analytics.ts.

auditorNone wired yet - eval is manual (Robert review).

eval modeshape

categoryIntegrations

stages3

dependssettings

what's inside - the parts that make up a skill 3/4 present

A skill is just a few plain-text files. Only the main one is required. The rest are optional, added as the work needs them. This is what the skill is made of; how it runs is just below.

The skill

state/skills/analytics/SKILL.md present

the skill itself, in plain text

The main file. It says what the skill is and lays out the steps in plain English.

Code

state/lib/analytics.ts present

code the skill can run

Reusable code this skill can call when it needs to.

Scripts

state/bin/analytics/ not present

helper scripts

Optional. Added when a skill has a few commands to run.

Loader

state/skills/analytics/AGENTS.md present

what the AI loads on the fly

Loaded automatically the moment this skill is needed. Kept short on purpose.

how it's graded - what counts as a good run 4 criteria · 2 deterministic · 2 judge

Each row is one thing a good run has to get right. deterministic means a quick check decides, pass or fail. judge means the AI reads the result and rates it. Grading each piece on its own (instead of one overall score) shows exactly where a run fell short, so the fix is obvious.

name

kind

check

scorecard_function_exists

deterministic

The getScorecard() function must be exported from state/lib/analytics.ts.

correct_return_type

judge

The getScorecard() function returns a valid scorecard structure with appropriate metric types, as defined by its API contract.

accurate_metric_aggregation

judge

The aggregated metrics in the scorecard accurately reflect the performance of snappy-* skills based on their inputs.

handles_cli_guard

deterministic

The implementation includes a try/catch block around realpathSync(process.argv[1]) as specified in the Gotchas section.

how it runs - the shared frame every skill uses 5/5 present

Every skill runs the same way. One part does the work, a separate part checks it, and a short loader hands the AI exactly what it needs for the job. Anything this skill doesn't use shows a one-line note saying why, on purpose, not by accident.

makes the work The worker

present

Exported functions in state/lib/analytics.ts. the worker

Does the actual work. Whatever it produces is what gets checked next.

checks the work The reviewer

present

None wired yet - eval is manual (Robert review). the checker

A separate checker grades the work, so the part that made it can't approve its own work.

frame

learns Self-correction

present

fixes itself learns from gaps

When a run hits a gap, the skill gets edited on the spot [FIXED] or queued for a bigger rewrite [LOGGED], so it keeps getting better.

tidies up Background fixes

present

queued for rewrite runs in the background

Bigger fixes that can't be made on the spot get queued and rewritten in the background later.

remembers Run history

present

state/log/pending-eval.ndjson pending runs

Every run is written down here, then reviewed by hand each week.

Critical rules the things this skill must not get wrong

ALWAYS use getScorecard() from state/lib/analytics.ts rather than re-aggregating raw logs
Eval is shape / manual — log a pending-eval.ndjson row on each run

what it has learned - fixes written back in over time sample

When a run hits something this skill didn't handle, the fix gets written back into the skill so it doesn't happen again. FIXED means it was corrected on the spot. LOGGED means it's queued for a bigger rewrite. Either way, the skill gets a little better and never makes the same mistake twice.

Loading feedback rows…

how the work flows- who makes it, who checks it

inputs settings

actor Exported functions in state/lib/analytics.ts.

1 generator

invoke

actor = Exported functions in state/lib/analytics.ts.

import { getScorecard } from "state/lib/analytics.ts"

+ eval for this step

auditor None wired yet - eval is manual (Robert review).

2 auditor

inspect

auditor = None wired yet - eval is manual (Robert review).

npx tsx -e 'import("/Users/robertboulos/projects/snappy-os/state/lib/analytics.ts").then(m => console.log(Object.keys(m)))'

+ eval for this step

3 data

eval log

`state/log/pending-eval.ndjson` (skill: "analytics")

+ eval for this step

SKILL.md- the skill, written out in plain English

analytics

Metrics aggregator for all snappy-* skills.

Ported from kernel snappy-analytics in Phase 0.5. See state/lib/analytics.ts for the full API surface.

Steps

getScorecard() - see state/lib/analytics.ts

Eval

Actor: the exported functions in state/lib/analytics.ts. Auditor: none wired yet - eval is manual (Robert review). File a state/log/pending-eval.ndjson row on each run.

Score convention:

Outcome	Score
Pass on first try	1.0
Failed first, auto-fix applied, re-check passed	0.5
Still failing or unrecoverable	0.0

Gotchas

via the Phase 0.5 driver. Only these rewrites were applied: already in state/lib/)

realpathSync(process.argv[1]) CLI guard wrapped in try/catch

See the kernel SKILL.md for the original long-form guidance if you need it

(read-only reference at the kernel path above).

Graduation

This skill is prose. Graduate by defining a deterministic auditor and flipping eval: auto.

Rubric

criteria:
  - name: scorecard_function_exists
    kind: deterministic
    check: "The getScorecard() function must be exported from state/lib/analytics.ts."
  - name: correct_return_type
    kind: judge
    check: "The getScorecard() function returns a valid scorecard structure with appropriate metric types, as defined by its API contract."
  - name: accurate_metric_aggregation
    kind: judge
    check: "The aggregated metrics in the scorecard accurately reflect the performance of snappy-* skills based on their inputs."
  - name: handles_cli_guard
    kind: deterministic
    check: "The implementation includes a try/catch block around realpathSync(process.argv[1]) as specified in the Gotchas section."

AGENTS.md- what the AI loads when this skill comes up

analytics - loader

Per-turn rules for the analytics skill. Full reference: state/skills/analytics/SKILL.md. Do not skip these.

Critical Rules

_(no failures recorded yet - Phase 0.5 mechanical port from kernel snappy-analytics. Read state/skills/analytics/SKILL.md and state/lib/analytics.ts before invoking.)_

ALWAYS use getScorecard() from state/lib/analytics.ts rather than re-aggregating raw logs
Eval is shape / manual - log a pending-eval.ndjson row on each run

Commands

| ui dashboard | state/skills/analytics/resources/ui.openui | |invoke: import { getScorecard } from "state/lib/analytics.ts" |verify: npx tsx -e 'import("/Users/robertboulos/projects/snappy-os/state/lib/analytics.ts").then(m => console.log(Object.keys(m)))' |eval log: state/log/pending-eval.ndjson (skill: "analytics")

OpenUI Resource

Skill-owned OpenUI Lang resource: state/skills/analytics/resources/ui.openui. Read it before rendering or editing this skill's generated component surface.
Treat this resource as a first-class artifact of the skill, not a generic chat response. Improve it when the skill's user-facing output needs to become richer.
System resources compose OpenUI primitives and inherit SnappyChat tokens. Use ui_contract: branded in SKILL.md only for deliberate platform or client visuals.

Known Pitfalls

Phase 0.5 port - kernel SKILL.md at ~/projects/snappy-kernel/skills/snappy-analytics/ is the long-form reference
Only mechanical rewrites applied (settings path, sibling lib paths, CLI guard)

Self-Test

An agent reading this should correctly:

[ ] Call getScorecard() from the lib rather than re-implementing
[ ] Log to pending-eval.ndjson (no auto auditor yet)
[ ] Know the kernel skill is the long-form reference

Self-report

If this loader fell short, append a line:

echo "[$(date -u +%FT%TZ)] analytics: <what was missing>" >> state/log/loader-feedback.log

Self-correcting loader (PID feedback)

This is the rule that makes loaders learn. Ported from snappy-kernel, where it demonstrably worked: the snappy-dom-cartographer skill mapped Skool admin UI once, every later ship-agent inherited the full map for free.

Before you finish, do two things:

1. Fix gaps (P - proportional). MANDATORY. If this loader didn't cover your case - if you had to read another file, run an undocumented command, work around a wrong selector, or discover a quirk - you MUST attempt an Edit to this AGENTS.md before you log.

Default action: edit this file. Surgical. Add the missing line, table

row, or code example where it belongs. No restructuring.

Only LOGGED is allowed when: the fix needs >10 lines, spans multiple

files, or requires a structural rewrite. In that case the state/regen/drain.sh queue picks it up asynchronously.

"I didn't have time" / "it's minor" / "the next agent will figure it out"

are NOT valid reasons. Minor gaps compound - that's the whole point of this loop.

Concrete example of a valid P-fix: discover agent-browser screenshot

takes path positionally not as --output <path>. One line in a table. Edit it in. Do not just log it.

The goal: the next agent never has to leave the loader.

2. Log the result.

echo "[$(date -u +%FT%TZ)] analytics: <what was missing or fixed> [FIXED|LOGGED]" >> state/log/loader-feedback.log

FIXED = you patched this loader inline (P-fix).
LOGGED = too large for inline; the PostToolUse enqueue + Stop-hook drain

will rewrite the loader from scratch on next session-end.

Do not skip this. Every agent run must leave the system better than it found it. The loader is the setpoint; you are the sensor; the gap is the error signal; closing the gap is the correction.

api.ts- the code it can call

#!/usr/bin/env npx tsx
/**
 * snappy-analytics/api.ts -- Metrics aggregator for all snappy-* skills.
 *
 * Pulls from the content engine DB and synthesizes scorecard data.
 * Terminal consumer skill -- read-only across the system.
 *
 * Usage:
 *   npx tsx api.ts scorecard          # content atom counts by status
 *
 * Or import as module:
 *   import { getScorecard } from "./analytics.ts";
 */

import { env } from "./env.ts";
import { realpathSync } from "fs";

const CONTENT_ENGINE = "https://rb-content-engine.fly.dev/sql";

async function contentEngineQuery(query: string) {
  const res = await fetch(CONTENT_ENGINE, {
    method: "POST",
    headers: { "Content-Type": "application/json" },
    body: JSON.stringify({ query }),
  });
  if (!res.ok) {
    const text = await res.text().catch(() => "");
    throw new Error(`Content engine query failed (${res.status}): ${text}`);
  }
  return res.json();
}

// --- Public API ---

/**
 * Get content pipeline scorecard -- atom counts by status and type.
 */
export async function getScorecard() {
  const [byStatus, byType, recent] = await Promise.all([
    contentEngineQuery("SELECT status, COUNT(*) as count FROM content_atoms GROUP BY status ORDER BY count DESC"),
    contentEngineQuery("SELECT type, status, COUNT(*) as count FROM content_atoms WHERE type IS NOT NULL GROUP BY type, status ORDER BY count DESC"),
    contentEngineQuery("SELECT id, type, topic, status, created_at FROM content_atoms ORDER BY created_at DESC LIMIT 10"),
  ]);

  return { byStatus, byType, recent };
}

// --- CLI ---

if ((() => { try { return import.meta.url === `file://${realpathSync(process.argv[1])}`; } catch { return false; } })()) {
  (async () => {
    const [, , cmd] = process.argv;

    switch (cmd) {
      case "scorecard": {
        const data = await getScorecard();

        console.log("=== CONTENT ATOMS BY STATUS ===");
        if (Array.isArray(data.byStatus)) {
          for (const row of data.byStatus) {
            console.log(`  ${row.status || "null"}: ${row.count}`);
          }
        } else {
          console.log(JSON.stringify(data.byStatus, null, 2));
        }

        console.log("\n=== BY TYPE + STATUS ===");
        if (Array.isArray(data.byType)) {
          for (const row of data.byType) {
            console.log(`  ${row.type || "untyped"} (${row.status}): ${row.count}`);
          }
        } else {
          console.log(JSON.stringify(data.byType, null, 2));
        }

        console.log("\n=== RECENT ATOMS ===");
        if (Array.isArray(data.recent)) {
          for (const row of data.recent) {
            console.log(`  [${row.id}] ${row.type || "untyped"} -- ${row.topic || "(no topic)"} (${row.status}) ${row.created_at}`);
          }
        } else {
          console.log(JSON.stringify(data.recent, null, 2));
        }
        break;
      }
      default:
        console.log("Usage: npx tsx api.ts scorecard");
    }
  })();
}

scripts- helper scripts it can run

prose-only skill - 1 inline code block live in SKILL.md above (no state/bin/ sidecar yet).

how we check it- the checks, plus the last 10 runs

rubric shape schema-shape check (no inline rubric)

recent mean 1.00 · 10 runs actor/auditor: unverifiable

deps settings

timestamp	verb	score	primary_issue	artifact
2026-05-03 13:02Z	-	1.00	-	-
2026-05-02 15:01Z	-	1.00	-	-
2026-05-02 13:01Z	-	1.00	-	-
2026-05-02 07:01Z	-	1.00	-	-
2026-05-01 21:02Z	-	1.00	-	-
2026-05-01 19:02Z	-	1.00	-	-
2026-05-01 15:02Z	-	1.00	-	-
2026-05-01 01:01Z	-	1.00	-	-
2026-04-25 04:11Z	-	1.00	-	-
2026-04-21 15:58Z	-	1.00	-	-