1.3천건 · 관련도순
Reviews SQL for security (injection, privileges), performance, maintainability, and quality across MySQL, PostgreSQL, SQL Server, Oracle, and other dialects. Use when reviewing a query, migration, stored procedure, or the SQL in a pull request.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when working with Entity Framework Core — modeling entities and relationships, migrations, LINQ query performance, change tracking, N+1 problems, and connection and transaction handling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Exasol User Defined Functions (UDFs) and Script Language Containers (SLCs). Covers `CREATE SCRIPT`, SCALAR and SET functions, variadic scripts with `EMITS(...)` and `default_output_columns`, the `ExaIterator` and `ExaMetadata` APIs, Python, Java, Lua, and R scripts, Lua execute scripts and `pquery`, BucketFS file access, GPU-accelerated UDFs, `ALTER SESSION SET SCRIPT_LANGUAGES` activation, and building custom Script Language Containers with `exaslct`, `exaslpm`, and `packages.yml`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Deploy and use the Exasol Text AI Extension (TXAIE) with notebook-connector. Covers `deploy_license`, `initialize_text_ai_extension`, the `PYTHON3_TXAIE` language container, the Extraction API classes `StandardExtractor`, `NamedEntityExtractor`, `TopicClassifierExtractor`, `PipelineExtractor`, and `BranchExtractor`, named-entity, zero-shot classification, and feature extraction runs, default-model installation, and result-table querying such as `TXAIE_AUDIT_LOG`.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Exasol database interaction via the exapump CLI and Exasol SQL. Covers SQL queries and DML/DDL such as `SELECT`, `INSERT`, `UPDATE`, `DELETE`, `MERGE`, `CREATE TABLE`, `ALTER TABLE`, and `DROP TABLE`, `CREATE CONNECTION` connection objects without import or export intent, schema inspection, table design, `exapump sql` and `exapump profile`, query profiling, analytics, and Exasol-specific SQL behavior outside exasol-import and exasol-export.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use Exasol JDBC-based virtual schemas for federated read-only access to external databases such as PostgreSQL, Oracle, MySQL, SQL Server, and DB2. Covers database-source adapter selection, `CREATE VIRTUAL SCHEMA`, `ALTER VIRTUAL SCHEMA`, `EXPLAIN VIRTUAL`, metadata refresh, and query-side troubleshooting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use Exasol document-file virtual schemas for federated read-only access to object and file storage — S3, Google Cloud Storage, Azure Blob Storage, and Azure Data Lake Storage Gen2 document files. Covers document-file adapter family selection, the EDML `MAPPING` definition, `CREATE VIRTUAL SCHEMA` usage, refresh workflows, and query-side troubleshooting.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. USE FOR: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, co...
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use for Azure AI: Search, Speech, OpenAI, Document Intelligence. Helps with search, vector/hybrid search, speech-to-text, text-to-speech, transcription, OCR. WHEN: AI Search, query search, vector search, hybrid search, semantic search, speech-to-text, text-to-speech, transcribe, OCR, convert text...
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Inter-agent communication protocol for C-suite agent teams. Defines invocation syntax, loop prevention, isolation rules, and response formats. Use when C-suite agents need to query each other, coordinate cross-functional analysis, or run board meetings with multiple agent roles.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Full SolanaOS operator skill — install the runtime, query Solana blockchain data via SolanaTracker RPC, manage wallets, run OODA trading loops, configure multi-venue strategies (spot + Hyperliquid + Aster perps), control BitAxe mining fleets, pair Seeker devices, and interact with the SolanaOS Hub. Use when asked about SolanaOS installation, Solana wallet balances, token research, trading strategy, OODA loops, gateway setup, Telegram bot configuration, mining fleet management, or any SolanaOS runtime operation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Complete SolanaOS agent skill — install, configure, and operate the autonomous Solana trading runtime with Honcho v3 epistemological memory, multi-venue perp trading (Hyperliquid + Aster), on-chain intelligence with USD pricing, Telegram bot, gateway API, Tailscale mesh, hardware integration, and cross-session recall. Use when asked to install SolanaOS, query Solana blockchain data, manage wallets, run OODA trading loops, configure strategies, control BitAxe mining fleets, pair Seeker devices, or operate any SolanaOS runtime surface.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reads an accounts payable exception list (mismatches, possible duplicates, missing or exhausted purchase orders, missing receipts, vendor or bank detail differences) with any invoice, purchase order and receipt data supplied, and returns a DRAFT action sheet: per line, the exception as stated, the facts as read, the difference where both sides exist, one proposed next action for the accounts payable clerk to perform, who or what it needs, and a draft query, with UNKNOWN wherever the data is silent. Use when the user asks to "review these invoice exceptions", "work through the AP exception queue", "what should I do with these blocked invoices", "propose next steps for the three-way match failures" or "sort out the duplicate and missing PO invoices". Do not use for a purchase order log screened for anomalies, use purchase-order-anomaly-review instead; for an expense claim against policy, use expense-policy-precheck. Drafts for human review; never approves, authorises or signs off.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Remote-sensing literature search, citation verification, sensor/platform/dataset query strategy, citation file management (.ris/.bib/.enw conversion), and reference management (BibTeX, related articles, DOI/arXiv lookup) across CrossRef, arXiv, Scopus, ScienceDirect, Semantic Scholar, and domain web sources. Use when the user needs coordinated multi-step literature workflows for remote sensing, Earth observation, geospatial AI, GIScience, photogrammetry, SAR, hyperspectral imaging, LiDAR, satellite missions, benchmark datasets, land-cover mapping, change detection, object detection, segmentation, retrieval, or multimodal remote-sensing foundation models. Also trigger on general literature-search needs during academic writing even without the word "Nature", such as searching for papers/literature, doing a literature review, verifying a citation, converting citation files, and Chinese phrasings like 文献检索、查文献、找文献、 文献综述检索、查论文、引文核对、参考文献管理、文献去重.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when designing, reviewing, modifying, migrating, optimizing, securing, operating, troubleshooting, or decommissioning data architectures across data model exploration, SQL, ISO SQL conformance, NoSQL, vector, graph, document, time-series, NewSQL, search, in-memory, SQLite, CDC/Debezium, DBMS storage/query/recovery internals, database incident prevention, hardware acceleration, cache, big-data, lakehouse, and warehouse systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Author and submit a Narrative workflow from a natural-language intent. Picks the closest example from `assets/examples/`, adapts it to the user's case, walks the YAML against the spec, resolves the data plane, and submits via `narrative_workflows_create` only after the user has approved the rendered spec. Use when: "create a workflow that does X", "schedule a daily refresh of dataset Y", "wrap this NQL as a workflow", "build a pipeline that creates view A then refreshes view B", "submit this workflow YAML", "productionize this query as a recurring job". (narrative-common)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Produce a coverage & quality profile of a Narrative dataset (or access rule): row count, per-column null/fill rate, cardinality, ranges, top-values, inferred column shape, and quality flags. Reads bundled stats + sample first, recovers missing/stale stats by configuring and recalculating them, and escalates to a cheap `/write-nql` query only for a measure no stat can provide. Descriptive, not prescriptive. Use when: "profile dataset N", "what does dataset N look like", "coverage and quality of <dataset>", "what id types does N emit", "null rates / cardinality for <dataset>", "is this dataset's stats fresh". (narrative-common)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Register a Snowflake table or view as a Narrative dataset from SQL, with no Configuration screen and no browser. Not for installing or configuring the native app, and not for querying a dataset that already exists. Use when: "register this table as a dataset", "register a Snowflake dataset from SQL", "onboard my_table to Narrative", "script dataset registration", "add this view to my data plane". (narrative-common)
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Retired. Project orientation moved to the remember skill (`/remember --project <name>` with no query). Use remember instead.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Given the product offering and existing page inventory, create new core landing and resource pages (homepage refresh, features, solutions, pricing, comparison, resource hubs, about) that capture core product intent using the query-fanout pattern. Use this skill whenever the user asks to "spawn pages", "generate landing pages", "create marketing pages", "build a pricing page", "add a solutions page", "build out the site", "fill in missing pages", or wants new top-level marketing/product pages. Output is one new page per route in the project's native file format (component or markdown), matching the existing page style and framework idiom.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Automate Attio CRM operations -- search records, query contacts and companies with advanced filters, manage notes, list attributes, and navigate your relationship data -- using natural language throug
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validates whether an API request is correct based on provided inputs (method, URL, headers, body, auth, query params).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Canonical patterns for writing custom MSBuild targets. Only activate in MSBuild/.NET build context. USE FOR: diagnosing and fixing custom target authoring anti-patterns, reviewing MSBuild target definitions for correctness, diagnosing broken SDK target chains across files (e.g., Directory.Build.targets silently redefining SDK targets), fixing targets that replace CompileDependsOn instead of extending it with $(CompileDependsOn), fixing query targets that return stale results due to Outputs vs Returns misuse, fixing missing Inputs/Outputs causing unnecessary rebuilds, fixing missing FileWrites registration. Covers DependsOnTargets vs BeforeTargets vs AfterTargets, the Build→CoreBuild three-level pattern, hooking into the build pipeline, the $(XxxDependsOn) chain-extension pattern. DO NOT USE FOR: incremental build tuning (use incremental-build), parallelization (use build-parallelism), general anti-patterns (use msbuild-antipatterns), non-MSBuild build systems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.