OR Key
drop another .md file to compare - side-by-side diff against weekly-newsletter-draft

weekly-newsletter-draft

Drafts your weekly team update from the past week's activity.
personal 2 files
Export

What it does for you

Drafts your weekly team update from the past week's activity.

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

eval modemanual

what's inside - the parts that make up a skill 2/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/weekly-newsletter-draft/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/weekly-newsletter-draft.ts not present
code the skill can run
Optional. Many skills are just words and need no code at all.
Scripts
state/bin/weekly-newsletter-draft/ not present
helper scripts
Optional. Added when a skill has a few commands to run.
Loader
state/skills/weekly-newsletter-draft/AGENTS.md present
what the AI loads on the fly
Loaded automatically the moment this skill is needed. Kept short on purpose.

how it runs - the shared frame every skill uses 4/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
not present

No work step here. This is probably a skill that reads or coordinates, not one that produces something.

checks the work The reviewer
present
Robert (weekly review) reviewed by hand
No automatic check. Robert reviews these by hand. The part that made it still isn't the part that approves it.
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 manual runs
Every run is written down here, then reviewed by hand each week.
Critical rules the things this skill must not get wrong
No must-not-break rules called out for this skill. Anything important lives in the writeup below.

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.

  1. Loading feedback rows…

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

Purpose

This skill creates a summarized, human-readable weekly changelog/newsletter based on the eval activity from the past week.

Usage

Run this at the end of each week. It will read state/log/evals.ndjson and construct a 4-section markdown summary.

Steps

  1. Read and parse all rows from state/log/evals.ndjson whose timestamp is within the past 7 days.
  2. Organize notable events, changes, or activity spikes by skill, type, or theme.
  3. Draft a markdown newsletter with 4 distinct sections (suggested: Highlights, System Changes, Notable Bugs/Fixes, Interesting Metrics).
  4. Output the completed markdown for team review.

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

weekly-newsletter-draft - Loader

This AGENTS.md loader is required for all snappy-os skills.

Purpose: Draft a markdown-format weekly progress newsletter by pulling evals from the last 7 days in state/log/evals.ndjson, organizing them into 4 meaningful sections, and outputting a ready-to-share summary.

How to execute: Follow the Steps in SKILL.md.

Quick brief:

  • Reads all evals.ndjson from state/log in the last 7 days
  • Groups and summarizes by activity, system changes, fixes, and notable trends
  • Outputs a markdown doc for forwarding

_No further implementation is needed in this loader; the skill runs via the declarative Steps._

<!-- kernel-ok: PiD self-correcting loader footer -->

Self-correcting loader (PID feedback)

Before you finish, log the result:

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

api.ts- the code it can call

⚠ no api.ts - this skill has no typed action surface

scripts- helper scripts it can run

prose-only skill - no sidecar under state/bin/ yet. Steps, if any, are described in SKILL.md.

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

rubric manual manual Robert review - no automated rubric
recent no runs actor/auditor: unverifiable
deps none declared

no recent runs logged - the eval contract is declared but nothing has been graded yet