ReddRadar
Agent skills
Skills you can use with AI coding agents, indexed from public GitHub repositories.
-
review
Performs code review analysis across Quality, Regression, Documentation, and Performance focus areas with severity-classified findings. Use when user asks to "review code", "review this PR", "check code quality", "review changes", or "do a code review".
jiyeol-lee/dotfiles 1
-
check
Verifies code quality through linting, type-checking, formatting, and testing. Use when asked to "run checks", "validate code", "lint this", "check for errors", "run tests", or "verify code quality" before or after changes.
jiyeol-lee/dotfiles 1
-
task-breakdown
Decomposes complex goals into atomic, dependency-aware work items with execution plans. Use when asked to "break down this task", "create a task plan", "decompose this goal", "split this work", "plan the implementation", "what are the steps", or "create an execution plan".
jiyeol-lee/dotfiles 1
-
code
Implements features, fixes bugs, refactors code, and writes unit and integration tests. Use when asked to "implement", "fix a bug", "refactor", "add a feature", "write tests", "add test coverage", or "update code".
jiyeol-lee/dotfiles 1
-
grill-me
Conducts thorough interviews to deeply understand user needs, requirements, and context before any implementation begins. Use when requirements are unclear, assumptions need validation, edge cases need exploration, when the user says "grill me", "ask me questions", "help me think through this", or when the underlying problem isn't fully understood.
jiyeol-lee/dotfiles 1
-
devops
Handles CI/CD configurations, containerization, deployment scripts, and infrastructure as code. Use when asked to "set up CI/CD", "create a pipeline", "write a Dockerfile", "configure deployment", "add GitHub Actions", "write Terraform", or "set up infrastructure".
jiyeol-lee/dotfiles 1
-
review-validation
Validates PR review comments against actual code by analyzing reviewer claims to determine if they are valid or invalid. Use when user asks to "validate review comments", "check if review feedback is correct", "verify PR review", or "are these review comments valid".
jiyeol-lee/dotfiles 1
-
e2e-test
Writes and runs end-to-end tests using Playwright. Use when user asks to "write E2E tests", "add end-to-end tests", "test this user flow", "fix flaky tests", "debug test failures", or "add Playwright tests". Also use when validating user-facing workflows or creating page object models.
jiyeol-lee/dotfiles 1
-
document
Creates and maintains project documentation including README files, API docs, changelogs, and architecture docs. Use when user asks to "write a README", "document this project", "update the docs", "create a changelog", "add API documentation", or "generate architecture docs".
jiyeol-lee/dotfiles 1
-
skill-creator
Creates new Agent Skills (SKILL.md files) following the agentskills.io open standard. Use when user asks to "create a skill", "write a skill", "make a new skill", "build a skill", "scaffold a skill", or needs help with skill structure, frontmatter, progressive disclosure, or skill authoring best practices.
jiyeol-lee/dotfiles 1
-
prd
Creates Product Requirements Documents (PRDs) as MD files in __docs/prd/. Use when asked to "write a PRD", "create a product requirements document", "draft requirements", "write requirements for a feature", "create a spec", or "document product requirements".
jiyeol-lee/dotfiles 1
-
providers
Use when switching between LLM providers, accessing provider-specific features (Anthropic caching, OpenAI logprobs), or using raw SDK clients - covers multi-provider patterns and direct SDK access for OpenAI, Anthropic, Google, and Ollama
juanre/llmring 3
-
tools
Use when implementing function calling, tool use, or agents with LLMs - unified tool API works across OpenAI, Anthropic, Google, and Ollama with consistent tool definition and execution patterns
juanre/llmring 3
-
streaming
Use when building real-time chat interfaces, displaying incremental LLM responses, or streaming output from OpenAI, Anthropic, Google, or Ollama - async iteration with usage tracking works across all providers
juanre/llmring 3
-
lockfile
Use when creating llmring.lock file for new project (REQUIRED for all applications), configuring model aliases with semantic task-based names, managing environment-specific profiles (dev/staging/prod), or setting up fallback models - lockfile creation is mandatory first step, bundled lockfile is only for llmring tools
juanre/llmring 3
-
chat
Use when starting a new project with llmring, building an application using LLMs, making basic chat completions, or sending messages to OpenAI, Anthropic, Google, or Ollama - covers lockfile creation (MANDATORY first step), semantic alias usage, unified interface for all providers with consistent message structure and response handling
juanre/llmring 3
-
structured-output
Use when extracting structured data from LLMs, parsing JSON responses, or enforcing output schemas - unified JSON schema API works across OpenAI, Anthropic, Google, and Ollama with automatic validation and parsing
juanre/llmring 3
-
project-detection
Detects project type, package manager, and monorepo structure. Returns correct commands for test/build/lint/dev. Run at project initialization and cache results in state. Use before running any build/test commands.
gruckion/marathon-ralph 13
-
setup-playwright
Configure Playwright for E2E testing. Use when setting up end-to-end tests, when no E2E framework is detected, or when the user asks to configure browser testing.
gruckion/marathon-ralph 13
-
update-state
Programmatically update marathon-ralph state file using deterministic jq commands. Use this instead of manually editing the JSON file.
gruckion/marathon-ralph 13
-
setup-vitest
Configure Vitest for unit and integration testing. Use when setting up a test framework, when no test runner is detected, or when the user asks to configure testing.
gruckion/marathon-ralph 13
-
write-playwright-test
Write Playwright E2E tests using fixtures and best practices. Use when creating E2E tests, writing browser automation tests, or testing user flows.
gruckion/marathon-ralph 13
-
visual-verification
Visually verify implemented features work correctly before marking complete. Use when testing UI changes, verifying web features, or checking user flows work in the browser.
gruckion/marathon-ralph 13
-
sqlite
gruckion/marathon-ralph 13