Install
$ agentstack add skill-kentico-xperience-by-kentico-kenticopilot-migrate-page-widgets ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
You are tasked with the process of migrating the widgets and sections of Page Builder from the legacy project to the new one.
Input Parameters
- Page Name - The name of the page, which widgets need to be migrated (e.g., 'home', 'doctors').
- Legacy Page URL - The URL of the page in the KX13 project (e.g., 'https://localhost:5001/en-us/home').
Structure of the projects
You are currently located in the root folder, which contains two subfolders:
KX13/- This folder contains the Kentico Xperience 13 project files. This is the legacy/source project.XbyK/- This folder contains the Xperience by Kentico project files. This is the new project.
Important
When migrating a page, ensure that everything that was fetched dynamically from the database will still be dynamically fetched from the database. Nothing can be statically hardcoded in the new project if it was dynamic in the legacy project.
Useful Documentation
- Use Kentico Docs MCP to read the following pages:
- Adjust your code and adapt
- Upgrade content retrieval code
- Content Retrieval
- Content Retriever API
- Page Builder
- Widgets for Page Builder
- Widget Properties
- Sections for Page Builder
- Section Properties
- Upgrade Widgets Introduction
- Use web fetch to read the following pages:
- Migration Tool README - Pages
Migration Steps
- Read all documentation links mentioned above.
- Review how the legacy page looks using the provided URL and identify all parts it consists of.
- Go through pages in the legacy project and identify the provided page.
- When you know the page, research which sections and widgets this page uses.
- If present, check how other widgets and sections are implemented in the new project.
- Migrate all the page builder widgets and sections identified in previous steps together with all their dependencies.
- When done with implementation, ensure that the new project builds successfully without errors and warnings. If there are issues, fix them until none are present.
Whenever unsure about anything, use Kentico Docs MCP to search for relevant information.
Output format
When done, provide the user with this exact output (without any additional text):
# Migration Complete
Page builder widget migration from the legacy project to the new one has been successfully completed.
**Next steps:**
- Review the changes to ensure everything looks as expected.
- Continue with the migrate-page skill to migrate individual pages.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: Kentico
- Source: Kentico/xperience-by-kentico-kenticopilot
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.