Jylhis

Track external upstream skill repositories: import a skill from upstream into this catalogue, modify it locally without losing the baseline, monitor the upstream for new commits since the last review, and review each upstream commit one-by-one to accept, skip, defer, or cherry-pick it into the local copy. Use when the user says "import skill from <repo>", "vendor <repo>", "monitor upstream for new commits", "what's changed upstream", "check upstream for updates", "review upstream commit", "backport <sha>", or "follow <repo> for new skills". Operates on `upstream/sources.yaml` (manifest), `upstream/decisions/<id>.log` (per-source review cursor), and `.cache/upstream/<id>.git` (local bare partial clone). Helper scripts under this skill's `scripts/` do the deterministic git work; the agent following this SKILL.md drives the decisions.

Produces a one-page cross-functional business snapshot for SMB owners — cash position (QuickBooks), sales trend (PayPal/Square), pipeline movement (HubSpot), this week's commitments (Calendar), urgent watch-list items (Gmail/Slack), and the single most important thing needing attention today. Proactively tries every available connector and gracefully scopes to whatever is connected — one connector gives a partial pulse; the full stack gives the full picture. Trigger when the user asks how the business is doing, wants a snapshot, a weekly summary, a Monday brief, or says anything like "what am I missing" or "catch me up on the business."

Reads AR/AP, historical cash timing, and known fixed costs from QuickBooks, PayPal, Stripe, or Square — or a CSV upload — and produces a 30/60/90-day cash flow forecast with percentage-variance confidence bands and named risk flags. Delivers a chat summary and a downloadable XLSX. Use when the user asks "forecast my cash flow," "will I make payroll," mentions "runway," or says "cash crunch." Falls back to CSV upload when no connector is live.

Scans HubSpot for stale deals, duplicate contacts, and missing fields, then fixes what the owner approves. Accepts optional scope argument for deals, contacts, or all.

Keeps HubSpot current without the owner opening it: creates and updates contacts and deals from email and calendar context, logs notes and calls, and flags stale records. The 'stop doing data entry' skill. Use when the user asks to update the CRM, log a call, clean up HubSpot, or add context to a deal.

Aggregates PayPal disputes, HubSpot feedback and tickets, and email sentiment (plus pasted or exported Google/Yelp reviews) into a themes report with verbatim evidence and a "do these three things this week" list. Use when the user asks how customers are feeling, for review analysis, what people are saying, or about disputes.

Drafts overdue-invoice reminder emails from QuickBooks and PayPal data, matched to each customer's payment history and tone (gentle for good customers, firm for repeat late payers). Sends via PayPal with owner approval; non-PayPal invoices queue as mail drafts. Use when the user asks "who owes me money," mentions overdue invoices, or wants to follow up on unpaid invoices.

Builds end-to-end hiring packets — job post, structured interview guide with scoring rubric, and offer letter template — from a hiring brief. Triggers on: 'help me hire', 'we're hiring for', 'write a job post', 'job description', 'JD', 'open role', 'create a job ad', 'interview questions', 'scoring rubric', 'draft an offer letter', 'send an offer', 'make a hiring packet', or any request to recruit for a position. When in doubt, trigger — covers the full hiring workflow from job post through DocuSign envelope creation via browser. Does NOT screen or rank applicants.

Create new Claude Code skills, improve existing skills, and measure skill quality through evals and benchmarks. Use when the user says things like "create a skill", "turn this into a skill", "make a skill for X", "write a SKILL.md", "run evals on my skill", "benchmark my skill", "optimize my skill description", "improve triggering", or "test my skill". Also use when the user has a workflow or conversation they want to capture as a reusable skill. Do not use for writing CLAUDE.md files, creating plugins, or general prompt engineering unrelated to skills.

Use for devenv.sh developer environment patterns including devenv.nix, devenv.yaml, devenv shell, devenv up, devenv init, devenv test, devenv languages, devenv processes, devenv services, pre-commit hooks in devenv, cachix caching, devenv.lock, direnv integration, ad-hoc nix environments, or enterShell configuration.

Use for Nix flakes structure and workflows including flake.nix, flake.lock, nix flake commands, nix develop, nix build, nix run, nix shell, nix fmt, inputs, outputs, devShells, packages, nixosConfigurations, follows, flake-utils, flake-parts, flake templates, eachDefaultSystem, or flake checks.

