Skill: ivangdavila/fox-news (version 1.0.0)

--- name: Fox News Monitor slug: fox-news version: 1.0.0 homepage: https://clawic.com/skills/fox-news description: Monitor Fox News sections and breaking updates with official RSS routes, live-event tracking, and optional outside verification. changelog: "Initial release with official feed routing, live coverage workflows, and section-based briefing formats for Fox News readers." metadata: {"clawdbot":{"emoji":"F","requires":{"bins":["curl"],"anyBins":["python3","python"],"config":["~/fox-news/"]},"os":["linux","darwin","win32"],"configPaths":["~/fox-news/"]}} --- ## Setup On first use, follow `setup.md` to lock activation scope, preferred sections, and whether the user wants Fox-only reads or source-balanced follow-up. ## When to Use User explicitly wants Fox News coverage, Fox News section monitoring, headline summaries from Fox-owned properties, or a Fox-first briefing with optional outside verification. Use this skill for section routing, official RSS sweeps, live-event follow-through, clip/article packaging, and concise recaps that keep reporting and opinion clearly separated. ## Requirements - Web access for current headlines and live coverage. - Clear user intent when opening multiple articles, clips, or rolling live updates. - Explicit permission before saving recurring preferences under `~/fox-news/`. ## Architecture Memory lives in `~/fox-news/`. See `memory-template.md` for the baseline structure. ```text ~/fox-news/ ├── memory.md # Activation scope, preferred sections, and balance defaults ├── sources.md # Approved Fox surfaces and section notes ├── runs.md # Fetch timestamps, live-event notes, and follow-up history └── briefs/ # Saved briefings when the user asks to archive them ``` ## Quick Reference | Topic | File | |-------|------| | Setup and activation behavior | `setup.md` | | Memory schema and status rules | `memory-template.md` | | Official feeds and section mapping | `feed-map.md` | | Repeatable fetch and briefing workflows | `workflow-patterns.md` | | Output shapes for fast or balanced summaries | `briefing-formats.md` | | Recovery paths for broken links or gated streams | `troubleshooting.md` | ## Data Storage Local notes in `~/fox-news/` may include: - preferred sections such as politics, U.S., world, business, opinion, or video - whether the user wants Fox-only output or a Fox-first summary with outside corroboration - recency expectations for breaking coverage versus recap mode - archived briefings only when the user asks to keep them ## Core Rules ### 1. Route Every Request to One Fox Surface First - Map the request to one primary surface before fetching: homepage, section feed, live page, video page, or opinion page. - Starting with one surface keeps the result focused and avoids mixing unrelated Fox News products. ### 2. Separate Reporting, Live Coverage, Video, and Opinion - Label each item by surface type before summarizing it. - Do not mix straight-news headlines with opinion pieces unless the user explicitly asks for both in one briefing. ### 3. Timestamp Everything That Claims Freshness - For every headline or clip, include when it was published or last updated when that information is available. - If a story is older than the requested window, label it as recap or background rather than presenting it as breaking. ### 4. Use Fox-Owned Sources First, Then Balance When Needed - Start with official Fox News pages and RSS feeds for Fox-specific requests. - If the user asks for analysis, controversy review, or credibility checking, add at least one independent confirmation and state that it is follow-up context beyond Fox coverage. ### 5. Confirm High-Volume Reads Before Opening or Pulling - Preview the sections, feeds, or number of links before opening many tabs or preparing a broad sweep. - Require explicit confirmation before opening multiple articles, clips, or rolling updates in one step. ### 6. Respect Access Boundaries - Do not request account passwords, TV-provider credentials, or Fox Nation credentials in chat. - If a live stream or full episode is gated, state the access boundary and fall back to public headlines, clips, or article coverage. ### 7. Persist Only Reusable Preferences - Save only durable context such as favored sections, briefing depth, and balance preference. - Do not save full article bodies or transient story details unless the user explicitly asks for an archive. ## Common Traps - Treating opinion headlines as straight reporting -> users get a distorted briefing. - Mixing stale recap items into "latest" coverage -> trust drops quickly. - Opening many Fox tabs without preview -> noisy and hard to recover from. - Assuming live TV access exists -> unnecessary dead ends when public article coverage is enough. - Giving outside analysis without labeling it as follow-up context -> scope becomes unclear. ## External Endpoints | Endpoint | Data Sent | Purpose | |----------|-----------|---------| | https://www.foxnews.com | Section paths, article URLs, and optional on-site search terms | Read current Fox News headlines, sections, live pages, and article details | | https://moxie.foxnews.com | RSS feed URLs only | Fetch official Fox News XML feeds for deterministic section sweeps | | https://help.foxnews.com | Help article URLs only | Confirm device support, app behavior, and access constraints when troubleshooting | No other data should be sent externally unless the user explicitly asks for non-Fox follow-up sources. ## Security & Privacy Data that may leave your machine: - HTTP requests to Fox News web pages, RSS feeds, and help pages - optional on-site search terms if the user asks for a Fox-site search workflow Data that stays local: - activation scope, preferred sections, and briefing defaults in `~/fox-news/` - fetch history and saved briefings only when the user wants them stored This skill does NOT: - collect or store Fox account credentials - bypass paywalls, TV-provider gates, or Fox Nation restrictions - post, share, or interact with social platforms automatically - access files outside `~/fox-news/` ## Trust This skill relies on Fox News-owned properties and may surface editorial positions from Fox reporting, live pages, and opinion products. Only install it if you want Fox-specific workflows and trust Fox as one of your news sources. ## Related Skills Install with `clawhub install <slug>` if user confirms: - `news` - General news briefings and preference-aware coverage beyond one outlet. - `digest` - Turn multiple reads into concise digests when Fox is only one input. - `monitoring` - Track recurring topics or entities across repeated checks. - `reading` - Manage reading order, queues, and follow-up decisions after a sweep. - `summarizer` - Compress long Fox articles or transcripts into tighter takeaways. ## Feedback - If useful: `clawhub star fox-news` - Stay updated: `clawhub sync`

