Discover and install skills, docs, and rules to enhance your AI agent's capabilities.
| Name | Contains | Score |
|---|---|---|
fern-api/fern How to author custom commands for the no-content-response CLI using the co-generated SDK. | Skills | |
fern-api/fern How to author custom commands for the multi-url-environment-reference CLI using the co-generated SDK. | Skills | |
civitai/civitai Manage Flipt feature flags - list, create, enable/disable, and configure rollout rules. Use when you need to control feature flag state or set up segmented rollouts. | Skills | |
NVIDIA/OpenShell Guide for developing the OpenShell TUI — a ratatui-based terminal UI for the OpenShell platform. Covers architecture, navigation, data fetching, theming, UX conventions, and development workflow. Trigger keywords - term, TUI, terminal UI, ratatui, openshell-tui, tui development, tui feature, tui bug. | Skills | |
cobusgreyling/loop-engineering Takes a structured list of changes from changelog-scan and produces a clean, categorized, user-facing release notes draft. Follows project voice and conventions. Never publishes — only proposes a draft file or section. | Skills | |
korchasa/flowai-plugins Guide for creating persistent AI rules — coding standards, project conventions, file-specific patterns. Use when users want to create a rule, set up conventions, or ask where rules go. Works across IDEs (Cursor, Claude Code, OpenCode). | Skills | |
garrytan/gbrain Morning preparation. Calendar lookahead, meeting context loading, open threads from yesterday, active task review. Extends briefing with actionable prep. | Skills | |
garrytan/gbrain Where new brain files go. Decision protocol for filing brain pages by primary subject, not by format or source. Reference for all brain-writing skills. | Skills | |
simstudioai/sim Validate an existing Sim webhook trigger against provider API docs and repository conventions | Skills | |
simstudioai/sim Audit React Query usage for best practices — key factories, staleTime, mutations, and server state ownership | Skills | |
odysseus-dev/odysseus Make scoped state changes with target confirmation, minimal mutation, and read-back verification | Skills | |
thedaviddias/Front-End-Checklist Use when applies to all interactive elements on touchscreen interfaces: buttons, links, checkboxes, radio buttons, form inputs, icon buttons, and menu items. Check CSS for min-width, min-height, width, height, and padding on interactive elements. Particularly important for icon-only buttons (close, delete, share) which are often made too small. | Skills | |
thedaviddias/Front-End-Checklist Use when reviewing rendered HTML, interactive components, or design-system patterns related to Avoid sensory-only instructions. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant. | Skills | |
thedaviddias/Front-End-Checklist Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use semantic list elements. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant. | Skills | |
thedaviddias/Front-End-Checklist Use when reviewing HTTP response headers for privacy hardening on any website that handles authentication, session state, or sensitive URL parameters. | Skills | |
thedaviddias/Front-End-Checklist Use when reviewing rendered HTML, interactive components, or design-system patterns related to Provide alternative text for objects. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant. | Skills | |
thedaviddias/Front-End-Checklist Use when reviewing CI coverage, automated checks, or test strategy related to Follow mocking best practices. Focus on whether the rule is continuously verified, not just documented. | Skills | |
thedaviddias/Front-End-Checklist Use when reviewing rendered HTML, interactive components, or design-system patterns related to Avoid meta refresh redirects. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant. | Skills | |
thedaviddias/Front-End-Checklist Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use descriptive link text. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant. | Skills | |
thedaviddias/Front-End-Checklist Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use exactly one main landmark. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant. | Skills |
Can't find what you're looking for? Evaluate a missing skill.