Add a new knowledge source (Google Doc, PDF, URL, blog post, meeting transcript, repo) to the AI Asset Registry project. Use this skill whenever the user wants to incorporate a new document, reference, or source material into the project's knowledge base — including when they say "add this doc", "incorporate this source", "register this reference", "I have a new document", "add this blog", or share a Google Doc/PDF/repo/blog link for project use. Also use when updating the knowledge registry with new information from any source, including Red Hat blog posts, Red Hat Developer blog articles, or external technical blog content.
Create Red Hat blog posts or review existing drafts through a multi-agent pipeline with iterative quality improvement. Use this skill whenever the user wants to write a blog post, create blog content, draft a Red Hat blog, review a blog draft, improve a blog post, or says things like "write a blog about X", "I need a blog post", "review my blog draft", "help me with a blog", "create a developer blog", or "blog about [topic]". Also use when the user shares a Google Doc or draft and wants it turned into a polished Red Hat blog post.
Create or update polished HTML presentations following Red Hat branding standards. Use this skill whenever the user wants to create a presentation, slide deck, overview page, pitch deck, scrolling narrative, executive summary page, or says things like "create a presentation about X", "I need a slide deck", "make an overview page", "build a presentation", "update the presentation", or "presentation for [audience]". Also use when the user has existing HTML presentations they want to refresh, extend, or adapt for a different audience. Covers both slide-deck format (keyboard-navigated, full-screen slides) and vertical-scrolling format (long-form narrative pages with fixed header navigation). Requires the superpowers plugin (for brainstorming) and benefits from Google Workspace MCP (for accessing GDrive source materials).
Set up, bootstrap, or health-check the ai-asset-registry repo on a machine. Use this whenever the user wants to get the repo working on a new or other computer, load/configure its MCP servers (slack, google-workspace, rhai-tracker), or verify/repair the environment — git submodule, skill symlinks, Jira credentials, the customer-tracker (c-track) clone. Also use it for anything blocking the Slack MCP specifically: "is the slack mcp installed correctly", "slack tools aren't loading", "did podman set up right", "install podman for slack", "my slack tokens expired / invalid_auth", or checking whether the podman engine (not just Podman Desktop) and its machine are ready. Trigger on phrases like "set up this repo", "bootstrap the repo", "load the repo on my other laptop", "check my environment", "is my setup correct", "my MCPs/symlinks/skills are broken", "run the doctor", or "did the .env load everything". Runs an idempotent bootstrap.sh: a read-only health check by default, or a setup mode that writes configs fro
Sync customer tracking data from the local HTML interest tracker to the shared Google Sheet via the rhai-tracker MCP. Use when the user says "sync the tracker", "push to the sheet", "update the shared tracker", "sync customers to gdrive", "compare local vs remote tracker", "diff the trackers", or wants to review what's changed between the local HTML tracker and the team's centralized Google Sheet. Also use when the user has updated the local HTML tracker and wants those changes reflected in the shared sheet, or when they want to see which customers are in one tracker but not the other.
Use when adding a new customer or updating an existing customer in the customer interest tracker from a meeting transcription, email thread, Jira ticket, pasted notes, or any source containing customer requirements/interests. Also use when the user says "add this customer", "update the tracker", "ingest this feedback", or shares a new transcription file.
Use when reviewing or refreshing the customer interest tracker for accuracy, staleness, or completeness. Also use when the user says "refresh the tracker", "check for stale items", "review action items", "update tracker status", or wants to audit the tracker against current project state.
Create a comprehensive multi-page HTML knowledge hub website for any product or technology, sourcing content from Google Docs, GitHub repos, Jira, Slack, and local docs. Use when the user wants to build a product information site, knowledge base, documentation hub, or "everything you need to know" site for a product, component, or technology. Also use when the user says "create a knowledge site", "build a product hub", "make an info site", "I need a product knowledge base", or references creating something similar to the MCP Gateway Knowledge Hub (RHCL site).