Cross-plugin workflow templates for common multi-plugin pipelines. Use this skill whenever the user asks about workflows, pipelines, end-to-end processes, "how do I go from X to Y", "what's the process for", "show me the steps", "workflow for", "pipeline from research to slides", "how do these plugins work together", or wants guidance on chaining multiple insight-wave plugins. Also trigger when a user describes a multi-step task that spans plugins — even if they don't say "workflow" explicitly.
From cogni-helpnpx claudepluginhub cogni-work/insight-wave --plugin cogni-helpThis skill is limited to using the following tools:
evals/evals.jsonreferences/workflows/docs-pipeline.mdreferences/workflows/full-onboarding.mdreferences/workflows/new-engagement.mdreferences/workflows/portfolio-to-pitch.mdreferences/workflows/research-to-slides.mdreferences/workflows/trend-to-marketing.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.
Provide step-by-step playbooks for common multi-plugin workflows. These are guided reference templates — not automated orchestration (that's cogni-consulting's job).
Read the workspace language from .workspace-config.json in the workspace root
(language field — "en" or "de"). Explain pipeline steps, use cases, 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.)/workflow, /consult, etc.)research-to-slides, trend-to-marketing, etc.)Six bundled templates covering the most common plugin chains:
| Workflow | Pipeline | Use case |
|---|---|---|
research-to-slides | research → narrative → visual | Analyst producing a presentation from research |
trend-to-marketing | tips → portfolio → marketing | GTM team turning trends into campaigns |
portfolio-to-pitch | portfolio → narrative → sales → visual | Sales creating a customer pitch deck |
docs-pipeline | doc-start → audit → generate → sync → power → claude → hub → bridge | Maintainer documenting the monorepo |
new-engagement | consulting setup → 4 phases | Consultant starting a structured engagement |
full-onboarding | workspace → help courses 1-11 | New user learning the full ecosystem |
Read the matching template from references/workflows/.
Present the pipeline visually — use the Mermaid diagram or ASCII flow from the template so the user can see the full chain at a glance.
Walk through each step with:
Adapt to context — if the user already has some steps done ("I have my portfolio data, now what?"), skip to the relevant step in the pipeline.
When /workflow is invoked with no argument, present the table above and ask
which workflow the user wants to explore.
The docs/workflows/ directory contains user-facing workflow tutorials generated by
cogni-docs. These complement the bundled templates above — the templates here are
step-by-step playbooks with commands and tips; the docs/ guides are narrative tutorials
with context and variations.
| docs/ workflow | Related template | Notes |
|---|---|---|
docs/workflows/research-to-report.md | research-to-slides | Same pipeline, docs version focuses on the report |
docs/workflows/portfolio-to-pitch.md | portfolio-to-pitch | Same pipeline |
docs/workflows/trends-to-solutions.md | trend-to-marketing | Same starting point, different end goal |
docs/workflows/consulting-engagement.md | new-engagement | Same pipeline |
docs/workflows/content-pipeline.md | trend-to-marketing | Marketing-focused variant |
When presenting a workflow, mention the corresponding docs/ guide if it exists:
"For a narrative walkthrough with more context, see docs/workflows/<name>.md."
If a user describes a pipeline that doesn't match any template, compose one on
the fly using the plugin catalog from the guide skill (../guide/references/plugin-catalog.md).
Explain the reasoning for each plugin choice.