Skip to content
Back to skills

News

ASecurity

Personalized news briefings that learn your interests, formats, and timing preferences.

  • 7 stars
  • 0 votes
  • 0 copies
  • 3 views
  • Added June 7, 2026
documentationrustgosecurity

Security analysis

A100/100

Scanned June 7, 2026

npx -y skills add modbender/skill-library-mcp --skill news --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of News?

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

Security grade badge for News
[![Security: A β€” Skills Directory](https://www.skillsdirectory.com/api/skills/modbender-news/badge)](https://www.skillsdirectory.com/skills/modbender-news)

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: News
slug: news
version: 1.0.1
homepage: https://clawic.com/skills/news
description: Personalized news briefings that learn your interests, formats, and timing preferences.
metadata: {"clawdbot":{"emoji":"πŸ“°","os":["linux","darwin","win32"]}}
changelog: Added structure with Core Rules and memory system
---

## When to Use

User wants personalized news briefings. Agent builds a news profile, delivers formatted briefings, learns interests over time, and handles multi-source coverage.

## Architecture

Memory lives in `~/news/`. See `memory-template.md` for setup.

```
~/news/
β”œβ”€β”€ memory.md       # Profile: interests, format, timing
β”œβ”€β”€ history.md      # Past briefings and engagement
└── sources.md      # Trusted sources and biases
```

## Quick Reference

| Topic | File |
|-------|------|
| Memory setup | `memory-template.md` |

## Core Rules

### 1. Build Profile Before Delivering
On first interaction, ask about:
- Specific interests (not generic categories)
- Proportions if multiple interests ("70% AI, 30% markets")
- Format preference (bullets, narrative, headlines-only)
- Timing (morning, evening, weekly, on-demand)

### 2. Check Memory First
Before every briefing, read `~/news/memory.md` for user preferences. Tailor content to their stated interests and format.

### 3. Facts First, Analysis Second
Lead with what happened before why it matters. Always include when news broke. Cite sources by name.

### 4. Multi-Source on Contested Topics
Present at least 2 sources when covering controversy. Note when sources disagree. State editorial leanings when relevant.

### 5. Never Fabricate
If uncertain whether something happened, say so. Never assume or invent news events.

### 6. Update Memory from Engagement
Track which stories user engages with vs skips. Periodically suggest profile adjustments based on patterns.

## Common Traps

- Presenting stale news as fresh β†’ destroys trust
- Single-source on controversy β†’ reckless reporting
- Generic categories ("tech") β†’ ask for specifics ("AI startups")
- Overwhelming with items β†’ morning briefings max 5-7 items

## Security & Privacy

**Data that stays local:**
- User preferences in `~/news/`
- Engagement history in `~/news/history.md`

**This skill does NOT:**
- Send data to external services
- Access files outside `~/news/`
- Store news content permanently

## Related Skills
Install with `clawhub install <slug>` if user confirms:
- `summarizer` β€” condense long articles
- `scrape` β€” extract web content
- `reading` β€” reading lists and tracking

## Feedback

- If useful: `clawhub star news`
- Stay updated: `clawhub sync`

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…