[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79EZZC2F8110XDBW5D2RVT8":3,"skill-same:01M79EZZC2F8110XDBW5D2RVT8":125},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":6,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M79EZZC2F8110XDBW5D2RVT8","notion-spec-to-implementation",null,"Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs\u002Ffeature specs and creating Notion plans + tasks from them.","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\u002Fnotion-spec-to-implementation\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fnotion-spec-to-implementation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: notion-spec-to-implementation\ndescription: Turn Notion specs into implementation plans, tasks, and progress tracking; use when implementing PRDs\u002Ffeature specs and creating Notion plans + tasks from them.\nmetadata:\n  short-description: Turn Notion specs into implementation plans, tasks, and progress tracking\n---\n\n# Spec to Implementation\n\nConvert a Notion spec into linked implementation plans, tasks, and ongoing status updates.\n\n## Quick start\n1) Locate the spec with `Notion:search`, then fetch it with `Notion:fetch`.\n2) Parse requirements and ambiguities using `reference\u002Fspec-parsing.md`.\n3) Create a plan page with `Notion:notion-create-pages` (pick a template: quick vs. full).\n4) Find the task database, confirm schema, then create tasks with `Notion:notion-create-pages`.\n5) Link spec ↔ plan ↔ tasks; keep status current with `Notion:notion-update-page`.\n\n## Tool-call guardrails\n- Notion tool availability can vary by workspace. If a Notion MCP call returns `Tool \u003Cname> not found`, treat that tool as unavailable for the rest of the current task. Do not retry it with different arguments or call it again later; use `Notion:search` and `Notion:fetch` where sufficient.\n- Use one literal search query per `Notion:search` call and include `filters: {}` when no narrower filter is needed. Run separate searches for alternate phrasings instead of putting `or` in a single query string.\n- Only send Notion page, database, or data-source URLs\u002FIDs to `Notion:fetch`; external connected-source search results are not fetch targets.\n- Create plans and task pages with explicit `parent` and `pages` fields. For task databases, fetch first and use the returned `collection:\u002F\u002F...` data source ID.\n- To append an implementation section to a spec, fetch the current section text first, then use `Notion:notion-update-page` with `command: \"update_content\"`, `properties: {}`, and exact `old_str` \u002F `new_str` content. For property-only edits, use `command: \"update_properties\"` with `content_updates: []`; the current deployed schema expects both top-level fields even when one is unused.\n\n## Workflow\n\n### 0) If Notion tools are unavailable, pause and ask the user to connect the Notion app:\n1. Enable the bundled Notion app for this plugin or session.\n2. Complete the Notion auth flow if Codex prompts for it.\n3. Restart Codex or the current session if the tools still do not appear.\n\nAfter the app is connected, finish your answer and tell the user to retry so they can continue with Step 1.\n\n### 1) Locate and read the spec\n- Search first (`Notion:search`); if multiple hits, ask the user which to use.\n- Fetch the page (`Notion:fetch`) and scan for requirements, acceptance criteria, constraints, and priorities. See `reference\u002Fspec-parsing.md` for extraction patterns.\n- Capture gaps\u002Fassumptions in a clarifications block before proceeding.\n\n### 2) Choose plan depth\n- Simple change → use `reference\u002Fquick-implementation-plan.md`.\n- Multi-phase feature\u002Fmigration → use `reference\u002Fstandard-implementation-plan.md`.\n- Create the plan via `Notion:notion-create-pages`, include: overview, linked spec, requirements summary, phases, dependencies\u002Frisks, and success criteria. Link back to the spec.\n\n### 3) Create tasks\n- Find the task database (`Notion:search` → `Notion:fetch` to confirm the data source and required properties). Patterns in `reference\u002Ftask-creation.md`.\n- Size tasks to 1–2 days. Use `reference\u002Ftask-creation-template.md` for content (context, objective, acceptance criteria, dependencies, resources).\n- Set properties: title\u002Faction verb, status, priority, relations to spec + plan, due date\u002Fstory points\u002Fassignee if provided.\n- Create pages with `Notion:notion-create-pages` using the database’s `data_source_id`.\n\n### 4) Link artifacts\n- Plan links to spec; tasks link to both plan and spec.\n- Optionally update the spec with a short “Implementation” section pointing to the plan and tasks using `Notion:notion-update-page`.\n\n### 5) Track progress\n- Use the cadence in `reference\u002Fprogress-tracking.md`.\n- Post updates with `reference\u002Fprogress-update-template.md`; close phases with `reference\u002Fmilestone-summary-template.md`.\n- Keep checklists and status fields in plan\u002Ftasks in sync; note blockers and decisions.\n\n## References and examples\n- `reference\u002F` — parsing patterns, plan\u002Ftask templates, progress cadence (e.g., `spec-parsing.md`, `standard-implementation-plan.md`, `task-creation.md`, `progress-tracking.md`).\n- `examples\u002F` — end-to-end walkthroughs (e.g., `ui-component.md`, `api-feature.md`, `database-migration.md`).\n","# Spec to Implementation\n\nConvert a Notion spec into linked implementation plans, tasks, and ongoing status updates.\n\n## Quick start\n1) Locate the spec with `Notion:search`, then fetch it with `Notion:fetch`.\n2) Parse requirements and ambiguities using `reference\u002Fspec-parsing.md`.\n3) Create a plan page with `Notion:notion-create-pages` (pick a template: quick vs. full).\n4) Find the task database, confirm schema, then create tasks with `Notion:notion-create-pages`.\n5) Link spec ↔ plan ↔ tasks; keep status current with `Notion:notion-update-page`.\n\n## Tool-call guardrails\n- Notion tool availability can vary by workspace. If a Notion MCP call returns `Tool \u003Cname> not found`, treat that tool as unavailable for the rest of the current task. Do not retry it with different arguments or call it again later; use `Notion:search` and `Notion:fetch` where sufficient.\n- Use one literal search query per `Notion:search` call and include `filters: {}` when no narrower filter is needed. Run separate searches for alternate phrasings instead of putting `or` in a single query string.\n- Only send Notion page, database, or data-source URLs\u002FIDs to `Notion:fetch`; external connected-source search results are not fetch targets.\n- Create plans and task pages with explicit `parent` and `pages` fields. For task databases, fetch first and use the returned `collection:\u002F\u002F...` data source ID.\n- To append an implementation section to a spec, fetch the current section text first, then use `Notion:notion-update-page` with `command: \"update_content\"`, `properties: {}`, and exact `old_str` \u002F `new_str` content. For property-only edits, use `command: \"update_properties\"` with `content_updates: []`; the current deployed schema expects both top-level fields even when one is unused.\n\n## Workflow\n\n### 0) If Notion tools are unavailable, pause and ask the user to connect the Notion app:\n1. Enable the bundled Notion app for this plugin or session.\n2. Complete the Notion auth flow if Codex prompts for it.\n3. Restart Codex or the current session if the tools still do not appear.\n\nAfter the app is connected, finish your answer and tell the user to retry so they can continue with Step 1.\n\n### 1) Locate and read the spec\n- Search first (`Notion:search`); if multiple hits, ask the user which to use.\n- Fetch the page (`Notion:fetch`) and scan for requirements, acceptance criteria, constraints, and priorities. See `reference\u002Fspec-parsing.md` for extraction patterns.\n- Capture gaps\u002Fassumptions in a clarifications block before proceeding.\n\n### 2) Choose plan depth\n- Simple change → use `reference\u002Fquick-implementation-plan.md`.\n- Multi-phase feature\u002Fmigration → use `reference\u002Fstandard-implementation-plan.md`.\n- Create the plan via `Notion:notion-create-pages`, include: overview, linked spec, requirements summary, phases, dependencies\u002Frisks, and success criteria. Link back to the spec.\n\n### 3) Create tasks\n- Find the task database (`Notion:search` → `Notion:fetch` to confirm the data source and required properties). Patterns in `reference\u002Ftask-creation.md`.\n- Size tasks to 1–2 days. Use `reference\u002Ftask-creation-template.md` for content (context, objective, acceptance criteria, dependencies, resources).\n- Set properties: title\u002Faction verb, status, priority, relations to spec + plan, due date\u002Fstory points\u002Fassignee if provided.\n- Create pages with `Notion:notion-create-pages` using the database’s `data_source_id`.\n\n### 4) Link artifacts\n- Plan links to spec; tasks link to both plan and spec.\n- Optionally update the spec with a short “Implementation” section pointing to the plan and tasks using `Notion:notion-update-page`.\n\n### 5) Track progress\n- Use the cadence in `reference\u002Fprogress-tracking.md`.\n- Post updates with `reference\u002Fprogress-update-template.md`; close phases with `reference\u002Fmilestone-summary-template.md`.\n- Keep checklists and status fields in plan\u002Ftasks in sync; note blockers and decisions.\n\n## References and examples\n- `reference\u002F` — parsing patterns, plan\u002Ftask templates, progress cadence (e.g., `spec-parsing.md`, `standard-implementation-plan.md`, `task-creation.md`, `progress-tracking.md`).\n- `examples\u002F` — end-to-end walkthroughs (e.g., `ui-component.md`, `api-feature.md`, `database-migration.md`).\n",{"name":5,"metadata":25,"description":7},{"short-description":26},"Turn Notion specs into implementation plans, tasks, and progress tracking","main","d9535210da9af28aa76bca80de80355197e1b6d6","skills\u002Fnotion-spec-to-implementation","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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add zfifteen\u002Fskills-catalog --skill notion-spec-to-implementation",{"tool":40,"command":41},"bunx","bunx skills add zfifteen\u002Fskills-catalog --skill notion-spec-to-implementation",{"tool":43,"command":44},"pnpm","pnpm dlx skills add zfifteen\u002Fskills-catalog --skill notion-spec-to-implementation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fnotion-spec-to-implementation\u002FSKILL.md",true,[48,54,60,64,68,72,76,80,84,88,93,97,101,105,109,113,117,121],{"path":49,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":52,"sourceHtmlUrl":53},"agents\u002Fopenai.yaml","REFERENCE","参考文档",339,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fnotion-spec-to-implementation\u002Fagents\u002Fopenai.yaml",{"path":55,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":58,"sourceHtmlUrl":59},"assets\u002Fnotion-small.svg","ASSET","资产文件",15777,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fnotion-spec-to-implementation\u002Fassets\u002Fnotion-small.svg",{"path":61,"resourceType":56,"resourceTypeDesc":57,"sizeBytes":62,"sourceHtmlUrl":63},"assets\u002Fnotion.png",8526,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fnotion-spec-to-implementation\u002Fassets\u002Fnotion.png",{"path":65,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":66,"sourceHtmlUrl":67},"evaluations\u002Fbasic-spec-implementation.json",2358,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fnotion-spec-to-implementation\u002Fevaluations\u002Fbasic-spec-implementation.json",{"path":69,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":70,"sourceHtmlUrl":71},"evaluations\u002FREADME.md",4422,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fnotion-spec-to-implementation\u002Fevaluations\u002FREADME.md",{"path":73,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":74,"sourceHtmlUrl":75},"evaluations\u002Fspec-to-tasks.json",2504,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fnotion-spec-to-implementation\u002Fevaluations\u002Fspec-to-tasks.json",{"path":77,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":78,"sourceHtmlUrl":79},"examples\u002Fapi-feature.md",14073,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fnotion-spec-to-implementation\u002Fexamples\u002Fapi-feature.md",{"path":81,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":82,"sourceHtmlUrl":83},"examples\u002Fdatabase-migration.md",2639,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fnotion-spec-to-implementation\u002Fexamples\u002Fdatabase-migration.md",{"path":85,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":86,"sourceHtmlUrl":87},"examples\u002Fui-component.md",2150,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fnotion-spec-to-implementation\u002Fexamples\u002Fui-component.md",{"path":89,"resourceType":90,"resourceTypeDesc":91,"sizeBytes":92,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",1057,{"path":94,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":95,"sourceHtmlUrl":96},"reference\u002Fmilestone-summary-template.md",455,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fnotion-spec-to-implementation\u002Freference\u002Fmilestone-summary-template.md",{"path":98,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":99,"sourceHtmlUrl":100},"reference\u002Fprogress-tracking.md",9018,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fnotion-spec-to-implementation\u002Freference\u002Fprogress-tracking.md",{"path":102,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":103,"sourceHtmlUrl":104},"reference\u002Fprogress-update-template.md",419,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fnotion-spec-to-implementation\u002Freference\u002Fprogress-update-template.md",{"path":106,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":107,"sourceHtmlUrl":108},"reference\u002Fquick-implementation-plan.md",479,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fnotion-spec-to-implementation\u002Freference\u002Fquick-implementation-plan.md",{"path":110,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":111,"sourceHtmlUrl":112},"reference\u002Fspec-parsing.md",7057,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fnotion-spec-to-implementation\u002Freference\u002Fspec-parsing.md",{"path":114,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":115,"sourceHtmlUrl":116},"reference\u002Fstandard-implementation-plan.md",3285,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fnotion-spec-to-implementation\u002Freference\u002Fstandard-implementation-plan.md",{"path":118,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":119,"sourceHtmlUrl":120},"reference\u002Ftask-creation-template.md",596,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fnotion-spec-to-implementation\u002Freference\u002Ftask-creation-template.md",{"path":122,"resourceType":50,"resourceTypeDesc":51,"sizeBytes":123,"sourceHtmlUrl":124},"reference\u002Ftask-creation.md",8025,"https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fnotion-spec-to-implementation\u002Freference\u002Ftask-creation.md",[126,133,140,147,156,163],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":20},"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":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":20},"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":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":146,"publishedAt":20},"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":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":151,"licenseFileUrl":152,"sourceHtmlUrl":153,"categories":154,"keywords":155,"publishedAt":20},"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":157,"name":158,"nameZh":6,"description":159,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":160,"categories":161,"keywords":162,"publishedAt":20},"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":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":20},"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",[],[]]