Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions .claude-plugin/plugin.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,6 @@
{
"name": "wordpress-api-pro",
"displayName": "WordPress API Pro",
"description": "Manage WordPress sites via REST API β€” posts, media, Elementor content, ACF/JetEngine fields, WooCommerce, SEO meta, site audit, and safe batch operations.",
"author": { "name": "Digitizer" }
}
17 changes: 17 additions & 0 deletions .claude/settings.json
Original file line number Diff line number Diff line change
@@ -0,0 +1,17 @@
{
"extraKnownMarketplaces": {
"digitizer-skills": {
"source": { "source": "github", "repo": "Digitizers/agent-skills" }
}
},
"enabledPlugins": {
"agent-skills@digitizer-skills": true,
"cloudways-mcp@digitizer-skills": true,
"hostinger-mcp@digitizer-skills": true,
Comment on lines +8 to +10

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Remove unrelated plugins from the project configuration

In a checkout of this standalone WordPress plugin, these project-scoped settings enable the entire marketplace suiteβ€”including hosting, ads, Aura, and Sumit pluginsβ€”even though repo-wide search shows no dependency on them. Contributors who have those plugins installed will therefore activate unrelated MCP integrations whenever they open this repository; keep only this project's required plugin entries, or leave personal marketplace selections in local settings.

Useful? React with πŸ‘Β / πŸ‘Ž.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Deliberate, spec-mandated (same as the sibling repos): the committed settings block declares the full Digitizers toolbox in every toolbox repo so team cloud/phone sessions load it everywhere. Claude Code prompts per user before activating project-declared plugins β€” nothing activates silently.

"aura-mcp@digitizer-skills": true,
"wordpress-api-pro@digitizer-skills": true,
"siteagent-elementor-studio@digitizer-skills": true,
"meta-ads-mcp@digitizer-skills": true,
"sumit-mcp@digitizer-skills": true
}
}
1 change: 1 addition & 0 deletions .claude/skills/wordpress-api-pro
16 changes: 16 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -87,6 +87,22 @@ cd wordpress-api-pro
bash INSTALL.sh
```

### Windows note

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Restore the documentation displaced by the Windows note

This replacement leaves the README ending immediately after the Windows note and removes roughly 300 lines of user-facing material, including setup requirements, environment configuration, quick-start commands, safety guidance, script documentation, and the ClawHub release procedure. Plugin packaging does not make those repository instructions obsolete, so retain the existing sections and insert the Windows guidance without truncating everything that followed the Claude Code installation block.

Useful? React with πŸ‘Β / πŸ‘Ž.


The plugin ships its skill through a git **symlink** (`skills/` β†’ the in-repo
source). On Windows, enable Developer Mode and set
`git config --global core.symlinks true` **before** cloning or installing β€”
the plugin cache clone inherits it. Changing the config does not repair an
existing checkout (the repo may have recorded `core.symlinks=false` locally).
To repair one, run these two commands inside it (the second re-materializes
only the plugin's symlink entries, so nothing else in your working tree is
touched):

git config core.symlinks true
git checkout -- skills/ .claude/skills/

Or simply re-clone. WSL also works. macOS/Linux need nothing.

Then restart Claude Code, export `WP_URL` / `WP_USERNAME` / `WP_APP_PASSWORD` (or set up `config/sites.json`), and ask Claude to use it. The ACF / SEO / JetEngine / plugin-detection scripts need `requests` (`pip install requests`); the core post/page/media/WooCommerce/batch scripts use the Python stdlib only.

> Pairs well with the [Elementor MCP kit](https://github.com/Digitizers/siteagent-elementor-studio): build pages with the MCP, then handle media uploads, SEO meta, custom fields, and WooCommerce with these scripts.
Expand Down
1 change: 1 addition & 0 deletions skills/wordpress-api-pro
Loading