[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ETPZ0VR1MPJFRG7FQFZ9KD":3,"skill-same:01M7ETPZ0VR1MPJFRG7FQFZ9KD":53},{"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":33,"commitSha":34,"skillDirectory":35,"forksCount":13,"repositoryHtmlUrl":36,"repositoryHomepageUrl":6,"ownerHtmlUrl":37,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":38,"install":39,"resources":52},"01M7ETPZ0VR1MPJFRG7FQFZ9KD","omh-cancel",null,"[omh] Aborting an active workflow: ending active workflow state cleanly. Use when the user says: cancel, stop the workflow, abort the run, cancel the loop.","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-cancel\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"omh-cancel\"\ndescription: \"[omh] Aborting an active workflow: ending active workflow state cleanly. Use when the user says: cancel, stop the workflow, abort the run, cancel the loop.\"\nlicense: MIT\ncompatibility: \"Requires the omh CLI on PATH (pip install oh-my-hermes).\"\nmetadata:\n  hermes:\n    tags: [workflow, oh-my-hermes, operator]\n    category: operator\n    phase: state-cleanup\n    role: tracker\n    quality_tier: evidence-gated\n---\n\n# Cancel\n\nThis is an OMH `cancel` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).\n\n## Why This Exists\n\n`cancel` exists so a request to stop ends the right thing: OMH clears the state this session owns, and work the host owns stops through the person's own host command, so nothing reads as stopped before a record or the host's own reply says it is.\n\n## Do Not Use When\n\n- The workflow finished and its outcome should be kept; record it with omh state finish instead of clearing it.\n- The user wants to see what is still running rather than stop it; use `omh-running-work-board`.\n- The user means cancelling something in their own product or accounts, such as an order, a subscription, or a meeting, rather than OMH or host work.\n\n## Examples\n\nGood example:\n\n- Prompt: cancel the loop and stop everything that is running\n- Expected behavior: Clear this session's OMH state with its own commands, name the host's stop commands (on Hermes, `\u002Floop stop` and `\u002Fstop`) for the person to run, and report each OMH clear from its result and each host stop as requested.\n- Why: The request spans OMH state and host-owned work, which stop through different owners.\n\nBad example:\n\n- Prompt: cancel: kill the background processes yourself and say everything stopped\n- Expected behavior: Leave the processes to the person's own stop command (on Hermes, `\u002Fstop`), and report them stopped only after the host's own reply.\n- Why: OMH never ends a host process, and a requested stop is not an observed one.\n\n## Completion Checklist\n\n- Every stopped item is named with its owner: OMH state or host work.\n- Each OMH clear cites its command result; each host stop stays requested until the host's reply is seen.\n- Nothing outside this session's own state was cleared, and no host process was ended by OMH.\n\n## Recovery Notes\n\n- If a session-bound clear is refused for a missing --session-ref, report the refusal rather than clearing without it.\n- If the host's reply to a stop never appears, keep the stop requested and ask the person what it said.\n\n\n\n## When to Use\n\nUse to cleanly end active adapted workflow state.\n\n    Strong routing signals: `cancel`, `$cancel`, `stop the workflow`, `abort the run`, `cancel the loop`\n\n## Catalog Metadata\n\nCategory: `operator`\nPhase: `state-cleanup`\nQuality tier: `evidence-gated`\nReasoning demand: `light`\n\nQuality bar:\n\n- Name each thing to stop and its owner: OMH state (workflow lifecycle, plan checklist, OMH goal) or host work (the running turn, background processes, delegations, a Hermes \u002Floop or \u002Fgoal).\n- Clear OMH state with its own commands: `omh state clear --workflow \u003Cname>` (`--session-ref` when session-bound), on Hermes `omh_todo action=clear`, and `omh goal cancel --goal \u003Cid>`; an OMH loop stops through its linked goal, and one without a goal has no cancel record.\n- Hand host work to the person's own stop command; on Hermes `\u002Fstop` (in a CLI or TUI session it ends every background process, and the classic CLI its background delegations too; on a messaging platform it interrupts the running turn rather than ending every background process), `\u002Floop stop`, `\u002Fgoal pause` or `\u002Fgoal clear`, `\u002Fheartbeat clear`, `\u002Fpause` (all new work on a gateway).\n- Report an OMH clear as done only from its command result, and a host stop as requested until the host's own reply to it is seen.\n\nRequired inputs:\n\n- active workflow state\n- cancellation intent\n\nExpected outputs:\n\n- cleared state\n- safe stop summary\n\nArtifact expectations:\n\n- state clear record when state exists\n\nSafety rules:\n\n- Never end, kill, or signal a host process, background job, or delegation from this workflow, through the terminal or any other tool (on Hermes, `process_manage` included); that stop is the person's own host command.\n- Clear only what this session owns; another session's plan, workflow state, or goal stays as it is.\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","# Cancel\n\nThis is an OMH `cancel` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).\n\n## Why This Exists\n\n`cancel` exists so a request to stop ends the right thing: OMH clears the state this session owns, and work the host owns stops through the person's own host command, so nothing reads as stopped before a record or the host's own reply says it is.\n\n## Do Not Use When\n\n- The workflow finished and its outcome should be kept; record it with omh state finish instead of clearing it.\n- The user wants to see what is still running rather than stop it; use `omh-running-work-board`.\n- The user means cancelling something in their own product or accounts, such as an order, a subscription, or a meeting, rather than OMH or host work.\n\n## Examples\n\nGood example:\n\n- Prompt: cancel the loop and stop everything that is running\n- Expected behavior: Clear this session's OMH state with its own commands, name the host's stop commands (on Hermes, `\u002Floop stop` and `\u002Fstop`) for the person to run, and report each OMH clear from its result and each host stop as requested.\n- Why: The request spans OMH state and host-owned work, which stop through different owners.\n\nBad example:\n\n- Prompt: cancel: kill the background processes yourself and say everything stopped\n- Expected behavior: Leave the processes to the person's own stop command (on Hermes, `\u002Fstop`), and report them stopped only after the host's own reply.\n- Why: OMH never ends a host process, and a requested stop is not an observed one.\n\n## Completion Checklist\n\n- Every stopped item is named with its owner: OMH state or host work.\n- Each OMH clear cites its command result; each host stop stays requested until the host's reply is seen.\n- Nothing outside this session's own state was cleared, and no host process was ended by OMH.\n\n## Recovery Notes\n\n- If a session-bound clear is refused for a missing --session-ref, report the refusal rather than clearing without it.\n- If the host's reply to a stop never appears, keep the stop requested and ask the person what it said.\n\n\n\n## When to Use\n\nUse to cleanly end active adapted workflow state.\n\n    Strong routing signals: `cancel`, `$cancel`, `stop the workflow`, `abort the run`, `cancel the loop`\n\n## Catalog Metadata\n\nCategory: `operator`\nPhase: `state-cleanup`\nQuality tier: `evidence-gated`\nReasoning demand: `light`\n\nQuality bar:\n\n- Name each thing to stop and its owner: OMH state (workflow lifecycle, plan checklist, OMH goal) or host work (the running turn, background processes, delegations, a Hermes \u002Floop or \u002Fgoal).\n- Clear OMH state with its own commands: `omh state clear --workflow \u003Cname>` (`--session-ref` when session-bound), on Hermes `omh_todo action=clear`, and `omh goal cancel --goal \u003Cid>`; an OMH loop stops through its linked goal, and one without a goal has no cancel record.\n- Hand host work to the person's own stop command; on Hermes `\u002Fstop` (in a CLI or TUI session it ends every background process, and the classic CLI its background delegations too; on a messaging platform it interrupts the running turn rather than ending every background process), `\u002Floop stop`, `\u002Fgoal pause` or `\u002Fgoal clear`, `\u002Fheartbeat clear`, `\u002Fpause` (all new work on a gateway).\n- Report an OMH clear as done only from its command result, and a host stop as requested until the host's own reply to it is seen.\n\nRequired inputs:\n\n- active workflow state\n- cancellation intent\n\nExpected outputs:\n\n- cleared state\n- safe stop summary\n\nArtifact expectations:\n\n- state clear record when state exists\n\nSafety rules:\n\n- Never end, kill, or signal a host process, background job, or delegation from this workflow, through the terminal or any other tool (on Hermes, `process_manage` included); that stop is the person's own host command.\n- Clear only what this session owns; another session's plan, workflow state, or goal stays as it is.\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,"compatibility":32},{"hermes":24},{"role":25,"tags":26,"phase":30,"category":29,"quality_tier":31},"tracker",[27,28,29],"workflow","oh-my-hermes","operator","state-cleanup","evidence-gated","Requires the omh CLI on PATH (pip install oh-my-hermes).","main","4c174e06a831864e98c30f630a7aa6c04738b094","skills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-cancel","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":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill omh-cancel",{"tool":45,"command":46},"bunx","bunx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill omh-cancel",{"tool":48,"command":49},"pnpm","pnpm dlx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill omh-cancel","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-cancel\u002FSKILL.md",true,[],[54,62,70,78,85,92],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":58,"sourceHtmlUrl":59,"categories":60,"keywords":61,"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":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":66,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":74,"sourceHtmlUrl":75,"categories":76,"keywords":77,"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":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"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":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"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":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"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",[],[]]