Guide · Agent skill
How to use the CMS Platform Workflow Guide agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The content-management-systems skill is a set of written instructions that tells an AI coding agent how to approach work on content management systems such as WordPress, Shopify, Drupal, Joomla and Webflow. It is aimed at developers, agencies and teams who maintain themes, plugins, modules or static export pipelines and have access to the codebase. After this guide you will know what the skill changes about the agent's behaviour, how to install it, how to trigger it with natural requests, and what to check before using it on a production site.
CMS Platform Workflow Guidegithub/awesome-copilot · MIT Download the skill Quick start
- 1Download the ZIP. Get the skill ZIP from this page and unzip it.
- 2Choose an install location. Place the folder in ~/.claude/skills/ for personal use or in .claude/skills/ inside a project.
- 3Or upload in the Claude apps. Go to Settings → Capabilities → Skills and upload the skill.
- 4Confirm both files are present. Check that SKILL.md and references/cms-platform-workflows.md are in the same folder.
- 5Describe a CMS task. Name the platform and the kind of change, such as a theme template, plugin, module or media upload.
- 6Review the seam and the diff. Check that the agent named the owning seam and kept changes small before accepting them.
What the skill makes the agent do
Without the skill, an agent will edit whatever file looks relevant. With it, the agent follows a fixed first pass: it identifies the platform category (self-hosted CMS, SaaS site builder, commerce platform, or hybrid/headless system), finds the owning implementation seam such as the theme layer, plugin layer, admin or editor surface, content model, media pipeline, or export step, and checks platform constraints before choosing an approach.
The skill also sets CMS conventions. It asks the agent to keep theme assets separate from user-uploaded media, keep important metadata in structured content fields rather than presentation markup, and treat previews, slugs, taxonomy, excerpts, meta fields and publish states as first-class concerns.
The skill is guidance only. It does not add tools and does not automate any platform.
Install the skill from the ZIP download
Download the ZIP for this skill from this page and unzip it. For a personal setup, place the unzipped folder in ~/.claude/skills/. For a single project, place it in the project's .claude/skills/ folder instead.
If you use the Claude apps, you can instead upload the skill under Settings → Capabilities → Skills.
- Personal install location: ~/.claude/skills/
- Project install location: .claude/skills/ inside your project
- Claude apps: Settings → Capabilities → Skills, then upload
Check the files after installing
The skill folder contains two files: SKILL.md, which holds the workflow and rules, and references/cms-platform-workflows.md, a compact table mapping common platforms to their extension surfaces and media conventions. The agent reads the reference when it needs the platform-specific mapping.
Keep both files together. If the reference file is missing, the platform notes will not be available to the agent.
How to trigger the skill with natural requests
You do not need a special command. Describe a CMS task in plain language and name the platform or the kind of work. The skill's description covers themes, plugins, apps, modules, admin panels, media uploads, content models, editors, markdown pipelines and static export workflows, so requests that mention those topics are the ones it is meant to handle.
- Add a field to the WordPress product template and keep the price in a custom field, not in the markup.
- Add a Shopify section that reads a metafield, and make sure the value survives a theme redesign.
- Create a Drupal module setting for the upload directory, with a safe default.
- Check that permalinks and asset paths still work after our static export build changes.
What to expect from the output
Expect the agent to name the platform and the seam it chose before editing, then make the smallest change that preserves the CMS structure. For editor or admin changes, the skill asks the agent to trace the stored field, validation rules, preview path and final render path together, so a good response should mention all four.
Expect it to use conventional folders such as uploads/ for authored media and img/ for theme assets unless the platform sets a stronger convention. Review these choices against the actual platform version you run.
Safety notes: scripts and network access
This skill runs no scripts and uses no network access, according to its listing. It requires nothing else to be installed. Because it only supplies guidance, the risk is in the changes the agent makes to your code, not in the skill itself.
The guidance is generic. It may suggest conventions that do not match a specific platform version, so review every change, especially for live sites, before deploying it.
Tips for getting better results
Name the platform and version you use, and say whether the site is server-rendered, static-exported or hosted remotely. The skill's first pass asks exactly these questions, so answering them up front saves a round trip.
Point the agent at the codebase you want changed. The skill assumes access to code, so it is not useful for simply editing page text on a hosted site.
- Give the platform name in the first sentence of the request.
- Say whether the change belongs in a theme, plugin, module or admin screen.
- Ask for a preview or validation step for markdown and renderer changes.
What people use it for
- Building or maintaining a WordPress theme or plugin with a clear template hierarchy.
- Adding a Drupal or Joomla module setting, with validation and permissions kept consistent with the admin code.
- Modifying Shopify or Webflow customisations within the platform's rules, such as keeping data in metafields so it survives a redesign.
- Reviewing a markdown or static export pipeline and checking permalinks and asset paths after a build change.
Frequently asked questions
How do I install the content-management-systems agent skill?
Download the ZIP from this page and unzip it. Put the folder in ~/.claude/skills/ for personal use, or in a project's .claude/skills/ folder. In the Claude apps, you can upload it under Settings → Capabilities → Skills.
Does the content-management-systems skill require anything else?
The listing says it requires nothing else to be installed. It runs no scripts and uses no network access. It is guidance for an agent that already has access to your codebase.
Is the content-management-systems skill free to use?
The skill is published under the MIT licence, as listed on this page. The source is in the github/awesome-copilot repository under skills/content-management-systems.
Which CMS platforms does this skill cover?
The description lists WordPress, Shopify, Wix, Squarespace, Drupal, WooCommerce, Joomla, HubSpot CMS Hub, Webflow and Adobe Experience Manager, plus similar platforms. The reference file maps common platforms to their extension surfaces and media conventions.
Why does the agent ignore my request or edit the wrong file?
The skill tells the agent to find the owning seam first, so a vague request can lead to a broad search. Name the platform, the part of the site (theme, plugin, admin screen, content model or export step) and the file if you know it.
How is this different from a plugin or a CMS-specific tool?
The skill does not add tools or automate any platform. It only shapes how the agent approaches CMS work. For platform-specific automation you would need a separate tool.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you are a developer or agency building or maintaining WordPress, Shopify, Drupal, Joomla or Webflow customisations, or a static export pipeline, and you have a codebase for the agent to work in. Pick something else if you only want to edit text on a hosted site, since the skill adds nothing for simple content entry, or if you need guidance tuned to one exact platform version, since this guidance is generic and should be reviewed before it touches a production site.
Download the skill