naver-news-briefing

Use the CLI script at scripts/naver_news_briefing.py.

Onboarding

• - Treat Naver Search API credentials as mandatory before the first real use.
• Tell the user early that search/briefing/watch flows will fail until client_id and client_secret are stored.
• If the user has not completed setup yet, direct them to run:

• - Present setup as the first-run path, not an optional advanced step.
• When helping with installation or first use, mention that credentials are stored in data/config.json and use DPAPI-backed secret storage on Windows when possible.

Workflow

1. 1. Store credentials once before any search/brief/watch command.

1. 2. Run a one-shot briefing.

1. 3. Manage persistent watch rules with optional operator metadata.

1. 4. Manage persistent keyword groups for recurring briefings.

1. 5. Run combined briefings.

1. 6. Convert chat-style automation requests into structured plans.

1. 7. Materialize plans into persistent configs.

Behavior

• - Parse positive keywords and -제외어 using the upstream tab-search policy.
• Interpret recent-news phrases such as 오늘, 최근 3일, 최근 2주, 한달, 이번주, 지난주 as a date window and remove that phrase from the API search query.
• Normalize more natural Korean sentence inputs by stripping request phrases, common 조사, duplicate tokens, and Korean exclusion phrases such as A 말고, B 빼고, C 제외 into -제외어 tokens.
• Parse practical schedule intent from Korean chat requests into interval, daily, weekly, or manual plans.
• Preserve operator-facing metadata on saved watch/group entries: label, tags, template, schedule, operator_hints, and original request context.
• Use DPAPI-backed secret storage on Windows when possible.
• Deduplicate watch notifications by (watch_id, link) so repeated cron runs emit only newly seen items.
• INLINECODE49 returns cron-friendly operator hints, recommended commands, and a storage-target recommendation (watch vs group).
• INLINECODE52 returns a more practical operator bundle: save command, run command, schedule object, cron line, OpenClaw-friendly systemEvent text, and a Korean confirmation summary.
• INLINECODE53 materializes a parsed plan into a saved watch or group configuration without owning cron wiring itself.
• INLINECODE56 returns chat-friendly combined text by default and structured JSON with --json.

Notes

• - Read references/upstream-notes.md before major edits.
• The skill uses headline/summary metadata from the Naver Search API. It does not fetch or summarize full article bodies.
• Keep additions additive: preserve existing search, watch-add, watch-list, watch-remove, and watch-check flows.
• Public user-facing documentation lives in README.md; keep it Korean-first and concrete.