dotfiles

Use this skill whenever the user asks for an overview, summary, recap, slide prep, retrospective input, or report of their completed work in the current Linear cycle, especially when they mention done tasks, current cycle, CUS, PER, PRs, pull requests, slide deck, HTML, PDF, Marp, or want the result saved into `private.plans/`. This skill verifies issues by assignee and `completedAt` window, enriches them with local git / PR context, and can emit both technical notes and slide-ready Markdown / Marp files.

Use this skill when the user asks to create a Linear task/issue/ticket (for example: "create a task in linear", "open a linear issue", "add a ticket in linear.app"). Before creating the issue, ensure these required fields are present: team, project, title, and assignee. Ask follow-up questions only for fields the user did not provide.

Generate onboarding emails for Perselio.com customers with analytics script deployment instructions. Use this skill whenever the user asks to write, draft, or compose an onboarding email, a script deployment email, a probe/sonda deployment message, or any customer communication about integrating Perselio tracking scripts. Also trigger when the user mentions "onboarding email", "sonda", "nasazeni sondy", "script deployment email", or asks to email a customer about their Perselio integration. Works with Linear issues to pull customer and site data automatically.

Use this skill when the user wants to turn currently staged git changes into a Linear issue and then start a feature branch for them. Trigger on phrases like "create a linear task based on the staged files", "make a ticket from my staged changes and branch off", "turn my staged diff into a linear issue + branch", or any request that combines inspecting staged work, opening a Linear issue, and starting a branch named after that issue. Always assigns the issue to the current user and the current cycle, and only creates the branch when on `develop`.

Add retrospective feedback from a local markdown file to a Linear retrospective issue. Use this skill whenever the user wants to submit retro notes, add retro feedback, merge retrospective content into a Linear issue, find the matching retrospective Linear task for today, or says things like "add this to the retro", "put my retro feedback into CUS-xxx", "merge my retro notes into Linear", "add retro from file to issue". Also trigger when the user references a local retro markdown file together with a Linear issue identifier (e.g. CUS-283).

Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.

Improve skill from current context

Use this skill when the user wants to spawn a new tmux session from a Linear task, create a dedicated git worktree with worktrunk, and optionally launch opencode to implement the task immediately. Trigger on requests like "spawn a tmux session for this Linear issue", "create a worktree from CUS-123", "start working on this ticket", "open this Linear task in opencode", or "make a separate feature env for this issue".