Skip to content
Back to skills

Distill Subject

ASecurity

Distill what a newsletter is ABOUT from its corpus — an evidence-cited read of through-line, topic clusters, lenses (ways of seeing), motifs, audience, boundaries, and formats. Step 4 of the Context Kit (Milestone 1). Run after the corpus is ingested. Use for "distill the subject", "what is this newsletter about", "analyze my archive", "read the corpus".

  • 2 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 27, 2026
ai-agents

Security analysis

A100/100

Scanned September 27, 2026

npx -y skills add Artifacts7/newsletter-context-kit --skill distill-subject --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Distill Subject?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Distill Subject
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/artifacts7-distill-subject/badge)](https://www.skillsdirectory.com/skills/artifacts7-distill-subject)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: distill-subject
description: >
  Distill what a newsletter is ABOUT from its corpus — an evidence-cited read of through-line,
  topic clusters, lenses (ways of seeing), motifs, audience, boundaries, and formats. Step 4 of
  the Context Kit (Milestone 1). Run after the corpus is ingested. Use for "distill the subject",
  "what is this newsletter about", "analyze my archive", "read the corpus".
---

# Distill Subject (step 4)

Produce the agent's own **evidence-backed** read of what the newsletter is about. Sharp and
falsifiable, not generic.

## Precondition
Corpus ingested (`extract-corpus`). Do NOT read the writer's intake/about first (anchoring, Q7).

## Procedure
1. **Scope** the corpus to the current voice era — exclude disowned/other-language issues; recency-weight (Q4). Use the manifest's dates/language.
2. **Read the BODY** of the scoped issues. For a large corpus, dispatch the close-read to a subagent (read `## BODY` only; recency-weight; return structured markdown) rather than loading it all yourself.
3. **Extract along the axes**, filling each with specifics not adjectives: through-line · topic clusters (ranked, ≥2 issue citations each) · lenses (recurring *ways of seeing*, distinct from topics — the highest-value) · motifs/fingerprints (self-coined terms, recurring questions) · audience · boundaries (explicit disavowals) · formats.
4. **Cite or cut** (D11): every claim names the issues that prove it. **Separate topic from lens.** Flag corpus fidelity (D12).
5. **Anti-slop tests** before shipping: substitution (cut anything true of any newsletter) · citation (all claims traceable) · surprise (≥1 latent observation) · disagreement-surface (≥1 gap vs. the stated identity, for step 5).

## Output
`newsletter-context/subject-observed.md` — the structured read + a reconcile preview. → hand to **`reconcile`** (step 5).

---
_**Language:** if the newsletter isn't in English, converse with the writer — and write outputs — in the newsletter's language._

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.