[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EV0TG53C932VTPD594AVK4":3,"skill-same:01M7EV0TG53C932VTPD594AVK4":52},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"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":32,"commitSha":33,"skillDirectory":34,"forksCount":13,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M7EV0TG53C932VTPD594AVK4","omh-meeting-brief",null,"[omh] Upcoming work meeting that lacks an agenda: agenda, prompts, decisions, and record template. Use when the user says: meeting-brief, meeting brief, meeting agenda, agenda, discussion prompts, decisions needed, record template, meeting topics.","mhyahya854\u002FAI-Second-Brain_Universal-Rules","mhyahya854","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F194078115?v=4","01M7EGSP2M9T858SDHJMXQ257Y","01M7EGSP3N6HN6879SVDPMD4DZ",0,"MIT","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-meeting-brief\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"omh-meeting-brief\"\ndescription: \"[omh] Upcoming work meeting that lacks an agenda: agenda, prompts, decisions, and record template. Use when the user says: meeting-brief, meeting brief, meeting agenda, agenda, discussion prompts, decisions needed, record template, meeting topics.\"\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [workflow, oh-my-hermes, meeting]\n    category: meeting\n    phase: preparation\n    role: operator\n    quality_tier: facilitation-gated\n---\n\n# Meeting Brief\n\nThis is an OMH `meeting-brief` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).\n\n## Why This Exists\n\n`meeting-brief` exists to turn scattered context into a focused agenda, discussion prompts, decision points, and a record template without pretending the meeting already happened.\n\n## Do Not Use When\n\n- The user needs observed meeting minutes, decisions, or action items but has not provided notes.\n- The request is strategy synthesis without a meeting audience, agenda, or decision ceremony.\n- The follow-up is implementation work that already has accepted requirements and should become a plan or handoff.\n\n## Examples\n\nGood example:\n\n- Prompt: Prepare a meeting agenda for a leadership sync on setup UX, plugin bridge defaults, and release risk.\n- Expected behavior: Prepare agenda topics, prompts, decisions needed, and a record template with unknowns marked.\n- Why: The request is preparation for a meeting and should separate prep from observed outcomes.\n\nBad example:\n\n- Prompt: meeting-brief summarize what the team decided yesterday.\n- Expected behavior: Ask for meeting notes or route to an ops\u002Fstatus summary with explicit evidence gaps.\n- Why: A prepared agenda cannot be treated as observed minutes or decisions.\n\n## Completion Checklist\n\n- The agenda, participants or audience, decisions needed, and record template are named.\n- Meeting prep, observed minutes, accepted decisions, and action ownership are separate states.\n- Missing context that would change the meeting structure is surfaced.\n\n## Recovery Notes\n\n- If participants, purpose, or decision owner are missing, ask for the one field that changes the agenda.\n- If minutes or decisions were not observed, keep the output as prep rather than record.\n\n\n\n## When to Use\n\nUse when Hermes should prepare a meeting agenda, discussion prompts, decision points, and a record template.\n\n    Strong routing signals: `meeting-brief`, `meeting brief`, `meeting agenda`, `agenda`, `discussion prompts`, `decisions needed`, `record template`, `meeting topics`, `회의 주제`, `회의 아젠다`, `아젠다`, `회의 준비`, `논의 질문`, `결정할 것`, `기록 템플릿`\n\n## Catalog Metadata\n\nCategory: `meeting`\nPhase: `preparation`\nQuality tier: `facilitation-gated`\nReasoning demand: `light`\n\nQuality bar:\n\n- Turn context into agenda topics, prompts, decisions needed, and a record template.\n- Keep prep distinct from actual meeting minutes or accepted decisions.\n- Identify missing context that would change the meeting structure.\n- Give the record template's action-item rows outcome, owner, due date, dependency, acceptance condition, and source columns, each marked unknown until the meeting record fills it.\n\nRequired inputs:\n\n- meeting goal\n- audience\n- known context\n- decision topics\n\nExpected outputs:\n\n- agenda\n- discussion prompts\n- decisions needed\n- action-item template\n\nArtifact expectations:\n\n- meeting brief or record template when the wrapper captures it\n\nSafety rules:\n\n- Do not claim the meeting happened from a prepared agenda.\n- Separate proposed action items from observed decisions.\n- Use a later status or decision record for actual meeting outcomes.\n\n## Runtime Evidence\n\nUse the current host's own tools and subagent\u002Ftask mechanism when available;\notherwise run the same lanes sequentially or name the unavailable capability.\nA prepared plan, handoff, checklist, or skill installation is not execution,\nreview, CI, merge-readiness, or merge evidence. Record actual tool results, or\n`not_observed` \u002F `not_available`, in the record; never invent dispatch or host\naccounting.\nTreat supplied context as advisory, not proof of hidden memory reads or writes.\nState scope, constraints, verification, and the stop condition before work.\nReply in the user's own words and the host's own voice: the host's persona owns\nreply language, tone, speech level, and sentence endings, progress updates\nincluded (where it sets no language, use the one the user wrote in), and OMH\nshapes structure and content only; OMH's record terms\n(surface, lane, wrapper, handoff, evidence boundary, not_observed) stay in\nrecords and tool calls, never in the sentence the user reads unless they ask\nabout one; and when a real unresolved user decision or a useful briefing discussion\nremains, offer one specific, content-linked question. Completed work needs no question;\nomit unrelated non-action footers and generic offers to continue.\nSupporting paths are relative to this skill directory; sibling skill paths are\nrelative to its parent. Resolve them from the host-provided skill base directory\n(`{baseDir}` on hosts that provide it), never a hardcoded install location.\nA named workflow not installed here is unavailable, not permission to emulate\nits host-specific capabilities. Verify through the real surface before done.\n","# Meeting Brief\n\nThis is an OMH `meeting-brief` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).\n\n## Why This Exists\n\n`meeting-brief` exists to turn scattered context into a focused agenda, discussion prompts, decision points, and a record template without pretending the meeting already happened.\n\n## Do Not Use When\n\n- The user needs observed meeting minutes, decisions, or action items but has not provided notes.\n- The request is strategy synthesis without a meeting audience, agenda, or decision ceremony.\n- The follow-up is implementation work that already has accepted requirements and should become a plan or handoff.\n\n## Examples\n\nGood example:\n\n- Prompt: Prepare a meeting agenda for a leadership sync on setup UX, plugin bridge defaults, and release risk.\n- Expected behavior: Prepare agenda topics, prompts, decisions needed, and a record template with unknowns marked.\n- Why: The request is preparation for a meeting and should separate prep from observed outcomes.\n\nBad example:\n\n- Prompt: meeting-brief summarize what the team decided yesterday.\n- Expected behavior: Ask for meeting notes or route to an ops\u002Fstatus summary with explicit evidence gaps.\n- Why: A prepared agenda cannot be treated as observed minutes or decisions.\n\n## Completion Checklist\n\n- The agenda, participants or audience, decisions needed, and record template are named.\n- Meeting prep, observed minutes, accepted decisions, and action ownership are separate states.\n- Missing context that would change the meeting structure is surfaced.\n\n## Recovery Notes\n\n- If participants, purpose, or decision owner are missing, ask for the one field that changes the agenda.\n- If minutes or decisions were not observed, keep the output as prep rather than record.\n\n\n\n## When to Use\n\nUse when Hermes should prepare a meeting agenda, discussion prompts, decision points, and a record template.\n\n    Strong routing signals: `meeting-brief`, `meeting brief`, `meeting agenda`, `agenda`, `discussion prompts`, `decisions needed`, `record template`, `meeting topics`, `회의 주제`, `회의 아젠다`, `아젠다`, `회의 준비`, `논의 질문`, `결정할 것`, `기록 템플릿`\n\n## Catalog Metadata\n\nCategory: `meeting`\nPhase: `preparation`\nQuality tier: `facilitation-gated`\nReasoning demand: `light`\n\nQuality bar:\n\n- Turn context into agenda topics, prompts, decisions needed, and a record template.\n- Keep prep distinct from actual meeting minutes or accepted decisions.\n- Identify missing context that would change the meeting structure.\n- Give the record template's action-item rows outcome, owner, due date, dependency, acceptance condition, and source columns, each marked unknown until the meeting record fills it.\n\nRequired inputs:\n\n- meeting goal\n- audience\n- known context\n- decision topics\n\nExpected outputs:\n\n- agenda\n- discussion prompts\n- decisions needed\n- action-item template\n\nArtifact expectations:\n\n- meeting brief or record template when the wrapper captures it\n\nSafety rules:\n\n- Do not claim the meeting happened from a prepared agenda.\n- Separate proposed action items from observed decisions.\n- Use a later status or decision record for actual meeting outcomes.\n\n## Runtime Evidence\n\nUse the current host's own tools and subagent\u002Ftask mechanism when available;\notherwise run the same lanes sequentially or name the unavailable capability.\nA prepared plan, handoff, checklist, or skill installation is not execution,\nreview, CI, merge-readiness, or merge evidence. Record actual tool results, or\n`not_observed` \u002F `not_available`, in the record; never invent dispatch or host\naccounting.\nTreat supplied context as advisory, not proof of hidden memory reads or writes.\nState scope, constraints, verification, and the stop condition before work.\nReply in the user's own words and the host's own voice: the host's persona owns\nreply language, tone, speech level, and sentence endings, progress updates\nincluded (where it sets no language, use the one the user wrote in), and OMH\nshapes structure and content only; OMH's record terms\n(surface, lane, wrapper, handoff, evidence boundary, not_observed) stay in\nrecords and tool calls, never in the sentence the user reads unless they ask\nabout one; and when a real unresolved user decision or a useful briefing discussion\nremains, offer one specific, content-linked question. Completed work needs no question;\nomit unrelated non-action footers and generic offers to continue.\nSupporting paths are relative to this skill directory; sibling skill paths are\nrelative to its parent. Resolve them from the host-provided skill base directory\n(`{baseDir}` on hosts that provide it), never a hardcoded install location.\nA named workflow not installed here is unavailable, not permission to emulate\nits host-specific capabilities. Verify through the real surface before done.\n",{"name":5,"license":14,"metadata":23,"description":7},{"hermes":24},{"role":25,"tags":26,"phase":30,"category":29,"quality_tier":31},"operator",[27,28,29],"workflow","oh-my-hermes","meeting","preparation","facilitation-gated","main","4c174e06a831864e98c30f630a7aa6c04738b094","skills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-meeting-brief","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules","https:\u002F\u002Fgithub.com\u002Fmhyahya854","2026-11-06 02:03:37",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill omh-meeting-brief",{"tool":44,"command":45},"bunx","bunx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill omh-meeting-brief",{"tool":47,"command":48},"pnpm","pnpm dlx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill omh-meeting-brief","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-meeting-brief\u002FSKILL.md",true,[],[53,61,69,77,84,91],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7EX4T721AAH60R0239P8WBZ","frontend-slides","Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT\u002FPPTX to web, or create slides for a talk\u002Fpitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzarazhangrui\u002Ffrontend-slides\u002Ffrontend-slides\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzarazhangrui\u002Ffrontend-slides\u002Ffrontend-slides\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":65,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":18},"01M7EX495RSHTTCEJVX7C83FA3","design-dna","Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects, etc.). Use this skill when: (1) a user wants to see the full 3-dimension design structure\u002Fschema, (2) a user provides images, screenshots, or URLs of reference designs and wants them analyzed into a structured JSON profile covering all three dimensions, (3) a user has a Design DNA JSON and content and wants a design generated from it, or (4) any combination of these phases. Triggers on \"design DNA\", \"extract design style\", \"analyze design\", \"design tokens from reference\", \"generate design from JSON\", \"design system from screenshot\", \"design profile\", \"style guide JSON\", \"visual effects analysis\", \"design with effects\", \"3d design analysis\".","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fzanwei\u002Fdesign-dna\u002Fdesign-dna\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":73,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":18},"01M7EX45RF2XZKRC3KDJDTT1PH","wireframe","Generate JSON wireframe with HTML preview","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fyhassy\u002Fwireframe-skill\u002Fwireframe-skill\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fyhassy\u002Fwireframe-skill\u002Fwireframe-skill\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":18},"01M7EWZEM3MHD48AYSYFR2C9JP","social-publishing","Schedule and publish social media posts across 13 platforms (X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, Pinterest) via the SocialClaw API. Use when the user wants to publish, schedule, or manage social media content programmatically. Requires SOCIALCLAW_API_KEY.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwshobson\u002Fagents\u002Fsocial-publishing\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":18},"01M7EWKDEK9840C728VXT78EQ9","hermes-tweet","Install and operate Hermes Tweet, a Hermes Agent plugin for X\u002FTwitter research, timeline reading, tweet analysis, and approval-gated private or state-changing operations. Use this skill when installing Hermes Tweet, researching X\u002FTwitter accounts, monitoring launch signals, investigating mentions, auditing giveaways, or preparing gated X operations. Use proactively when a Hermes Agent workflow needs current X\u002FTwitter context. Requires XQUIK_API_KEY for read and action tools.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwshobson\u002Fagents\u002Fhermes-tweet\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":18},"01M7EWASXP3NZWW95CJPT2CRWN","refactoring-ui","Audit and fix visual hierarchy, spacing, color, and depth in web UIs. Use when the user mentions \"my UI looks off\" (or amateur\u002Funprofessional), \"fix the design\", \"Tailwind styling\", \"color palette\", \"visual hierarchy\", \"design system\", \"spacing scale\", or \"component styling\". Also trigger when building consistent design tokens, creating dark mode themes, improving data-visualization clarity, or polishing UI details before launch. Covers grayscale-first workflow, constrained design scales, shadows, and component styling. For typeface selection, see web-typography. For usability audits, see ux-heuristics.","https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Fwondelai\u002Fskills\u002Frefactoring-ui\u002FSKILL.md",[],[]]