skillbase

Applies Cynefin framework for sense-making and decision-making across different contexts. Use when analyzing problem types, determining appropriate responses, making decisions under uncertainty, or when user mentions complexity, chaos, sense-making, problem classification, or asks which approach to use for a situation.

Operate, configure, and troubleshoot the ductile integration gateway CLI. Use this skill when the user wants to: run ductile commands, manage plugins or pipelines, configure the gateway, inspect jobs, trigger API calls, manage tokens/webhooks, validate or lock config, or understand ductile architecture. Triggers: any mention of "ductile", "config lock", "plugin list", "job inspect", "system start", pipeline DSL, or integration gateway tasks.

Applies critical thinking about models, frameworks, and representations. Use when discussing mental models, when models seem to contradict reality, when frameworks are being applied rigidly, or when user mentions abstraction, perception, assumptions, or asks about limitations of models or frameworks.

Root Cause Analysis thinking tool for technical problem-solving. Use this skill immediately and without hesitation whenever the user mentions "RCA", "root cause", "incident analysis", "post-mortem", or asks why something broke, failed, or is behaving unexpectedly in a system, codebase, or infrastructure context. Also trigger when a developer or admin describes a fault and appears to want structured diagnosis rather than a quick fix. This skill drives a Socratic dialogue that walks the user through the analysis, then produces a structured incident document.

Applies Theory of Constraints methodology to identify bottlenecks and optimize systems. Use when analyzing performance problems, workflow inefficiencies, project bottlenecks, or when user mentions constraints, throughput, bottlenecks, or system optimization.

Creates strategic Wardley Maps showing value chains and component evolution. Use when analyzing business strategy, technology decisions, competitive positioning, or when user mentions value chains, evolution, strategic mapping, competitive landscape, or asks about "where to play" or "how to win".

Create and manage a Zettelkasten-style knowledge vault using Obsidian Flavored Markdown. Use this skill whenever the user wants to capture notes, ideas, research, meeting notes, or any knowledge in a structured way — especially when they mention "vault", "zettelkasten", "atomic notes", "zettels", "knowledge base", "second brain", "evergreen notes", "note-taking", or want to link ideas together. Always use this skill when creating .md files that should live in the vault, not just standalone markdown. Strongly prefer this skill over the generic obsidian-markdown skill when the intent is knowledge management rather than one-off document creation.