Sponsored by

Find leads on Reddit on auto pilot

Topic: linux

64 skills in this topic.

testing-api-assertions Verify API requests in tests. Use when testing that correct API calls are made for create, update, or delete operations. Use when testing mutations, form submissions, or actions with backend side effects.
stacklok/toolhive-studio 121
testing-api-overrides Test that components send correct query parameters or request arguments. Use when testing filtering, sorting, pagination, or any read operation where request parameters matter. Use for test-scoped mock customization.
stacklok/toolhive-studio 121
deep-links Deep links in ToolHive Studio. Use when implementing, debugging, or asking about deep link features (toolhive-gui:// protocol), adding new deep link intents, understanding the deep link architecture, IPC model, or platform/packaging support.
stacklok/toolhive-studio 121
security-vuln-remediation Remediate security vulnerabilities found by Grype or pnpm audit. Use when a security scan fails, a CVE needs fixing, or you need to analyze, upgrade, override, or ignore a vulnerable dependency.
stacklok/toolhive-studio 121
testing-api-assertions Verify API requests in tests. Use when testing that correct API calls are made for create, update, or delete operations. Use when testing mutations, form submissions, or actions with backend side effects.
stacklok/toolhive-studio 121
skill-creator Create new AI agent skills for Claude Code, Codex, and Cursor. Use when asked to create a skill, add a new agent capability, or set up a slash command.
stacklok/toolhive-studio 121
skill-editor REQUIRED for editing any skill file. Ensures changes sync to Claude, Codex, and Cursor. Never edit .claude/skills/ files directly - always use this skill.
stacklok/toolhive-studio 121
deep-links Deep links in ToolHive Studio. Use when implementing, debugging, or asking about deep link features (toolhive-gui:// protocol), adding new deep link intents, understanding the deep link architecture, IPC model, or platform/packaging support.
stacklok/toolhive-studio 121
testing-with-api-mocks Start here for all API mocking in tests. Covers auto-generation, fixtures, and when to use other skills. Required reading before creating, refactoring, or modifying any test involving API calls.
stacklok/toolhive-studio 121
testing-api-overrides Test that components send correct query parameters or request arguments. Use when testing filtering, sorting, pagination, or any read operation where request parameters matter. Use for test-scoped mock customization.
stacklok/toolhive-studio 121
self-improve
ebowwa/seed 2
distributed-claude-receiver You are a remote Claude instance running on a VPS. Receive messages via chat.sh wrapper, maintain persistent context, use Z.ai GLM backend via Doppler.
ebowwa/seed 2
distributed-claude-sender Send prompts to a remote Claude instance on a VPS for distributed AI collaboration, different model backends, or independent context.
ebowwa/seed 2
propose-change Propose code changes to the supervisor Claude. Generate diffs and rationale, but do not execute. Wait for supervisor approval.
ebowwa/seed 2
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
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
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
z-tools Review GitHub pull requests with Jira context using local `prdump`, `jiradump`, and `gh` tools. Use when a user asks for a PR review by providing a PR URL and Jira ticket URL(s), or when a PR description references Jira IDs/URLs that should be pulled for additional context.
dreikanter/dotfiles 1
z-tools Review GitHub pull requests with Jira context using local `prdump`, `jiradump`, and `gh` tools. Use when a user asks for a PR review by providing a PR URL and Jira ticket URL(s), or when a PR description references Jira IDs/URLs that should be pulled for additional context.
dreikanter/dotfiles 1
prdump Dump GitHub PR details (title, branch, description, discussion, reviews, inline comments) using the local `prdump` CLI tool. Use when a user wants to inspect or review a PR by URL.
dreikanter/dotfiles 1
notes Create and access notes in date-based archive. Create notes with auto-incremented IDs, generate daily todos with task rollover, find latest notes by type (note/todo/backlog/weekly), search by ID/slug/tags/content.
dreikanter/dotfiles 1
jiradump Dump Jira ticket details and comments using the local `jiradump` CLI tool. Use when a user wants to inspect a Jira ticket by URL or key (e.g., ABC-123).
dreikanter/dotfiles 1
firefox-bookmarks Analyze Firefox bookmarks and tags directly from the places.sqlite database. Extract recent bookmarks, analyze tag popularity, find bookmark statistics, and explore bookmark metadata. Use when working with Firefox bookmarks, analyzing bookmark usage, organizing tags, or extracting bookmark data from Firefox profiles.
dreikanter/dotfiles 1
eod Generate a daily EOD report and save it as a note. Optional arg: date in free format (e.g. 'yesterday', '2d ago', 'last Friday', '2026-03-05').
dreikanter/dotfiles 1