[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6AC40ZH16GDP4CGRD5FT7XH":3,"skill-same:01M6AC40ZH16GDP4CGRD5FT7XH":61},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":25,"linkOnly":26,"markdownContent":27,"markdownBody":28,"frontMatter":29,"refName":33,"commitSha":34,"skillDirectory":35,"forksCount":36,"repositoryHtmlUrl":37,"repositoryHomepageUrl":6,"ownerHtmlUrl":38,"ownerBlogUrl":39,"ownerDescription":6,"updatedAt":40,"install":41,"resources":54},"01M6AC40ZH16GDP4CGRD5FT7XH","airtable-filters",null,"Use this skill when the user wants to find, filter, or narrow down Airtable records by field values, even when they don't explicitly say \"filter.\"","openai\u002Fplugins","openai","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F14957082?v=4","01M6AC29YGCR4S2NTJFV0G8B81","OpenAI","01M6AC38CEN570NMR96RNGD2NK",7942,"MIT","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Fblob\u002Fmain\u002Fplugins\u002Fairtable\u002Fskills\u002Fairtable-filters\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[24],"airtable filters","2026-11-10 10:12:30",false,"---\nname: airtable-filters\ndescription: Use this skill when the user wants to find, filter, or narrow down Airtable records by field values, even when they don't explicitly say \"filter.\"\nlicense: MIT\nmetadata:\n  version: '1.0.0'\n  author: airtable\n---\n\n# Airtable MCP Filters\n\nMCP tools that list or display records from tables or interface pages accept an optional `filters` parameter, using the same schema.\n\nWhen querying records from an interface page, these filters are combined with the page's built-in filters using AND.\n\n## Schema shape\n\nWhen no top-level `operator` is specified, conditions are combined with AND. The first element in a condition's `operands` array is always a **field ID** — look up the table's schema to find field IDs before filtering.\n\n## Field type categories\n\n-   **Text-like**: singleLineText, multilineText, email, url, phoneNumber, richText, barcode\n-   **Numeric**: number, percent, currency, rating, duration, autoNumber, count\n-   **Date**: date, dateTime, createdTime, lastModifiedTime\n-   **Single select**: singleSelect\n-   **Multiple selects**: multipleSelects\n-   **Single collaborator**: singleCollaborator\n-   **Multiple collaborators**: multipleCollaborators\n-   **Linked records**: multipleRecordLinks\n-   **Attachment**: multipleAttachments\n-   **Checkbox**: checkbox\n\nComputed fields (formula, rollup, lookup) support whichever operators match their result type.\n\n## Comparison operators\n\n| Operator                | Second operand                     | Field categories                                                                                                                   |\n| ----------------------- | ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |\n| `=`                     | string, number, boolean, choice ID | text-like, numeric, date, checkbox, single select, multiple selects, single collaborator, multiple collaborators, linked records   |\n| `!=`                    | string, number, choice ID          | text-like, numeric, date, single select, single collaborator                                                                       |\n| `\u003C`, `>`, `\u003C=`, `>=`    | number or date value object        | numeric, date                                                                                                                      |\n| `contains`              | string                             | text-like, linked records                                                                                                          |\n| `doesNotContain`        | string                             | text-like, linked records                                                                                                          |\n| `doesNotContain`        | array of IDs                       | multiple selects, multiple collaborators                                                                                           |\n| `isEmpty`, `isNotEmpty` | _(none)_                           | text-like, numeric, date, single select, multiple selects, single collaborator, multiple collaborators, linked records, attachment |\n| `hasAnyOf`, `hasAllOf`  | array of IDs                       | multiple selects, multiple collaborators, linked records                                                                           |\n| `isAnyOf`               | array of IDs                       | single select, single collaborator                                                                                                 |\n| `isNoneOf`              | array of IDs                       | single select, single collaborator, linked records                                                                                 |\n| `isWithin`              | date range object                  | date                                                                                                                               |\n| `filename`, `fileType`  | string or `\"image\"`\u002F`\"text\"`       | attachment                                                                                                                         |\n\nWhen matching a field against multiple values, prefer dedicated operators (`isAnyOf`, `isNoneOf`, `hasAnyOf`, `hasAllOf`) over combining multiple `=` conditions with `or`\u002F`and`, when those operators are available for the field type.\n\n## Field-type rules\n\n### Select fields\n\nFor select fields, operand values must be **choice IDs** (e.g., `\"selABCDEFGHIJKLM\"`), not display names. Look up the table's schema to find choice IDs before filtering.\n\n### Collaborator fields\n\nWhen filtering by a collaborator group ID, use `operatorOptions` to match individual members of the group instead of the literal group ID. See the tool's `operatorOptions` parameter for details.\n\nExample operand: `{\"operator\": \"hasAnyOf\", \"operands\": [\"fldCRi9oz2vRLcIWr\", \"ugpDUVUnftA7H9bG8\"], \"operatorOptions\": {\"matchGroupsByMembership\": true}}`\n\n### Attachment fields\n\nUse `fileType` to filter attachments by type (e.g., `\"image\"`, `\"text\"`) rather than `isNotEmpty` when the user specifies a file type.\n\n### Date fields\n\nDate comparisons (`=`, `!=`, `\u003C`, `>`, `\u003C=`, `>=`) use a date value object instead of a raw date string, and `isWithin` uses a date range object. The tool schema defines the available modes for each. Always include `timeZone`.\n\n## Composing conditions\n\nA filter's top-level operands array can contain two or more conditions, which are combined with the top-level operator (AND by default). For simple multi-condition filters, this flat structure is sufficient.\n\nWhen the logic requires mixing AND and OR, nest a filter object as one of the operands. Each nested filter has its own operator and operands.\n\n**OR inside AND** — useful when one condition is fixed and another allows multiple alternatives:\n\n> \"Scripted videos that are either in Writing or Pre-Production\"\n> → Bucket = Scripted AND (Status = Writing OR Status = Pre-Production)\n\n**AND inside OR** — useful when you want records matching either a simple condition or a combination:\n\n> \"Approved videos, or videos assigned to Bailey that are in Cut 2\"\n> → Status = Approved OR (Editor = Bailey AND Status = Cut 2 Ready)\n\nWhen combining many conditions on different fields, prefer a flat AND rather than unnecessary nesting. Only nest when the logic genuinely requires mixed AND\u002FOR at different levels.\n\nPrefer composing all conditions into a single `filters` object rather than splitting them across multiple calls. A single call with a composed filter is more efficient and returns the correct result set directly.\n\n## Examples\n\nFilter where a text field equals \"orange\" OR a number field is greater than 5:\n\n```json\n{\n    \"operator\": \"or\",\n    \"operands\": [\n        {\"operator\": \"=\", \"operands\": [\"fld8WsrpLHHevsnW8\", \"orange\"]},\n        {\"operator\": \">\", \"operands\": [\"fldulcCPDVz87Bmnw\", 5]}\n    ]\n}\n```\n\nFilter for records where a date field is within the past week:\n\n```json\n{\n    \"operands\": [\n        {\n            \"operator\": \"isWithin\",\n            \"operands\": [\"fldABC12345678x\", {\"mode\": \"pastWeek\", \"timeZone\": \"America\u002FNew_York\"}]\n        }\n    ]\n}\n```\n","# Airtable MCP Filters\n\nMCP tools that list or display records from tables or interface pages accept an optional `filters` parameter, using the same schema.\n\nWhen querying records from an interface page, these filters are combined with the page's built-in filters using AND.\n\n## Schema shape\n\nWhen no top-level `operator` is specified, conditions are combined with AND. The first element in a condition's `operands` array is always a **field ID** — look up the table's schema to find field IDs before filtering.\n\n## Field type categories\n\n-   **Text-like**: singleLineText, multilineText, email, url, phoneNumber, richText, barcode\n-   **Numeric**: number, percent, currency, rating, duration, autoNumber, count\n-   **Date**: date, dateTime, createdTime, lastModifiedTime\n-   **Single select**: singleSelect\n-   **Multiple selects**: multipleSelects\n-   **Single collaborator**: singleCollaborator\n-   **Multiple collaborators**: multipleCollaborators\n-   **Linked records**: multipleRecordLinks\n-   **Attachment**: multipleAttachments\n-   **Checkbox**: checkbox\n\nComputed fields (formula, rollup, lookup) support whichever operators match their result type.\n\n## Comparison operators\n\n| Operator                | Second operand                     | Field categories                                                                                                                   |\n| ----------------------- | ---------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------- |\n| `=`                     | string, number, boolean, choice ID | text-like, numeric, date, checkbox, single select, multiple selects, single collaborator, multiple collaborators, linked records   |\n| `!=`                    | string, number, choice ID          | text-like, numeric, date, single select, single collaborator                                                                       |\n| `\u003C`, `>`, `\u003C=`, `>=`    | number or date value object        | numeric, date                                                                                                                      |\n| `contains`              | string                             | text-like, linked records                                                                                                          |\n| `doesNotContain`        | string                             | text-like, linked records                                                                                                          |\n| `doesNotContain`        | array of IDs                       | multiple selects, multiple collaborators                                                                                           |\n| `isEmpty`, `isNotEmpty` | _(none)_                           | text-like, numeric, date, single select, multiple selects, single collaborator, multiple collaborators, linked records, attachment |\n| `hasAnyOf`, `hasAllOf`  | array of IDs                       | multiple selects, multiple collaborators, linked records                                                                           |\n| `isAnyOf`               | array of IDs                       | single select, single collaborator                                                                                                 |\n| `isNoneOf`              | array of IDs                       | single select, single collaborator, linked records                                                                                 |\n| `isWithin`              | date range object                  | date                                                                                                                               |\n| `filename`, `fileType`  | string or `\"image\"`\u002F`\"text\"`       | attachment                                                                                                                         |\n\nWhen matching a field against multiple values, prefer dedicated operators (`isAnyOf`, `isNoneOf`, `hasAnyOf`, `hasAllOf`) over combining multiple `=` conditions with `or`\u002F`and`, when those operators are available for the field type.\n\n## Field-type rules\n\n### Select fields\n\nFor select fields, operand values must be **choice IDs** (e.g., `\"selABCDEFGHIJKLM\"`), not display names. Look up the table's schema to find choice IDs before filtering.\n\n### Collaborator fields\n\nWhen filtering by a collaborator group ID, use `operatorOptions` to match individual members of the group instead of the literal group ID. See the tool's `operatorOptions` parameter for details.\n\nExample operand: `{\"operator\": \"hasAnyOf\", \"operands\": [\"fldCRi9oz2vRLcIWr\", \"ugpDUVUnftA7H9bG8\"], \"operatorOptions\": {\"matchGroupsByMembership\": true}}`\n\n### Attachment fields\n\nUse `fileType` to filter attachments by type (e.g., `\"image\"`, `\"text\"`) rather than `isNotEmpty` when the user specifies a file type.\n\n### Date fields\n\nDate comparisons (`=`, `!=`, `\u003C`, `>`, `\u003C=`, `>=`) use a date value object instead of a raw date string, and `isWithin` uses a date range object. The tool schema defines the available modes for each. Always include `timeZone`.\n\n## Composing conditions\n\nA filter's top-level operands array can contain two or more conditions, which are combined with the top-level operator (AND by default). For simple multi-condition filters, this flat structure is sufficient.\n\nWhen the logic requires mixing AND and OR, nest a filter object as one of the operands. Each nested filter has its own operator and operands.\n\n**OR inside AND** — useful when one condition is fixed and another allows multiple alternatives:\n\n> \"Scripted videos that are either in Writing or Pre-Production\"\n> → Bucket = Scripted AND (Status = Writing OR Status = Pre-Production)\n\n**AND inside OR** — useful when you want records matching either a simple condition or a combination:\n\n> \"Approved videos, or videos assigned to Bailey that are in Cut 2\"\n> → Status = Approved OR (Editor = Bailey AND Status = Cut 2 Ready)\n\nWhen combining many conditions on different fields, prefer a flat AND rather than unnecessary nesting. Only nest when the logic genuinely requires mixed AND\u002FOR at different levels.\n\nPrefer composing all conditions into a single `filters` object rather than splitting them across multiple calls. A single call with a composed filter is more efficient and returns the correct result set directly.\n\n## Examples\n\nFilter where a text field equals \"orange\" OR a number field is greater than 5:\n\n```json\n{\n    \"operator\": \"or\",\n    \"operands\": [\n        {\"operator\": \"=\", \"operands\": [\"fld8WsrpLHHevsnW8\", \"orange\"]},\n        {\"operator\": \">\", \"operands\": [\"fldulcCPDVz87Bmnw\", 5]}\n    ]\n}\n```\n\nFilter for records where a date field is within the past week:\n\n```json\n{\n    \"operands\": [\n        {\n            \"operator\": \"isWithin\",\n            \"operands\": [\"fldABC12345678x\", {\"mode\": \"pastWeek\", \"timeZone\": \"America\u002FNew_York\"}]\n        }\n    ]\n}\n```\n",{"name":5,"license":15,"metadata":30,"description":7},{"author":31,"version":32},"airtable","1.0.0","main","0722921d5542fc593105c27bd52630babd8b8c2a","plugins\u002Fairtable\u002Fskills\u002Fairtable-filters",1025,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins","https:\u002F\u002Fgithub.com\u002Fopenai","https:\u002F\u002Fopenai.com\u002F","2026-11-14 08:11:13",{"source":8,"skillName":5,"commands":42,"prompt":52,"zipAvailable":53},[43,46,49],{"tool":44,"command":45},"npx","npx skills add openai\u002Fplugins --skill airtable-filters",{"tool":47,"command":48},"bunx","bunx skills add openai\u002Fplugins --skill airtable-filters",{"tool":50,"command":51},"pnpm","pnpm dlx skills add openai\u002Fplugins --skill airtable-filters","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Fblob\u002Fmain\u002Fplugins\u002Fairtable\u002Fskills\u002Fairtable-filters\u002FSKILL.md",true,[55],{"path":56,"resourceType":57,"resourceTypeDesc":58,"sizeBytes":59,"sourceHtmlUrl":60},"agents\u002Fopenai.yaml","REFERENCE","参考文档",247,"https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Fblob\u002Fmain\u002Fplugins\u002Fairtable\u002Fskills\u002Fairtable-filters\u002Fagents\u002Fopenai.yaml",[62,81,92,110,137,150],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":71,"publishedAt":25},"01M6ACYN431ER9AFG508JJH3VT","supabase-postgres-best-practices","Postgres performance optimization and best practices from Supabase. Use this skill when writing, reviewing, or optimizing Postgres queries, schema designs, or database configurations.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Fblob\u002Fmain\u002Fplugins\u002Fsupabase\u002Fskills\u002Fsupabase-postgres-best-practices\u002FSKILL.md",[68],{"categoryNo":69,"categoryName":70,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口",[72,73,74,75,76,77,78,79,80],"best practices","supabase postgres best practices","writing","performance","sql","code","database","metrics","examples",{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":88,"publishedAt":25},"01M6ACQRGGJYVNDPQWB9XGWRNZ","minimal-skill","Minimal example skill for plugin-eval tests. Use when the user wants a compact demonstration of a well-structured skill.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Fblob\u002Fmain\u002Fplugins\u002Fplugin-eval\u002Ffixtures\u002Fminimal-skill\u002FSKILL.md",[87],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[89,90,91],"minimal skill","example skill","plugin",{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":25},"01M6ACQ406M83341YPKPEXBXDZ","physical-ai-neural-reconstruction","Router for NVIDIA NuRec\u002FNRE: USDZ rendering, NCore conversion, 3DGS, gRPC sensor sim, PhysicalAI HF datasets. Do NOT use for SimReady or infra setup.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnvidia\u002Fskills\u002Fphysical-ai-neural-reconstruction\u002FSKILL.md",[],[100,101,102,103,104,105,106,107,108,109],"physical ai neural reconstruction","https","python","github","docker","setup","toolkit","gpu","index","grpc",{"skillNo":111,"name":112,"nameZh":6,"description":113,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":114,"categories":115,"keywords":119,"publishedAt":25},"01M6ACPVRFPVATXD7H38Z56QC5","physical-ai-infrastructure-setup-and-resilient-scaling","Use when the user wants to set up, scale, validate, or harden NVIDIA physical AI infrastructure for synthetic data generation workflows across local MicroK8s or Azure AKS, including Kubernetes clusters, inference endpoint deployment, OSMO deployment, workload submission readiness, and infrastructure failure recovery. Trigger keywords: physical ai infrastructure, resilient scaling, SDG infrastructure, microk8s, azure aks, NVCF deployment, NIM Operator, OSMO deploy, workflow scaling. Don't trigger for: OSMO log summarization or workload-only operations unless infrastructure setup, scaling, validation, or recovery is requested.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnvidia\u002Fskills\u002Fphysical-ai-infrastructure-setup-and-resilient-scaling\u002FSKILL.md",[116],{"categoryNo":117,"categoryName":118,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000011","运维与部署",[120,105,121,122,123,124,125,126,127,128,129,130,131,132,133,134,135,136],"physical ai infrastructure setup and resilient scaling","infrastructure","validation","terraform","deployment","synthetic data","workload","ml","cli","kubernetes","inference","workflow","workflows","component","validate","deploy","azure",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":144,"publishedAt":25},"01M6ACPG9JPDSS6MMKVKR3P56E","omniverse-usd-performance-tuning","Top-level workflow skill for USD performance diagnosis and optimization. Use for slow loading, high memory, low FPS, or 'optimize my scene' requests; delegates auth\u002Fruntime setup to Phase 0 owners.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnvidia\u002Fskills\u002Fomniverse-usd-performance-tuning\u002FSKILL.md",[143],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[145,75,146,102,147,148,131,105,127,149],"omniverse usd performance tuning","auth","memory","triage","authentication",{"skillNo":151,"name":152,"nameZh":6,"description":153,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":96,"licenseFileUrl":6,"sourceHtmlUrl":154,"categories":155,"keywords":157,"publishedAt":25},"01M6ACP73X9YS5Y730C2WE58YF","omniverse-realtime-viewer","Use as the top-level router for Omniverse Realtime Viewer USD app requests and focused viewer reference documents.","https:\u002F\u002Fgithub.com\u002Fopenai\u002Fplugins\u002Fblob\u002Fmain\u002Fplugins\u002Fnvidia\u002Fskills\u002Fomniverse-realtime-viewer\u002FSKILL.md",[156],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},[158,159,102,131,160,161,162,127,124,163,107,164],"omniverse realtime viewer","realtime","electron","react","documents","cpp","typescript"]