Loading...
Loading...
Found 191 Skills
A Google Search API alternative and SERP API alternative on fetcher.sh — pay-per-call in USDC via x402, or prepaid credits with a Bearer key, no API key application. Use when the user wants programmatic Google search results as clean JSON, including Google's own operators — site:, filetype:, intitle:, and quoted exact phrases — plus pagination, language (hl), and country/region scoping. Also covers rank tracking input, competitive research, and search-result monitoring without Google's own Custom Search API quota and billing.
TanStack Table v8 patterns - useReactTable, column definitions, sorting, filtering, pagination, row selection, virtual scrolling, server-side data
Perform complete database health, correctness, performance, reliability, and scalability audits across SQL, NoSQL, key-value, cache, search, and managed database systems. Detects the existing database and query layer, then checks indexes, query plans, schemas, constraints, relations, transactions, locks, pagination, pooling, caching, migrations, backups, observability, security, retention, replication, partitioning, and capacity. Use when diagnosing slow queries, reviewing an entire data layer, preparing for growth, reducing database cost, or safely optimizing production workloads.
Build, debug, review, and explain integrations with the Listen Notes Podcast API (PodcastAPI.com). Use for podcast or episode search, metadata, recommendations, playlists, transcripts, pagination, authentication, mock-server testing, API usage, caching and attribution rules, pricing, quotas, and billing questions.
Critical Standard Bottom-Up Self-Check (check-standards, Convergence Gate) after Java backend code generation/modification. **This skill must be loaded after any Java code is written or modified—including scattered coding that does not follow the complete development process (e.g., "write an XX interface"/"write a Controller"/"help me write this code"): this skill must be loaded and verified before delivering code products to users**. It uses grep/ast-grep to actually scan and verify each standard—comments (class/field/method Javadoc/step comments, including private and extracted methods), logs (full class @Slf4j, each business method has logs, ERROR exceptions with stack traces), transaction rollbackFor, constructor injection, layered boundaries, SQL in XML, unified return body, pagination limit, password encryption, SQL comments/injection/WHERE, and all other verification items, with "File:Line Number" evidence attached to each item; **No level distinction—any item that is not implemented properly (regardless of importance) will be listed in the pending confirmation list to confirm with the user whether to complete it**. **Correct intermediate product naming and paths before verification** (Technical Solution 3.x.1 / Interface List 3.x.2 / Standard Verification Report 5.2.x / Acceptance Report 5.3.x, remove the task ID prefix T0xx from file names and move to the module version directory). Trigger scenarios: after writing code, after code generation, after modifying code, **before delivering code**, pre-submission check, code standard verification/review, comment and log verification, code review, standard self-check, bottom-up check, acceptance review, product file naming correction, file renaming and relocation, **perform standard scanning on specified directories/modules/packages (e.g., "run check-standards on xx directory"/"verify order module standards"/"only scan the code modified this time")**. It can be used with ai-dev-workflow 5.2 standard verification node / 5.3 acceptance, or triggered independently (output the report in the dialogue and prompt the user for confirmation when there are no docs/no process).
Serverpod ORM with PostgreSQL or SQLite — CRUD, filters, sorting, pagination, includes, transactions, raw SQL, client-side database. Use when reading or writing data at runtime. To declare tables and relations instead, use serverpod-models.
Diagnose and improve slow Django database-backed endpoints with evidence-first profiling, query-plan review, index selection, ORM loading fixes, batching, database-side computation, materialized views, and pagination choices. Use when a Django view, API, job, report, queryset, or database query is slow and the right optimization path is not obvious.
Read and compare Django/PostgreSQL query execution plans using QuerySet.explain(), EXPLAIN, EXPLAIN ANALYZE, scan types, joins, estimates, actual timing, buffers, and row counts. Use when one SQL query dominates Django latency or when an index, ORM rewrite, pagination change, or materialized view needs proof from a query plan.
Fetch and export public X (Twitter) data with a self-contained Python CLI built on the twikit library — no developer API keys, just the user's own login cookies. Covers user profiles, a user's tweets/replies/likes, single tweets, threads, search, followers/following, home/bookmark timelines, with JSON/JSONL/CSV/SQLite output and resumable pagination. Use whenever the user wants to scrape, download, collect, archive, monitor, or analyze tweets or X/Twitter accounts, export a timeline or follower list to a file or dataset, pull X data for research, or build a tweet corpus — even if they don't name the tool. Requires the user's own X login cookies (auth_token + ct0, or username/password login).
Use when working with multi-item data, batches, paginated APIs, rate-limited APIs, fan-out across multiple branches, anything that needs to "do this for each", or any time the user mentions looping, iterating, batching, paging, parallelism, or "loop over items". Triggers on "loop", "iterate", "for each", "batch", "page through", "paginate", "rate limit", "process all", "fan-out", "parallel branches", "concurrency", or any node that should run once vs once-per-item.
Patterns for building reactive apps including subscription management, optimistic updates, cache behavior, and paginated queries with cursor-based loading
RESTful API design, error handling, versioning, and best practices. Use when designing APIs, reviewing endpoints, implementing error responses, or setting up API structure. Triggers on "design API", "review API", "REST best practices", or "API patterns".