Summarize Signal

Given a candidate item from the substacker Trend Scout fetch, WebFetches the full post or arXiv abstract and produces a one-line "teaches X" summary plus signal_type classification (mechanism / empirical / tool / opinion / announcement / benchmark). Distinguishes teaching-content from capability-announcement explicitly. Use during the weekly run, after fetching and before ranking. Trigger keywords — summarize, signal type, mechanism vs announcement, teaching content.

200 stars 25 forksWriting & Content Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add lyndonkl/claude

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add lyndonkl/claude --skill summarize-signal
Manual install
git clone --depth 1 https://github.com/lyndonkl/claude.git /tmp/claude
mkdir -p ~/.claude/skills
cp -r /tmp/claude/skills/summarize-signal ~/.claude/skills/summarize-signal

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Summarize Signal

## Workflow

```
Per candidate item:
- [ ] Step 1: WebFetch the URL; ask: "Extract the core argument in 300 words. What mechanism does this teach? Is there a diagram/analogy? Is this a capability announcement?"
- [ ] Step 2: Classify signal_type: mechanism | empirical | tool | opinion | announcement | benchmark
- [ ] Step 3: Classify intuition_density: high (diagram + analogy + worked example) | medium | low (prose-only announcement)
- [ ] Step 4: Compose one-line summary framed as "teaches that X" or "shows that Y"
- [ ] Step 5: Voice-check the summary against voice-profile don'ts
```

## Signal type taxonomy

- **mechanism**: teaches HOW something works (attention heads, routing, retrieval)
- **empirical**: reports a measurement/experiment (benchmark diff, ablation result)
- **tool**: introduces or reviews a specific tool/library
- **opinion**: position piece, no new data
- **announcement**: capability release, model drop, version bump — no mechanism
- **benchmark**: leaderboard update, SOTA claim without teaching

## Output per item

Appends to candidate record:

```json
{
  "summary": "Teaches that X",
  "signal_type": "mechanism",
  "intuition_density": "high",
  "teaches_mechanism": true,
  "full_text_excerpt_300w": "..."
}
```

## Guardrails

1. One WebFetch per item. Fetch failure → `summary: "FETCH_FAILED"` and let ranker drop.
2. Never hallucinate a mechanism. If the post doesn't teach one, say so explicitly.
Read the full skill on GitHub

Details

Skill name
summarize-signal
Path
skills/summarize-signal/SKILL.md
Repo updated
1 September 2026

FAQ

What does the Summarize Signal skill do?

Given a candidate item from the substacker Trend Scout fetch, WebFetches the full post or arXiv abstract and produces a one-line "teaches X" summary plus signal_type classification (mechanism / empirical / tool / opinion / announcement / benchmark). Distinguishes teaching-content from capability-announcement explicitly. Use during the weekly run, after fetching and before ranking. Trigger keywords — summarize, signal type, mechanism vs announcement, teaching content.

How do I install the Summarize Signal skill?

Claude Code plugin: /plugin marketplace add lyndonkl/claude. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Summarize Signal popular?

It lives in lyndonkl/claude, which has 200 GitHub stars and 25 forks.

Related skills

Abstraction Concrete Examples

200

lyndonkl/claude

Builds structured abstraction ladders that translate high-level principles into concrete, actionable examples across 3-5 levels. Bridges communication gaps, reveals hidden assumptions, and tests whether abstract ideas work in practice. Use when explaining concepts at different expertise levels, moving between abstract principles and concrete implementation, identifying edge cases by testing ideas against scenarios, designing layered documentation, decomposing complex problems into actionable steps, or bridging strategy-execution gaps.

Testing & QA25

Academic Letter Architect

200

lyndonkl/claude

Guides the creation of evidence-based academic recommendation letters, reference letters, and award nominations that combine concrete examples, meaningful comparisons, and genuine enthusiasm. Use when writing recommendation letters for students, postdocs, or colleagues, or when user mentions recommendation letter, reference, nomination, letter of support, endorsement, or needs help with strong advocacy and comparative statements.

Research & Science25

Adr Architecture

200

lyndonkl/claude

Documents significant architectural and technical decisions with full context, alternatives considered, trade-offs analyzed, and consequences understood. Creates a decision trail that helps teams understand why decisions were made. Use when choosing between technology options, making infrastructure decisions, establishing standards, migrating systems, or when user mentions ADR, architecture decision, technical decision record, or decision documentation.

Software Development25

Sweep Stale Seeds

200

lyndonkl/claude

Identifies substacker seeds older than 30 days with status=seed and no incoming related_seeds links, flags them for writer review, and recommends keep / promote-to-draft / kill based on density score. Does NOT auto-execute any action. Emits a review list to ops/librarian/YYYY-MM-DD-stale-sweep.md. Run at session start after ingest, once per day max. Trigger keywords — stale, sweep, review, old seeds, cleanup, gardener, corpus hygiene.

Writing & Content25

Structural Review

200

lyndonkl/claude

Performs pass-1 structural review of a substacker essay draft — argument flow, out-of-order moves, buried topic sentences, missing pivots, weak signposting, paragraph-logic issues. Emits the "Argument flow" and "Structural blockers" sections of the Editor artifact. Use when reviewing a draft's macro-structure before addressing voice, when a draft feels like it meanders, or when the user asks whether the argument lands. Trigger keywords — structure, argument flow, outline, signposting, meandering, pivot, macro edit, substantive edit.

Writing & Content25

Translation Reframing Audience Shift

200

lyndonkl/claude

Adapts content for different audiences while preserving core accuracy, changing tone, depth, emphasis, and framing to match audience expertise and goals. Use when technical content needs business framing, strategic vision needs tactical translation, expert knowledge needs simplification, formal content needs casual tone, long-form needs summarization, internal content needs external framing, or cross-cultural adaptation is needed. Use when user mentions "explain to", "reframe for", "translate for [audience]", "adapt for [executives/engineers/customers]", or "same content, different audience".

Writing & Content25

Browse the most popular Claude skills, all writing & content skills, or write your own with the skills generator.