Add AI authorship disclosure per WordPress AI Guidelines#7
Add AI authorship disclosure per WordPress AI Guidelines#7Jameswlepage merged 2 commits intotrunkfrom
Conversation
Adds disclosure to README and creates docs/ai-authorship.md with detailed breakdown of how skills were created, reviewed, and tested. Fixes #6
|
|
||
| Agent Skills are portable bundles of instructions, checklists, and scripts that help AI assistants (Claude, Copilot, Codex, Cursor, etc.) understand WordPress development patterns, avoid common mistakes, and follow best practices. | ||
|
|
||
| > **AI Authorship Disclosure:** These skills were generated using GPT-5.2 Codex (High Reasoning) from official Gutenberg and WordPress documentation, then reviewed and edited by WordPress contributors. We tested skills with AI assistants and iterated based on results. This is v1, and skills will improve as the community uses them and contributes fixes. See [docs/ai-authorship.md](docs/ai-authorship.md) for details. ([WordPress AI Guidelines](https://make.wordpress.org/ai/handbook/ai-guidelines/)) |
There was a problem hiding this comment.
Overkill to link to the root docs? It will help if we're gonna let agents self-contribute and whenever folks are migrating to the next context product, but otherwise probably excessive.
There was a problem hiding this comment.
Conversely, a reasonable number of in-content links to docs helps get folks there who might not otherwise see / know about them
docs/ai-authorship.md
Outdated
|
|
||
| 3. **Contributor Review**: WordPress contributors reviewed each skill for accuracy, alignment with current best practices, and completeness. | ||
|
|
||
| 4. **AI-Assisted Testing**: Skills were tested by using them with AI coding assistants (Codex and Claude Code) on real WordPress development tasks, sourced from [WP Bench](https://make.wordpress.org/ai/2026/01/14/introducing-wp-bench-a-wordpress-ai-benchmark/) to verify they produce correct guidance. That said, skills have not (yet) been run across a formal evaluation system, as one does not exist. |
There was a problem hiding this comment.
as one does not exist.
This would be a good place to link to a ticket. If we don't have one (yet), I think italics would help this (IMO) important explanation not get lost in the wall of text.
docs/ai-authorship.md
Outdated
|
|
||
| All v1 skills followed the same process described above. As skills diverge in their development history, this table will be updated. | ||
|
|
||
| | Skill | AI Generated | Human Reviewed | Tested | Notes | |
There was a problem hiding this comment.
What are Notes supposed to represent? I'd assume they would be regarding the skills efficacy or other things that came up during or may have influenced review . We have an existing source of truth for skill contents.
docs/ai-authorship.md
Outdated
| | wp-project-triage | Yes | Yes | Yes | Includes detection scripts | | ||
| | wp-block-development | Yes | Yes | Yes | Core Gutenberg block patterns | | ||
| | wp-block-themes | Yes | Yes | Yes | theme.json, templates, patterns | | ||
| | wp-plugin-development | Yes | Yes | Yes | Hooks, settings API, security | |
There was a problem hiding this comment.
Beyond the scope, but IMO would be good to link these directly to the relevant SKILL.md. A big feedback point around skills is the friction around auditing them (not showing authors or having versions, not being able to easily tell/inspect what's inside the skill or scripts it bundles etc), so reducing the number of paths for humans/agents to see the specific skills feels like a low-effort "best practice" thing we can do 🤔
|
|
||
| ## Evolution | ||
|
|
||
| This disclosure will be updated as: |
There was a problem hiding this comment.
No need for a changelog or a last-updated because we have the commit history, right?
justlevine
left a comment
There was a problem hiding this comment.
Overall love it, none of the comments are particularly "blocking" imo.
|
Noting that its worth watching what lands in WordPress/wordpress-develop#10850 and replicating that here (and other WP AI-related repos) |
- Italicize "as one does not exist" for emphasis on eval caveat - Remove redundant Notes column from per-skill table - Link each skill name to its SKILL.md for easier auditing
Summary
Addresses the requirements in the WordPress AI Guidelines for transparent disclosure of AI-assisted contributions.
Fixes #6