path: briefing-formats.md
content: # Briefing Formats - Fox News Desk

## Quick Headlines

Use when the user wants a fast scan.

```text
FOX NEWS QUICK SCAN

1. [Headline] - [one-sentence summary]
   Surface: Latest | Updated: [time]

2. [Headline] - [one-sentence summary]
   Surface: Politics | Updated: [time]

3. [Headline] - [one-sentence summary]
   Surface: World | Updated: [time]
```

Rules:
- Maximum 5 items
- One sentence each
- Include surface and time
- Do not mix opinion unless requested

## Standard Fox Briefing

Use for a fuller Fox-specific read.

```text
FOX NEWS BRIEFING

TOPLINE
- What changed in the last [window]

HEADLINES
1. [Headline]
   Surface: [latest/politics/world/live]
   Why it matters: [1-2 sentences]

2. [Headline]
   Surface: [latest/politics/world/live]
   Why it matters: [1-2 sentences]

FOLLOW-UP
- Ask for a deeper read, live watch, or outside verification
```

Rules:
- Maximum 7 items
- Keep article summaries tighter than analysis
- Label every item by surface

## Balanced Follow-Up

Use only when the user asks for context beyond Fox coverage.

```text
FOX-FIRST WITH OUTSIDE VERIFICATION

FOX COVERAGE
- [Fox summary]

OUTSIDE CHECK
- [Independent source summary]

TAKEAWAY
- Where they align, differ, or leave uncertainty
```

Rules:
- Start with Fox coverage because that is the requested source
- Add outside context only as a separate block
- Never blur source boundaries

## Live Event Update

Use for active stories that keep changing.

```text
FOX LIVE UPDATE

Latest update seen: [time]
Current state: [1-2 sentences]
New since last check:
- [change 1]
- [change 2]

Open questions:
- [uncertainty or next check trigger]
```

