Lazyvim expert

Skill papanito/ai-skills/skills/lazyvim-expert

[MIRROR] My personal AI skills

Install

npx -y skills add papanito/ai-skills --skill lazyvim-expert

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

specialized protocol for Neovim/LazyVim configuration. Handles lazy.nvim plugin specs, Lua API integration (Snacks, LazyVim.util), and Cloud Engineering LSP/DAP setups.

SKILL.md

1.3 KB, 321 tokens by cl100k_base, as published. Nobody here has run it

lazyvim-config-engineer

CONTEXT

Target: LazyVim (v10+).
Environment: Linux/Cloud (K8s, Go, Terraform, Rust).
Stack: lazy.nvim, Snacks.nvim, Mason, Treesitter, Telescope/Picker.

INHERITANCE RULES

Architecture: Modular files in ~/.config/nvim/lua/plugins/*.lua.
Preference: opts = function(_, opts) over config = ... to preserve upstream defaults.
Merging: vim.tbl_deep_extend("force", ...) or table.insert(opts.sources, ...).
Extras first: Check LazyVim.extras (e.g. lang.go) before custom specs.

CLOUD-NATIVE WORKFLOW

Schema-awareness: Configure yamlls for Kubernetes/GitHub Actions schemas.
Root detection: LazyVim.root() for monorepo/SRE workspace logic.
Tooling: Snacks.terminal or Snacks.picker for CLI integrations (fzf, ripgrep, yq).

OUTPUT SCHEMA

All code blocks follow the LazyVim starter template:

return {
  "author/plugin-name",
  dependencies = { "optional/dependency" },
  opts = function(_, opts)
    return vim.tbl_deep_extend("force", opts, {
      property = "value",
    })
  end,
}

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most project setup skills give in 321 tokens

Counted across 999 of the 1,637 authors here whose files we hold, read 2026-08-07

ask one question at a timein 29 of 999, across 28 files
detect the package manager from lockfilesin 28 of 999, across 9 files
present findings to the userin 26 of 999, across 5 files
explore current repo statein 24 of 999, across 3 files
update the agent skills block in place if it existsin 24 of 999, across 3 files
install husky lint-staged and prettierin 23 of 999, across 4 files
create the lintstagedrc filein 22 of 999, across 3 files
commit all changed filesin 22 of 999, across 3 files
run lint-staged to verify it worksin 22 of 999, across 3 files
create the husky pre-commit filein 21 of 999, across 2 files
create a prettierrc file if missingin 21 of 999, across 2 files
initialize huskyin 21 of 999, across 2 files

Said here and by no other author read

place plugin specs in modular lua files
prefer opts functions over config functions
merge options with vim.tbl_deep_extend
check lazyvim extras before custom specs
configure yamlls schemas for kubernetes
use lazyvim root for workspace logic

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.