---
name: nl-dossier-tracker
description: "Deep brief on ONE Dutch legislative dossier: current phase, timeline, moties and votes, EU forcing function, and a framed passage forecast (likelihood band, decisive variable, assumptions, two scenarios, base rate). Use for 'dossier tracker', 'will it pass', 'passage signals', 'dossier {number}', 'wet {name}', 'wetsvoorstel', 'TK dossier', 'legislative dossier', 'bill outlook', 'where does bill X stand and will it pass'. Not for: recurring watching or alerts on dossiers (use nl-monitor); individual-MP defection risk or stakeholder maps (use nl-parliamentary-positioning); 6-36 month foresight across topics (use nl-horizon-scan); a quick one-off status lookup with no forecast (use nl-gov-data)."
metadata:
  stromy-client-summary: "Get a deep brief on one Dutch legislative file: where it stands, what happened, and how likely it is to pass."
---
<!--
  GENERATED FILE — DO NOT EDIT.
  Owner:       scripts/sync-mcp-skill-stubs.py (via sync-on-mcp-skill-change.yml)
  Source:      MCPs/nl-gov-data/skills/nl-dossier-tracker/SKILL.md
  This workflow pushes DIRECT to this repo's main — a local edit here will be
  overwritten or rejected non-fast-forward. Edit the source, push, then:
    gh workflow run sync-on-mcp-skill-change.yml -R stromy-org/stromy-org
  Hand-authored skill? Set `_local: true` in frontmatter instead.
-->

# Dossier Tracker (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

1. Read the main skill instructions:
   → call the `fs_read` tool on the `nl-gov-data` MCP with `path="skills/nl-dossier-tracker/SKILL.md"`.

   **Read it to the end.** `fs_read` returns one page at a time. If the result's `next_offset_chars` is not null — or the returned text ends in a `<<< PARTIAL READ … >>>` block — the body is incomplete: call `fs_read` again with `offset_chars` set 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.

2. Discover reference files (and any other skill assets), then read on demand:
   → call `fs_list` with `path="skills/nl-dossier-tracker"` (and `path="skills/nl-dossier-tracker/references"`),
   → call `fs_read` with `path="skills/nl-dossier-tracker/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.