Rules:
- Say when the last live update was seen
- Avoid over-summarizing if the page is still moving quickly
- Offer a next check time if the user wants monitoring


path: feed-map.md
content: # Feed Map - Fox News Desk

Use official Fox-owned surfaces first.

## Primary Surfaces

| Surface | URL | Use When | Notes |
|---------|-----|----------|-------|
| Latest feed | `https://moxie.foxnews.com/google-publisher/latest.xml` | User wants a fast top-line sweep | Broadest Fox headline mix |
| Politics feed | `https://moxie.foxnews.com/google-publisher/politics.xml` | Politics-specific monitoring | Better than homepage filtering |
| U.S. page | `https://www.foxnews.com/us` | Domestic news requests | Use page routing when RSS is too broad |
| World page | `https://www.foxnews.com/world` | International coverage | Use before general search |
| Opinion page | `https://www.foxnews.com/opinion` | User explicitly wants columnist or editorial coverage | Keep separate from straight-news summaries |
| Video page | `https://www.foxnews.com/video` | User wants clips, segments, or show highlights | Good fallback when live TV is gated |
| Live page | `https://www.foxnews.com/live-news` | Ongoing events and rolling updates | Best for fast-changing stories |
| Apps and products | `https://www.foxnews.com/apps-products/index.html` | App or device workflow questions | Use with help pages for support checks |

## Routing Rules

1. Use one surface first, not three at once.
2. Prefer RSS for deterministic headline capture and page routes for live or editorial context.
3. Keep `opinion` and `video` requests explicit so they do not leak into general briefings.

## Fast Shell Checks

When shell access is available, these are the fastest low-risk probes:

```bash
curl -s https://moxie.foxnews.com/google-publisher/latest.xml | head
curl -s https://moxie.foxnews.com/google-publisher/politics.xml | head
curl -s https://www.foxnews.com/live-news | head
```

For quick title extraction from RSS:

```bash
python3 - <<'PY'
import xml.etree.ElementTree as ET
import urllib.request

url = "https://moxie.foxnews.com/google-publisher/latest.xml"
root = ET.fromstring(urllib.request.urlopen(url).read())
for item in root.findall(".//item")[:5]:
    print(item.findtext("title", "").strip())
PY
```

Use commands only to inspect public pages and feeds. Do not automate credentialed playback or account flows.


path: memory-template.md
content: # Memory Template - Fox News Monitor

Create `~/fox-news/memory.md` with this structure:

```markdown
# Fox News Monitor Memory

## Status
status: ongoing
version: 1.0.0
last: YYYY-MM-DD
integration: pending

## Context
- When this skill should activate automatically
- Preferred Fox sections and topics
- Preferred briefing depth and recency window

## Coverage Defaults
- Fox-only or Fox-first plus outside corroboration
- Opinion included only on request or allowed by default
- Live coverage preference versus recap preference

## Safety Defaults
- Confirmation required before multiple opens: yes/no
- Save archived briefings when requested: yes/no
- Outside verification required for contested stories: yes/no

## Notes
- Repeated section preferences inferred from usage
- Known source constraints, broken paths, or access limits
- Proven briefing patterns that worked well

---
*Updated: YYYY-MM-DD*
```

## Status Values

| Value | Meaning | Behavior |
|-------|---------|----------|
| `ongoing` | Preferences are still evolving | Keep learning while delivering answers |
| `complete` | Defaults are stable | Use saved preferences with minimal extra questions |
| `paused` | User wants fewer setup questions | Operate with explicit requests only |
| `never_ask` | User asked to stop setup prompts | Do not probe for more defaults |

## Rules

- Keep notes in natural language outside the required status fields.
- Update `last` whenever section defaults, safety defaults, or balance preferences change.
- Save durable patterns, not one-off headlines.
- Never remove prior notes without explicit user instruction.


path: setup.md
content: # Setup - Fox News Monitor

If `~/fox-news/` does not exist or is empty, start with transparent onboarding. Explain which local files can be created, why they help, and ask for confirmation before writing.

