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

publish

Publishes your written content to your site.

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

personal 2 files 10 recent evals

Export

What it does for you

Publishes your written content to your site.

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/publish.ts.

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

eval modeshape

categoryContent

stages1

dependsdrafts

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/publish/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/publish.ts present

code the skill can run

Reusable code this skill can call when it needs to.

Scripts

state/bin/publish/ not present

helper scripts

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

Loader

state/skills/publish/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 · 3 deterministic · 1 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

check_deploy_status_executes

deterministic

The checkDeployStatus() function must execute without unhandled exceptions when provided with checkDeployStatus_input.

get_recent_deploys_executes

deterministic

The getRecentDeploys() function must execute without unhandled exceptions when provided with getRecentDeploys_input.

pending_eval_log_entry_created

deterministic

A new row must be appended to state/log/pending-eval.ndjson for each skill execution.

output_reflects_publish_ts_api

judge

The output of checkDeployStatus() and getRecentDeploys() must accurately reflect the behavior defined in state/lib/publish.ts.

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/publish.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 treat deploy status as scope-only by default. There is no apply path here; this lib reads, doesn't write.
ALWAYS distinguish from publish-bootstrap — that one publishes the npm package; this one is for MDX deploys.

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 drafts

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

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

1 data

eval log

`state/log/pending-eval.ndjson` (skill: "publish") — manual until auditor wired

+ eval for this step

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

publish

Git-based MDX publishing operations for all snappy-* skills.

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

Steps

checkDeployStatus() - see state/lib/publish.ts
getRecentDeploys() - see state/lib/publish.ts

Eval

Actor: the exported functions in state/lib/publish.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: check_deploy_status_executes
    kind: deterministic
    check: "The checkDeployStatus() function must execute without unhandled exceptions when provided with checkDeployStatus_input."
  - name: get_recent_deploys_executes
    kind: deterministic
    check: "The getRecentDeploys() function must execute without unhandled exceptions when provided with getRecentDeploys_input."
  - name: pending_eval_log_entry_created
    kind: deterministic
    check: "A new row must be appended to state/log/pending-eval.ndjson for each skill execution."
  - name: output_reflects_publish_ts_api
    kind: judge
    check: "The output of checkDeployStatus() and getRecentDeploys() must accurately reflect the behavior defined in state/lib/publish.ts."

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

publish - loader

Per-turn rules for the publish skill. Full reference: state/skills/publish/SKILL.md.

Critical Rules

_(no failures recorded yet - this skill has not produced hard-won rules. Read state/skills/publish/SKILL.md before invoking, and verify deploys via independent fetch - the actor != auditor rule applies to deploy status too.)_

ALWAYS treat deploy status as scope-only by default. There is no apply path here; this lib reads, doesn't write.
ALWAYS distinguish from publish-bootstrap - that one publishes the npm package; this one is for MDX deploys.

Commands

| ui dashboard | state/skills/publish/resources/ui.openui | |invoke (TS): import { checkDeployStatus, getRecentDeploys } from "../lib/publish.ts" |eval log: state/log/pending-eval.ndjson (skill: "publish") - manual until auditor wired

OpenUI Resource

Skill-owned OpenUI Lang resource: state/skills/publish/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

The skill .md is a Phase 0.5 port stub; full behavior detail lives in state/lib/publish.ts. Read the lib source before assuming behavior.

Self-Test

An agent reading this should correctly:

[ ] Distinguish publish from publish-bootstrap
[ ] Read state/lib/publish.ts for the actual API surface
[ ] Log to pending-eval.ndjson since this is manual-eval

Self-report

If this loader fell short, append a line:

echo "[$(date -u +%FT%TZ)] publish: <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)] publish: <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-publish/api.ts -- Git-based MDX publishing operations for all snappy-* skills.
 *
 * Usage:
 *   npx tsx api.ts status <slug>           # check if blog post is live (HTTP status)
 *   npx tsx api.ts deploys                 # list recent Vercel deployments
 *
 * Or import as module:
 *   import { checkDeployStatus, getRecentDeploys } from "./publish.ts";
 */

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

const SITE_URL = "https://snappy.ai";
const VERCEL_API = "https://api.vercel.com";

interface DeployStatus {
  slug: string;
  url: string;
  status: number;
  ok: boolean;
}

interface VercelDeployment {
  uid: string;
  url: string;
  state: string;
  created: string;
  readyState: string;
}

/** Checks if a blog post is live by HTTP GET. Returns status code. */
export async function checkDeployStatus(slug: string): Promise<DeployStatus> {
  const url = `${SITE_URL}/blog/${slug}`;
  try {
    const res = await fetch(url, { method: "GET", redirect: "follow" });
    return { slug, url, status: res.status, ok: res.ok };
  } catch (err: any) {
    return { slug, url, status: 0, ok: false };
  }
}

/** Lists recent Vercel deployments for the snappy-website project. */
export async function getRecentDeploys(limit = 10): Promise<VercelDeployment[]> {
  const token = env("VERCEL_TOKEN");
  const res = await fetch(`${VERCEL_API}/v6/deployments?limit=${limit}&projectId=snappy-website`, {
    headers: { Authorization: `Bearer ${token}` },
  });
  if (!res.ok) {
    const body = await res.text();
    throw new Error(`Vercel API ${res.status}: ${body}`);
  }
  const data = await res.json();
  return (data.deployments ?? []).map((d: any) => ({
    uid: d.uid,
    url: d.url,
    state: d.state,
    created: new Date(d.created).toISOString(),
    readyState: d.readyState,
  }));
}

// --- CLI ---

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

    switch (cmd) {
      case "status": {
        const [slug] = args;
        if (!slug) { console.error("Usage: api.ts status <slug>"); process.exit(1); }
        const result = await checkDeployStatus(slug);
        console.log(`${result.url} -> ${result.status} ${result.ok ? "OK" : "FAIL"}`);
        break;
      }
      case "deploys": {
        const deploys = await getRecentDeploys();
        console.log(`${deploys.length} recent deployments:`);
        for (const d of deploys) {
          console.log(`  ${d.created}\t${d.state}\t${d.readyState}\t${d.url}`);
        }
        break;
      }
      default:
        console.log("Usage: npx tsx api.ts [status|deploys] ...");
    }
  })();
}

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 0.90 · 10 runs actor/auditor: unverifiable

deps drafts

timestamp	verb	score	primary_issue	artifact
2026-04-26 23:47Z	-	0.50	-	-
2026-04-25 04:11Z	-	1.00	-	-
2026-04-21 15:58Z	-	1.00	-	-
2026-04-21 15:57Z	-	1.00	-	-
2026-04-21 03:53Z	-	1.00	-	-
2026-04-18 20:36Z	-	1.00	-	-
2026-04-26 23:47Z	-	0.50	-	-
2026-04-25 04:11Z	-	1.00	-	-
2026-04-21 15:58Z	-	1.00	-	-
2026-04-21 15:57Z	-	1.00	-	-