Hugging Face WP hands the prompt to a model on the Inference API or a dedicated endpoint, then drops the response back into WordPress as a post, a block or a stored result. The Hub owns the conversation. WordPress owns the artifact: a row in wp_posts with a title, status and author, plus wp_postmeta keys describing the model ID and task that produced it.

That artifact is what an editorial team can govern, and what the default Posts screen handles poorly. SleekView reads the same wp_posts rows and the same wp_postmeta the plugin already writes. Title, status and author sit alongside model ID, task type and endpoint as real columns. Sort by date, filter to drafts on a single model, or pull every generation that used a specific task such as text-generation or summarization, all without opening each post.

Inline edits go through the standard WordPress CRUD layer, so post-save hooks still fire, Yoast still indexes, and any plugin-side meta the integration reads on update stays consistent. Bulk-flip ten queued drafts from a single model into pending review in one pass.

Hugging Face WP is so cheap to trigger that volume grows before any reporting is in place. The default Posts screen turns that volume into a wall of titles with no way to see which model produced what or which task type was used. SleekView reads the same wp_posts rows and the same wp_postmeta keys and turns them into columns a team can sort, filter and edit.

Editorial leads stop opening every draft to check the model. Governance stops guessing about disclosure coverage. Ops stops scrolling for an older checkpoint that has not been retired.

Same data, same plugin, very different operating posture once model and task are first-class columns.