[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M79FAY400THHJDBD8NJR9X19":3,"skill-same:01M79FAY400THHJDBD8NJR9X19":56},{"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":35,"commitSha":36,"skillDirectory":37,"forksCount":14,"repositoryHtmlUrl":38,"repositoryHomepageUrl":6,"ownerHtmlUrl":39,"ownerBlogUrl":6,"ownerDescription":40,"updatedAt":41,"install":42,"resources":55},"01M79FAY400THHJDBD8NJR9X19","prompts-presentation",null,"Apply the \"Presentation\" prompt-library workflow: transform the provided material (notes, findings, research results, code, arguments, data, or conversation context) into a clean, presentation-ready structure suitable for slides, talks, or executive briefings. Preserve the core narrative and key evidence while adding logical flow, visual cues, and audience- appropriate abstraction. Use when the user says \"turn this into a presentation\", \"make slides from this\", \"presentation structure for these findings\", \"use the presentation prompt\", or runs \u002Fprompts-presentation.","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\u002Fprompts-presentation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: prompts-presentation\ndescription: >\n  Apply the \"Presentation\" prompt-library workflow: transform the provided material (notes,\n  findings, research results, code, arguments, data, or conversation context) into a clean,\n  presentation-ready structure suitable for slides, talks, or executive briefings. Preserve\n  the core narrative and key evidence while adding logical flow, visual cues, and audience-\n  appropriate abstraction.\n  Use when the user says \"turn this into a presentation\", \"make slides from this\", \"presentation\n  structure for these findings\", \"use the presentation prompt\", or runs \u002Fprompts-presentation.\nwhen-to-use: \"Converting raw research, analysis, or meeting output into slide-deck or talk-ready form. Triggers: 'presentation', 'slides', 'deck', 'talk outline', 'executive summary for slides'. Focuses on structure and narrative flow rather than full prose.\"\nargument-hint: \"\u003Cmaterial, findings, notes, or context to structure as a presentation>\"\nallowed-tools: [\"read_file\", \"grep\", \"list_dir\"]\nmetadata:\n  short-description: \"Convert material into clean, presentation-ready slide structure and narrative\"\n  canonical-codex-skill: \"\u002FUsers\u002Fvelocityworks\u002F.codex\u002Fskills\u002Fprompts-presentation\u002FSKILL.md\"\n  version: \"1.0.0\"\n---\n\n# Presentation — Grok Port\n\nTurn the current material into a well-structured, audience-ready presentation outline that can be directly turned into slides or a talk.\n\n## Purpose\n\nThe original prompt is deliberately minimal (\"Turn this into a presentation\") because the heavy lifting is in the disciplined extraction of narrative, evidence, and visual logic from messy source material. This Grok port keeps the contract simple while giving the model tools to ground the structure in the actual artifacts.\n\n## Invocation\n\n```\n\u002Fprompts-presentation \u003Cmaterial, notes, findings, paper, meeting transcript, or research artifact>\n```\n\nThe full user-provided content plus any referenced files become the source.\n\n## Core Task\n\nTransform the input into a presentation:\n\n- Identify the through-line \u002F core story the audience should take away.\n- Organize into a logical sequence of sections or slides.\n- Surface the strongest evidence, data points, or arguments for each section.\n- Add appropriate visual or rhetorical cues (e.g., \"show the key plot here\", \"quote this one sentence\", \"use a simple diagram of X\").\n- Balance depth: enough technical substance for experts, clear framing for a broader audience.\n- Keep the total scope reasonable for a 10–30 minute talk (or the length implied by the material).\n\n## Recommended Output Structure (Adapt as Needed)\n\n```\n# Presentation Title\n(One compelling line)\n\n## 1. Opening \u002F Hook\n- The single most important question or claim\n- Why it matters now (context or stakes)\n\n## 2. Context & Setup (2–4 slides)\n- Key background the audience must have\n- Current state of the art or prior results (brief)\n- The specific gap or problem this work addresses\n\n## 3. Core Contribution \u002F Method (3–6 slides)\n- The central idea, algorithm, structure, or finding\n- How it works (high-level first, then one level of detail)\n- Key evidence or results (tables, figures, numbers, structural proofs)\n\n## 4. Why This Matters \u002F Implications (2–3 slides)\n- What changes if this is correct or adopted\n- Surprising consequences or new capabilities\n- Relation to bigger open questions (especially PGS invariants or laws when relevant)\n\n## 5. Limitations & Open Questions (1–2 slides)\n- Honest boundaries of the current result\n- What remains unproven or untested\n- Natural next experiments or extensions\n\n## 6. Call to Action \u002F Closing\n- The one thing the audience should remember or do\n- Any concrete ask (review this PR, replicate this experiment, etc.)\n\n## Appendix (optional)\n- Detailed data, proofs, code snippets, or references that support the main narrative but would break flow in the live talk\n```\n\nFor each slide\u002Fsection, include:\n- Suggested title\n- 1–3 bullet points of content (keep sparse — slides are not prose)\n- Speaker notes or \"show X here\" cues where helpful\n- Any recommended visuals (diagram, plot, table, quote, code fragment)\n\n## Grok Adaptations\n\n- When source material lives in files: use `read_file` and `grep` to extract the actual strongest evidence rather than summarizing from memory.\n- For research talks: explicitly surface PGS objects, invariants, and rule applications in the \"Core Contribution\" section when the work is in this domain (per AGENTS.md).\n- Preserve the voice and intellectual honesty of the original material; do not add hype.\n\n## Success Criteria\n\n- A listener who only attends the talk would come away with the correct core message and the key supporting evidence.\n- The structure has clear narrative momentum (problem → approach → evidence → implication).\n- Slide content is sparse and visual-friendly (not dense paragraphs).\n- The outline is immediately usable by the user (or a slide tool) to build the actual deck.\n- No important claim in the presentation is weaker in the source material than presented.\n\n## Guardrails\n\n- This skill produces **structure and narrative**, not finished slide files (unless the environment has additional slide-generation tools and the user explicitly asks).\n- Do not invent visuals or data points.\n- If the source material is weak or incomplete for a good presentation, say so and suggest what is missing rather than papering over gaps with elegant structure.\n\nThis minimal but powerful prompt-library skill is now a reliable \"narrative extraction + visual logic\" tool for Grok.\n","# Presentation — Grok Port\n\nTurn the current material into a well-structured, audience-ready presentation outline that can be directly turned into slides or a talk.\n\n## Purpose\n\nThe original prompt is deliberately minimal (\"Turn this into a presentation\") because the heavy lifting is in the disciplined extraction of narrative, evidence, and visual logic from messy source material. This Grok port keeps the contract simple while giving the model tools to ground the structure in the actual artifacts.\n\n## Invocation\n\n```\n\u002Fprompts-presentation \u003Cmaterial, notes, findings, paper, meeting transcript, or research artifact>\n```\n\nThe full user-provided content plus any referenced files become the source.\n\n## Core Task\n\nTransform the input into a presentation:\n\n- Identify the through-line \u002F core story the audience should take away.\n- Organize into a logical sequence of sections or slides.\n- Surface the strongest evidence, data points, or arguments for each section.\n- Add appropriate visual or rhetorical cues (e.g., \"show the key plot here\", \"quote this one sentence\", \"use a simple diagram of X\").\n- Balance depth: enough technical substance for experts, clear framing for a broader audience.\n- Keep the total scope reasonable for a 10–30 minute talk (or the length implied by the material).\n\n## Recommended Output Structure (Adapt as Needed)\n\n```\n# Presentation Title\n(One compelling line)\n\n## 1. Opening \u002F Hook\n- The single most important question or claim\n- Why it matters now (context or stakes)\n\n## 2. Context & Setup (2–4 slides)\n- Key background the audience must have\n- Current state of the art or prior results (brief)\n- The specific gap or problem this work addresses\n\n## 3. Core Contribution \u002F Method (3–6 slides)\n- The central idea, algorithm, structure, or finding\n- How it works (high-level first, then one level of detail)\n- Key evidence or results (tables, figures, numbers, structural proofs)\n\n## 4. Why This Matters \u002F Implications (2–3 slides)\n- What changes if this is correct or adopted\n- Surprising consequences or new capabilities\n- Relation to bigger open questions (especially PGS invariants or laws when relevant)\n\n## 5. Limitations & Open Questions (1–2 slides)\n- Honest boundaries of the current result\n- What remains unproven or untested\n- Natural next experiments or extensions\n\n## 6. Call to Action \u002F Closing\n- The one thing the audience should remember or do\n- Any concrete ask (review this PR, replicate this experiment, etc.)\n\n## Appendix (optional)\n- Detailed data, proofs, code snippets, or references that support the main narrative but would break flow in the live talk\n```\n\nFor each slide\u002Fsection, include:\n- Suggested title\n- 1–3 bullet points of content (keep sparse — slides are not prose)\n- Speaker notes or \"show X here\" cues where helpful\n- Any recommended visuals (diagram, plot, table, quote, code fragment)\n\n## Grok Adaptations\n\n- When source material lives in files: use `read_file` and `grep` to extract the actual strongest evidence rather than summarizing from memory.\n- For research talks: explicitly surface PGS objects, invariants, and rule applications in the \"Core Contribution\" section when the work is in this domain (per AGENTS.md).\n- Preserve the voice and intellectual honesty of the original material; do not add hype.\n\n## Success Criteria\n\n- A listener who only attends the talk would come away with the correct core message and the key supporting evidence.\n- The structure has clear narrative momentum (problem → approach → evidence → implication).\n- Slide content is sparse and visual-friendly (not dense paragraphs).\n- The outline is immediately usable by the user (or a slide tool) to build the actual deck.\n- No important claim in the presentation is weaker in the source material than presented.\n\n## Guardrails\n\n- This skill produces **structure and narrative**, not finished slide files (unless the environment has additional slide-generation tools and the user explicitly asks).\n- Do not invent visuals or data points.\n- If the source material is weak or incomplete for a good presentation, say so and suggest what is missing rather than papering over gaps with elegant structure.\n\nThis minimal but powerful prompt-library skill is now a reliable \"narrative extraction + visual logic\" tool for Grok.\n",{"name":5,"metadata":24,"description":28,"when-to-use":29,"allowed-tools":30,"argument-hint":34},{"version":25,"short-description":26,"canonical-codex-skill":27},"1.0.0","Convert material into clean, presentation-ready slide structure and narrative","\u002FUsers\u002Fvelocityworks\u002F.codex\u002Fskills\u002Fprompts-presentation\u002FSKILL.md","Apply the \"Presentation\" prompt-library workflow: transform the provided material (notes, findings, research results, code, arguments, data, or conversation context) into a clean, presentation-ready structure suitable for slides, talks, or executive briefings. Preserve the core narrative and key evidence while adding logical flow, visual cues, and audience- appropriate abstraction. Use when the user says \"turn this into a presentation\", \"make slides from this\", \"presentation structure for these findings\", \"use the presentation prompt\", or runs \u002Fprompts-presentation.\n","Converting raw research, analysis, or meeting output into slide-deck or talk-ready form. Triggers: 'presentation', 'slides', 'deck', 'talk outline', 'executive summary for slides'. Focuses on structure and narrative flow rather than full prose.",[31,32,33],"read_file","grep","list_dir","\u003Cmaterial, findings, notes, or context to structure as a presentation>","main","d9535210da9af28aa76bca80de80355197e1b6d6","skills\u002Fprompts-presentation","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":43,"prompt":53,"zipAvailable":54},[44,47,50],{"tool":45,"command":46},"npx","npx skills add zfifteen\u002Fskills-catalog --skill prompts-presentation",{"tool":48,"command":49},"bunx","bunx skills add zfifteen\u002Fskills-catalog --skill prompts-presentation",{"tool":51,"command":52},"pnpm","pnpm dlx skills add zfifteen\u002Fskills-catalog --skill prompts-presentation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fzfifteen\u002Fskills-catalog\u002Fblob\u002Fmain\u002Fskills\u002Fprompts-presentation\u002FSKILL.md",true,[],[57,64,71,78,87,94],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"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":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"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":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":82,"licenseFileUrl":83,"sourceHtmlUrl":84,"categories":85,"keywords":86,"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":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"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":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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",[],[]]