Sponsored by

Find leads on Reddit on auto pilot

Topic: neovim

14 skills in this topic.

skill-creator Create effective skills. Use when creating or updating skills.
n4vysh/dotfiles 5
terraform-module Inspect Terraform module specs from cache when seeing module sources.
n4vysh/dotfiles 5
clarifying-intent Use when user asks to create, build, design, add, or generate something — especially when the request is vague, underspecified, or the scope is unclear. Use before starting creative work, features, components, or any new functionality.
l-lin/dotfiles 16
clear-writing Use when writing or editing any prose humans will read — documentation, commit messages, error messages, UI text, reports, or explanations. Also use when user says "write clearly", "clear writing", or "improve writing".
l-lin/dotfiles 16
code-simplifier Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Use when asked to "simplify code", "clean up code", "refactor for clarity", "improve readability", or review recently modified code for elegance. Focuses on project-specific best practices.
l-lin/dotfiles 16
tmux Use when you need a persistent terminal environment for long-running processes, programs requiring a TTY, REPLs, debuggers, TUI apps, or concurrent terminals — while the agent continues executing other commands.
l-lin/dotfiles 16
writing-skill Use when creating new skills, editing existing skills, or verifying skills work before deployment
l-lin/dotfiles 16
pi-extension-builder Use when user says "create pi extension", "build extension for pi", "extend pi", or wants to customize pi agent behavior with tools, commands, events, or UI components.
l-lin/dotfiles 16
jira Manage JIRA tickets. Use it when the user mentions JIRA with ticket IDs like FOO-123.
l-lin/dotfiles 16
datadog-pup Use when interacting with Datadog resources using the `pup` CLI, especially for APM traces, metrics, monitors, notebooks, and synthetic tests.
l-lin/dotfiles 16
napkin Maintain a per-repo napkin as a continuously curated runbook (not a session log). Activates EVERY session. Read and curate it before work, keep only recurring high-value guidance, organize by priority-sorted categories, and cap each category at top 10 items..
l-lin/dotfiles 16
code-simplifier Simplify and refine code for clarity, consistency, and maintainability while preserving functionality. Use when asked to "simplify", "clean up", or "refactor" code, after writing complex code that could benefit from simplification, or when code has grown hard to follow.
caarlos0/dotfiles 206
go-doc Get documentation for any Go library using `go doc`. Use when asked about Go package documentation, API reference, function signatures, or how to use a specific Go library/package.
caarlos0/dotfiles 206
go-performance Analyze and optimize Go program performance. Use when asked to profile Go code, find performance bottlenecks, analyze memory allocations, detect memory leaks, write benchmarks, or optimize CPU/memory usage.
caarlos0/dotfiles 206