thehelpfultipperthehelpfultipper/wp-agent-mcp/.cursor/skills/wp-agent-toolkit-cursor-plugin/SKILL.mdwp-agent-toolkit-cursor-plugin
Skill1 starsChanged 33 days agoMITView on GitHub
Packages rules and skills into a Cursor plugin bundle and documents how to connect to the local MCP server and a WP root.
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-demoSkill
- wp-agent-toolkit-design-bridgeSkill
- wp-agent-toolkit-mcp-serverSkill
- wp-agent-toolkit-orchestratorSkill
- 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, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use when preparing the Cursor Marketplace plugin bundle and wiring it to the local MCP server.
- Distinctive: line 16
verify wp-cli is available
- Distinctive: line 29
Create a concise README section describing:
≈ “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
Cursor Plugin Packaging (POC)
When to use
Use when preparing the Cursor Marketplace plugin bundle and wiring it to the local MCP server.
Required plugin contents
- .cursor/rules/*.mdc (project rules)
- .cursor/skills/* (skills listed in this repo)
- Documentation for local configuration:
- choose WP root
- verify wp-cli is available
- run "build index"
- run "audit component"
UX guidelines
- Provide a "happy path" workflow:
- Connect local WP root
- Build index
- Audit existence/variants
- Find similar usage
- (Optional) apply patch
Output requirement
Create a concise README section describing:
- native run vs docker run for MCP server
- troubleshooting steps (wp-cli missing, db access)
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.