pproenca
@pproenca
Public Skills
Invalid-Name
by pproenca
This skill has an uppercase letter in the name which should fail validation.
too-long-skill
by pproenca
This skill has more than 500 lines which should fail validation.
invalid--name
by pproenca
This skill has consecutive hyphens in the name which should fail validation.
valid-skill
by pproenca
A valid test skill with proper formatting. This skill should pass all validations and serves as a reference for the expected format.
missing-references
by pproenca
This skill references rules that do not have corresponding files in the references directory.
missing-description
by pproenca
A collection of AI agent skills following the Agent Skills open format
tui-explorer
by pproenca
Discover and replay terminal UI paths using agent-tui. Use when you need to launch a TUI app, explore navigation with bounded BFS, generate markdown acceptance tests, and verify those tests repeatedly. Do not use for web or desktop GUI automation.
agent-tui
by pproenca
Automate terminal UI (TUI) apps with agent-tui for testing, inspection, demos, and scripted interactions. Use when automating CLI/TUI flows, regression testing terminal apps, verifying interactive behavior, or extracting structured text from terminal UIs. Also use when asked what agent-tui is, how it works, or to demo it. Do not use for web browsers, GUI apps, or non-terminal interfaces.
root-cause-tracing
by pproenca
This skill should be used when the user asks to "find the root cause", "trace the bug", "why is this happening", "where does this come from", or when errors occur deep in the call stack. Systematically traces backward to identify the source.
getting-started
by pproenca
This skill is loaded automatically at session start via SessionStart hook. Establishes protocols for finding and using skills, checking skills before tasks, brainstorming before coding, and creating tasks for checklists.
systematic-debugging
by pproenca
This skill should be used when the user reports a "bug", "not working", "fix this", "debug", "test failing", or when investigating unexpected behavior. Four-phase framework ensuring root cause understanding before attempting solutions.
finishing-a-development-branch
by pproenca
Guide completion of development work by presenting merge/PR options. Use when "I'm done", "merge this", "create PR", "finish up", or when implementation is complete and tests pass.
condition-based-waiting
by pproenca
This skill should be used when the user mentions "flaky tests", "race condition", "timing issues", "wait for", "test sometimes fails", or when tests have inconsistent pass/fail behavior. Replaces arbitrary timeouts with condition polling.
simple-git-worktrees
by pproenca
This skill should be used when the user asks to "create worktree", "remove worktree", "work in worktree", "switch to worktree", "clean up worktree", mentions "repo--branch pattern", or during plan execution when worktree isolation is needed. Documents the sibling directory worktree pattern for simple, safe git worktree workflows.
defense-in-depth
by pproenca
This skill should be used when the user asks for "defensive coding", "input validation", "prevent bugs", "multiple validation layers", or when fixing bugs caused by invalid data reaching deep execution. Validates at every layer.