Creator Assistant Knowledge

Creator Assistant Knowledge is an add-on for Creator Assistant – Hub that lets you maintain a private, admin-only knowledge base. Entries are vectorized and stored in your Qdrant cluster so the AI can draw on them when answering search queries — without ever exposing them to site visitors.

Your existing posts and pages are never modified. The plugin creates a new private post type (ca_knowledge) and creates draft entries when visitors give negative feedback on an AI answer. No public content is touched.

Key features

• Private knowledge base — a dedicated Knowledge section appears in the WordPress admin where you can write private articles, FAQs, and reference material for the AI. These entries are completely invisible to visitors: they have no public URL, do not appear in search results, and are never linked from the frontend.
• Automatic indexing into a private collection – knowledge entries are vectorized by Creator Assistant Hub whenever they are published or updated, into a Qdrant collection this plugin owns (creator_assistant_knowledge_chunk) rather than the shared one. Nothing else on the site can read them: only the AI Overview answer does.
• Feedback loop — when a visitor reports that an AI Overview answer did not help (or a search query receives no answer at all), the plugin automatically creates a draft knowledge entry pre-filled with the query and the AI response. Admins can review and improve these drafts, then publish them so the AI learns from the gap.
• No duplicate drafts – before creating one, the plugin compares the query with the searches already assigned to existing entries. The same question asked in different words is added to the entry that already covers it instead of producing a second draft, and the entry counts one more request. How similar two searches have to be is a setting.
• Sorted by demand – the entry list shows how many times each gap was asked for, and the column sorts, so you can answer the questions people actually ask first.
• Origin at a glance – the entry list also shows why each draft exists: a negative rating, an unanswered search, or written by hand, so you know which entries came from a real gap before you open them.
• Sources shown only to editors – knowledge entries contribute to the AI answer, and the AI Overview panel lists them as sources only for users who can edit them, linking to the edit screen. A visitor never sees them: a source with no public URL would be a dead link, and the knowledge base stays invisible end-to-end.

Requirements

• Creator Assistant – Hub installed, activated, and configured.
• Creator Assistant Search (for the feedback feature).
• WordPress 6.6 or higher.
• PHP 7.4 or higher.

External services

This plugin relies on Creator Assistant – Hub for its connections to OpenAI and Qdrant; see the Hub’s own “External services” section for full details on that data flow. This plugin’s own use of those services:

• OpenAI: knowledge base entries are sent to the Embeddings API (via the Hub) whenever they are published or updated, to generate the vector used to index them and to match visitor searches against private entries.

  • Service: https://platform.openai.com/
  • Privacy Policy: https://openai.com/policies/privacy-policy
  • Terms of Use: https://openai.com/policies/terms-of-use

• Qdrant Cloud: knowledge entry vectors are stored in two collections this plugin owns (creator_assistant_<id>_knowledge_chunk and creator_assistant_<id>_knowledge_intent, where <id> is the random identifier Creator Assistant Hub gives each site so several sites can share one Qdrant cluster), separate from the Hub’s shared collection so nothing else can read them.

  • Service: https://cloud.qdrant.io/
  • Privacy Policy: https://qdrant.tech/legal/privacy-policy/
  • Terms of Service: https://qdrant.tech/legal/terms_and_conditions/

Data is only transmitted once you have configured Creator Assistant – Hub with your own API credentials and accepted its Terms of Service. Nothing is transmitted automatically upon activation of this plugin.

Development

The plugin ships no compiled assets: assets/js/feedback.js, assets/js/editor-panel.js and assets/css/feedback.css are hand-written and need no build step. Only the PHP development tooling has to be installed to work on it.

composer install installs PHPCS with the WordPress and VIP standards, PHPStan and PHPUnit. Then:

• npm run lint:php runs PHPCS, npm run fix:php applies the automatic fixes.
• npm run analyse:php runs PHPStan, which also scans the Hub and Search sibling plugins because their classes are used throughout.
• npm test runs the unit tests. They use hand-written WordPress stubs and load neither WordPress, a database, nor the Hub.
• npm run check runs the WordPress.org Plugin Check CLI.