[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75CJS08TYF0NG7ZBD6DCY23":3,"skill-same:01M75CJS08TYF0NG7ZBD6DCY23":74},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":28,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M75CJS08TYF0NG7ZBD6DCY23","convex-setup-auth",null,"Sets up Convex auth, identity mapping, and access control. Use for login, auth providers, users tables, protected functions, or roles in a Convex app.","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fconvex-setup-auth\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: convex-setup-auth\ndescription:\n  Sets up Convex auth, identity mapping, and access control. Use for login, auth\n  providers, users tables, protected functions, or roles in a Convex app.\n---\n\n# Convex Authentication Setup\n\nImplement secure authentication in Convex with user management and access\ncontrol.\n\n## When to Use\n\n- Setting up authentication for the first time\n- Implementing user management (users table, identity mapping)\n- Creating authentication helper functions\n- Setting up auth providers (Convex Auth, Clerk, WorkOS AuthKit, Auth0, custom\n  JWT)\n\n## When Not to Use\n\n- Auth for a non-Convex backend\n- Pure OAuth\u002FOIDC documentation without a Convex implementation\n- Debugging unrelated bugs that happen to surface near auth code\n- The auth provider is already fully configured and the user only needs a\n  one-line fix\n\n## First Step: Choose the Auth Provider\n\nConvex supports multiple authentication approaches. Do not assume a provider.\n\nBefore writing setup code:\n\n1. Ask the user which auth solution they want, unless the repository already\n   makes it obvious\n2. If the repo already uses a provider, continue with that provider unless the\n   user wants to switch\n3. If the user has not chosen a provider and the repo does not make it obvious,\n   ask before proceeding\n\nCommon options:\n\n- [Convex Auth](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fconvex-auth) - good default when\n  the user wants auth handled directly in Convex\n- [Clerk](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fclerk) - use when the app already uses\n  Clerk or the user wants Clerk's hosted auth features\n- [WorkOS AuthKit](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fauthkit\u002F) - use when the app\n  already uses WorkOS or the user wants AuthKit specifically\n- [Auth0](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fauth0) - use when the app already uses\n  Auth0\n- Custom JWT provider - use when integrating an existing auth system not covered\n  above\n\nLook for signals in the repo before asking:\n\n- Dependencies such as `@clerk\u002F*`, `@workos-inc\u002F*`, `@auth0\u002F*`, or Convex Auth\n  packages\n- Existing files such as `convex\u002Fauth.config.ts`, auth middleware, provider\n  wrappers, or login components\n- Environment variables that clearly point at a provider\n\n## After Choosing a Provider\n\nRead the provider's official guide and the matching local reference file:\n\n- Convex Auth: [official docs](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fconvex-auth), then\n  `references\u002Fconvex-auth.md`\n- Clerk: [official docs](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fclerk), then\n  `references\u002Fclerk.md`\n- WorkOS AuthKit: [official docs](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fauthkit\u002F), then\n  `references\u002Fworkos-authkit.md`\n- Auth0: [official docs](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fauth0), then\n  `references\u002Fauth0.md`\n\nThe local reference files contain the concrete workflow, expected files and env\nvars, gotchas, and validation checks.\n\nUse those sources for:\n\n- package installation\n- client provider wiring\n- environment variables\n- `convex\u002Fauth.config.ts` setup\n- login and logout UI patterns\n- framework-specific setup for React, Vite, or Next.js\n\nFor shared auth behavior, use the official Convex docs as the source of truth:\n\n- [Auth in Functions](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Ffunctions-auth) for\n  `ctx.auth.getUserIdentity()`\n- [Storing Users in the Convex Database](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fdatabase-auth)\n  for optional app-level user storage\n- [Authentication](https:\u002F\u002Fdocs.convex.dev\u002Fauth) for general auth and\n  authorization guidance\n- [Convex Auth Authorization](https:\u002F\u002Flabs.convex.dev\u002Fauth\u002Fauthz) when the\n  provider is Convex Auth\n\nPrefer official docs over recalled steps, because provider CLIs and Convex Auth\ninternals change between versions. Inventing setup from memory risks outdated\npatterns. For third-party providers, only add app-level user storage if the app\nactually needs user documents in Convex. Not every app needs a `users` table.\nFor Convex Auth, follow the Convex Auth docs and built-in auth tables rather\nthan adding a parallel `users` table plus `storeUser` flow, because Convex Auth\nalready manages user records internally. After running provider initialization\ncommands, verify generated files and complete the post-init wiring steps the\nprovider reference calls out. Initialization commands rarely finish the entire\nintegration.\n\n## Core Pattern: Protecting Backend Functions\n\nThe most common auth task is checking identity in Convex functions.\n\n```ts\n\u002F\u002F Bad: trusting a client-provided userId\nexport const getMyProfile = query({\n  args: { userId: v.id(\"users\") },\n  handler: async (ctx, args) => {\n    return await ctx.db.get(args.userId);\n  },\n});\n```\n\n```ts\n\u002F\u002F Good: verifying identity server-side\nexport const getMyProfile = query({\n  args: {},\n  handler: async (ctx) => {\n    const identity = await ctx.auth.getUserIdentity();\n    if (!identity) throw new Error(\"Not authenticated\");\n\n    return await ctx.db\n      .query(\"users\")\n      .withIndex(\"by_tokenIdentifier\", (q) =>\n        q.eq(\"tokenIdentifier\", identity.tokenIdentifier),\n      )\n      .unique();\n  },\n});\n```\n\n## Workflow\n\n1. Determine the provider, either by asking the user or inferring from the repo\n2. Ask whether the user wants local-only setup or production-ready setup now\n3. Read the matching provider reference file\n4. Follow the official provider docs for current setup details\n5. Follow the official Convex docs for shared backend auth behavior, user\n   storage, and authorization patterns\n6. Only add app-level user storage if the docs and app requirements call for it\n7. Add authorization checks for ownership, roles, or team access only where the\n   app needs them\n8. Verify login state, protected queries, environment variables, and production\n   configuration if requested\n\nIf the flow blocks on interactive provider or deployment setup, ask the user\nexplicitly for the exact human step needed, then continue after they complete\nit. For UI-facing auth flows, offer to validate the real sign-up or sign-in flow\nafter setup is done. If the environment has browser automation tools, you can\nuse them. If it does not, give the user a short manual validation checklist\ninstead.\n\n## Reference Files\n\n### Provider References\n\n- `references\u002Fconvex-auth.md`\n- `references\u002Fclerk.md`\n- `references\u002Fworkos-authkit.md`\n- `references\u002Fauth0.md`\n\n## Checklist\n\n- [ ] Chosen the correct auth provider before writing setup code\n- [ ] Read the relevant provider reference file\n- [ ] Asked whether the user wants local-only setup or production-ready setup\n- [ ] Used the official provider docs for provider-specific wiring\n- [ ] Used the official Convex docs for shared auth behavior and authorization\n      patterns\n- [ ] Only added app-level user storage if the app actually needs it\n- [ ] Did not invent a cross-provider `users` table or `storeUser` flow for\n      Convex Auth\n- [ ] Added authentication checks in protected backend functions\n- [ ] Added authorization checks where the app actually needs them\n- [ ] Clear error messages (\"Not authenticated\", \"Unauthorized\")\n- [ ] Client auth provider configured for the chosen provider\n- [ ] If requested, production auth setup is covered too\n","# Convex Authentication Setup\n\nImplement secure authentication in Convex with user management and access\ncontrol.\n\n## When to Use\n\n- Setting up authentication for the first time\n- Implementing user management (users table, identity mapping)\n- Creating authentication helper functions\n- Setting up auth providers (Convex Auth, Clerk, WorkOS AuthKit, Auth0, custom\n  JWT)\n\n## When Not to Use\n\n- Auth for a non-Convex backend\n- Pure OAuth\u002FOIDC documentation without a Convex implementation\n- Debugging unrelated bugs that happen to surface near auth code\n- The auth provider is already fully configured and the user only needs a\n  one-line fix\n\n## First Step: Choose the Auth Provider\n\nConvex supports multiple authentication approaches. Do not assume a provider.\n\nBefore writing setup code:\n\n1. Ask the user which auth solution they want, unless the repository already\n   makes it obvious\n2. If the repo already uses a provider, continue with that provider unless the\n   user wants to switch\n3. If the user has not chosen a provider and the repo does not make it obvious,\n   ask before proceeding\n\nCommon options:\n\n- [Convex Auth](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fconvex-auth) - good default when\n  the user wants auth handled directly in Convex\n- [Clerk](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fclerk) - use when the app already uses\n  Clerk or the user wants Clerk's hosted auth features\n- [WorkOS AuthKit](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fauthkit\u002F) - use when the app\n  already uses WorkOS or the user wants AuthKit specifically\n- [Auth0](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fauth0) - use when the app already uses\n  Auth0\n- Custom JWT provider - use when integrating an existing auth system not covered\n  above\n\nLook for signals in the repo before asking:\n\n- Dependencies such as `@clerk\u002F*`, `@workos-inc\u002F*`, `@auth0\u002F*`, or Convex Auth\n  packages\n- Existing files such as `convex\u002Fauth.config.ts`, auth middleware, provider\n  wrappers, or login components\n- Environment variables that clearly point at a provider\n\n## After Choosing a Provider\n\nRead the provider's official guide and the matching local reference file:\n\n- Convex Auth: [official docs](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fconvex-auth), then\n  `references\u002Fconvex-auth.md`\n- Clerk: [official docs](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fclerk), then\n  `references\u002Fclerk.md`\n- WorkOS AuthKit: [official docs](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fauthkit\u002F), then\n  `references\u002Fworkos-authkit.md`\n- Auth0: [official docs](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fauth0), then\n  `references\u002Fauth0.md`\n\nThe local reference files contain the concrete workflow, expected files and env\nvars, gotchas, and validation checks.\n\nUse those sources for:\n\n- package installation\n- client provider wiring\n- environment variables\n- `convex\u002Fauth.config.ts` setup\n- login and logout UI patterns\n- framework-specific setup for React, Vite, or Next.js\n\nFor shared auth behavior, use the official Convex docs as the source of truth:\n\n- [Auth in Functions](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Ffunctions-auth) for\n  `ctx.auth.getUserIdentity()`\n- [Storing Users in the Convex Database](https:\u002F\u002Fdocs.convex.dev\u002Fauth\u002Fdatabase-auth)\n  for optional app-level user storage\n- [Authentication](https:\u002F\u002Fdocs.convex.dev\u002Fauth) for general auth and\n  authorization guidance\n- [Convex Auth Authorization](https:\u002F\u002Flabs.convex.dev\u002Fauth\u002Fauthz) when the\n  provider is Convex Auth\n\nPrefer official docs over recalled steps, because provider CLIs and Convex Auth\ninternals change between versions. Inventing setup from memory risks outdated\npatterns. For third-party providers, only add app-level user storage if the app\nactually needs user documents in Convex. Not every app needs a `users` table.\nFor Convex Auth, follow the Convex Auth docs and built-in auth tables rather\nthan adding a parallel `users` table plus `storeUser` flow, because Convex Auth\nalready manages user records internally. After running provider initialization\ncommands, verify generated files and complete the post-init wiring steps the\nprovider reference calls out. Initialization commands rarely finish the entire\nintegration.\n\n## Core Pattern: Protecting Backend Functions\n\nThe most common auth task is checking identity in Convex functions.\n\n```ts\n\u002F\u002F Bad: trusting a client-provided userId\nexport const getMyProfile = query({\n  args: { userId: v.id(\"users\") },\n  handler: async (ctx, args) => {\n    return await ctx.db.get(args.userId);\n  },\n});\n```\n\n```ts\n\u002F\u002F Good: verifying identity server-side\nexport const getMyProfile = query({\n  args: {},\n  handler: async (ctx) => {\n    const identity = await ctx.auth.getUserIdentity();\n    if (!identity) throw new Error(\"Not authenticated\");\n\n    return await ctx.db\n      .query(\"users\")\n      .withIndex(\"by_tokenIdentifier\", (q) =>\n        q.eq(\"tokenIdentifier\", identity.tokenIdentifier),\n      )\n      .unique();\n  },\n});\n```\n\n## Workflow\n\n1. Determine the provider, either by asking the user or inferring from the repo\n2. Ask whether the user wants local-only setup or production-ready setup now\n3. Read the matching provider reference file\n4. Follow the official provider docs for current setup details\n5. Follow the official Convex docs for shared backend auth behavior, user\n   storage, and authorization patterns\n6. Only add app-level user storage if the docs and app requirements call for it\n7. Add authorization checks for ownership, roles, or team access only where the\n   app needs them\n8. Verify login state, protected queries, environment variables, and production\n   configuration if requested\n\nIf the flow blocks on interactive provider or deployment setup, ask the user\nexplicitly for the exact human step needed, then continue after they complete\nit. For UI-facing auth flows, offer to validate the real sign-up or sign-in flow\nafter setup is done. If the environment has browser automation tools, you can\nuse them. If it does not, give the user a short manual validation checklist\ninstead.\n\n## Reference Files\n\n### Provider References\n\n- `references\u002Fconvex-auth.md`\n- `references\u002Fclerk.md`\n- `references\u002Fworkos-authkit.md`\n- `references\u002Fauth0.md`\n\n## Checklist\n\n- [ ] Chosen the correct auth provider before writing setup code\n- [ ] Read the relevant provider reference file\n- [ ] Asked whether the user wants local-only setup or production-ready setup\n- [ ] Used the official provider docs for provider-specific wiring\n- [ ] Used the official Convex docs for shared auth behavior and authorization\n      patterns\n- [ ] Only added app-level user storage if the app actually needs it\n- [ ] Did not invent a cross-provider `users` table or `storeUser` flow for\n      Convex Auth\n- [ ] Added authentication checks in protected backend functions\n- [ ] Added authorization checks where the app actually needs them\n- [ ] Clear error messages (\"Not authenticated\", \"Unauthorized\")\n- [ ] Client auth provider configured for the chosen provider\n- [ ] If requested, production auth setup is covered too\n",{"name":5,"description":7},"main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fconvex-setup-auth",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add agisota\u002Fold-one --skill convex-setup-auth",{"tool":38,"command":39},"bunx","bunx skills add agisota\u002Fold-one --skill convex-setup-auth",{"tool":41,"command":42},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill convex-setup-auth","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fconvex-setup-auth\u002FSKILL.md",true,[46,52,58,62,66,70],{"path":47,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":50,"sourceHtmlUrl":51},"agents\u002Fopenai.yaml","REFERENCE","参考文档",485,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fconvex-setup-auth\u002Fagents\u002Fopenai.yaml",{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"assets\u002Ficon.svg","ASSET","资产文件",394,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fconvex-setup-auth\u002Fassets\u002Ficon.svg",{"path":59,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Fauth0.md",7542,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fconvex-setup-auth\u002Freferences\u002Fauth0.md",{"path":63,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fclerk.md",6340,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fconvex-setup-auth\u002Freferences\u002Fclerk.md",{"path":67,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fconvex-auth.md",8400,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fconvex-setup-auth\u002Freferences\u002Fconvex-auth.md",{"path":71,"resourceType":48,"resourceTypeDesc":49,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fworkos-authkit.md",6318,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fconvex-setup-auth\u002Freferences\u002Fworkos-authkit.md",[75,82,89,98,105,112],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":93,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":104,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]