Explore skills
Showing 17521–17550 of 72065 skills
Review code changes for bugs, regressions, convention violations, and high-value cleanup opportunities. Use for diffs, commit ranges, hosted PR/MR URLs, branches, paths, staged changes, or working-tree changes.
kairyou/agent-tools
Stars: 179Claude CodeCodexUniversal AI-powered web scraper for any platform. Scrape data from Instagram, Facebook, TikTok, YouTube, LinkedIn, X/Twitter, Google Maps, Google Search, Google Trends, Reddit, Airbnb, Yelp, and 15+ more platforms. Use for lead generation, brand monitoring, competitor analysis, influencer discovery, trend research, content analytics, audience analysis, review analysis, SEO intelligence, recruitment, or any data extraction task.
apify/agent-skills
Stars: 2.5kClaude CodeCodexCreate or inspect Convex accounts. Use when the user wants to set up a new account, check account details, or manage keys.
Convex-Dev/convex
Stars: 119Claude CodeCodexResolve or register Convex Name System (CNS) names. Use when the user wants to look up a CNS name, register a new name, or update a name's target.
Convex-Dev/convex
Stars: 119Claude CodeCodexUse Convex DB — a lattice-backed SQL database. Use when helping users write queries, connect via JDBC or PostgreSQL clients, create tables, insert/query data, or use the direct lattice API.
Convex-Dev/convex
Stars: 119Claude CodeCodexConvex Lisp language reference — CVM conventions, calling library code, actor definitions, juice and error codes. Use when writing or debugging CVM source for queries, transactions or actors.
Convex-Dev/convex
Stars: 119Claude CodeCodexDeploy an actor (smart contract) to the Convex network. Use when the user wants to create a new on-chain actor with exported functions.
Convex-Dev/convex
Stars: 119Claude CodeCodexWork with DLFS, the Data Lattice File System — run a local DLFS server, manage drives, and read, write and list files through its MCP tools or WebDAV. Use when interacting with DLFS or working on the convex-dlfs module.
Convex-Dev/convex
Stars: 119Claude CodeCodexInspect and maintain an Etch store — Convex's content-addressed database. Use when examining peer storage, diagnosing corruption, garbage collecting, or reading data by hash.
Convex-Dev/convex
Stars: 119Claude CodeCodexJuice accounting — the cost of computation and bandwidth on the CVM. Use when reasoning about transaction execution cost, diagnosing a :JUICE failure, or pricing a new CVM operation.
Convex-Dev/convex
Stars: 119Claude CodeCodexRun isolated local Convex networks and in-process lattice node networks for development. Use when testing against local peers, reproducing peer or P2P replication issues, exercising NodeServer or P2PNode sync, or when no remote network is configured.
Convex-Dev/convex
Stars: 119Claude CodeCodexMemory accounting and allowances — the cost of on-chain storage, and how to minimise and reclaim it. Use when reasoning about state growth, diagnosing a :MEMORY failure, or designing actors that store data.
Convex-Dev/convex
Stars: 119Claude CodeCodexOperate a Convex peer — create, start, list, back up, or instantiate a network genesis. Use when running a peer against a network or setting up a new network.
Convex-Dev/convex
Stars: 119Claude CodeCodexProtocol versions, migrations and the v1 upgrade — which semantics to write against, and how to change CVM behaviour without forking the network. Use when changing core functions, juice costs, encodings or on-chain libraries.
Convex-Dev/convex
Stars: 119Claude CodeCodexExecute a read-only CVM query on the Convex network. Use when reading on-chain state, checking balances, looking up accounts, or evaluating Convex Lisp expressions.
Convex-Dev/convex
Stars: 119Claude CodeCodexCreate and manage fungible tokens on Convex. Use when the user wants to create a new token, check token balances, or manage token supply.
Convex-Dev/convex
Stars: 119Claude CodeCodexExecute a CVM transaction on the Convex network. Use when the user wants to modify on-chain state, call actor functions, or define values.
Convex-Dev/convex
Stars: 119Claude CodeCodexTrust monitors — Convex's composable on-chain authorisation model. Use when writing access control, restricting actor functions, defining who may mint or upgrade, or reviewing authorisation logic.
Convex-Dev/convex
Stars: 119Claude CodeCodexUse this whenever you need to know what is actually in a database, warehouse, or DuckDB file before you trust it: inventory, column profiles, PII detection, grain and data-quality problems, verified joins, ER diagrams, ad-hoc SQL probes, segmentation, and the semantic layer a repo declares (dbt, Ossie, SLayer, or Cube). Trigger it on an unmet precondition, not on phrasing: if you are about to write or fix SQL against tables whose columns, types, grain, or join keys you have not verified in this session, use this FIRST. That includes dbt work (building a model, fixing one, debugging wrong numbers) whenever the ticket names source tables without spelling out their schema. It applies mid-task too: on reaching a table you have not inspected, stop and use this rather than guess column names. Also for "what's in my duckdb", "is this data any good", "how do these tables relate". Read-only; writes only the .dex/ cache. It does not author the model: transform does, and maintain reconciles a project that has drifted.
exmergo/dex
Stars: 136Claude CodeCodexUse this to find out whether an existing dbt project or semantic layer (dbt, Ossie, SLayer or Cube) is correct against its warehouse, and if not, why. `maintain verify` checks the project as it stands; against a .dex/ snapshot, `maintain check` finds schema, volume, grain, and semantic drift and `maintain reconcile` proposes the fix. Reach for it whenever an existing project is suspected wrong, whether or not anything is known to have changed: "this model is wrong, work out why", "the numbers look too high", "some rows are missing", "this column is empty", "duplicates in my fact table", "the project is broken", "diagnose why this test fails", "a test fails and nobody changed the model", "which models have no tests", "how good is our test coverage", "did anything drift", "the metric definition changed". Read-only; fixes come back as reviewable diffs and never overwrite hand-written work. Writing the fix, or repairing a model you just edited, is transform's; a data question with no project is explore's.
exmergo/dex
Stars: 136Claude CodeCodexUse this to author and change a dbt project or a semantic layer: bootstrap a project (`transform init`), write or refactor models from staging to marts, add tests and docs, and define semantic models, entities, dimensions, and metrics in MetricFlow, Apache Ossie or SLayer YAML. Reach for it instead of editing model files by hand whenever a change spans more than one file or must stay consistent with the project: it validates the edit against the real schema, returns a reviewable diff with a plan id, and catches what otherwise fails at `dbt run`, such as wrong columns or broken refs. Bug-fix tickets count: "this model returns wrong numbers, fix it" is a transform task. Also for "build a staging model for this table", "define a revenue metric", "add a dimension to this entity". Warehouse builds are dev-target only, gated, and cost-surfaced first. If you have not verified the source tables' columns or grain, use explore first. For a project that drifted from the warehouse, use maintain.
exmergo/dex
Stars: 136Claude CodeCodexAPI developer specializing in clean, well-documented REST APIs
Vinix24/vnx-orchestration
Stars: 63Claude CodeCodexSystem architecture specialist for designing scalable solutions that handle complexity and evolve under change
Vinix24/vnx-orchestration
Stars: 63Claude CodeCodexBackend developer creating fault-tolerant, scalable server-side solutions
Vinix24/vnx-orchestration
Stars: 63Claude CodeCodexMulti-project Control Centre supervisor. Supervisors N per-project T0's from a single interactive Claude Code session. Read-only orchestration — no code writes.
Vinix24/vnx-orchestration
Stars: 63Claude CodeCodexSEO data analysis, pattern identification, and actionable insights generation
Vinix24/vnx-orchestration
Stars: 63Claude CodeCodexSystematic debugging specialist focused on root cause analysis
Vinix24/vnx-orchestration
Stars: 63Claude CodeCodexFull-coverage formatted Excel report generation with Dutch market compatibility
Vinix24/vnx-orchestration
Stars: 63Claude CodeCodexRead-only runbook for how the VNX fabric actually works — state resolution, the single-entry dispatch door, gate invocation, the horizon planning layer, the plan-gate panel, and the hard gotchas that repeatedly bite (PATH-break, dual-CLI, codex-cert, classifier-protected actions). Use when you need to look up a fabric operation instead of rediscovering it, or when a fabric command behaves unexpectedly. Companion to the t0-orchestrator skill (judgment) and vnx-manager (infra maintenance); this one is pure reference.
Vinix24/vnx-orchestration
Stars: 63Claude CodeCodexVNX feature-execution kickoff preflight. USE THIS when starting or resuming a feature or track from its plan: checking worktree/queue/staging health, finding the first promoteable dispatch, and handing off to @t0-orchestrator. Reads the feature's track + plan doc from Horizon's tracks DB (`vnx horizon`, alias `vnx objective`); the repo FEATURE_PLAN.md is a generic example, not the source, and PR_QUEUE.md is gone (ADR-047).
Vinix24/vnx-orchestration
Stars: 63Claude CodeCodex