Agent Skills

Operate the Canva MCP for branded design work — social posts, presentations, marketing collateral, one-pagers. Use when the user wants to create or edit a Canva design, fill a brand template, resize for another format, or export a design ("Canva", "פוסט לרשתות", "מצגת", "brand template", "עצב לי", "make a deck in Canva"). Not for AI image generation or upscaling (magnific-studio), not for UI/product mockups or design-to-code (figma-studio), and not for building slide files locally (the pptx skill).

Drive a pull request to convergence through the Codex AI reviewer — build → PR → @codex review → verify each finding against HEAD → fix the real ones with regression tests → re-trigger until clean → human reviews last. Use when a PR is open or just pushed and should be reviewed, when the user mentions "codex", "@codex review", "the review loop", "ultrareview", or asks to iterate a PR to green.

Use this skill IMMEDIATELY whenever the message contains "fable-mode", "fable mode", "פייבל", or "מצב פייבל" — including as a prefix before a task (e.g. "fable-mode: review this...") — no matter what the task itself is. Also use it proactively, unprompted, in two situations: (1) the user wants a fact double-checked or verified against a live source instead of answered from memory — "double-check", "can you verify", "is this still true", "I don't trust my memory", current versions/limits/pricing/capabilities of tools, APIs, or services; (2) the task is costly if wrong — production changes, migrations, deletions, security, money, architecture commitments, debugging, or research synthesis. Enforces strict planning, verification, and calibrated claims; stays active for the rest of the conversation until "fable-mode off" / "כבה מצב פייבל". Do NOT use for casual questions, trivial edits, creative writing, or when "fable" appears only as an ordinary word (writing a fable, defining it).

Route design work through the Figma MCP — client-site mockups, UI screens, design-to-code, code-to-design, FigJam diagrams. Use when the user wants to mock up a page or screen, implement a Figma design as code, push a page into Figma, diagram a flow, or shares a figma.com URL ("Figma", "FigJam", "mockup", "מוקאפ", "design-to-code"). Not for branded social posts or presentations (canva-studio) and not for AI image generation or upscaling (magnific-studio).

Audit and cut GitHub Actions minutes consumption in a repo — measure real usage first, hunt REDUNDANT work before optimizing existing work (does this job need to run at all? at this frequency? only then tune it), detect double-builds against deploy platforms (Vercel/Netlify/Cloudflare Pages/Cloudways), then propose exact diffs grouped by delete/reduce-frequency/optimize. Use whenever the user's intent is to SPEND LESS on CI — reduce GitHub Actions minutes, audit CI cost or billing, ask why Actions usage is high, ask what CI work can be cut or is redundant, request a CI-efficiency review of `.github/workflows/`, or mention "gha-optimizer". Read-only by default — never edits workflows without explicit approval. The dividing line is intent, not subject matter: this skill answers "what is our CI costing us, and what can we delete?" It is the wrong skill for "make this CI work" — writing a new workflow, or fixing a red/failing/misconfigured job — where the user wants MORE working CI, not less CI.