Email, calendars, task management, and automation (7.8K skills)
Read, create, and update notes in Espen's Obsidian vault (PARA method). Use when asked about notes, tasks, projects, dashboards, daily logs, or anything in the vault.
The English summary is being prepared. Showing the original description.
Delegate tasks to specialized subagents for parallel or sequential execution.
The English summary is being prepared. Showing the original description.
Delegate a coding task to Mistral Vibe and supervise the result via git diff. Trigger: /vibe <instruction>. Claude orchestrates, Vibe codes. Also handles /vibe-report [--since N] [--project NAME] [--fails] — token/cost/failure report.
The English summary is being prepared. Showing the original description.
Closed-loop compare-adjust-repeat workflow for fitting Blender models to supplied front/side/back/top templates and originals. Use when the user asks to compare the product to templates/originals and adjust until it fits across all dimensions, or when all views must pass measurable bbox/centroid/silhouette/edge validation before export.
The English summary is being prepared. Showing the original description.
Harmonize multiple Blender skills into a coherent pipeline with clear activation precedence, handoff artifacts, dependency gates, and conflict-resolution rules. Use when a Blender task spans several skills, when reference-locked work conflicts with generic production workflow, after adding/updating skills, or when repeated failures indicate skill interference or missing inter/intra-play.
The English summary is being prepared. Showing the original description.
End-to-end production workflow guidance for Blender — the order to assemble scenes (block-out → camera → light → forms → materials → detail → render → composite → export), critique protocols, time budgets, and recovery patterns. Use whenever the user asks to "make a complete scene / hero shot / production-quality render", "what's the right order to do this", "set up a full pipeline", or has a multi-step request crossing modeling + lighting + materials + rendering. Make sure to use this skill for any request that spans multiple phases of 3D work, even if the user does not say "workflow" — also covers "make a final image of X", "produce a hero render", "professional-looking result".
The English summary is being prepared. Showing the original description.
Use when a task touches a Jupyter or marimo notebook, asks to productionise or schedule notebook logic, or when you are tempted to do the work in a notebook — extract logic into tested modules, keep the notebook thin and reproducible, and commit it the way the repo does
The English summary is being prepared. Showing the original description.
Use when an analiz task arrives in done (approved) - turn the approved split into implementation tasks with repository, AC, derived_from and ordering arguments
The English summary is being prepared. Showing the original description.
Use when you start an analiz task - explore every affected repository and resolve unknowns before writing the report
The English summary is being prepared. Showing the original description.
Use when a task in code_review was sent back before (an earlier need_revision comment exists) - verify every prior point was fixed at its root
The English summary is being prepared. Showing the original description.
Use when an approved analiz spans more than one repository - split the work per repository and open one or more tasks per repository, each carrying its own plan slice
The English summary is being prepared. Showing the original description.
Use when you finish an analiz report - the human must approve the analysis before any implementation task is created, via the analiz_review column
The English summary is being prepared. Showing the original description.
Use when a product decision or feature needs a written record - what to capture in a task document (PRD, decision record) and where to attach it, since TaskTrooper has no epic
The English summary is being prepared. Showing the original description.
Use when a task is in pm_uat - verify every acceptance criterion and the human's comments yourself in the browser, on a device, or over a loopback HTTP request, record a verdict per criterion, then move to human_uat or need_revision
The English summary is being prepared. Showing the original description.
Use when planning a delivery request as the only orchestration agent - one board-writing subtask, backlog first, one approval question, then move approved tasks to todo
The English summary is being prepared. Showing the original description.
Use when a task changes any screen, form, dialog, menu or control - Lighthouse/axe scan of the changed screens, a keyboard walk, and the thresholds that fail a task
The English summary is being prepared. Showing the original description.
Use when you create an implementation board task directly - the required fields, one-role-one-deliverable rule, and dependency ordering
The English summary is being prepared. Showing the original description.
Wire the automation test project into the repository's own pipeline so every task must pass the suite before it can leave QA
The English summary is being prepared. Showing the original description.
Use when a stakeholder sends a request - route it to backlog tasks, an analiz task, or a focused question, decide ask-vs-assume with a Definition of Ready, and ask only what a wrong guess would actually cost
The English summary is being prepared. Showing the original description.
Use when defining a feature - name what is in scope, out of scope, and assumed, and handle mid-flight expansion without corrupting in-progress tasks
The English summary is being prepared. Showing the original description.
Use when the stakeholder asks about an analysis outcome or its implementation tasks - understand the human approval gate and review the tasks the architect created once the human approved
The English summary is being prepared. Showing the original description.
Use when the stakeholder asks a factual or status question about the workspace - call the matching read tool and answer conversationally, without creating tasks or asking for approval
The English summary is being prepared. Showing the original description.
Use when opening an analiz task for the system-architect - the required fields, what the criteria may say, and what the description must hand over
The English summary is being prepared. Showing the original description.
Use when starting a mobile task that could be Flutter or native - decide from the existing app, platform-specific needs, and the analiz task
The English summary is being prepared. Showing the original description.