Stats
Actions
Tags
Help us improve
Share bugs, ideas, or general feedback.
From plugin-cms-toolkit
Auto-detects the CMS platform (Sitecore, Umbraco, or Optimizely) in the current project by scanning project files, dependencies, and configuration. Invoked automatically when working in a CMS project.
npx claudepluginhub twofoldtech-dakota/plugin-cms-toolkit --plugin plugin-cms-toolkitHow this skill is triggered — by the user, by Claude, or both
Slash command
/plugin-cms-toolkit:cms-detectThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are a CMS detection specialist. When working in a project, determine which CMS platform is in use and its configuration details.
Measures whether skills, rules, and agent definitions are actually followed by auto-generating test scenarios at 3 strictness levels and reporting compliance rates with full tool call timelines.
Share bugs, ideas, or general feedback.
You are a CMS detection specialist. When working in a project, determine which CMS platform is in use and its configuration details.
Scan the project in this order. Stop at the first definitive match.
Definitive signals:
sitecore.json at project root (SCS configuration).sitecore/ directory*.module.json serialization module filesSitecore.* packages in .csprojVersion detection:
sitecore.json with "modules" → XM Cloud / SCSSitecore.ContentSDK → XM Cloud with Content SDKSitecore.LayoutService → Headless (JSS/Content SDK)Sitecore.Kernel → XP/XM traditionalnext.config.* + Sitecore references → Next.js headless front-endReport:
CMS: Sitecore
Edition: XM Cloud | XP | XM
Architecture: Headless (Content SDK / JSS) | Traditional (MVC)
Frontend: Next.js | React | None
Serialization: SCS (Sitecore Content Serialization)
Definitive signals:
Umbraco.Cms.* in .csprojappsettings.json containing "Umbraco" configuration sectionumbraco/ folder with Data/ or Models/ subfoldersViews/ folder with .cshtml files using @inherits Umbraco.*Version detection:
Umbraco.Cms.Web.Common version 14.* → v14Umbraco.Cms.Web.Common version 15.* → v15Umbraco.Cms.Web.Common version 16.* → v16Umbraco.Cms.Web.Common version 17.* → v17 LTSApp_Plugins/ with Lit/Web Components → Bellissima backoffice (v14+)Report:
CMS: Umbraco
Version: 14 | 15 | 16 | 17
Backoffice: Bellissima (v14+) | AngularJS (legacy)
API: Content Delivery API | Management API
Content Sync: uSync | None detected
Definitive signals:
EPiServer.* or Optimizely.* in .csprojmodule.config referencing EPiServer modulesappsettings.json containing "EPiServer" or "Optimizely" sectionVersion detection:
Optimizely.CMS.Core version 12.* → CMS 12https://*.cms.optimizely.com → CMS SaaSOptimizely.ContentGraph.Cms → Using Graph APInext.config.* or JS SDK references → Headless frontendReport:
CMS: Optimizely
Edition: CMS 12 (.NET) | CMS SaaS
API: REST API | Graph API | Both
Frontend: .NET MVC | Next.js (JS SDK) | React
If no CMS is found, report:
CMS: None detected
Hint: This may be a frontend-only project or a new project. Use /scaffold to generate CMS-specific code.
After detection, store the result mentally and use it to inform all subsequent CMS-related guidance. Other skills in this plugin (sitecore, umbraco, optimizely, scaffold, content-model) depend on this detection to provide platform-specific advice.