wp-agent-toolkit-orchestrator
Skill1 starsChanged 33 days agoMITView on GitHub
Orchestrates building WP Agent MCP end-to-end by invoking the bootstrap, MCP, Cursor plugin, helper plugin, and demo skills in the correct order.
In this repository11 other files it gives its agents.
- .cursor/rules/00-project-overview.mdcCursor rule
- .cursor/rules/10-architecture-and-safety.mdcCursor rule
- .cursor/rules/20-indexing-and-audit-contracts.mdcCursor rule
- .cursor/rules/30-mcp-implementation-guidelines.mdcCursor rule
- .cursor/rules/40-wp-introspection-guidelines.mdcCursor rule
- wp-agent-toolkit-bootstrapSkill
- wp-agent-toolkit-cursor-pluginSkill
- wp-agent-toolkit-demoSkill
- wp-agent-toolkit-design-bridgeSkill
- wp-agent-toolkit-mcp-serverSkill
- wp-agent-toolkit-wp-helper-pluginSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use when the user asks to build, scaffold, or implement the WP Agent MCP plugin.
- Very specific: line 21
Ensure PROJECT_CONTEXT.md exists and matches the POC spec.
- Distinctive: line 26
Write demo prompts + acceptance checklist + troubleshooting.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
WP Agent MCP Orchestrator
When to use
Use when the user asks to build, scaffold, or implement the WP Agent MCP plugin.
Responsibilities
- Drive an end-to-end vertical slice: connect -> index -> audit -> similarity -> (optional) patch apply.
- Delegate to the specialized skills below instead of doing everything at once:
- /wp-agent-toolkit-bootstrap
- /wp-agent-toolkit-mcp-server
- /wp-agent-toolkit-cursor-plugin
- /wp-agent-toolkit-wp-helper-plugin
- /wp-agent-toolkit-demo
Execution plan (always follow in order)
- Ensure
PROJECT_CONTEXT.mdexists and matches the POC spec. - Bootstrap repo structure (directories, placeholder manifests, configs).
- Implement MCP server endpoints + indexer schema + contracts.
- Implement Cursor plugin packaging (skills, rules, settings guidance).
- Optional: generate WP helper plugin skeleton (runtime registry).
- Write demo prompts + acceptance checklist + troubleshooting.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.