publisher-nl
Skill8 starsChanged 3 months agoApache-2.0View on GitHub
Turn a finished, warrant-labelled analysis into a publishable Dutch markdown article. Use when the user asks to write/publish a completed analysis as an article ("schrijf een artikel", "maak er een publicabel stuk van", "publiceer dit", "turn this into a piece"). This skill writes only; it does not research. It preserves the warrant chain: no new load-bearing facts, no stronger phrasing than the analysis supports, weak claims hedged and attributed.
In this repository21 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- belief-revisionSkill
- fallacy-bias-and-manipulation-analysisSkill
- first-principles-thinkingSkill
- intuitive-thinkingSkill
- investigative-reasoningSkill
- journalistic-article-reviewSkill
- osint-researchSkill
- peer-reviewSkill
- publisher-nlSkill
- scientific-fact-classificationSkill
- belief-revisionSkill
- fallacy-bias-and-manipulation-analysisSkill
- first-principles-thinkingSkill
- intuitive-thinkingSkill
- investigative-reasoningSkill
- journalistic-article-reviewSkill
- osint-researchSkill
- peer-reviewSkill
- scientific-fact-classificationSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
25 rules. About 0 are common, 23 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈23
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 18
If the input is unaudited or source-light, stop and offer to run the right analytical skill first.
- Distinctive: line 22
Write in Dutch markdown.
- Distinctive: line 23
Do no new research and add no factual claim absent from the analysis.
- Distinctive: line 25
Every load-bearing article sentence must trace to that inventory.
- Distinctive: line 27
Do not show warrant labels in the article.
- Distinctive: line 28
Always include "Wat we (nog) niet weten" and "Bronvermelding".
- Distinctive: line 41
If removing a weakly warranted claim collapses the conclusion, stop and flag the gap.
- Very specific: line 45
Ask for or use the target word count.
- Very specific: line 80
Use numbered HTML superscript markers: <sup>[1]</sup>.
- Distinctive: line 81
Put markers after the supported clause or sentence, after punctuation.
- Distinctive: line 83
Every marker must resolve to one Bronvermelding item, and every item must be cited.
- Distinctive: line 84
Prefer traced primary sources over secondaries.
- Distinctive: line 87
If sources share funding, ownership, mandate, or alignment, note that they are not independent corroboration.
- Distinctive: line 88
If no URL exists, describe the document and say so.
- Distinctive: line 94
Do not move quotes into misleading contexts or borrow wording without attribution.
- Distinctive: line 105
No stylistic en/em dashes.
- Distinctive: line 106
Prefer active verbs, concrete nouns, dates, documents, and numbers.
- Distinctive: line 107
Avoid naamwoordstijl, tangconstructies, anglicisms, and needless jargon.
- Distinctive: line 109
No needless repetition. Repeat the kernboodschap only when the slot adds the earned resonance.
- Distinctive: line 110
Do a spelling/grammar pass before delivery.
- Distinctive: line 116
no new facts or memory claims slipped in.
- Distinctive: line 117
every load-bearing sentence traces to the inventory.
- Distinctive: line 118
no phrasing exceeds its calibration ceiling.
- Distinctive: line 119
all weak claims are hedged and attributed.
- Distinctive: line 125
all markers and Bronvermelding entries match.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Publisher NL
Convert a completed truth-seeking analysis into a Dutch article that reads well without breaking the evidence chain.
Use Only When
- Input is a finished analysis from
investigative-reasoning,peer-review,scientific-fact-classification,osint-research,fallacy-bias-and-manipulation-analysis,first-principles-thinking, orbelief-revision; - the user wants a publishable article, not a summary, first-pass research, or an opinion piece in the user's own voice;
- the analysis includes warrant labels and sources.
If the input is unaudited or source-light, stop and offer to run the right analytical skill first. Do not fill gaps from memory.
Non-Negotiables
- Write in Dutch markdown.
- Do no new research and add no factual claim absent from the analysis.
- Inventory before writing: core verdict, load-bearing claims + warrant labels, open questions, bias self-audit, sources, and source-network caveats.
- Every load-bearing article sentence must trace to that inventory.
- Preserve the analysis's uncertainty. You may write more cautiously, never more strongly.
- Do not show warrant labels in the article; express warrant through sourcing, attribution, and hedging.
- Always include "Wat we (nog) niet weten" and "Bronvermelding".
- State final word count excluding "Bronvermelding" and superscript markers, plus whether the language check was manual or tool-assisted.
Calibration
| Analysis label | Strongest article phrasing |
(traced) | Direct assertion with source marker. |
(deferred to consensus) | Assertion naming the body where it carries weight. |
(deferred, fragile) | Hedged assertion naming the failure mode. |
(memory — unverified) | Hedged, attributed, never load-bearing alone. |
(user-supplied — unverified) | Same; if central, the article is not ready. |
If removing a weakly warranted claim collapses the conclusion, stop and flag the gap.
Length
Ask for or use the target word count. Count everything except "Bronvermelding" and <sup>[n]</sup> markers. Aim for +/-10%. If no target is given, write only as long as the material warrants. Never cut attribution, hedges, source markers, or "Wat we (nog) niet weten" to hit length.
Article Shape
# [Kop]
[Inleiding: 1-3 alinea's with probleemstelling, these, kernboodschap/conclusie.]
## [Tussenkop]
[Kern: claim-by-claim, logical chapter order, source markers after supported clauses or sentences.<sup>[1]</sup>]
## [Tussenkop]
[Next step in the argument.<sup>[2]</sup>]
## Wat we (nog) niet weten
[Open questions and relevant bias-audit caveats.]
## [Slot]
[Return to the kernboodschap or final open question. No new claims.]
## Bronvermelding
1. Titel bron — Auteur/uitgever, datum (geraadpleegd dd-mm-jjjj).
<https://www.voorbeeld.nl/bron>Headline and tussenkoppen must stay within the calibration ceiling: honest, specific, no clickbait. Provocative chapter titles are allowed only for genuinely strong findings, never for thin context.
Source Markers And Bronvermelding
- Use numbered HTML superscript markers:
<sup>[1]</sup>. - Put markers after the supported clause or sentence, after punctuation.
- Number sources by first appearance; reuse the same number for repeat citations.
- Every marker must resolve to one Bronvermelding item, and every item must be cited.
- Prefer traced primary sources over secondaries.
- Each entry: descriptive line, two trailing spaces, URL on the next indented line.
- Include access dates from the analysis's
(traced)labels. - If sources share funding, ownership, mandate, or alignment, note that they are not independent corroboration.
- If no URL exists, describe the document and say so.
Quotes And Confidential Sources
- Quote verbatim; mark omissions with
[...]and insertions with[redactie: ...]. - Label translations and keep the original recoverable.
- Do not move quotes into misleading contexts or borrow wording without attribution.
- Protect confidential sources: do not name or identify them in text or Bronvermelding, including by singling detail. Use only a safe description and state that the identity is known but withheld.
- Apply Raad voor de Journalistiek guidance on publication/quotes and source protection, and SPJ ethics on truthful quotation, attribution, anonymity, and keeping promises. If these norms become article-supporting sources, cite them:
- RvdJ Leidraad C. Publicatie: https://rvdj.nl/leidraad/c-publicatie/ (geraadpleegd 08-06-2026).
- RvdJ Leidraad B. Voorbereiding/Nieuwsgaring: https://rvdj.nl/leidraad/b-voorbereidingnieuwsgaring/ (geraadpleegd 08-06-2026).
- SPJ Code of Ethics mirror: https://www2.hawaii.edu/~jour/spj/SPJcode.html (geraadpleegd 08-06-2026; canonieke vindplaats spj.org gaf 403).
Dutch Style
- Good Dutch, official spelling, correct compounds, required hyphens, and correct diacritics.
- Varied sentence length, roughly 15-20 words on average.
- No stylistic en/em dashes; use comma, colon, full stop, or restructure.
- Prefer active verbs, concrete nouns, dates, documents, and numbers.
- Avoid naamwoordstijl, tangconstructies, anglicisms, and needless jargon.
- Enumerations: introduce with a colon; separate items with semicolons; end the last with a full stop.
- No needless repetition. Repeat the kernboodschap only when the slot adds the earned resonance.
- Do a spelling/grammar pass before delivery; use a checker if available, otherwise read manually.
Final Check
Before delivery, verify:
- no new facts or memory claims slipped in;
- every load-bearing sentence traces to the inventory;
- no phrasing exceeds its calibration ceiling;
- all weak claims are hedged and attributed;
- intro has probleemstelling, these, and kernboodschap/conclusie;
- chapters follow a clear order and all have tussenkoppen;
- "Wat we (nog) niet weten" and slot are present;
- quotes, translations, and confidential sources are handled cleanly;
- Dutch spelling, grammar, punctuation, and repetition are checked;
- all markers and Bronvermelding entries match;
- word count is on target or the constraint is explicitly surfaced.
Deliver one markdown article. If the analysis is insufficient, say what is missing instead of writing around the gap.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

