Chatbot Builder Skill for WordPress
A working WordPress chat plugin with a REST endpoint, a settings page, a shortcode and a block, written with you in your own repository.
Prompt file instant downloadchatbot-builder-wordpress.txt
Get this skill and 2,500+ others
$9/mo or $59 a year
Get Library · $9/moGet LibraryNothing is charged. A −30% code for your first payment arrives 2 days before the trial ends.
Need just this skill?
One file, paid once. No updates, no connector.
Costs about the same as 2 months of Library.
Included in your plan
Ask your AI for it by name, or pick it in your dashboard. No need to buy the file.
Use it in your AIPay once, keep foreverInstant download30-day money-back guarantee
As featured onProduct HuntFazierKittyLaunch
Secure checkout by Stripe
Trademarks of their respective owners. KissMySkills is not affiliated with or endorsed by them.
How it works
Ask it something hard.
Or have every skill inside your AI.
Questions before you buy? A person answers, usually the same day: hello@kissmyskills.com
// the file itself
The first lines of the file your AI will read, exactly as delivered. Nothing rewritten for the page.
You are a WordPress plugin builder, and the developer builds it with you: a chat widget, a REST route and a settings page. You have been activated to ship a plugin that keeps the key server side.
// what's inside
A WordPress developer or agency contractor who has to ship a chat widget on a client site this week.
// two ways to get it
$9/mo cancel anytime, or $59 a year
$19 one payment
Already on Library or Both? This one is included, no need to buy the file.
// ask your assistant
Go to kissmyskills.com/pages/connector and set up the "Chatbot Builder Skill for WordPress" prompt (handle: chatbot-builder-wordpress) for me
Paste it into Claude, ChatGPT, Claude Code, Cursor or Codex. Your AI walks you through connecting KissMySkills (about 3 minutes, 7-day free trial) and loads the prompt. What your AI will read →
Most WordPress chat tutorials end at a box posting to admin-ajax.php with the API key sitting in an enqueued script. A wordpress chatbot plugin built that way hands the key to anyone who opens view source, returns 403 the moment a page cache serves yesterday's nonce, and cannot stream a token, because wp_remote_post only returns once the whole body has arrived.
This is a build guide, not a plugin. You put the file in your project and open it with Claude Code or Cursor, it asks which WordPress and PHP version you are on, whether the widget is public, and where your content lives. Then it builds with you: the header block and activation hook, a settings page writing to wp_options, register_rest_route with a real permission_callback, nonce and capability checks, a shortcode and a block, transients, and WP_Query for your posts.
One purchase, yours permanently. Pay once, keep forever. The file stays in your repo and works again on the next client site.
After checkout, the download link lands in your inbox. Save the .txt file anywhere on your device.
Any AI chat you already use: Claude, ChatGPT, Gemini, Grok, Copilot or another.
Open the .txt file, copy the prompt section and paste it into Claude or ChatGPT - or add it to a Project so it is always there.
Your AI is now configured as a specialist. Ask it anything inside its domain.
No technical knowledge required.
With Library there is nothing to download. Connect your AI once, then ask for any skill by name.
No. It is a build guide you load into Claude Code, Cursor or any assistant that reads your codebase, and it writes the plugin with you. You end up owning the PHP, the REST route and the widget, so you can change the model provider, rebrand it for the next client, or hand it to plugin review without a licence attached.
It writes with you, in your editor, on your files. You still read every line, run it on a staging site, and decide what ships. The guide explains each choice before it makes it, so when the nonce check fails or the stream stalls behind nginx you know which piece to look at instead of pasting the error back in and hoping.
Sometimes, and the guide tells you how to find out on day one rather than at launch. It sends the right headers, closes the output buffers and sets X-Accel-Buffering so nginx stops buffering. Some managed hosts still buffer at a layer you cannot reach, so it also builds the non streaming fallback and a test that tells you which path you are on.
Claude Code and Cursor first, since both can read your project and write files with you. It also works pasted into Claude, ChatGPT, Gemini or Copilot if you describe your project instead. Any assistant that accepts a long instruction file will follow it.
This one and 2,500+ others, inside Claude, ChatGPT, Claude Code, Codex or Cursor. Cancel anytime.