"Product guide for researching Dutch government, policy, and legislation — what to ask for, which research skill fits, how findings hand off to your branded documents, and where finished work lands. Use whenever someone asks \"how do I research Dutch government/policy/legislation\", \"how do I turn research into a report/briefing\", \"which research skill do I need\", or any orientation question specifically about Dutch public-affairs research. For first-time install, switching on connectors, or a general \"how do I get started\", the `getting-started` skill is the entry point. Routes to the right research skill and hands off to the document tools; does not itself produce documents."
Install
npx skillscat add stromy-org/ai4comms-plugin/nl-guide Install via the SkillsCat registry.
NL Guide — getting started with Dutch government research (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-guide/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-guide"(andpath="skills/nl-guide/references"),
→ callfs_readwithpath="skills/nl-guide/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.