Mmcp.market

content-management-systems skill

by github·github/awesome-copilot·39k stars·MIT

Workflow for building and modifying content management systems across WordPress, Shopify, Wix, Squarespace, Drupal, WooCommerce, Joomla, HubSpot CMS Hub, Webflow, Adobe Experience Manager, and similar platforms. Use when working on CMS themes, plugins, apps, modules, admin panels, media uploads, content models, editors, markdown pipelines, or static export workflows.

A100/100content scan

Is the content-management-systems skill safe?

Clean: nothing in its files matched our rules. We read 2 files in the folder on 2026-09-28.

No findings.

Install the content-management-systems skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description. 

git clone --depth 1 https://github.com/github/awesome-copilot.git /tmp/awesome-copilot
mkdir -p ~/.claude/skills
cp -r /tmp/awesome-copilot/skills/content-management-systems ~/.claude/skills/content-management-systems
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

Content Management Systems

Use this skill when the user is working on a content management system or on software that behaves like one.

This skill focuses on the seams that matter in CMS work:

  • themes and templates
  • plugins, apps, modules, and extensions
  • admin and editor interfaces
  • media and upload handling
  • content models, taxonomy, and metadata
  • render pipelines and static export flows

When to Use This Skill

  • The user mentions a CMS platform such as WordPress, Shopify, Drupal, Joomla, Webflow, Squarespace, Wix, WooCommerce, HubSpot CMS Hub, or Adobe Experience Manager.
  • The task is about theme development, template changes, or design system work inside a CMS.
  • The task is about plugins, modules, apps, or extension points.
  • The task touches editor UX, previews, taxonomy, slugs, SEO fields, or publishing behavior.
  • The task involves uploads, media libraries, authored assets, markdown rendering, or static export.

First Pass

  1. Identify the platform category: self-hosted CMS, SaaS site builder, commerce platform, or hybrid/headless system.
  2. Find the owning implementation seam before editing:
  • theme or template layer
  • plugin, app, module, or extension layer
  • admin or editor surface
  • content model or storage layer
  • media pipeline
  • export, deploy, or rendering pipeline
  1. Check platform constraints before choosing an approach:
  • what is editable locally
  • what is authored content versus code
  • where media belongs
  • whether the final site is server-rendered, static-exported, or hosted remotely

CMS Rules

  • Follow the platform's naming and folder conventions for themes, modules, template parts, or sections.
  • Keep theme assets separate from user-uploaded media unless the platform explicitly combines them.
  • Prefer structured content fields over storing important metadata inside presentation markup.
  • Treat previews, slugs, taxonomy, excerpts, meta fields, and publish states as first-class CMS concerns.
  • Prefer safe defaults and graceful fallback behavior when config, theme selection, or content input is invalid.
  • When changing editor or admin behavior, trace the stored field, validation rules, preview path, and final render path together.

Common Workflows

Themes and Templates

  • Start at the template loader or theme runtime, not at a downstream include.
  • Preserve the platform's template hierarchy and partial naming conventions.
  • Keep presentation changes close to templates and shared theme helpers.

Plugins, Apps, and Modules

  • Add behavior at the platform's extension seam instead of scattering logic into templates.
  • Keep migrations, seed data, and configuration updates explicit and versioned.
  • Document the extension's setup assumptions when the platform requires activation or registration.

Admin and Editor UX

  • Keep forms aligned with the stored content model.
  • Prefer author-facing previews when content transformations are non-trivial.
  • Keep validation, CSRF or equivalent safeguards, and permissions consistent with the surrounding admin code.

Media and Uploads

  • Use a dedicated upload path for authored media.
  • Keep decorative or theme-owned imagery in the active theme folder.
  • Default to conventional locations like uploads/ for authored media and img/ for theme assets unless the platform dictates a stronger convention.
  • When a CMS supports configurable media directories, expose the setting with a safe fallback.

Content Models and Migrations

  • Distinguish content entities clearly: pages, posts, products, entries, collections, taxonomies, and settings.
  • Prefer migration files or exportable schema definitions over ad hoc runtime mutations.
  • Keep slugs, publish dates, excerpts, canonical metadata, and taxonomy relations structured.

Markdown, HTML, and Static Export

  • Decide whether markdown is authored input, intermediate content, or build output before changing the renderer.
  • Pair renderer changes with preview or validation when feasible.
  • For static-exported CMS systems, validate rewritten permalinks and asset paths after build changes.

Identifying the Owning Seam

