user.key-logger

Log user-initiated events and system activities in Neovim via Lua.

1|Updated Oct 26, 2025
One-click install
npx skills add https://github.com/NeKon69/nvim-dot --skill user-key-logger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: user.key-logger
Source: https://github.com/NeKon69/nvim-dot/tree/main/.agents/skills/user.key-logger
Command: npx skills add https://github.com/NeKon69/nvim-dot --skill user-key-logger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a mechanism to log various user interactions and system events within the Neovim environment, aiding in debugging and understanding user behavior.

Core Features & Use Cases

  • Event Logging: Records events such as User, FileType, TermOpen, and BufEnter with relevant details.
  • Diagnostic Output: Writes detailed diagnostics and session information to a log file.
  • Use Case: Developers can use this to track how a specific feature is being used or to diagnose unexpected behavior by reviewing the logged events.

Quick Start

Load the user.key-logger skill to begin logging events.

Frequently Asked Questions about user.key-logger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I log user activity and events in Neovim for debugging?

Logging user activity in Neovim involves capturing events like BufEnter, FileType changes, and TermOpen. This skill records these user-initiated events and system activities using Lua scripting to aid debugging and behavior analysis.

What Neovim events can I track to monitor user behavior?

You can track User commands, FileType changes, TermOpen, and BufEnter events in Neovim. Capturing these specific event types records detailed user interactions and system activities for diagnostic purposes.

How do I write diagnostic output to a log file in Neovim?

Writing diagnostic output to a log file in Neovim is done by executing Lua-based logging functions that capture event details. This records session information and specific user interactions for review.

Do I need Lua scripting to track Neovim buffer events?

Yes, you need Neovim's Lua scripting environment to execute the side-effect driven logging functions that capture buffer events. Lua is required to track events like BufEnter and TermOpen.

Why should I use event tracking for Neovim debugging instead of manual inspection?

Event tracking for Neovim debugging automatically records user interactions and system events to a log file. This provides a detailed diagnostic trail of user behavior and unexpected issues for review.