cogni-workspace

Standard theme picker for all cogni-works ecosystem plugins. Discovers themes from the standard cogni-workspace themes directory and the user's workspace themes directory, then presents an interactive picker via AskUserQuestion. Returns the absolute path to the selected theme.md file. Use this skill whenever a downstream skill needs a theme — before generating slides, dashboards, web narratives, big pictures, storyboards, HTML reports, or any other themed output. Triggers on phrases like "pick a theme", "choose theme", "which theme", "select a theme", or when any visual output skill needs theme resolution. Also triggers when skills internally need theme selection as a prerequisite step. This is the single standard entry point for theme selection across both cogni-works and cogni-works-pro marketplaces.

File and track GitHub issues (bugs, feature requests, change requests, questions) against cogni-works ecosystem plugins. Guides users through a short consultation to capture the right details, resolves the target plugin's repository automatically, drafts issues from templates, creates them via `gh` CLI, and tracks them locally. Use this skill whenever the user wants to report a bug, request a feature, file a change request, ask a question about a plugin, list filed issues, or check issue status. Also trigger when the user says things like "this plugin is broken", "I found a problem with {plugin}", "can we get X added to {plugin}", "{plugin} doesn't work", "open an issue", "something is wrong with {plugin}", "das Plugin funktioniert nicht", "Fehler in {plugin}", or any complaint/suggestion about a specific plugin — even if they don't use the word "issue".

Manage visual design themes for the workspace — extract themes from live websites (via Chrome), PowerPoint templates, or presets, then store and apply them to all visual outputs (slides, documents, diagrams, reports). Also audits and improves existing themes: contrast/accessibility checks, palette harmony, typography pairing, and completeness review. Use this skill whenever the user mentions themes, brand colors, visual identity, extracting styles, or wants consistent look-and-feel across outputs. Also triggers when the user wants to review, audit, fix, or improve a theme — e.g., "my theme feels off", "check contrast", "improve my colors". Also triggers when the user needs help choosing or building a theme — e.g., "what theme for my brand?", "help me pick a theme", "I need a visual identity for my startup". Even if the user just says "make it match our brand", "use our company colors", or "grab the style from that site", this skill applies.

Initialize a cogni-works workspace with shared foundation for marketplace plugins. Use this skill whenever someone asks to create, set up, scaffold, or initialize a workspace — including phrases like "set up my workplace", "get started with cogni", "create a new project workspace", or any mention of workspace initialization. Also trigger when someone runs a fresh plugin install and needs the shared foundation that plugins depend on.

This skill should be used when the user asks to "update workspace", "refresh workspace", "sync workspace", "update plugins", "re-scan plugins", or mentions updating an existing cogni-works workplace. Handles plugin re-discovery, environment variable refresh, and configuration updates without losing user data.

Diagnose and report on the health of a cogni-works workspace. Use this skill whenever the user mentions workspace status, health, diagnostics, or troubleshooting — including check workspace, is my workspace ok, something broke, why isn't my plugin working, diagnose workspace, verify workspace, or any situation where understanding the workspace state would help resolve a problem. Even if the user doesn't explicitly say status, trigger this skill when they describe symptoms that suggest a misconfigured workspace (missing env vars, plugins not found, themes not loading). This is the first skill to reach for when debugging workspace issues.