[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DXG6DFVSAPB6ATMWR6QGMV":3,"skill-same:01M6DXG6DFVSAPB6ATMWR6QGMV":87},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":61,"updatedAt":62,"install":63,"resources":76},"01M6DXG6DFVSAPB6ATMWR6QGMV","motherduck-rest-api",null,"MotherDuck REST API control-plane reference. Use when calling api.motherduck.com to provision service accounts, create, list, rotate, or revoke access tokens, configure Duckling instance sizes and read scaling, inspect active accounts, or mint Dive embed sessions. Not for SQL or data-plane query work.","cianfhoghlaim\u002Fcianfhoghlaim","cianfhoghlaim","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F57019547?v=4","01M6DWR3GAV495PYDTZSR1FZNX","Cian Mac (an Déisigh Uí) Liatháin || Deacy-Lyons","01M6DWR3N3Z768BB64XVJN0AY2",4,"MIT","https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fcianfhoghlaim\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmotherduck\u002Fmotherduck-rest-api\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"motherduck rest api","motherduck","REST","api","rest api","mint","control","scaling","tokens","active","query","calling","sessions","use","read","work","configure","access","create","sql","2026-11-10 10:12:30",false,"---\nname: motherduck-rest-api\ndescription: MotherDuck REST API control-plane reference. Use when calling api.motherduck.com to provision service accounts, create, list, rotate, or revoke access tokens, configure Duckling instance sizes and read scaling, inspect active accounts, or mint Dive embed sessions. Not for SQL or data-plane query work.\nlicense: MIT\n---\n\n# REST API Administration\n\nUse this skill when the user needs to manage MotherDuck service accounts, supported token operations, Duckling configuration, active accounts, or Dive embed sessions through the REST API.\n\n## Source Of Truth\n\n- Prefer current MotherDuck REST API documentation, the public OpenAPI spec at `https:\u002F\u002Fapi.motherduck.com\u002Fdocs\u002Fspecs`, or an explicit OpenAPI spec supplied by the user.\n- For token scope and embed behavior, cross-check the REST API docs and the Embedded Dives docs because they include operational constraints not obvious from the raw schema.\n- If the MotherDuck MCP `ask_docs_question` feature is available, use it to check whether public REST API guidance has changed.\n- Treat endpoint availability, preview status, token fields, and role requirements as current only when backed by the supplied spec or current docs.\n\n## Default Posture\n\n- Treat the REST API as the control plane; SQL and data-plane queries go through a database connection, not the REST API.\n- Use `https:\u002F\u002Fapi.motherduck.com` as the base URL unless the user provides another environment.\n- Authenticate with `Authorization: Bearer ${MOTHERDUCK_ADMIN_TOKEN}` and keep admin read-write tokens in backend-managed secrets.\n- Never use read-scaling tokens for REST API administration.\n- Prefer read-before-write flows for configuration changes so the current account, service account, Duckling config, or Dive metadata is known before mutation.\n- Treat `POST \u002Fv1\u002Fusers` as service-account creation unless current docs explicitly broaden the API.\n- Assume active-account, Duckling configuration, service-account creation, service-account token creation, and Dive embed-session endpoints require an organization admin bearer token unless current docs say otherwise.\n- Never expose generated access tokens in logs, browser code, client bundles, or committed files.\n- Confirm destructive deletes with the user. Deleting a user permanently deletes that user and all of their data.\n\n## Workflow\n\n1. Identify whether the task is service-account provisioning, token management, Duckling sizing, active-account inspection, or Dive embedding.\n2. Confirm the admin token location and the target `username` or `dive_id`; never invent production identifiers.\n3. Check token scope before calling token endpoints: users can create tokens for themselves, and admins can create tokens for service accounts, but admins cannot create tokens for other non-service-account members through the API.\n4. For Duckling config changes, read the current config first, then update both `read_write` and `read_scaling` because the `PUT` payload requires both.\n5. Preserve response fields that are only returned once, especially newly created token strings and embed session strings.\n6. Surface API errors by status and response body; do not hide `400`, `401`, `403`, `404`, or `500` responses behind success-shaped fallbacks.\n\n## Open Next\n\n- Read `references\u002FREST_API_GUIDE.md` for endpoint summaries, auth headers, request payloads, curl examples, validation limits, and operational gotchas.\n\n## Related Skills\n\n- `motherduck-query` for SQL and data-plane query work\n- `motherduck-connect` for connection tokens and application connection posture\n- `motherduck-security-governance` for admin-token handling, service-account posture, and access-boundary questions\n- `motherduck-create-dive` for designing Dives before minting embed sessions\n","# REST API Administration\n\nUse this skill when the user needs to manage MotherDuck service accounts, supported token operations, Duckling configuration, active accounts, or Dive embed sessions through the REST API.\n\n## Source Of Truth\n\n- Prefer current MotherDuck REST API documentation, the public OpenAPI spec at `https:\u002F\u002Fapi.motherduck.com\u002Fdocs\u002Fspecs`, or an explicit OpenAPI spec supplied by the user.\n- For token scope and embed behavior, cross-check the REST API docs and the Embedded Dives docs because they include operational constraints not obvious from the raw schema.\n- If the MotherDuck MCP `ask_docs_question` feature is available, use it to check whether public REST API guidance has changed.\n- Treat endpoint availability, preview status, token fields, and role requirements as current only when backed by the supplied spec or current docs.\n\n## Default Posture\n\n- Treat the REST API as the control plane; SQL and data-plane queries go through a database connection, not the REST API.\n- Use `https:\u002F\u002Fapi.motherduck.com` as the base URL unless the user provides another environment.\n- Authenticate with `Authorization: Bearer ${MOTHERDUCK_ADMIN_TOKEN}` and keep admin read-write tokens in backend-managed secrets.\n- Never use read-scaling tokens for REST API administration.\n- Prefer read-before-write flows for configuration changes so the current account, service account, Duckling config, or Dive metadata is known before mutation.\n- Treat `POST \u002Fv1\u002Fusers` as service-account creation unless current docs explicitly broaden the API.\n- Assume active-account, Duckling configuration, service-account creation, service-account token creation, and Dive embed-session endpoints require an organization admin bearer token unless current docs say otherwise.\n- Never expose generated access tokens in logs, browser code, client bundles, or committed files.\n- Confirm destructive deletes with the user. Deleting a user permanently deletes that user and all of their data.\n\n## Workflow\n\n1. Identify whether the task is service-account provisioning, token management, Duckling sizing, active-account inspection, or Dive embedding.\n2. Confirm the admin token location and the target `username` or `dive_id`; never invent production identifiers.\n3. Check token scope before calling token endpoints: users can create tokens for themselves, and admins can create tokens for service accounts, but admins cannot create tokens for other non-service-account members through the API.\n4. For Duckling config changes, read the current config first, then update both `read_write` and `read_scaling` because the `PUT` payload requires both.\n5. Preserve response fields that are only returned once, especially newly created token strings and embed session strings.\n6. Surface API errors by status and response body; do not hide `400`, `401`, `403`, `404`, or `500` responses behind success-shaped fallbacks.\n\n## Open Next\n\n- Read `references\u002FREST_API_GUIDE.md` for endpoint summaries, auth headers, request payloads, curl examples, validation limits, and operational gotchas.\n\n## Related Skills\n\n- `motherduck-query` for SQL and data-plane query work\n- `motherduck-connect` for connection tokens and application connection posture\n- `motherduck-security-governance` for admin-token handling, service-account posture, and access-boundary questions\n- `motherduck-create-dive` for designing Dives before minting embed sessions\n",{"name":5,"license":15,"description":7},"main","5ace051462d0639f59bcc60912f4ec08c1a96772",".agents\u002Fskills\u002Fmotherduck\u002Fmotherduck-rest-api",1,"https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fcianfhoghlaim","https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim","cianfhoghlaim.ie","Irish-British teacher, mathematician, foghlaimeoir || minority-language AI researcher || Lucht Siúil ||\r\nFine Gael + Alliance Party + Liberal Democrats Member","2026-11-14 03:06:52",{"source":8,"skillName":5,"commands":64,"prompt":74,"zipAvailable":75},[65,68,71],{"tool":66,"command":67},"npx","npx skills add cianfhoghlaim\u002Fcianfhoghlaim --skill motherduck-rest-api",{"tool":69,"command":70},"bunx","bunx skills add cianfhoghlaim\u002Fcianfhoghlaim --skill motherduck-rest-api",{"tool":72,"command":73},"pnpm","pnpm dlx skills add cianfhoghlaim\u002Fcianfhoghlaim --skill motherduck-rest-api","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fcianfhoghlaim\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmotherduck\u002Fmotherduck-rest-api\u002FSKILL.md",true,[77,83],{"path":78,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":81,"sourceHtmlUrl":82},"bmad-skill-manifest.yaml","REFERENCE","参考文档",629,"https:\u002F\u002Fgithub.com\u002Fvladtara\u002Fhealthcabinet\u002Fblob\u002Fmaster\u002F_bmad\u002Fbmm\u002F4-implementation\u002Fbmad-agent-dev\u002Fbmad-skill-manifest.yaml",{"path":84,"resourceType":79,"resourceTypeDesc":80,"sizeBytes":85,"sourceHtmlUrl":86},"references\u002FREST_API_GUIDE.md",10433,"https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fcianfhoghlaim\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmotherduck\u002Fmotherduck-rest-api\u002Freferences\u002FREST_API_GUIDE.md",[88,108,124,145,169,192],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":49},"01M6DXR6F7GB4JSD67XTX6WY4A","dagster-init","Initialize a dagster project using the create-dagster cli. Create a dagster project, uv virtual environment, and everything needed for a user to run dg dev or dg check defs successfully. (project)","https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fcianfhoghlaim\u002Fblob\u002Fmain\u002Fdocs\u002Fresearch\u002Fdagster\u002Fdagster-dspy\u002F.claude\u002Fskills\u002Fdagster-init\u002FSKILL.md",[],[95,96,97,98,99,100,101,102,103,104,105,106,47,107],"init","dagster","dagster init","run","project","uv","environment","user","initialize","check","virtual","dev","cli",{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":112,"categories":113,"keywords":117,"publishedAt":49},"01M6DXQZ2HSP548JH2V3FQ7H2V","create-custom-dagster-component","Create a custom Dagster Component with demo mode support, realistic asset structure, and optional custom scaffolder using the dg CLI. Use this skill if there is no Component included in an existing integration or if Dagster does not have the integration.","https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fcianfhoghlaim\u002Fblob\u002Fmain\u002Fdocs\u002Fresearch\u002Fdagster\u002Fdagster-dspy\u002F.claude\u002Fskills\u002Fcreate-custom-dagster-component\u002FSKILL.md",[114],{"categoryNo":115,"categoryName":116,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[118,47,96,119,120,107,121,122,42,123],"component","create custom dagster component","support","demo","structure","integration",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":49},"01M6DXHPZMQ4VAXH9PGBK2PNNP","pydantic-ai-harness","Extend Pydantic AI agents with batteries-included capabilities from pydantic-ai-harness -- currently Code Mode, which collapses many tool calls into one sandboxed Python execution. Use when the user mentions pydantic-ai-harness, CodeMode, Monty, code mode, or tool sandboxing, when they want an agent to run agent-written Python, or when a Pydantic AI agent would benefit from orchestrating multiple tool calls in a single sandboxed script.","https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fcianfhoghlaim\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpydantic\u002Fpydantic-ai-harness\u002FSKILL.md",[],[131,132,133,134,98,135,136,42,102,137,138,139,140,141,142,143,144],"Pydantic","harness","pydantic ai","pydantic ai harness","batteries","pydantic-ai","tool","sandboxing","execution","capabilities","code","ai agents","python","ai agent",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":155,"publishedAt":49},"01M6DXH7JE54YEHM58JY8KY2AK","building-pydantic-ai-agents","Build AI agents with Pydantic AI — tools, capabilities (including on-demand loading), structured output, streaming, testing, and multi-agent patterns. Use when the user mentions Pydantic AI, imports pydantic_ai, or asks to build an AI agent, add tools\u002Fcapabilities, defer capability loading, stream output, define agents from YAML, or test agent behavior.","https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fcianfhoghlaim\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fpydantic\u002Fbuilding-pydantic-ai-agents\u002FSKILL.md",[151,154],{"categoryNo":152,"categoryName":153,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":115,"categoryName":116,"taxonomyType":21,"taxonomyTypeDesc":22},[142,131,133,156,143,157,144,158,159,160,161,162,42,163,164,165,166,167,140,168],"building pydantic ai agents","testing","structured output","define","agent patterns","patterns","build","behavior","multi-agent","Tools","yaml","streaming","test",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":178,"publishedAt":49},"01M6DXGCVB0WSHBQ7BSA56A12C","motherduck-share-data","Create and manage MotherDuck data shares for zero-copy, read-only data distribution. Use whenever someone wants to share a database with team members, another organization, or the public — covers CREATE SHARE, access\u002Fvisibility\u002Fupdate modes, GRANT READ ON SHARE, attaching share URLs, UPDATE SHARE, and REFRESH DATABASE.","https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fcianfhoghlaim\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmotherduck\u002Fmotherduck-share-data\u002FSKILL.md",[175],{"categoryNo":176,"categoryName":177,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000033","数据分析师",[179,180,30,181,42,182,183,184,185,186,43,187,46,188,189,190,191,47],"share","data","motherduck share data","distribution","organization","manage","only","refresh","public","team","ZeRO","database","update",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":198,"publishedAt":49},"01M6DXG9NMFYC72KJWQVJ1D6BZ","motherduck-security-governance","Explain MotherDuck security, governance, and access-control patterns. Use for any question about SOC 2, GDPR, compliance, data residency, regions, SSO, service accounts, token handling, tenant isolation, sharing boundaries, snapshots and recovery, or governance posture — including when a security_compliance_owner, technical_owner, or application_builder is evaluating MotherDuck.","https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fcianfhoghlaim\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmotherduck\u002Fmotherduck-security-governance\u002FSKILL.md",[],[199,200,201,30,202,203,204,46,205,206,207,208,209,180,210,211,35,212,42,213],"governance","security","motherduck security governance","sso","sharing","recovery","explain","technical","compliance","soc","gdpr","snapshots","token","question","builder"]