Help us improve
Share bugs, ideas, or general feedback.
From be-civic
Use at the end of a Be Civic application procedure, after eligibility has passed and the document checklist has been gathered. Produces a Be Civic-styled application dossier — index page, bring-originals callout, checklist table, filled official forms, disclaimer — that the user prints and submits to the filing authority. Agent-tooling sub-skill; produces an artefact rather than running a Belgian admin process.
npx claudepluginhub be-civic/be-civic-plugin --plugin be-civicHow this skill is triggered — by the user, by Claude, or both
Slash command
/be-civic:bc-dossier-compilationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
<Tip>
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Explores codebases via GitNexus: discover repos, query execution flows, trace processes, inspect symbol callers/callees, and review architecture.
Share bugs, ideas, or general feedback.
Invoked from a parent application process at session end, after eligibility has passed, intent is confirmed, and the checklist of required documents has been gathered. Produces a Be Civic-styled application dossier — an index page listing every document the user must file, the "bring originals" callout, the checklist table, and the filled official forms — that the user prints and submits to the filing authority.
The dossier is the artefact the user files. Be Civic does not stage or store it; the agent renders it locally on the user's machine.
Invoke this sub-skill only when:
application dossier.dossier-compilation in its requires.If any of these are unmet, do not render the dossier. Continue gathering with the user under the parent process's guidance.
The full-capability path requires pdf_generation, file_read, and structured_output. If any are unavailable, degrade per the table:
| Missing capability | Degraded behaviour |
|---|---|
pdf_generation | Emit the dossier markdown only. Tell the user once: "I can't render PDF in this session. Save the markdown I produce, then convert via your browser's print-to-PDF or a converter like pandoc." Walk them through one render path. |
file_read | The agent cannot save artefacts locally. Narrate the dossier content inline in chat; tell the user to copy it to a local file themselves. |
structured_output | Render the index page as plain prose rather than tables; mark each document with a clear "Bring in original" / "Copy acceptable" prefix. |
Tell the user once, briefly, which path you are taking. Do not over-explain — the user wants the dossier, not an apology for what the agent cannot do.
The index page is the cover of the dossier. Render the template below, filling each {placeholder} from the parent process's inputs and the user's gathered context.
<!-- Be Civic Application Index — generated {generated_date} -->
{ width=120px }
# {application_title}
**Prepared for:** {user_name_or_self_reference}
**Date prepared:** {generated_date}
**Filing authority:** {filing_authority}
**Process:** `{parent_process_id}` v{parent_process_version} ({version_status})
---
> **Bring these in original — the printout is not sufficient:**
> - {original_required_1}
> - {original_required_2}
## What this dossier contains
| § | Document | Form | Source |
|---|----------|------|--------|
| 1 | {document_name} | {form_required} | {source} |
| ... | ... | ... | ... |
## Notes for the filing officer
{agent_note_or_omit}
---
*This dossier was prepared by the user with the assistance of an AI agent
using Be Civic context. Be Civic publishes public information only and has
no legal standing. Verify with the relevant authority before filing —
procedures vary and change.*
The logo URL is stable and served at the apex; embedding it as a remote ![]() is fine for renderers with web access. If the renderer is offline or strips remote images, omit the logo line — do not block rendering on it.
The checklist enumerates every document in the dossier. One row per document. Use a markdown table — long document names wrap to a second line within the cell rather than overflowing the page edge.
Columns:
Original, Certified copy, Apostilled, Sworn translation, Printout acceptable. Pull from the parent process's ## Required documents section, where each row carries a form-required marker.The "Form" column drives Step 5.
Above the checklist table, render the originals callout. Include every document where "Form" is anything other than Printout acceptable:
Bring these in original — the printout is not sufficient:
- {document_1}
- {document_2}
Before closing the dossier handoff (Step 8), say this out loud to the user:
"You'll need to bring these documents in original form — the dossier I'm preparing is for your reference, not a substitute for the originals. Specifically: {list}."
If the parent process's ## Bring in original section is empty (rare for application processes, but possible — e.g., a fully digital filing), omit both the callout and the verbal reminder.
After the index page and checklist, append every official form the user must file. These are pulled from the parent process body (Annexes, declarations, fee receipts, attestations, etc.). For each form:
Do not invent or paraphrase form fields. If unsure of a value, leave the field blank and flag it to the user before rendering.
A4 portrait is the default for the entire dossier. Override per page where content demands it:
## ...) to keep the dossier scannable. The index page sits on its own page.If the renderer does not support a particular instruction (e.g., browser print-to-PDF has limited orientation control), accept the limitation and tell the user.
Save the dossier to the visible surface with the user's permission. Default path: ${SUBSTRATE_DATA}/<procedure-slug>/documents/dossier/{parent_process_id}-dossier-{YYYY-MM-DD}.{md,pdf}.
Repeat the originals reminder from Step 5. Confirm the user understands the dossier is a reference, not a substitute for the originals.
This sub-skill does not submit anything at session end. The dossier is rendered locally; the parent process's own lifecycle continues independently.
Verify with the relevant authority before filing — procedures vary and change.