Loading...
Loading...
Found 1,766 Skills
MariaDB-specific features and capabilities that go beyond standard MySQL. Use when evaluating MariaDB, optimizing an existing MariaDB application, reviewing code or schema for MariaDB improvements, asking what MariaDB can do that other databases cannot, or migrating from Oracle to MariaDB. Also use when the user asks what could be improved in how a codebase uses MariaDB, or asks about MariaDB advantages over MySQL or PostgreSQL.
Manual-invocation skill — run only when the user explicitly asks for "run-ui-registry-variations" or invokes it as a slash command. Do not auto-trigger on adjacent topics. Force UI work through shadcnblocks, Aceternity, or https://shadcn.darkmatter.io; validate private registry access before use; build exactly three user-reviewable variations.
Adversarial scenario analysis and threat modeling for Solidity smart contracts. Use when analyzing contracts from an attacker's perspective, identifying multi-step attack vectors, or performing threat modeling. Covers flash loan attacks, oracle manipulation, MEV/front-running, governance exploits, reentrancy scenarios, access control bypasses, economic logic exploits, and cross-contract composability risks. Triggers on tasks involving adversarial analysis, threat modeling, attack scenarios, attack vectors, exploit analysis, or red team review.
Perses variable lifecycle management: create Text and List variables at global, project, or dashboard scope. Handle variable chains with dependencies (A depends on B depends on C). Supports 14+ interpolation formats. Uses MCP tools when available, percli CLI as fallback. Use for "perses variable", "dashboard variable", "perses filter", "add variable". Do NOT use for datasource management (use perses-datasource-manage).
Regulatory variant interpretation -- GWAS association lookup, eQTL analysis, chromatin state annotation, regulatory element overlap, and trait ontology resolution. Connects GWAS Catalog, GTEx, ENCODE, RegulomeDB, OpenTargets, OLS ontology, and Ensembl regulatory features. Use when users ask about non-coding variants, GWAS hits, eQTLs, regulatory elements, enhancer/promoter variants, or trait-associated SNPs.
Perform a structured maintainer-style PR review for the mariadb-operator repository. Gathers PR context, triages the change, and evaluates correctness, safety, pitfalls, backwards compatibility and code quality against the project conventions documented in AGENTS.md. Use whenever the user mentions a mariadb-operator PR number or URL and wants any kind of judgment on it — "review this PR", "what do you think of #1234", "is this safe to merge", "assess this diff", "take a look at this change" — even if they don't literally say "review".
Create logo components with multiple variants (icon, wordmark, logo) and light/dark modes. Use when the user provides logo SVG files and wants to create a variant-based logo component following the Clerk pattern in the Elements project.
Variant and attribute selection on product detail pages. Use when modifying variant selectors, debugging "Add to Cart" button state, understanding option availability, or adding discount badges to options.
Perform a Cynical Review and produce a findings report. Use when the user requests a critical review of something
Guides hands-on actuarial analyst work for insurance, reinsurance, and pension—reserving and loss development (IBNR, triangles, chain-ladder diagnostics), pricing and rate indication support (experience, trend, credibility, basic GLM at spec level), data validation and model I/O review, reporting packs and workpapers, assumption application under actuary direction, and statutory tie-outs at analyst depth. Use when the user mentions actuarial analyst, loss development, IBNR, reserve analysis, rate indication, pricing support, actuarial workpaper, triangle analysis, credibility, experience study, actuarial reporting, or reserve roll-forward—not actuary sign-off (actuary), consulting engagements (actuarial-consulting), assumption governance (assumption-setting), ALM strategy (asset-liability-management), P&C legal depth (property-casualty-insurance), charts only (data-visualization), or ETL-only pipelines (data-scrubbing).
Adversarial review (对抗 review) of a finished deliverable — a change ready for a PR, an investigation report, a recommendation, a batch of record edits — before it is reported to the user. Spawns fresh reviewer subagents briefed to disprove it from three directions (open, over-engineering, residue), verifies and fixes what holds, then reports. Run once per deliverable when it is considered done, and on request at level strong (强力) or max (极致). Not for answers to questions, lookups, or steps inside a task.
Translates game design prose into engine-neutral implementation invariants and validation checks. Use when implementing or reviewing game mechanics where idle, hold-only, mashing, spam, safe waiting, or repeated scoring pulses must be prevented from dominating skilled play.