[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6DXGCVB0WSHBQ7BSA56A12C":3,"skill-same:01M6DXGCVB0WSHBQ7BSA56A12C":76},{"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":42,"linkOnly":43,"markdownContent":44,"markdownBody":45,"frontMatter":46,"refName":47,"commitSha":48,"skillDirectory":49,"forksCount":50,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":53,"ownerDescription":54,"updatedAt":55,"install":56,"resources":69},"01M6DXGCVB0WSHBQ7BSA56A12C","motherduck-share-data",null,"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.","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-share-data\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41],"motherduck share data","share","motherduck","data","read","distribution","organization","manage","only","use","refresh","create","public","access","team","ZeRO","database","update","2026-11-10 10:12:30",false,"---\nname: motherduck-share-data\ndescription: 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.\nlicense: MIT\n---\n\n# Share Data with MotherDuck\n\nUse this skill when you need to distribute a MotherDuck database without copying data. Shares are read-only, zero-copy database clones and should be treated as explicit provisioning operations.\n\n## Source Of Truth\n\n- Prefer the current MotherDuck sharing docs and SQL reference first.\n- If the MotherDuck MCP `ask_docs_question` feature is available, use it before falling back to public docs.\n- Keep the sharing model aligned with the documented behavior:\n  - zero-copy and metadata-only\n  - database-granularity sharing\n  - read-only recipients\n  - owner-controlled update mode\n\n## Prerequisites\n\n- MotherDuck connection established via `motherduck-connect`\n- Source database identified via `motherduck-explore`\n- Share SQL validated via `motherduck-query`\n\n## Default Posture\n\n- Default internal sharing to `ACCESS ORGANIZATION`, `VISIBILITY DISCOVERABLE`, and `UPDATE AUTOMATIC`.\n- Use `UPDATE MANUAL` when the recipient needs a stable snapshot or versioned delivery.\n- Use `ACCESS RESTRICTED` or `VISIBILITY HIDDEN` when distribution should stay tightly controlled.\n- Confirm whether the recipient is an internal user, another organization, or public before choosing access and visibility.\n- For write-heavy publishers, verify the DuckDB client version is one MotherDuck supports before relying on checkpoint or concurrent-write behavior during share-update workflows.\n- Never treat a share as row-level security. Shares operate at database granularity.\n\n## Workflow\n\n1. Identify the exact database to publish and who should consume it.\n2. Decide sensitivity, discoverability, and freshness requirements before writing SQL.\n3. Create the share with explicit access, visibility, and update settings.\n4. If access is restricted, grant readers explicitly. If the share is hidden or link-based, distribute the share URL directly.\n5. Have recipients `ATTACH` the shared database and query it read-only.\n6. If the share uses `UPDATE MANUAL`, the owner runs `UPDATE SHARE` and consumers run `REFRESH DATABASE` when a new snapshot is ready.\n\n## Open Next\n\n- Read `references\u002FSHARE_PLAYBOOK.md` for the full SQL playbook, access\u002Fupdate decision matrix, consumer workflow, and common failure modes.\n\n## Related Skills\n\n- `motherduck-connect` for MotherDuck authentication and connection setup\n- `motherduck-explore` for discovering databases, tables, columns, and existing shares\n- `motherduck-query` for validating share SQL and downstream queries\n- `motherduck-duckdb-sql` for DuckDB SQL syntax and lookup support\n","# Share Data with MotherDuck\n\nUse this skill when you need to distribute a MotherDuck database without copying data. Shares are read-only, zero-copy database clones and should be treated as explicit provisioning operations.\n\n## Source Of Truth\n\n- Prefer the current MotherDuck sharing docs and SQL reference first.\n- If the MotherDuck MCP `ask_docs_question` feature is available, use it before falling back to public docs.\n- Keep the sharing model aligned with the documented behavior:\n  - zero-copy and metadata-only\n  - database-granularity sharing\n  - read-only recipients\n  - owner-controlled update mode\n\n## Prerequisites\n\n- MotherDuck connection established via `motherduck-connect`\n- Source database identified via `motherduck-explore`\n- Share SQL validated via `motherduck-query`\n\n## Default Posture\n\n- Default internal sharing to `ACCESS ORGANIZATION`, `VISIBILITY DISCOVERABLE`, and `UPDATE AUTOMATIC`.\n- Use `UPDATE MANUAL` when the recipient needs a stable snapshot or versioned delivery.\n- Use `ACCESS RESTRICTED` or `VISIBILITY HIDDEN` when distribution should stay tightly controlled.\n- Confirm whether the recipient is an internal user, another organization, or public before choosing access and visibility.\n- For write-heavy publishers, verify the DuckDB client version is one MotherDuck supports before relying on checkpoint or concurrent-write behavior during share-update workflows.\n- Never treat a share as row-level security. Shares operate at database granularity.\n\n## Workflow\n\n1. Identify the exact database to publish and who should consume it.\n2. Decide sensitivity, discoverability, and freshness requirements before writing SQL.\n3. Create the share with explicit access, visibility, and update settings.\n4. If access is restricted, grant readers explicitly. If the share is hidden or link-based, distribute the share URL directly.\n5. Have recipients `ATTACH` the shared database and query it read-only.\n6. If the share uses `UPDATE MANUAL`, the owner runs `UPDATE SHARE` and consumers run `REFRESH DATABASE` when a new snapshot is ready.\n\n## Open Next\n\n- Read `references\u002FSHARE_PLAYBOOK.md` for the full SQL playbook, access\u002Fupdate decision matrix, consumer workflow, and common failure modes.\n\n## Related Skills\n\n- `motherduck-connect` for MotherDuck authentication and connection setup\n- `motherduck-explore` for discovering databases, tables, columns, and existing shares\n- `motherduck-query` for validating share SQL and downstream queries\n- `motherduck-duckdb-sql` for DuckDB SQL syntax and lookup support\n",{"name":5,"license":15,"description":7},"main","5ace051462d0639f59bcc60912f4ec08c1a96772",".agents\u002Fskills\u002Fmotherduck\u002Fmotherduck-share-data",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-10-12 08:07:09",{"source":8,"skillName":5,"commands":57,"prompt":67,"zipAvailable":68},[58,61,64],{"tool":59,"command":60},"npx","npx skills add cianfhoghlaim\u002Fcianfhoghlaim --skill motherduck-share-data",{"tool":62,"command":63},"bunx","bunx skills add cianfhoghlaim\u002Fcianfhoghlaim --skill motherduck-share-data",{"tool":65,"command":66},"pnpm","pnpm dlx skills add cianfhoghlaim\u002Fcianfhoghlaim --skill motherduck-share-data","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fcianfhoghlaim\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmotherduck\u002Fmotherduck-share-data\u002FSKILL.md",true,[70],{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002FSHARE_PLAYBOOK.md","REFERENCE","参考文档",11715,"https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fcianfhoghlaim\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmotherduck\u002Fmotherduck-share-data\u002Freferences\u002FSHARE_PLAYBOOK.md",[77,97,115,136,160,183],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":42},"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",[],[84,85,86,87,35,88,89,90,91,92,93,94,95,96],"init","dagster","dagster init","cli","run","dev","virtual","check","initialize","user","environment","uv","project",{"skillNo":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":101,"categories":102,"keywords":108,"publishedAt":42},"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",[103],{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[109,35,85,110,87,111,112,113,33,114],"component","create custom dagster component","support","demo","integration","structure",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":42},"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",[],[122,123,124,125,126,127,128,88,129,130,131,132,133,93,33,134,135],"harness","Pydantic","pydantic ai","pydantic ai harness","python","ai agents","ai agent","code","capabilities","execution","sandboxing","tool","pydantic-ai","batteries",{"skillNo":137,"name":138,"nameZh":6,"description":139,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":140,"categories":141,"keywords":146,"publishedAt":42},"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",[142,145],{"categoryNo":143,"categoryName":144,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000008","测试与质量",{"categoryNo":104,"categoryName":105,"taxonomyType":106,"taxonomyTypeDesc":107},[127,123,124,147,148,126,128,149,130,150,151,152,153,154,33,155,156,157,158,159],"building pydantic ai agents","testing","test","streaming","yaml","Tools","multi-agent","behavior","build","patterns","agent patterns","define","structured output",{"skillNo":161,"name":162,"nameZh":6,"description":163,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":164,"categories":165,"keywords":166,"publishedAt":42},"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",[],[167,168,26,169,170,171,172,27,173,174,175,37,176,177,178,33,179,180,181,182],"security","governance","motherduck security governance","compliance","soc","gdpr","sso","sharing","recovery","explain","technical","question","builder","snapshots","token","control",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":195,"publishedAt":42},"01M6DXG6DFVSAPB6ATMWR6QGMV","motherduck-rest-api","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.","https:\u002F\u002Fgithub.com\u002Fcianfhoghlaim\u002Fcianfhoghlaim\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fmotherduck\u002Fmotherduck-rest-api\u002FSKILL.md",[189,192],{"categoryNo":190,"categoryName":191,"taxonomyType":106,"taxonomyTypeDesc":107},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":193,"categoryName":194,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000030","开发工程师",[196,197,198,26,199,200,201,35,37,202,203,28,33,204,205,206,207,208,209,182],"REST","api","rest api","motherduck rest api","sessions","sql","configure","work","mint","calling","query","active","tokens","scaling"]