[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79G1VT1K82HMMEWW71K6FQK":3,"skill-same:01M79G1VT1K82HMMEWW71K6FQK":59},{"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":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M79G1VT1K82HMMEWW71K6FQK","supabase",null,"Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase\u002Fssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector).","zfifteen\u002Fskills-catalog","zfifteen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F221906715?v=4","01M79CQFXDZM5J5CJTCECPFA66","Dionisio Alberto Lopez III","01M79CQFY4C62PN8A2T5KDAHGA",1,"MIT","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: supabase\ndescription: \"Use when doing ANY task involving Supabase. Triggers: Supabase products (Database, Auth, Edge Functions, Realtime, Storage, Vectors, Cron, Queues); client libraries and SSR integrations (supabase-js, @supabase\u002Fssr) in Next.js, React, SvelteKit, Astro, Remix; auth issues (login, logout, sessions, JWT, cookies, getSession, getUser, getClaims, RLS); Supabase CLI or MCP server; schema changes, migrations, security audits, Postgres extensions (pg_graphql, pg_cron, pg_vector).\"\nmetadata:\n  author: supabase\n  version: \"0.1.2\"\n---\n\n# Supabase\n\n## Core Principles\n\n**1. Supabase changes frequently — verify against changelog and current docs before implementing.**\nDo not rely on training data for Supabase features. Function signatures, config.toml settings, and API conventions change between versions.\n\nFirst, fetch `https:\u002F\u002Fsupabase.com\u002Fchangelog.md` (a lightweight summary index — not a heavy pull), scan for `breaking-change` tags relevant to your task, and follow the linked page for any that apply. Then look up the relevant topic using the documentation access methods below.\n\n**2. Verify your work.**\nAfter implementing any fix, run a test query to confirm the change works. A fix without verification is incomplete.\n\n**3. Recover from errors, don't loop.**\nIf an approach fails after 2-3 attempts, stop and reconsider. Try a different method, check documentation, inspect the error more carefully, and review relevant logs when available. Supabase issues are not always solved by retrying the same command, and the answer is not always in the logs, but logs are often worth checking before proceeding.\n\n**4. Exposing tables to the Data API:** Depending on the user's [Data API settings](https:\u002F\u002Fsupabase.com\u002Fdashboard\u002Fproject\u002F\u003Cref>\u002Fintegrations\u002Fdata_api\u002Fsettings), newly created tables may not be automatically exposed via the Data (REST) API. If this is the case, `anon` and `authenticated` roles will need to be explicitly granted access.\n\n> Note that this is separate from RLS, which controls which _rows_ are visible once a table is accessible, not whether the table is accessible at all.\n\nWhen a user reports a SQL-created table is unexpectedly inaccessible, check their Data API settings and whether the roles have been granted access via explicit `GRANT` SQL. When granting public (`anon`\u002F`authenticated`) access, always enable RLS too. See [Exposing a Table to the Data API](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fapi\u002Fsecuring-your-api.md) for the full setup workflow.\n\n**5. RLS in exposed schemas.**\nEnable RLS on every table in any exposed schema, which includes `public` by default. This is critical in Supabase because tables in exposed schemas can be reachable through the Data API when the `anon`\u002F`authenticated` roles have access (see [Exposing a Table to the Data API](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fapi\u002Fsecuring-your-api.md)). For private schemas, prefer RLS as defense in depth. After enabling RLS, create policies that match the actual access model rather than defaulting every table to the same `auth.uid()` pattern.\n\n**6. Security checklist.**\nWhen working on any Supabase task that touches auth, RLS, views, storage, or user data, run through this checklist. These are Supabase-specific security traps that silently create vulnerabilities:\n\n- **Auth and session security**\n  - **Never use `user_metadata` claims in JWT-based authorization decisions.** In Supabase, `raw_user_meta_data` is user-editable and can appear in `auth.jwt()`, so it is unsafe for RLS policies or any other authorization logic. Store authorization data in `raw_app_meta_data` \u002F `app_metadata` instead.\n  - **Deleting a user does not invalidate existing access tokens.** Sign out or revoke sessions first, keep JWT expiry short for sensitive apps, and for strict guarantees validate `session_id` against `auth.sessions` on sensitive operations.\n  - **If you use `app_metadata` or `auth.jwt()` for authorization, remember JWT claims are not always fresh until the user's token is refreshed.**\n\n- **API key and client exposure**\n  - **Never expose the `service_role` or secret key in public clients.** Prefer publishable keys for frontend code. Legacy `anon` keys are only for compatibility. In Next.js, any `NEXT_PUBLIC_` env var is sent to the browser.\n\n- **RLS, views, and privileged database code**\n  - **Views bypass RLS by default.** In Postgres 15 and above, use `CREATE VIEW ... WITH (security_invoker = true)`. In older versions of Postgres, protect your views by revoking access from the `anon` and `authenticated` roles, or by putting them in an unexposed schema.\n  - **UPDATE requires a SELECT policy.** In Postgres RLS, an UPDATE needs to first SELECT the row. Without a SELECT policy, updates silently return 0 rows — no error, just no change.\n  - **Do not put `security definer` functions in an exposed schema.** Keep them in a private or otherwise unexposed schema.\n\n- **Storage access control**\n  - **Storage upsert requires INSERT + SELECT + UPDATE.** Granting only INSERT allows new uploads but file replacement (upsert) silently fails. You need all three.\n\nFor any security concern not covered above, fetch the Supabase product security index: `https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fsecurity\u002Fproduct-security.md`\n\n## Supabase CLI\n\nAlways discover commands via `--help` — never guess. The CLI structure changes between versions.\n\n```bash\nsupabase --help                    # All top-level commands\nsupabase \u003Cgroup> --help            # Subcommands (e.g., supabase db --help)\nsupabase \u003Cgroup> \u003Ccommand> --help  # Flags for a specific command\n```\n\n**Supabase CLI Known gotchas:**\n\n- `supabase db query` requires **CLI v2.79.0+** → use MCP `execute_sql` or `psql` as fallback\n- `supabase db advisors` requires **CLI v2.81.3+** → use MCP `get_advisors` as fallback\n- When you need a new migration SQL file, **always** create it with `supabase migration new \u003Cname>` first. Never invent a migration filename or rely on memory for the expected format.\n\n**Version check and upgrade:** Run `supabase --version` to check. For CLI changelogs and version-specific features, consult the [CLI documentation](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Freference\u002Fcli\u002Fintroduction) or [GitHub releases](https:\u002F\u002Fgithub.com\u002Fsupabase\u002Fcli\u002Freleases).\n\n## Supabase MCP Server\n\nFor setup instructions, server URL, and configuration, see the [MCP setup guide](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fgetting-started\u002Fmcp).\n\n**Troubleshooting connection issues** — follow these steps in order:\n\n1. **Check if the server is reachable:**\n   `curl -so \u002Fdev\u002Fnull -w \"%{http_code}\" https:\u002F\u002Fmcp.supabase.com\u002Fmcp`\n   A `401` is expected (no token) and means the server is up. Timeout or \"connection refused\" means it may be down.\n\n2. **Check `.mcp.json` configuration:**\n   Verify the project root has a valid `.mcp.json` with the correct server URL. If missing, create one pointing to `https:\u002F\u002Fmcp.supabase.com\u002Fmcp`.\n\n3. **Authenticate the MCP server:**\n   If the server is reachable and `.mcp.json` is correct but tools aren't visible, the user needs to authenticate. The Supabase MCP server uses OAuth 2.1 — tell the user to trigger the auth flow in their agent, complete it in the browser, and reload the session.\n\n## Supabase Documentation\n\nBefore implementing any Supabase feature, find the relevant documentation. Use these methods in priority order:\n\n1. **MCP `search_docs` tool** (preferred — returns relevant snippets directly)\n2. **Fetch docs pages as markdown** — any docs page can be fetched by appending `.md` to the URL path.\n3. **Web search** for Supabase-specific topics when you don't know which page to look at.\n\n## Making and Committing Schema Changes\n\n**To make schema changes, use `execute_sql` (MCP) or `supabase db query` (CLI).** These run SQL directly on the database without creating migration history entries, so you can iterate freely and generate a clean migration when ready.\n\nDo NOT use `apply_migration` to change a local database schema — it writes a migration history entry on every call, which means you can't iterate, and `supabase db diff` \u002F `supabase db pull` will produce empty or conflicting diffs. If you use it, you'll be stuck with whatever SQL you passed on the first try.\n\n**When ready to commit** your changes to a migration file:\n\n1. **Run advisors** → `supabase db advisors` (CLI v2.81.3+) or MCP `get_advisors`. Fix any issues.\n2. **Review the Security Checklist above** if your changes involve views, functions, triggers, or storage.\n3. **Generate the migration** → `supabase db pull \u003Cdescriptive-name> --local --yes`\n4. **Verify** → `supabase migration list --local`\n\n## Reference Guides\n\n- **Skill Feedback** → [references\u002Fskill-feedback.md](references\u002Fskill-feedback.md)\n  **MUST read when** the user reports that this skill gave incorrect guidance or is missing information.\n","# Supabase\n\n## Core Principles\n\n**1. Supabase changes frequently — verify against changelog and current docs before implementing.**\nDo not rely on training data for Supabase features. Function signatures, config.toml settings, and API conventions change between versions.\n\nFirst, fetch `https:\u002F\u002Fsupabase.com\u002Fchangelog.md` (a lightweight summary index — not a heavy pull), scan for `breaking-change` tags relevant to your task, and follow the linked page for any that apply. Then look up the relevant topic using the documentation access methods below.\n\n**2. Verify your work.**\nAfter implementing any fix, run a test query to confirm the change works. A fix without verification is incomplete.\n\n**3. Recover from errors, don't loop.**\nIf an approach fails after 2-3 attempts, stop and reconsider. Try a different method, check documentation, inspect the error more carefully, and review relevant logs when available. Supabase issues are not always solved by retrying the same command, and the answer is not always in the logs, but logs are often worth checking before proceeding.\n\n**4. Exposing tables to the Data API:** Depending on the user's [Data API settings](https:\u002F\u002Fsupabase.com\u002Fdashboard\u002Fproject\u002F\u003Cref>\u002Fintegrations\u002Fdata_api\u002Fsettings), newly created tables may not be automatically exposed via the Data (REST) API. If this is the case, `anon` and `authenticated` roles will need to be explicitly granted access.\n\n> Note that this is separate from RLS, which controls which _rows_ are visible once a table is accessible, not whether the table is accessible at all.\n\nWhen a user reports a SQL-created table is unexpectedly inaccessible, check their Data API settings and whether the roles have been granted access via explicit `GRANT` SQL. When granting public (`anon`\u002F`authenticated`) access, always enable RLS too. See [Exposing a Table to the Data API](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fapi\u002Fsecuring-your-api.md) for the full setup workflow.\n\n**5. RLS in exposed schemas.**\nEnable RLS on every table in any exposed schema, which includes `public` by default. This is critical in Supabase because tables in exposed schemas can be reachable through the Data API when the `anon`\u002F`authenticated` roles have access (see [Exposing a Table to the Data API](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fapi\u002Fsecuring-your-api.md)). For private schemas, prefer RLS as defense in depth. After enabling RLS, create policies that match the actual access model rather than defaulting every table to the same `auth.uid()` pattern.\n\n**6. Security checklist.**\nWhen working on any Supabase task that touches auth, RLS, views, storage, or user data, run through this checklist. These are Supabase-specific security traps that silently create vulnerabilities:\n\n- **Auth and session security**\n  - **Never use `user_metadata` claims in JWT-based authorization decisions.** In Supabase, `raw_user_meta_data` is user-editable and can appear in `auth.jwt()`, so it is unsafe for RLS policies or any other authorization logic. Store authorization data in `raw_app_meta_data` \u002F `app_metadata` instead.\n  - **Deleting a user does not invalidate existing access tokens.** Sign out or revoke sessions first, keep JWT expiry short for sensitive apps, and for strict guarantees validate `session_id` against `auth.sessions` on sensitive operations.\n  - **If you use `app_metadata` or `auth.jwt()` for authorization, remember JWT claims are not always fresh until the user's token is refreshed.**\n\n- **API key and client exposure**\n  - **Never expose the `service_role` or secret key in public clients.** Prefer publishable keys for frontend code. Legacy `anon` keys are only for compatibility. In Next.js, any `NEXT_PUBLIC_` env var is sent to the browser.\n\n- **RLS, views, and privileged database code**\n  - **Views bypass RLS by default.** In Postgres 15 and above, use `CREATE VIEW ... WITH (security_invoker = true)`. In older versions of Postgres, protect your views by revoking access from the `anon` and `authenticated` roles, or by putting them in an unexposed schema.\n  - **UPDATE requires a SELECT policy.** In Postgres RLS, an UPDATE needs to first SELECT the row. Without a SELECT policy, updates silently return 0 rows — no error, just no change.\n  - **Do not put `security definer` functions in an exposed schema.** Keep them in a private or otherwise unexposed schema.\n\n- **Storage access control**\n  - **Storage upsert requires INSERT + SELECT + UPDATE.** Granting only INSERT allows new uploads but file replacement (upsert) silently fails. You need all three.\n\nFor any security concern not covered above, fetch the Supabase product security index: `https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fsecurity\u002Fproduct-security.md`\n\n## Supabase CLI\n\nAlways discover commands via `--help` — never guess. The CLI structure changes between versions.\n\n```bash\nsupabase --help                    # All top-level commands\nsupabase \u003Cgroup> --help            # Subcommands (e.g., supabase db --help)\nsupabase \u003Cgroup> \u003Ccommand> --help  # Flags for a specific command\n```\n\n**Supabase CLI Known gotchas:**\n\n- `supabase db query` requires **CLI v2.79.0+** → use MCP `execute_sql` or `psql` as fallback\n- `supabase db advisors` requires **CLI v2.81.3+** → use MCP `get_advisors` as fallback\n- When you need a new migration SQL file, **always** create it with `supabase migration new \u003Cname>` first. Never invent a migration filename or rely on memory for the expected format.\n\n**Version check and upgrade:** Run `supabase --version` to check. For CLI changelogs and version-specific features, consult the [CLI documentation](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Freference\u002Fcli\u002Fintroduction) or [GitHub releases](https:\u002F\u002Fgithub.com\u002Fsupabase\u002Fcli\u002Freleases).\n\n## Supabase MCP Server\n\nFor setup instructions, server URL, and configuration, see the [MCP setup guide](https:\u002F\u002Fsupabase.com\u002Fdocs\u002Fguides\u002Fgetting-started\u002Fmcp).\n\n**Troubleshooting connection issues** — follow these steps in order:\n\n1. **Check if the server is reachable:**\n   `curl -so \u002Fdev\u002Fnull -w \"%{http_code}\" https:\u002F\u002Fmcp.supabase.com\u002Fmcp`\n   A `401` is expected (no token) and means the server is up. Timeout or \"connection refused\" means it may be down.\n\n2. **Check `.mcp.json` configuration:**\n   Verify the project root has a valid `.mcp.json` with the correct server URL. If missing, create one pointing to `https:\u002F\u002Fmcp.supabase.com\u002Fmcp`.\n\n3. **Authenticate the MCP server:**\n   If the server is reachable and `.mcp.json` is correct but tools aren't visible, the user needs to authenticate. The Supabase MCP server uses OAuth 2.1 — tell the user to trigger the auth flow in their agent, complete it in the browser, and reload the session.\n\n## Supabase Documentation\n\nBefore implementing any Supabase feature, find the relevant documentation. Use these methods in priority order:\n\n1. **MCP `search_docs` tool** (preferred — returns relevant snippets directly)\n2. **Fetch docs pages as markdown** — any docs page can be fetched by appending `.md` to the URL path.\n3. **Web search** for Supabase-specific topics when you don't know which page to look at.\n\n## Making and Committing Schema Changes\n\n**To make schema changes, use `execute_sql` (MCP) or `supabase db query` (CLI).** These run SQL directly on the database without creating migration history entries, so you can iterate freely and generate a clean migration when ready.\n\nDo NOT use `apply_migration` to change a local database schema — it writes a migration history entry on every call, which means you can't iterate, and `supabase db diff` \u002F `supabase db pull` will produce empty or conflicting diffs. If you use it, you'll be stuck with whatever SQL you passed on the first try.\n\n**When ready to commit** your changes to a migration file:\n\n1. **Run advisors** → `supabase db advisors` (CLI v2.81.3+) or MCP `get_advisors`. Fix any issues.\n2. **Review the Security Checklist above** if your changes involve views, functions, triggers, or storage.\n3. **Generate the migration** → `supabase db pull \u003Cdescriptive-name> --local --yes`\n4. **Verify** → `supabase migration list --local`\n\n## Reference Guides\n\n- **Skill Feedback** → [references\u002Fskill-feedback.md](references\u002Fskill-feedback.md)\n  **MUST read when** the user reports that this skill gave incorrect guidance or is missing information.\n",{"name":5,"metadata":24,"description":7},{"author":5,"version":25},"0.1.2","main","d9535210da9af28aa76bca80de80355197e1b6d6","skills\u002Fsupabase","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog","https:\u002F\u002Fgithub.com\u002Fzfifteen","I like to measure things.","2026-07-19 23:41:54",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add zfifteen\u002Fskills-catalog --skill supabase",{"tool":39,"command":40},"bunx","bunx skills add zfifteen\u002Fskills-catalog --skill supabase",{"tool":42,"command":43},"pnpm","pnpm dlx skills add zfifteen\u002Fskills-catalog --skill supabase","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase\u002FSKILL.md",true,[47,53],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"assets\u002Ffeedback-issue-template.md","ASSET","资产文件",459,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase\u002Fassets\u002Ffeedback-issue-template.md",{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"references\u002Fskill-feedback.md","REFERENCE","参考文档",1035,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fsupabase\u002Freferences\u002Fskill-feedback.md",[60,67,74,81,90,97],{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M79GXQ2PWPT2E4CJYHXVJ0YE","Zotero","Use Zotero Desktop from Codex to enable\u002Fprobe the local API, search a local Zotero library, list items\u002Fcollections\u002Ftags, export BibTeX, insert citation keys into LaTeX or Markdown drafts, read indexed full text when requested, and import BibTeX\u002FRIS records into Zotero through the connector server. Use when the user mentions Zotero, citations, references.bib, BibTeX export, local Zotero API, localhost:23119, or adding citations from a Zotero library.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzotero\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M79GXN85NETKBE06865CWK6Z","zoom-apps-sdk","Use when using Apps SDK.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-apps-sdk\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M79GXCYD7FGYS932J9N9RFFY","youtube","Obtain accurate, timestamped YouTube video transcripts (preferring manual captions over auto-generated) as the primary deliverable, then derive summaries, key claims, or notes from that transcript.  Use when the user provides a YouTube URL (or video ID) and wants the transcript, a faithful summary, key claims with attribution, timestamped notes, or \"what does this video actually say\".  The skill is transcript-first: never substitute metadata, title, description, or search snippets for the spoken content.  Triggers: \"youtube transcript\", \"get the transcript of this video\", \"summarize this youtube video\", \"what did they say in https:\u002F\u002Fyoutube.com\u002F...\", \"key claims from this talk\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyoutube\u002FSKILL.md",[],[],{"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":85,"licenseFileUrl":86,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M79GX8EXHHYM566BKR7MS778","yeet","Publish local changes to GitHub by confirming scope, committing intentionally, pushing the branch, and opening a draft PR through the GitHub app from this plugin, with `gh` used only as a fallback where connector coverage is insufficient.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":94,"categories":95,"keywords":96,"publishedAt":19},"01M79GX2HFJPX84NMRE5VBTYX9","x-post-creator","Create X-ready post threads and co-located story packages from the active conversation or referenced project material. Use when the user says turn this into an X-post, \u002Fx-post, make this into an X thread, or wants plain-language social posts with supporting images saved to docs\u002Fx-posts\u002F[story-name]\u002F.","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-post-creator\u002FSKILL.md",[],[],{"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":103,"publishedAt":19},"01M79GWXQT4HBT6QME6QSBZJFA","x-api","Search, read, and write X posts through the local X API MCP server (the same backend used by the Codex x-api skill). Use for searching X\u002Fx.com, reading threads and replies, creating lists, staging\u002Fpublishing posts for @alltheputs, finding high-visibility reply targets for research outreach, ingesting public context, or any request that mentions \u002Fx-api or \"search X\".","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]