What would be your preferred interface for creating agent skills in WordPress?

a) all front-matter fields in the editor area (ACF-style), or

b) all front-matter fields in the sidebar panel?

Thanks to the "Agent Skills Discovery via Well-Known URIs" RFC from Cloudflare we can have WordPress as the Skills CMS with the convenience of `npx skills add https://…`

I really hope we eventually arrive at an open package standard for bundling these custom AI plugins that can be self-hosted and installed using any AI GUI harness.

Currently all the nice AI things are mostly available to developers who can run CLI commands.

See https://github.com/cloudflare/agent-skills-discovery-rfc

So when is every new plugin an AI plugin?

1. Exponential — late 2029
2. Linear — by 2038.

Nice read from Casey: https://caseyrb.com/blog/ai-plugins-on-wordpress-org/

Agent skills and instructions need a CMS so that teams can collaborate on these critical assets without having to learn git and cli tooling.

WordPress is a CMS. Can we make it do this?

There is a proposal to add a wp_knowledge post type (and a matching taxonomy) to WP core https://make.wordpress.org/core/2026/06/22/merge-proposal-guidelines-built-on-knowledge/ but it is not landing soon. The idea is to test it as a plugin first.

Check your AI tool memories (under ~/.codex/memories and ~/.claude/projects). I find that most of them are actually polluting the context and not helping.

We often overlook how WordPress was THE vibe coding of the previous decades. Now there are just way more options available.

the no-tool and no-rag approach of claude code feels to be wasting tokens and working through things slower. what's your experience?

same model in cursor is way faster and productive.

The Jetpack monorepo is 767MB 🐡

Mostly because of the tracked build files (roughly 360MB) which are not even part of the current work tree.

Would you trust AI to run this?

Will it actually apply those single quotes when running it?

It created the ~ directory itself during previous runs so it is trying to clean up.

Responded to @kasparsd:

I first heard about this concept from Adam Jacob on the Changelog podcast covering his Swamp project https://changelog.com/friends/130

Here is a crazy idea — pull requests will get replaced by issues or feature requests as the primary way of contributing to open source projects.

Pull requests require that we trust the code offered for merging. Yes, we can ask AI to review the code but there is still a lot of risk associated with it.

As humans we can reliably control only the inputs to the AI models which is the issue or feature request describing the desired outcomes.

Responded to @py2toz:

@py2toz with a 6V panel you don’t need MPPT since it is so close to the voltage of the board.

I would connect it directly to Heltec’s 5V pins since the onboard TP4054 can handle 6.5V per datasheet.

Wrote about my experience here https://kaspars.net/blog/solar-lora-meshtastic

Federated and independent web is a user experience and usability challenge.

Here is a great list of known issues and how they’re being addressed across the ecosystem. https://wedistribute.org/2026/04/the-seven-deadly-fediverse-ux-sins-a-redemption-report-card/

Funny how macOS search (both Finder and Spotlight) is so bad that I don’t even think of using it.

Imagine how bad AI would do if it couldn’t search properly.

Are there recent Mac apps that are trying to solve this?

Somebody should unleash AI agents on the WP trac backlog, have it track all steering decisions and see where we land. We sure could get a core committer skill out this 😅

Responded to @kasparsd:

A sidecar approach might work better but it would require polling for filesystem changes and parsing the cache files which do have the response headers in there.

Spent the Saturday afternoon exploring ways to add surrogate-key (also known as cache tags) support for Nginx fastcgi cache which is otherwise great with state-while-revalidate support, etc.

Considered creating an Nginx module but there don't appear to be any hookable events when the cache files are written. The idea would be too keep an index of tags mapped to cache files on disk and have a route for invalidating by tags.

Responded to @kasparsd:

I worked on an API for that a while back: https://github.com/wpelevator/encrypted-secrets

The Connectors screen in WP 7.0 would really benefit from encrypted options unless we want to expose those API keys to anyone with access to wp-admin/options.php

ChatGPT wouldn't do it, Claude wouldn't do it.

Eventually tried Perplexity and it was able to generate notes with correct code snippets from my WordPress course videos. Amazing since it didn't have to invent anything — just capture everything I said and include the relevant code snippets.

The trick was to create 1 FPS videos with full audio so that it still has access to full video contents and audio but with ~5% of the file size. Worked great.