Help users find the right insight-wave plugin or skill for their task. Use this skill whenever the user asks "which plugin should I use", "what can I do with insight-wave", "find me a skill for X", "recommend a plugin", "where do I start", "help me find the right tool", "what plugins are available", "I need to do X — which plugin handles that?", or any question about plugin capabilities, ecosystem navigation, or tool selection. Also trigger when a user seems lost or unsure which plugin to use for a specific task — even if they don't explicitly ask for guidance.
From cogni-helpnpx claudepluginhub cogni-work/insight-wave --plugin cogni-helpThis skill is limited to using the following tools:
evals/evals.jsonreferences/plugin-catalog.mdDesigns and optimizes AI agent action spaces, tool definitions, observation formats, error recovery, and context for higher task completion rates.
Enables AI agents to execute x402 payments with per-task budgets, spending controls, and non-custodial wallets via MCP tools. Use when agents pay for APIs, services, or other agents.
Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.
Help users navigate the insight-wave ecosystem by matching their task to the right plugin(s). Users often know what they want to accomplish but not which of the 15+ plugins handles it. Your job is to bridge that gap quickly and accurately.
Read the workspace language from .workspace-config.json in the workspace root
(language field — "en" or "de"). Present recommendations, descriptions, and
guidance in that language.
If the file is missing or unreadable, detect the user's language from their message. If still unclear, default to English.
Keep in English regardless of language setting:
cogni-trends, cogni-narrative, etc.)/cheatsheet, /workflow, etc.)Read the catalog at references/plugin-catalog.md — it contains every plugin,
its skills, key commands, and typical use cases.
Match the user's intent to 1-3 plugins. Think about what they're actually trying to accomplish, not just keyword matches. "I need to make slides" could mean cogni-visual (presentation from narrative), course-deck (training slides), or cogni-marketing (campaign materials).
Present recommendations with:
docs/plugin-guide/<plugin>.md for detailed guidance (if the docs/ directory exists)For multi-plugin tasks, suggest a sequence: "Start with cogni-research for the
report, then cogni-narrative to shape the story, then cogni-visual for slides."
Mention the /workflow command if a matching workflow template exists.
For learning-oriented queries ("how does X work?", "explain X", "I want to
understand X"), also recommend the docs/ resources listed in the plugin catalog's
"User Documentation" section. Point to docs/getting-started.md for new users and
docs/ecosystem-overview.md for ecosystem questions.
If the user's task doesn't match any plugin, say so clearly. Don't force-fit a plugin to a task it wasn't designed for. Suggest the user check if a community plugin exists or consider building one.
When the user asks for an overview (no specific task), present the ecosystem map:
Research & Intelligence: cogni-research, cogni-trends, cogni-claims, cogni-portfolio Content & Transformation: cogni-narrative, cogni-copywriting, cogni-visual Go-to-Market: cogni-marketing, cogni-sales Orchestration: cogni-consulting, cogni-workspace Support & Learning: cogni-help (this plugin)
For detailed information on any plugin, read the full catalog reference.