Loading...
Loading...
Found 158 Skills
Guidance for using the App Store Connect CLI in this repo (flags, output formats, pagination, auth, and discovery). Use when asked to run or design asc commands or interact with App Store Connect via the CLI.
Use when creating, applying, or validating overlay files including x-speakeasy extensions. Covers overlay syntax, JSONPath targeting, retries, pagination, naming, grouping, open enums, global headers, custom security. Triggers on "create overlay", "apply overlay", "overlay file", "x-speakeasy", "add extension", "configure retries", "add pagination", "overlay for retries".
This skill provides comprehensive knowledge for TanStack Query v5 (React Query) server state management in React applications. It should be used when setting up data fetching with useQuery, implementing mutations with useMutation, configuring QueryClient, managing caching strategies, migrating from v4 to v5, implementing optimistic updates, using infinite queries, or encountering query/mutation errors. Use when: initializing TanStack Query in React projects, configuring QueryClient settings, creating custom query hooks, implementing mutations with error handling, setting up optimistic updates, using useInfiniteQuery for pagination, migrating from React Query v4 to v5, debugging stale data issues, fixing caching problems, resolving v5 breaking changes, implementing suspense queries, or setting up query devtools. Keywords: TanStack Query, React Query, useQuery, useMutation, useInfiniteQuery, useSuspenseQuery, QueryClient, QueryClientProvider, data fetching, server state, caching, staleTime, gcTime, query invalidation, prefetching, optimistic updates, mutations, query keys, query functions, error boundaries, suspense, React Query DevTools, v5 migration, v4 to v5, request waterfalls, background refetching, cacheTime renamed, loading status renamed, pending status, initialPageParam required, keepPreviousData removed, placeholderData, query callbacks removed, onSuccess removed, onError removed, object syntax required
This skill should be used when user asks to "query Supabase", "list Supabase tables", "get Supabase schema", "search Supabase records", "check Supabase database", "Supabase auth", "Supabase authentication", "RLS policy", "row level security", "Supabase foreign key", "table relationships", "Supabase join", "Supabase filter", "Supabase pagination", or needs guidance on Supabase database patterns, auth flows, RLS policies, or query best practices.
RESTful API design guidelines following the Richardson Maturity Model through to Level 3 (HATEOAS) for Ruby on Rails. This skill should be used when designing, building, reviewing, or refactoring REST APIs to ensure proper resource modeling, HTTP method semantics, hypermedia controls, content negotiation, and API evolvability. Triggers on tasks involving API controllers, serializers, routing, link relations, pagination, error handling, or HTTP caching in Rails.
USE FOR web search. Returns ranked results with snippets, URLs, thumbnails. Supports freshness filters, SafeSearch, Goggles for custom ranking, pagination. Primary search endpoint.
Provides usage guidance for Instructure UI (InstUI) React components. Use when working with @instructure/ui packages, when asked how to use InstUI components, which component to choose, or how to apply props, guidelines, theming, or accessibility rules. Covers AiInformation, Alert, AppNav, Avatar, Badge, Billboard, Breadcrumb, Button, Byline, Calendar, Checkbox, CheckboxGroup, CloseButton, ColorContrast, ColorIndicator, ColorMixer, ColorPicker, ColorPreset, CondensedButton, ContextView, DataPermissionLevels, DateInput, DateInput2, DateTimeInput, DrawerLayout, Drilldown, Editable, FileDrop, Flex, FormField, FormFieldGroup, Grid, Heading, IconButton, Img, InlineList, InPlaceEdit, InstUISettingsProvider, Link, List, Menu, Metric, MetricGroup, Modal, NutritionFacts, NumberInput, Overlay, Pages, Pagination, Pill, Popover, ProgressBar, ProgressCircle, RadioInput, RadioInputGroup, RangeInput, Rating, Responsive, Select, SideNavBar, SimpleSelect, SourceCodeEditor, Spinner, Table, Tabs, Tag, Text, TextArea, TextInput, TimeSelect, ToggleButton, ToggleDetails, ToggleGroup, Tooltip, TopNavBar, Tray, TreeBrowser, TruncateText, View.
Netra MCP trace-debugging workflow focused on query_traces and get_trace_by_id, including exact input parameters, filter schema, operators, sorting, and pagination patterns.
Composes, debugs, and optimizes Guillotine GraphQL queries for Enonic XP headless content delivery. Covers query construction, variable usage, filtering, aggregation, pagination, sorting, and TypeScript type generation from the auto-generated Guillotine schema. Use when writing or troubleshooting Guillotine queries, querying custom content types through GraphQL, or generating typed interfaces from Guillotine responses. Don't use for content type XML definitions, non-Enonic GraphQL APIs (Apollo, Hasura), server-side lib-content queries, or Guillotine deployment and CORS configuration.
Uses the TweetSmash REST API to fetch bookmarks, inspect labels, and add or remove labels from saved tweets. Use when integrating TweetSmash into scripts, agents, workflows, cron jobs, or internal tools that need bookmark retrieval, filtering, pagination, or label management. Do not use for direct browser automation inside TweetSmash, unrelated X or Twitter APIs, or tasks that only need product marketing copy.
Test and troubleshoot Enable Banking sandbox integrations, ASPSP sandbox behavior, Mock ASPSP setup, sandbox credentials, AIS authorization simulation, transaction pagination quirks, and sandbox limitations. Use when Codex needs to choose a sandbox bank, find test credentials, explain why a sandbox ASPSP behaves differently from production, configure Mock ASPSP data, or implement project code that must work against Enable Banking sandbox environments.
Use this skill when the user wants to read or search their Monologue notes through the Monologue Notes REST API. It covers authentication with the MONOLOGUE_API_KEY environment variable, safe token handling, listing notes, fetching a single note, pagination, filters, and error handling. The API is read-only and should be accessed with direct HTTP requests such as curl or any equivalent REST client.