Use for Home Manager module patterns including home.nix, home.packages, home-manager programs modules, home.file, xdg configuration, declarative dotfiles, user configuration, home-manager switch, homeConfigurations, nix-darwin integration, programs.git, programs.zsh, programs.neovim, programs.direnv, home.stateVersion, or flake-based Home Manager.

Use for Nix debugging and troubleshooting including infinite recursion, hash mismatch, IFD import from derivation, build failures, nix log, nix why-depends, evaluation errors, attribute missing, unfree package errors, collision errors, builtins.trace, nix repl, nix eval, nix path-info, store paths, garbage collection, closure size analysis, or slow evaluation diagnosis.

Use when working with Nix expression language fundamentals including syntax, expressions, functions, builtins, let-in bindings, with expressions, inherit, rec, attrsets, attribute sets, string interpolation, derivations, import, fetchurl, fixed-point patterns, nixpkgs lib functions, lambdas, operators, or lazy evaluation.

Use for NixOS module system patterns including configuration.nix, writing modules, mkOption, mkIf, mkMerge, mkEnableOption, mkDefault, mkForce, mkPackageOption, services, systemd units, systemd hardening, networking, firewall, fileSystems, boot, option types, types.submodule, imports, or module arguments.

Use for nixpkgs package management patterns including mkDerivation, callPackage, overlays, override, overrideAttrs, buildPythonPackage, buildRustPackage, buildNpmPackage, buildGoModule, packageOverrides, derivations, fetchFromGitHub, fetchers, stdenv, build phases, nativeBuildInputs, buildInputs, cross-platform packaging, or wrapProgram.

Marchyo NixOS/Home Manager module development specialist. Use when creating, modifying, or debugging modules in the Marchyo flake — including options, tests, and integration patterns.

Diagnose Nix/NixOS build and evaluation failures in the Marchyo flake. Use when a `nix build`, `nixos-rebuild`, or `nix flake check` fails — to read the error trace, locate the offending expression, and propose a fix.

NixOS and Home Manager module development for the Marchyo flake. Use when adding modules, defining options, writing tests, or modifying the NixOS/Home Manager configuration structure.

Use this skill to generate well-branded interfaces and assets for Jylhis (jylhis.com, the personal/technical site of Markus Jylhänkangas), either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for prototyping.

Applies the Jylhis brand colors and typography to any artifact that benefits from the jylhis.com look-and-feel — slides, docs, mockups, diagrams, exported images, or production UI. Use it when brand colors, type, visual formatting, or company/personal design standards apply.

Use this skill to audit a Jylhis design-system surface (web showcase, preview card, prototype, terminal theme, CLI script, or TUI integration) against the system's accessibility commitments and the CLI/TUI design conventions. Combines automated validators with a manual review playbook covering web a11y (WCAG 2.1 AA/AAA), non-web a11y (WCAG2ICT), CLI conventions (clig.dev / GNU / 12-Factor / GitHub-CLI accessibility work), TUI design (Ratatui / Bubble Tea / Textual + WAI APG), CVD spot-checking, and keyboard / focus walk-through. Produces a structured markdown report with severity-tagged findings and pointers back to the canonical specs.

Modern Emacs Lisp development practices (Emacs 30/31) — coding and naming conventions, lexical binding, macro hygiene, hooks vs. advice, defcustom/setopt, use-package patterns, modern libraries (pcase/seq/map/cl-lib/rx), debugging, and ERT testing. Use when writing or reviewing any Elisp in this repo (lisp/init-*.el, early-init.el, init.el, test/).

Knowledge base on GNU Emacs internals (Emacs 30/31) — garbage collection, object representation, buffers and text, the redisplay engine, the command loop and keymaps, byte/native compilation, threads, and the build/dump pipeline. Use when explaining or debugging core Emacs behavior, tuning performance (GC, redisplay, startup), reasoning about native-comp/eln caches, or reviewing Elisp whose correctness depends on runtime semantics.

Manage git worktrees, project catalogs, and repository discovery with the mw CLI. Use when navigating projects, syncing repositories, checking worktree status, or managing repos.