content-audit

Audit Kentico Xperience 13 content models via SQL queries and export Markdown and JSON reports.

14|7|Updated Nov 25, 2025
One-click install
npx skills add https://github.com/Kentico/xperience-by-kentico-kenticopilot --skill content-audit-kentico
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: content-audit
Source: https://github.com/Kentico/xperience-by-kentico-kenticopilot/tree/main/plugins/kx13-content-audit/skills/content-audit
Command: npx skills add https://github.com/Kentico/xperience-by-kentico-kenticopilot --skill content-audit-kentico

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps you quickly inspect and validate a Kentico Xperience 13 (KX13) project's content model by turning database and structure details into structured Markdown and JSON reports.

Core Features & Use Cases

  • End-to-end KX13 content auditing: Queries a KX13 SQL Server database and exports structured data used to understand page types, content tree, and related configuration.
  • Actionable reporting outputs: Produces a Markdown report (and related JSON artifacts) that you can use for analysis, migration planning, documentation, or review.
  • Flexible export scopes and filters: Lets you audit everything or target specific sites, page types, page builder components, forms, custom tables, and more with filters like site name, class patterns, and page-path prefixes.

Quick Start

Ask the agent to run a full audit for your KX13 database and export the Markdown report, using the default output folder, by requesting: "Audit my KX13 content model and generate the content-model report."

Frequently Asked Questions about content-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I audit a Kentico Xperience 13 content model before migration?

A KX13 content audit queries your SQL Server database to inspect page types, the content tree, and page builder components, exporting structured Markdown and JSON reports. It validates your content model and migration readiness.

How do I export Kentico page types and custom tables to JSON?

Running a KX13 database audit exports custom tables and page types to JSON artifacts. You can scope the export by site name, class patterns, or page-path prefixes to filter the structured content model data.

What is included in a KX13 page builder usage and content tree report?

A KX13 content audit report includes structured findings on page types, content tree structure, page builder components, forms, and custom tables. It outputs Markdown and JSON artifacts for analysis and migration planning.

Can I filter a Kentico content audit by specific site or page path?

Yes, you can filter a KX13 content audit by site name, class patterns, and page-path prefixes. This allows you to target specific sites, page types, or content tree branches for focused reporting.

Does the Kentico content audit require a specific .NET environment setup?

Yes, the KX13 content audit requires a .NET 8-based CLI workflow. It performs workspace solution detection and connection-string preflight checks before executing database queries and generating report files.

What are the limitations of auditing a Kentico content model via SQL queries?

Auditing a KX13 content model via SQL queries is limited to read-only inspection of database structures. It generates static Markdown and JSON artifacts for analysis and does not modify the live content tree or page builder configuration.