Install AI skills for WordPress, Divi, Elementor and Shopify Print

Quick answer

Install a reviewed skill in the AI tool on your computer, confirm that the current session can find it, and start with a read-only task. A skill supplies instructions and sometimes scripts. Site access comes separately through an authorized editor, file connection or API. Choose the skill for the site's actual platform and builder before allowing changes.

Applies to

Customers using Codex or Claude Code with an Interactive Online-hosted WordPress website, or with a separately hosted Shopify store. These are AI-agent skills, not WordPress plugins to upload through Plugins. A plugin in an AI app's marketplace is also different from a WordPress plugin. WordPress Pro is a community skill name and does not describe a hosting plan or a WordPress product subscription.

1. Choose the smallest useful set

• Routine page wording or an image: start with the site's normal editor. ChatGPT or Claude can prepare the copy for you to paste.
• WordPress code: use WordPress Pro or the WordPress project's task-specific skills.
• Elementor pages: use the matching builder workflow. Jezweb's WordPress Elementor skill currently declares Claude Code compatibility.
• Divi 5: distinguish Elegant Themes' built-in AI Agent from the separate DiviOps skill and connector workflow.
• Shopify: use Shopify's AI Toolkit and the skills for the relevant store or theme task. Shopify storefronts run on Shopify, not inside a cPanel document root.

2. Review the source and choose an installation scope

1. Use the publisher links in the platform guides below. Read the skill's SKILL.md, referenced files, scripts, prerequisites and license before installing. A familiar name in a directory is not proof of publisher identity.
2. Prefer a project installation when you only need the skill for one website. Use a personal installation when you deliberately want it across projects. Inspect existing copies first; two copies can load conflicting instructions.
3. Keep downloaded skills, private configuration and recovery copies outside the site's public web folder. If your local project is later uploaded, exclude its instruction and credential folders from public deployment.
4. Keep the complete skill folder, including required references or scripts. For a published plugin bundle, use its supported installer rather than copying a single Markdown file out of the bundle.

3. Load the skill in Codex or Claude Code

In Codex, use the built-in $skill-installer with the exact GitHub skill-folder URL. Ask it to identify existing copies and the destination before installation. Current OpenAI documentation describes repository and user discovery under .agents/skills; older distributions may use different paths. Use the installer and confirm what your actual session discovers.

In Claude Code, follow the publisher's plugin installation instructions when supplied. For a reviewed standalone skill, copy its complete folder into .claude/skills/skill-name/ in the intended project, with SKILL.md directly inside it. Personal skills use ~/.claude/skills/. Preserve existing files and use one installation method. Follow the client's reload or restart instructions when a new skill is absent.

4. Verify the installation before connecting a site

1. Open the intended website project. Ask the assistant to identify the installed skill, its file path, required references and any missing dependencies. Compare its answer with the files on disk and the tool's skill list.
2. Use the exact discovered name, for example $wordpress-pro in Codex or /wordpress-pro for a standalone Claude Code skill. Plugin-provided command names can be namespaced; use the name shown by that client.
3. Request a read-only explanation of a sanitized local file. A successful answer proves that narrow exercise, not access to the hosting account.
4. Before a site write, verify the site identity, affected page, authorized connection, recoverable checkpoint and requested change. Keep live publication as a deliberate reviewed action.

Skill not showing up in Codex or Claude Code

Check the exact folder name, front matter, installation scope, missing referenced files and duplicate copies. A folder nested one level too deep may not be discovered. A skill that expects a browser or MCP server cannot create those tools by itself. In ordinary ChatGPT or Claude conversations, check that product's current skills and app capabilities separately; installing a local Codex or Claude Code skill does not install it in every chat product.

When to contact support

Contact Interactive Online when the hosting account, WordPress installation, document root or available access method is unclear. Provide the affected page URL, tool and plugin versions, time and time zone, and the exact redacted error. Exclude passwords, Application Passwords, keys, tokens, cookies and customer records. Skill publishers handle their own installation defects and feature requirements; AI subscriptions, paid builders and connector licenses are separate from hosting.

Related help

• WordPress Pro setup and a scoped coding task
• Official WordPress skills by task
• WordPress Elementor for Claude Code
• DiviOps skills and native Divi 5 editing
• Shopify AI Toolkit setup
• Keep website project instructions in AGENTS.md and CLAUDE.md

Documentation and downloads

• OpenAI: skill discovery and installation
• Anthropic: Claude Code skill locations and invocation

Documentation and source review by Interactive Online: November 2, 2026. Installation sources and instructions were reviewed. A new installation or connected editing test was not performed for this article; confirm the versions, tools and permissions available in your own environment.