"Recurring monitoring and alert product for Dutch parliamentary and legislative activity. Watches a defined topic/dossier/actor matrix over weekly windows and produces a weekly briefing: breaking alerts, dossier-status, forward agenda. Use whenever the user wants a topic or dossier set monitored on a cadence, asks for a weekly brief, asks 'what changed', wants a threshold alert on a watched dossier, or wants a re-runnable digest. Not for: single-dossier passage forecasting (→ nl-dossier-tracker); 6-36 month foresight (→ nl-horizon-scan); toezeggingen delivery tracking (→ nl-accountability); contradiction hunting (→ nl-tensions); a one-off pull-up-and-summarise on a named dossier with no recurring cadence (→ nl-gov-data)."
Install
npx skillscat add stromy-org/ai4comms-plugin/nl-monitor Install via the SkillsCat registry.
NL Monitor (MCP-hosted skill)
This skill's full instructions are hosted on the nl-gov-data MCP server. Do not hardcode workflow logic locally — always fetch the live version from the MCP.
Loading instructions
Read the main skill instructions:
→ call thefs_readtool on thenl-gov-dataMCP withpath="skills/nl-monitor/SKILL.md".Read it to the end.
fs_readreturns one page at a time. If the result'snext_offset_charsis not null — or the returned text ends in a<<< PARTIAL READ … >>>block — the body is incomplete: callfs_readagain withoffset_charsset to that value and concatenate, repeating until it comes back null. Do not start work on a partial skill body. Hard rules and anti-patterns often sit in the final third, and a partial read fails silently — it looks like a complete skill.Discover reference files (and any other skill assets), then read on demand:
→ callfs_listwithpath="skills/nl-monitor"(andpath="skills/nl-monitor/references"),
→ callfs_readwithpath="skills/nl-monitor/references/<file>".
Follow the instructions returned by the MCP exactly.
This MCP is the only correct path
Produce this skill's output only by following the live SKILL.md fetched above and calling the nl-gov-data MCP's own tools. Do not substitute a local or identically-named base skill from elsewhere, and do not invent your own output path. A locally-produced or unbranded artifact is wrong output, not a fallback — it bypasses the server-side brand and quality gates.