Does it detect specific CMS versions?

Yes, it scans assembly versions and configuration schemas to identify specific versions, such as differentiating between Umbraco 14 and 17 LTS.

Which CMS platforms are supported by this skill?

The skill currently detects Sitecore (XM Cloud, XP, XM), Umbraco (v14 and newer), and Optimizely (CMS 12 and SaaS editions).

What happens if my project doesn't use a supported CMS?

The skill will report that no CMS was detected and can suggest scaffolding tools to help you initialize a new CMS project from scratch.

Does this skill require manual execution?

No, it is a non-invocable skill that runs automatically to provide context to other CMS-specific tools within the toolkit.

How does it distinguish between Headless and Traditional architectures?

It analyzes project signals such as the presence of Sitecore Layout Service, Next.js configurations, or Optimizely Content Graph references to determine the architectural pattern.

CMS Platform Detector

Name: CMS Platform Detector
Author: twofoldtech-dakota

bytwofoldtech-dakota

•

Gestión de Contenido

Automatically identifies Sitecore, Umbraco, and Optimizely CMS platforms and their specific configurations within a project.

The CMS Platform Detector is a foundational utility designed to ground Claude's assistance in the specific context of enterprise .NET Content Management Systems. By performing a multi-layered scan of project files, NuGet dependencies, and configuration schemas, the skill accurately identifies whether a project is built on Sitecore (including XM Cloud), Umbraco, or Optimizely. Beyond simple identification, it determines the platform version, architecture style (Headless vs. Traditional), and frontend frameworks in use, ensuring that subsequent development guidance is technically accurate and platform-specific.

Características Principales

01Architecture analysis to distinguish between Headless (JSS/SaaS) and Traditional (MVC) setups

02Version-specific identification for modern .NET CMS editions

03Automated detection of Sitecore, Umbraco, and Optimizely platforms

041 GitHub stars

05Automatic workspace configuration for downstream CMS development tools

06Dependency scanning via .csproj and NuGet package analysis

Casos de Uso

01Ensuring development commands are tailored to the correct CMS version (e.g., Umbraco 14+ vs legacy)

02Switching between different enterprise CMS repositories while maintaining context-aware AI assistance

03Identifying the specific architecture of a legacy CMS project during the discovery phase

Características Principales

01Architecture analysis to distinguish between Headless (JSS/SaaS) and Traditional (MVC) setups

02Version-specific identification for modern .NET CMS editions

03Automated detection of Sitecore, Umbraco, and Optimizely platforms

041 GitHub stars

05Automatic workspace configuration for downstream CMS development tools

06Dependency scanning via .csproj and NuGet package analysis

Casos de Uso

01Ensuring development commands are tailored to the correct CMS version (e.g., Umbraco 14+ vs legacy)

02Switching between different enterprise CMS repositories while maintaining context-aware AI assistance

03Identifying the specific architecture of a legacy CMS project during the discovery phase