Skip to content
Skills Library
Programming · Review & audit

phpbb-export-verification

/phpbb-export-verification

Validate phpBB personal exports and static archives for visibility, privacy, rendering fidelity, output completeness, and real-data failures before publication. Use when checking a personal data export or static archive (HTML/ZIP/SQL conversion) for leaked private content, broken rendering, or missing data before release.

Licence
LGPL
Last repository change
09.11.2026

Assessment and security

91/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content26 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 09.11.2026, without references to retired models or APIs.

Licence

LGPL, otwarta.

What it does and when to use it

Validate phpBB personal exports and static archives for visibility, privacy, rendering fidelity, output completeness, and real-data failures before publication. Use when checking a personal data export or static archive (HTML/ZIP/SQL conversion) for leaked private content, broken rendering, or missing data before release.

Original author description

Validate phpBB personal exports and static archives for visibility, privacy, rendering fidelity, output completeness, and real-data failures before publication. Use when checking a personal data export or static archive (HTML/ZIP/SQL conversion) for leaked private content, broken rendering, or missing data before release.

How it works

SKILL.md has no level-two headings · 15 lines, 285 words

SKILL.md preview
---
name: phpbb-export-verification
description: "Validate phpBB personal exports and static archives for visibility, privacy, rendering fidelity, output completeness, and real-data failures before publication. Use when checking a personal data export or static archive (HTML/ZIP/SQL conversion) for leaked private content, broken rendering, or missing data before release."
---

# phpBB Export Verification

Identify whether this is a personal data export or public static archive. Inventory included categories and visibility rules for posts, private messages, attachments, profiles and moderation data. Use an authorized disposable local copy for sensitive real data; do not publish a database, SQL dump, credentials, PM attachment, or private reference document with the output.

Build synthetic fixtures for each relevant permission/visibility case, including deleted/unapproved content, private forums, unavailable attachments and non-ASCII/BBCode content. Apply one consistent eligibility rule to category counts, queries, rendered entries and attachments. Prefer core visibility/log/text-rendering services to reimplementing authorization or unserializing log internals.

Test HTML and ZIP outputs where supported. Validate the archive, relative assets, link/board URL handling, smileys, attachment ordering and filenames, and offline rendering without network-only fonts or assets. Treat dump-derived HTML, URLs and paths as untrusted. Keep temporary databases and manifests containing private information outside publishable output.

A complete ZIP, HTTP 200 and empty server log are insufficient. Inspect generated HTML for rendered PHP warning/notice/fatal markup as well as broken images, empty sections and count mismatches. Exercise both a small fixture and an authorized large representative account/dataset; diagnose output errors and rerun before claiming readiness.

For SQL archive conversion, distinguish structural dump checks from relational fidelity: compare imported row/field counts, missing topic/first-post relationships, Unicode and replacement characters. Test entity and code-block rendering through the real phpBB storage/preview boundary before blaming stored data; a CLI seed tool can itself double-decode entities.

Use the project's incremental render mode for template-only checks if it preserves relevant inputs; run a full export when fetching/import behavior changes. Report the tested dataset scope and a safe real example URL or artifact. Do not expose private content merely to demonstrate a result.

Versions

The database has no other skills named phpbb-export-verification.

Database snapshot: 13.11.2026 · package version e3b90e3537b3 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 81phpbb-extension-releases
    Prepare, package, publish, and verify phpBB extension releases or explicitly requested rolling development refreshes using the shared release tools. Does not authorize a release from a merge alone. Use when asked to tag, package, publish, or refresh a dev release of an…
  • 100phpbb-extension-validation
    Validate a phpBB 3.3 extension's source for security issues, coding-guideline violations, language-system misuse, and packaging problems, then emit a BBCode validation report with [valdeny]/[valinfo] findings and an Approve/Deny recommendation. Use when asked to validate,…
  • 86static-site-publishing
    Use when building or previewing static websites.
  • 100data-flow
    The JSON-to-custom-element rendering pipeline used for data tables and list-rendered content. Defines toTagName key conversion, the lifecycle from fetch to DOM, and the strict scope (data tables only — other features have their own patterns). Use when rendering tabular or list…
  • 100review-docs
    Review and improve Syncpack documentation for clarity, completeness, and consistency. Use when enhancing docs or validating before publication.
  • 90rendering-strategies
    When the user wants to choose or optimize rendering strategy for SEO. Also use when the user mentions "SSR," "SSG," "CSR," "ISR," "static rendering," "dynamic rendering," "server-side rendering," "client-side rendering," "JavaScript rendering," "pre-rendering," "prerender,"…

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.