Regardless of platform, locate the owning seam before editing by mapping the codebase to these CMS roles:

  • Runtime bootstrap and request routing
  • Admin or editor controllers and their view templates
  • Theme loading, template hierarchy, and shared template helpers
  • Repositories, models, or schema/migration files for content, taxonomy, and settings
  • Markdown or content transformation utilities
  • Static export, deploy, or render pipeline entry points

Step to the owning seam first, then make the smallest change that preserves the CMS structure.

Platform Notes

See references/cms-platform-workflows.md for a compact mapping of common CMS platforms, extension surfaces, and media conventions.

More skills from github/awesome-copilot

  • Aacquire-codebase-knowledgeUse this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.
  • Aacreadiness-assessRun the AgentRC readiness assessment on the current repository and produce a static HTML dashboard at reports/index.html. Wraps `npx github:microsoft/agentrc readiness` and hands off rendering to the @ai-readiness-reporter custom agent. Supports policies (--policy) for org-specific scoring. Use when asked to assess, audit, or score the AI readiness of a repo.
  • Aacreadiness-generate-instructionsGenerate tailored AI agent instruction files via AgentRC instructions command. Produces .github/copilot-instructions.md (default, recommended for Copilot in VS Code) plus optional per-area .instructions.md files with applyTo globs for monorepos. Use after running /acreadiness-assess to close gaps in the AI Tooling pillar.
  • Aacreadiness-policyHelp the user pick, write, or apply an AgentRC policy. Policies customise readiness scoring by disabling irrelevant checks, overriding impact/level, setting pass-rate thresholds, or chaining org baselines with team overrides. Use when the user asks about strict mode, AI-only scoring, custom weights, CI gating, or wants org-wide standardisation.
  • Aad-campaign-analyzerUse this skill when the user shares ad campaign performance data and asks what to cut, scale, or test. Trigger for prompts like "analyze my ad campaigns", "where am I wasting ad spend", "reallocate my ad budget", "which ads are actually working", or "ROAS analysis". Do not trigger for campaign planning or creative generation without performance data.
  • Aadd-educational-commentsAdd educational comments to the file specified, or prompt asking for file to comment if one is not provided.
  • Aadobe-illustrator-scriptingWrite, debug, and optimize Adobe Illustrator automation scripts using ExtendScript (JavaScript/JSX). Use when creating or modifying scripts that manipulate documents, layers, paths, text frames, colors, symbols, artboards, or any Illustrator DOM objects. Covers the complete JavaScript object model, coordinate system, measurement units, export workflows, and scripting best practices.
  • Aagent-architectureDesign AI agent architectures through requirements discovery, or audit and diagnose architectural flaws in existing agents. Architecture only; excludes implementation and general code review.
  • Aagent-governancePatterns and techniques for adding governance, safety, and trust controls to AI agent systems. Use this skill when: - Building AI agents that call external tools (APIs, databases, file systems) - Implementing policy-based access controls for agent tool usage - Adding semantic intent classification to detect dangerous prompts - Creating trust scoring systems for multi-agent workflows - Building audit trails for agent actions and decisions - Enforcing rate limits, content filters, or tool restrictions on agents - Working with any agent framework (PydanticAI, CrewAI, OpenAI Agents, LangChain, AutoGen)
  • Aagent-owasp-complianceCheck any AI agent codebase against the OWASP Agentic Security Initiative (ASI) Top 10 risks. Use this skill when: - Evaluating an agent system's security posture before production deployment - Running a compliance check against OWASP ASI 2026 standards - Mapping existing security controls to the 10 agentic risks - Generating a compliance report for security review or audit - Comparing agent framework security features against the standard - Any request like "is my agent OWASP compliant?", "check ASI compliance", or "agentic security audit"
  • Aagent-skill-stackFind, evaluate, and assemble the smallest compatible set of AI Agent Skills for an end-to-end natural-language goal. Use when a user wants Skills for a multi-step workflow, asks which Skills fit a project, needs an installed-Skill audit or conflict check, has low Skill recall, wants indirect helpers such as humanizers or compliance checks, or wants a project-specific Skill Stack with controlled installation. Search local Skills, registries, GitHub, and OpenCLI; compare adoption, verified fit, safety, and overlap. Do not use for locating one known or common Skill; use the generic find-skills workflow.
  • Aagent-supply-chainVerify supply chain integrity for AI agent plugins, tools, and dependencies. Use this skill when: - Generating SHA-256 integrity manifests for agent plugins or tool packages - Verifying that installed plugins match their published manifests - Detecting tampered, modified, or untracked files in agent tool directories - Auditing dependency pinning and version policies for agent components - Building provenance chains for agent plugin promotion (dev → staging → production) - Any request like "verify plugin integrity", "generate manifest", "check supply chain", or "sign this plugin"

All agent skills → · MCP servers