Skip to content

Add wp-knowledge skill - #67

Open
artpi wants to merge 7 commits into
WordPress:trunkfrom
artpi:codex/wp-guideline-skill
Open

artpi wants to merge 7 commits into
WordPress:trunkfrom
artpi:codex/wp-guideline-skill

Conversation

@artpi

@artpi artpi commented Jun 10, 2026 •

Copy link
Copy Markdown

Summary

Adds a new wp-knowledge skill for WordPress Guidelines and Knowledge integrations, covering the wp_knowledge CPT, wp_knowledge_type taxonomy, /wp/v2/knowledge, /wp/v2/content-guidelines

What is wp knowledge

Knowledge is mostly a convention and a CPT meant to create a unified procedure to store agent-related data on WordPress.
It's currently shipped in Gutenberg 23.6 and was slated to enter Core in 7.1 but was postponed.

More about overall strategy and context:
https://piszek.com/2026/07/03/wordpress-ai-strategy/
https://piszek.com/2026/07/03/wp-knowledge-beyond-ai/

@artpi artpi changed the title [codex] Add wp-guideline skill [codex] Add wp-knowledge skill Aug 5, 2026
@artpi
artpi marked this pull request as ready for review August 5, 2026 13:28
@github-actions

github-actions Bot commented Aug 5, 2026 •

Copy link
Copy Markdown
Contributor

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: artpi <artpi@git.wordpress.org>
Co-authored-by: gziolo <gziolo@git.wordpress.org>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

@artpi artpi changed the title [codex] Add wp-knowledge skill Add wp-knowledge skill Aug 5, 2026

Until Knowledge ships in Core, require WordPress 7.0+ behavior through Gutenberg 23.6+ with the Guidelines experiment active. Do not create parallel post types such as `wp_skill`, `wp_memory`, or plugin-specific options when the target site supports `wp_knowledge`.

Settings > Guidelines is a user-facing surface on top of Knowledge. Its scope rows are still `wp_knowledge` posts with `wp_knowledge_type=guideline`; use `/wp/v2/content-guidelines` only for that Settings experience and `/wp/v2/knowledge` for general document rows.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I need to double-check with @aagam-shah, but I think it uses the default /wp/v2/knowledge endpoint now. There is only one additional endpoint that returns the list of guideline types because they are filterable, and plugins can add or remove their UI sections.

@gziolo

gziolo commented Aug 6, 2026

Copy link
Copy Markdown
Member

Nice work, this matches Gutenberg trunk almost everywhere. Two notes:

/wp/v2/content-guidelines is legacy. It was removed from Gutenberg. The replacement is /wp/v2/knowledge/guideline-scopes, a read-only registry that lists the guideline scopes with their UI labels. All rows (including guideline rows) go through the regular /wp/v2/knowledge collection. Scopes are also extensible via the wp_guideline_scopes filter, worth mentioning since the skill presents the list as fixed.

Type term helper. Gutenberg already ships wp_knowledge_get_or_create_type_term(), which does what the custom my_plugin_get_knowledge_type_term_id() example does (plus locale handling). Might be simpler to point to that.

Everything else looks good to me.

@artpi

artpi commented Aug 6, 2026

Copy link
Copy Markdown
Author

Two notes:

Good catch, addressed!

@bgrgicak
bgrgicak requested a review from a team September 22, 2026 05:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants