weekly-review

Extracts read-later articles from Inkdrop inbox notes and organizes them into themed notebooks.

Updated Apr 8, 2017
One-click install
npx skills add https://github.com/localmin/dotfiles --skill weekly-review-localmin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weekly-review
Source: https://github.com/localmin/dotfiles/tree/main/coding-agents/skills/weekly-review
Command: npx skills add https://github.com/localmin/dotfiles --skill weekly-review-localmin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires @inkdropapp/mcp-server.

What problem does it solve? Daily inbox summary notes in Inkdrop accumulate articles marked "read later" that never get processed. This Skill runs a weekly review that extracts those pending articles, forces a keep-or-discard decision, and files kept items into themed notebooks so the inbox stays clean. ## Core Features & Use Cases - Targeted Extraction: Searches Inkdrop via MCP with month-scoped title filters and parallel note reads to find only "read later" sections, avoiding expensive full-inbox scans. - Two-Way Triage: Each article is either grown into a standalone note with tags and a themed notebook destination, or deleted from the daily summary. - NotebookLM Escalation: Detects tags with three or more accumulated notes and proposes promotion to NotebookLM topics. - Use Case: Every Monday, review last week's inbox summaries, deep-read the saved AI engineering articles, add your own commentary, tag them (e.g., harness-eng), and move them into tech/AI. ## Quick Start Run the weekly review for my Inkdrop inbox covering 2026-04-28 through 2026-05-04 and help me triage the read-later articles.

Frequently Asked Questions about weekly-review

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize read-later articles in Inkdrop?

Run a weekly review that searches inbox daily summaries for sections marked read-later, then decide per article: grow it into a standalone tagged note in a themed notebook, or delete the section from the daily summary.

How to call the Inkdrop MCP server from Antigravity CLI?

Use stateless invocation: pipe a JSON-RPC tools/call payload via echo into op run with the inkdrop env file and npx @inkdropapp/mcp-server. Avoid enabling the MCP server persistently, since that triggers 1Password popups on unrelated operations.

Why should I avoid list-notes on a large Inkdrop inbox?

list-notes fetches every note in the notebook, which becomes slow as the inbox grows. Instead use search-notes with a title modifier like book:inbox title:"inbox 2026-04" to scope results by month, running parallel queries when the period spans months.

When should I create a new tag in Inkdrop versus reuse existing ones?

Create a new tag only when the article's subtheme will keep accumulating notes over time, such as harness-eng or prompt-caching. For one-off or event-specific articles, reuse an existing tag to prevent tag sprawl.

What timeout should I use for Inkdrop MCP calls?

Use 60 seconds for stateless invocations since op run authentication and npx startup add latency, and 30 seconds for persistent MCP connections in Claude Code or Codex. Retry once on failure in either mode.