## Your Attitude

Be current-aware, source-explicit, and calm. Keep the workflow Fox-specific without becoming credulous, and answer the user's question first before asking optional preference questions.

## Priority Order

### 1. First: Integration Preference

Early in the conversation, clarify activation behavior:
- Should this skill activate whenever the user explicitly asks for Fox News?
- Should it stay narrow to Fox-only output, or is Fox-first plus outside verification preferred?
- Should opinion content stay excluded unless explicitly requested?

### 2. Then: Coverage Shape

Establish what is most useful right now:
- Preferred sections such as latest, politics, U.S., world, business, opinion, or video
- Preferred output depth: quick headlines, standard briefing, or deeper follow-up
- Whether live-event monitoring is wanted or article recap is enough

### 3. Finally: Safety and Storage Defaults

If the user wants persistent behavior, capture:
- Whether multi-link opens always require confirmation
- Whether archived briefings should be saved locally when requested
- Whether outside corroboration is the default on contested topics

If the user wants speed, keep conservative defaults and use explicit confirmation for high-volume actions.

## What You Are Saving Internally

Track only durable operational context:
- activation scope and when to use the skill automatically
- favorite sections and briefing depth
- Fox-only versus balanced follow-up preference
- known live-coverage limits, gated surfaces, and proven fallbacks

After memory updates, summarize the change in plain language so the user can correct it immediately.


path: troubleshooting.md
content: # Troubleshooting - Fox News Desk

## RSS Feed Is Slow or Empty

Symptoms:
- Feed returns stale items or no visible headlines.

Actions:
1. Fall back to the matching section page on `foxnews.com`.
2. Compare latest feed against the section page before claiming nothing changed.
3. Label the result as a page-based read instead of an RSS sweep.

## Live Coverage Is Gated or Not Useful

Symptoms:
- Live stream asks for a provider login or the page is video-heavy without enough text.

Actions:
1. Use `live-news` article coverage first.
2. Fall back to `video` clips or the closest section article.
3. State the access boundary instead of pushing credentialed playback.

## Opinion and News Keep Mixing

Symptoms:
- Search results or homepage links include opinion content in a straight-news request.

Actions:
1. Re-route to the specific section feed or page.
2. Exclude `opinion` unless the user asked for it.
3. Relabel any ambiguous item before keeping it in the briefing.

## Story Feels Too One-Sided

Symptoms:
- The user wants analysis, controversy review, or credibility checking.

Actions:
1. Keep the Fox summary as the first block.
2. Add one or more independent follow-up sources as a separate block.
3. State clearly where the extra context came from and why it was added.


path: workflow-patterns.md
content: # Workflow Patterns - Fox News Desk

Use these patterns to keep Fox-specific work focused and auditable.

## Section Sweep

1. Confirm which section matters most.
2. Pull one official feed or section page.
3. Return 3-7 items with timestamps and surface labels.
4. Offer follow-up only for the items the user selects.

## Breaking Event Follow-Through

1. Start with `live-news` if the event is still moving.
2. Note the latest update time before summarizing.
3. If the user wants context, add the nearest section page or one related article.
4. If the claim is contested, add at least one independent follow-up source and label it clearly as outside verification.

## Opinion or Host-Focused Read

1. Confirm the user wants opinion, host commentary, or show clips rather than straight reporting.
2. Route to `opinion` or `video`, not the general latest feed.
3. Label the output as opinion, segment, or commentary before summarizing.

## Multi-Link Handling

1. Show the candidate links with section labels.
2. Ask the user to choose one, or confirm opening several.
3. Require explicit confirmation before opening more than one link.
4. Report exactly what was opened or fetched.

## App and Device Support

1. Use the apps/products page for official product entry points.
2. Use help pages to confirm supported devices, login expectations, or playback limitations.
3. If playback is gated, pivot to public clips or written coverage instead of pushing credentials.


Security scan verdicts — ClawScan: suspicious | static analysis: clean | VirusTotal: clean | SkillSpector: clean (LOW)