CtrlK
BlogDocsLog inGet started
Tessl Logo

neomatrix369/content-distiller

Extract actionable insights and valuable artifacts from web posts, articles, and technical documentation. Use when summarizing content, extracting key ideas from URLs/articles, preserving code snippets and diagrams, or creating visual summaries. Triggers on requests like "summarize this post", "extract insights from", "distill this article", "what are the key takeaways", or when a URL is shared for analysis.

97

1.25x

Quality

100%

Does it follow best practices?

Impact

94%

1.25x

Average score across 5 eval scenarios

Overview
Skills
Evals
Files
name:
content-distiller
description:
Extract actionable insights and valuable artifacts from web posts, articles, and technical documentation. Use when summarizing content, extracting key ideas from URLs/articles, preserving code snippets and diagrams, or creating visual summaries. Triggers on requests like "summarize this post", "extract insights from", "distill this article", "what are the key takeaways", or when a URL is shared for analysis.
license:
MIT
metadata:
{"version":"0.2.0","audience":"developers-and-technical-pms","focus":"actionable-extraction"}

Content Distiller

Extract value from content using MoSCoW priority system. Match output density to content density.

Usage

When given content (URL, article, or pasted text), analyze and extract using this structure:

🔴 MUST — Always Include

🎯 CORE THESIS

One sentence — the big idea.

💡 TOP INSIGHTS (3-5 max)

  1. [Insight] — Why it matters: [one line]
  2. [Insight] — Why it matters: [one line]
  3. [Insight] — Why it matters: [one line]

⚡ IMMEDIATE TAKEAWAYS

What can be applied right now?


🟡 SHOULD — Include Only If Present

📦 CODE & CONFIG

Preserve exactly, copy-paste ready:

[Purpose in 5 words]

[Full code — never truncate]

⚠️ Requires: [dependencies/setup] 💬 Key insight: [what's non-obvious]

📊 DIAGRAMS

Use Animated SVG when:

  • Sequential process needs temporal clarity (API request→processing→response)
  • Cause-and-effect relationships drive understanding (event triggers cascade)
  • Before/after states show transformation impact
  • Multiple layers/stages revealed progressively reduce cognitive load
  • Animation patterns: fade-in sequence, highlighting flows, state transitions, progressive layering

Use Mermaid for:

  • Static relationships (class hierarchies, entity relationships)
  • Architecture overviews without temporal dimension
  • Simple flowcharts where flow is self-evident
  • Standard diagrams (UML, ERD, network topology)

Choose based on: Does animation clarify causality, sequence, or impact? If static conveys it, use Mermaid.

📈 DATA & BENCHMARKS

WhatValueSignificance

🟢 COULD — Include If Notably Valuable

  • 🧠 Mental Model: [Framework]: [One-line explanation]
  • 📌 Quotable: One memorable quote
  • 🐛 Gotcha: Common mistake or caveat
  • ❓ Follow-up: Question for further exploration

⚫ WON'T — Skip Unless Requested

  • Full article recap/paraphrasing
  • Author bio or background
  • Tangential references
  • SEO filler content

Output Rules

  1. Adaptive length: Simple post → 🔴 only. Technical → 🔴 + 🟡. Deep dive → all sections.
  2. Omit empty sections: No headers for sections without content.
  3. Visual hierarchy: Use dividers and emoji for scanning.
  4. Concise: Each insight ≤ 2 lines.
  5. Code fidelity: Complete, copy-paste ready.
  6. Diagrams: Animated SVG for temporal/causal clarity (sequences, transformations, cascades), Mermaid for static structures (architecture, relationships), or ASCII (simple visuals). Prioritize understanding over decoration.
  7. No fluff: Bold key terms only. No filler phrases.

Install with Tessl CLI

npx tessl i neomatrix369/content-distiller
Workspace
neomatrix369
Visibility
Public
Created
Last updated
Publish Source
CLI
Badge
neomatrix369/content-distiller badge