[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ETVR8TF7NPJXS0NP1VC19W":3,"skill-same:01M7ETVR8TF7NPJXS0NP1VC19W":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},"01M7ETVR8TF7NPJXS0NP1VC19W","omh-files",null,"[omh] Folder cleanup, renames, or deletions: policy overlay for local file tasks - add path scoping and destructive-action gates after preferring native file tools for ordinary list, search, organize, copy, move, and rename actions. Use when the user says: workspace-file-operator, workspace file operator, file operator, file operation, file operations, filesystem task, filesystem operation, file system task.","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-files\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"omh-files\"\ndescription: \"[omh] Folder cleanup, renames, or deletions: policy overlay for local file tasks - add path scoping and destructive-action gates after preferring native file tools for ordinary list, search, organize, copy, move, and rename actions. Use when the user says: workspace-file-operator, workspace file operator, file operator, file operation, file operations, filesystem task, filesystem operation, file system task.\"\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [workflow, oh-my-hermes, filesystem]\n    category: filesystem\n    phase: file-task\n    role: guide\n    quality_tier: workflow-surface-gated\n---\n\n# Workspace File Operator\n\nThis is an OMH `workspace-file-operator` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).\n\n## Why This Exists\n\n`workspace-file-operator` exists because a delete, overwrite, or bulk move often has no undo point: it scopes the path, confirms each destructive step, records beforehand whether a checkpoint covers the target (Hermes takes none unless checkpoints are on), and reports only what file evidence shows.\n\n## Do Not Use When\n\n- An ordinary list, search, read, or one-file edit inside a known folder; use the native file tools directly.\n- The request converts files or produces a deck, PDF, or attachment; use `omh-materials-package` or `omh-deliverable-package`.\n\n## Examples\n\nGood example:\n\n- Prompt: workspace-file-operator list files in the reports folder and move old PDFs into archive after confirmation.\n- Expected behavior: Produce `prepare_workspace_file_operator_card` with required context, wrapper actions, and not-evidence boundaries.\n- Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution.\n\nBad example:\n\n- Prompt: workspace-file-operator delete every matching file without path scope or confirmation.\n- Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened.\n- Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence.\n\n## Completion Checklist\n\n- The path root, allowed file operations, excluded paths, destructive-operation policy, and stop condition are explicit.\n- Delete, overwrite, move, rename, permission change, archive mutation, upload, and download are gated, or marked missing and not run.\n- With nobody to answer the confirmation (a scheduled job, a one-shot run, a webhook run), an irreversible or externally visible action is not run: it is handed to a person's turn and its confirmation is recorded as missing.\n- Checkpoint availability is recorded before any destructive step, and the confirmation gate holds either way; without an observed checkpoint covering the target, a reversible copy or a move to trash comes first.\n- Directory listings, file contents, hashes, diffs, and operation results are reported only from observed file evidence.\n\n## Recovery Notes\n\n- If the target path or folder is missing, ask for the smallest path scope needed before preparing the operation.\n- If delete, overwrite, move, rename, chmod, or irreversible cleanup is requested, require an explicit confirmation gate.\n- If the request is file conversion, deck\u002FPDF export, or attachment delivery, route to materials-package or deliverable-package instead.\n- On Hermes, when a checkpoint covers the change, the user's `\u002Frollback` restores it and `\u002Fdiff session` shows what the session changed since the checkpoint baseline; cite either only after the user runs it.\n- On Hermes, a write that its own file guards refuse or hold for approval (a sensitive system path, a protected instruction file) is that gate's outcome to record, `blocked` or the user's answer, never a write to retry through another tool.\n\n\n\n## When to Use\n\nUse when Hermes should prepare or supervise local workspace\u002Ffile-system operations such as listing, searching, organizing, copying, moving, renaming, archiving, or deleting files without claiming the operation ran.\n\n    Strong routing signals: `workspace-file-operator`, `workspace file operator`, `file operator`, `file operation`, `file operations`, `filesystem task`, `filesystem operation`, `file system task`, `file system operation`, `list files`, `list folder`, `list directory`, `find local files`, `search files`, `organize files`, `organize folder`, `move file`, `move files`, `copy file`, `copy files`, `rename file`, `rename files`, `delete file`, `delete files`, `remove file`, `remove files`, `archive files`, `downloads folder`, `reports folder`, `folder cleanup`, `file cleanup`, `파일 작업`, `파일 조작`, `파일 정리`, `파일 검색`, `파일 찾아`, `파일 이동`, `파일 복사`, `파일 이름 변경`, `파일 삭제`, `폴더 정리`, `다운로드 폴더`, `디렉터리 목록`\n\n## Catalog Metadata\n\nCategory: `filesystem`\nPhase: `file-task`\nQuality tier: `workflow-surface-gated`\nReasoning demand: `standard`\n\nQuality bar:\n\n- Name the user-facing workflow objective, required context, next action, and stop condition.\n- Separate prepared guidance from observed platform, runtime, connector, file, memory, or delivery evidence.\n- Expose missing tools, credentials, targets, or observations as user-visible gaps.\n\nRequired inputs:\n\n- user request\n- target context\n- delivery or status expectation\n- known missing evidence\n\nExpected outputs:\n\n- workspace_file_task_card\u002Fv1\n- file_operation_scope\u002Fv1\n- file_observation_manifest\u002Fv1 when observed\n- file_confirmation_gate\u002Fv1 when destructive\n- next action\n- prepared-vs-observed boundary\n\nArtifact expectations:\n\n- workspace_file_task_card\u002Fv1 metadata-only wrapper card when prepared\n- file_operation_scope\u002Fv1 with path root, allowed operations, excluded paths, and stop condition\n- file_observation_manifest\u002Fv1 only when directory listings, file stats, hashes, diffs, or operation output are observed\n- session_file_activity\u002Fv1 (`omh quality-evidence file-activity --hermes-session \u003Cid> --json`) cited in that manifest for which workspace files a Hermes session's read_file, write_file, and patch calls named and the outcome Hermes recorded; never as file-content, hash, diff, test, review, CI, or merge evidence\n- file_confirmation_gate\u002Fv1 for delete, overwrite, move, rename, chmod, archive mutation, or irreversible cleanup, recording checkpoint availability before the step and keeping the confirmation either way: on Hermes, checkpoints are off unless the user turned them on (`checkpoints.enabled`, or a session started with the `--checkpoints` flag), and one covers only the directory Hermes snapshots for the step (for a terminal command, its working directory), minus its excludes (among them archives, media, logs, `.env` files, and dependency and build folders) and its limits (a file over the size cap, 10 MB by default, or a directory with more than 50,000 entries), so record `available` only when the user's `\u002Frollback` lists checkpoints for a directory that holds the target and the target is not excluded or over a limit, `not_available` otherwise, and `not_observed` until then\n\nSafety rules:\n\n- A workspace file operator card is not file read, file write, copy, move, rename, delete, archive, upload, download, permission change, or destructive filesystem evidence unless observed file-operation output records it.\n- Do not claim connector, gateway, runtime, file generation, memory mutation, or host automation evidence from prepared guidance.\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","# Workspace File Operator\n\nThis is an OMH `workspace-file-operator` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).\n\n## Why This Exists\n\n`workspace-file-operator` exists because a delete, overwrite, or bulk move often has no undo point: it scopes the path, confirms each destructive step, records beforehand whether a checkpoint covers the target (Hermes takes none unless checkpoints are on), and reports only what file evidence shows.\n\n## Do Not Use When\n\n- An ordinary list, search, read, or one-file edit inside a known folder; use the native file tools directly.\n- The request converts files or produces a deck, PDF, or attachment; use `omh-materials-package` or `omh-deliverable-package`.\n\n## Examples\n\nGood example:\n\n- Prompt: workspace-file-operator list files in the reports folder and move old PDFs into archive after confirmation.\n- Expected behavior: Produce `prepare_workspace_file_operator_card` with required context, wrapper actions, and not-evidence boundaries.\n- Why: The prompt names a real workflow surface that Hermes can orchestrate without hiding execution.\n\nBad example:\n\n- Prompt: workspace-file-operator delete every matching file without path scope or confirmation.\n- Expected behavior: Report the missing observed evidence or authority instead of claiming the external step happened.\n- Why: Prepared OMH guidance is not platform, runtime, connector, file, memory, or delivery evidence.\n\n## Completion Checklist\n\n- The path root, allowed file operations, excluded paths, destructive-operation policy, and stop condition are explicit.\n- Delete, overwrite, move, rename, permission change, archive mutation, upload, and download are gated, or marked missing and not run.\n- With nobody to answer the confirmation (a scheduled job, a one-shot run, a webhook run), an irreversible or externally visible action is not run: it is handed to a person's turn and its confirmation is recorded as missing.\n- Checkpoint availability is recorded before any destructive step, and the confirmation gate holds either way; without an observed checkpoint covering the target, a reversible copy or a move to trash comes first.\n- Directory listings, file contents, hashes, diffs, and operation results are reported only from observed file evidence.\n\n## Recovery Notes\n\n- If the target path or folder is missing, ask for the smallest path scope needed before preparing the operation.\n- If delete, overwrite, move, rename, chmod, or irreversible cleanup is requested, require an explicit confirmation gate.\n- If the request is file conversion, deck\u002FPDF export, or attachment delivery, route to materials-package or deliverable-package instead.\n- On Hermes, when a checkpoint covers the change, the user's `\u002Frollback` restores it and `\u002Fdiff session` shows what the session changed since the checkpoint baseline; cite either only after the user runs it.\n- On Hermes, a write that its own file guards refuse or hold for approval (a sensitive system path, a protected instruction file) is that gate's outcome to record, `blocked` or the user's answer, never a write to retry through another tool.\n\n\n\n## When to Use\n\nUse when Hermes should prepare or supervise local workspace\u002Ffile-system operations such as listing, searching, organizing, copying, moving, renaming, archiving, or deleting files without claiming the operation ran.\n\n    Strong routing signals: `workspace-file-operator`, `workspace file operator`, `file operator`, `file operation`, `file operations`, `filesystem task`, `filesystem operation`, `file system task`, `file system operation`, `list files`, `list folder`, `list directory`, `find local files`, `search files`, `organize files`, `organize folder`, `move file`, `move files`, `copy file`, `copy files`, `rename file`, `rename files`, `delete file`, `delete files`, `remove file`, `remove files`, `archive files`, `downloads folder`, `reports folder`, `folder cleanup`, `file cleanup`, `파일 작업`, `파일 조작`, `파일 정리`, `파일 검색`, `파일 찾아`, `파일 이동`, `파일 복사`, `파일 이름 변경`, `파일 삭제`, `폴더 정리`, `다운로드 폴더`, `디렉터리 목록`\n\n## Catalog Metadata\n\nCategory: `filesystem`\nPhase: `file-task`\nQuality tier: `workflow-surface-gated`\nReasoning demand: `standard`\n\nQuality bar:\n\n- Name the user-facing workflow objective, required context, next action, and stop condition.\n- Separate prepared guidance from observed platform, runtime, connector, file, memory, or delivery evidence.\n- Expose missing tools, credentials, targets, or observations as user-visible gaps.\n\nRequired inputs:\n\n- user request\n- target context\n- delivery or status expectation\n- known missing evidence\n\nExpected outputs:\n\n- workspace_file_task_card\u002Fv1\n- file_operation_scope\u002Fv1\n- file_observation_manifest\u002Fv1 when observed\n- file_confirmation_gate\u002Fv1 when destructive\n- next action\n- prepared-vs-observed boundary\n\nArtifact expectations:\n\n- workspace_file_task_card\u002Fv1 metadata-only wrapper card when prepared\n- file_operation_scope\u002Fv1 with path root, allowed operations, excluded paths, and stop condition\n- file_observation_manifest\u002Fv1 only when directory listings, file stats, hashes, diffs, or operation output are observed\n- session_file_activity\u002Fv1 (`omh quality-evidence file-activity --hermes-session \u003Cid> --json`) cited in that manifest for which workspace files a Hermes session's read_file, write_file, and patch calls named and the outcome Hermes recorded; never as file-content, hash, diff, test, review, CI, or merge evidence\n- file_confirmation_gate\u002Fv1 for delete, overwrite, move, rename, chmod, archive mutation, or irreversible cleanup, recording checkpoint availability before the step and keeping the confirmation either way: on Hermes, checkpoints are off unless the user turned them on (`checkpoints.enabled`, or a session started with the `--checkpoints` flag), and one covers only the directory Hermes snapshots for the step (for a terminal command, its working directory), minus its excludes (among them archives, media, logs, `.env` files, and dependency and build folders) and its limits (a file over the size cap, 10 MB by default, or a directory with more than 50,000 entries), so record `available` only when the user's `\u002Frollback` lists checkpoints for a directory that holds the target and the target is not excluded or over a limit, `not_available` otherwise, and `not_observed` until then\n\nSafety rules:\n\n- A workspace file operator card is not file read, file write, copy, move, rename, delete, archive, upload, download, permission change, or destructive filesystem evidence unless observed file-operation output records it.\n- Do not claim connector, gateway, runtime, file generation, memory mutation, or host automation evidence from prepared guidance.\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},"guide",[27,28,29],"workflow","oh-my-hermes","filesystem","file-task","workflow-surface-gated","main","4c174e06a831864e98c30f630a7aa6c04738b094","skills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-files","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-files",{"tool":44,"command":45},"bunx","bunx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill omh-files",{"tool":47,"command":48},"pnpm","pnpm dlx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill omh-files","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-files\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",[],[]]