[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ETPMGS1PNR0ATRC3HAC3GK":3,"skill-same:01M7ETPMGS1PNR0ATRC3HAC3GK":80},{"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},"01M7ETPMGS1PNR0ATRC3HAC3GK","omh-biomedical-evidence",null,"[omh] Public variant claims to cross-check: retrieve and reconcile source-labelled biomedical evidence with identity, conflict and freshness checks. Use when the user says: biomedical-evidence, biomedical evidence reconciliation, ClinVar cross-check, variant evidence matrix, BioMCP capture reconciliation.","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-biomedical-evidence\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"omh-biomedical-evidence\"\ndescription: \"[omh] Public variant claims to cross-check: retrieve and reconcile source-labelled biomedical evidence with identity, conflict and freshness checks. Use when the user says: biomedical-evidence, biomedical evidence reconciliation, ClinVar cross-check, variant evidence matrix, BioMCP capture reconciliation.\"\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [workflow, oh-my-hermes, analysis]\n    category: analysis\n    phase: biomedical-evidence\n    role: operator\n    quality_tier: evidence-gated\n---\n\n# Biomedical Evidence\n\nThis is an OMH `biomedical-evidence` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).\n\n## Why This Exists\n\nPublic sources can disagree about a variant while describing different alleles, diseases or assertion domains. Preserve those differences and their provenance before any synthesis; a fetched record is not a clinical recommendation.\n\n## First Steps\n\n- Read `toolkit\u002FREADME.md` and `references\u002Fexecution-and-qa.md`; inspect the installed BioMCP version and help before any public retrieval.\n- Require public entities only; name exact identifiers, source terms, isolated workspace and a 40-second per-retrieval host timeout before capturing unmodified stdout\u002Fstderr.\n- Run `toolkit\u002Fscripts\u002Freconcile.py` only against a hash-checked local capture envelope; never execute provider text or install an upstream skill pack.\n\n## Do Not Use When\n\n- For explaining one supplied paper, use `omh-paper-learning`; for broad literature discovery, use `ulw-research`.\n- For generic server configuration and connection diagnostics, load the host's MCP setup guidance instead.\n- For sequence analysis or omics pipelines, select an available computational biology specialist instead; this method does not implement those analyses.\n- For a patient's diagnosis, care, trial eligibility or treatment choice, stop and refer to an appropriately qualified professional; this toolkit cannot provide that decision.\n\n## Examples\n\nGood example:\n\n- Prompt: Cross-check public BRAF V600E and melanoma records across ClinVar and ClinicalTrials.gov, retaining conflicting assertions and missing update dates.\n- Expected behavior: Capture exact public queries, reconcile raw JSON offline, and report identity\u002Fdate gaps with both source receipts.\n- Why: Source comparison is bounded and does not ask for patient care.\n\nBad example:\n\n- Prompt: Use these patient records to select a therapy and decide whether the patient can join a trial.\n- Expected behavior: Refuse patient-level processing and clinical decisions; offer only public-source provenance checking.\n- Why: Registry status and source annotations are not clinical eligibility or treatment evidence.\n\n## Completion Checklist\n\n- Both source attempts have raw hashes and exact receipts, or missing\u002Ffailing sources are explicitly partial with nonzero status.\n- Entity\u002Fbuild\u002Ftranscript, disease basis, original assertions, conflicts and absent source times remain visible; no eligibility or clinical inference appears.\n- Read both output files, verify hashes and report synthetic tests separately from real retrieval; do not claim distribution or live availability from preparation.\n\n## Recovery Notes\n\n- If BioMCP is unavailable, keep captures unobserved and prepare only the explicit isolated setup; never fabricate a source response.\n- If a source fails or JSON changes, preserve stdout\u002Fstderr and a partial report; audit an updated adapter before accepting unknown schemas.\n- If disease labels or allele aliases cannot be matched literally, preserve the mismatch and ask for authoritative identifiers rather than silently broadening.\n\n\n\n## When to Use\n\nUse when public gene\u002Fvariant and disease assertions must be cross-checked against ClinVar and trial registry records, preserving source failures and disagreements rather than inferring a clinical conclusion.\n\n    Strong routing signals: `biomedical-evidence`, `biomedical evidence reconciliation`, `ClinVar cross-check`, `variant evidence matrix`, `BioMCP capture reconciliation`\n\n## Catalog Metadata\n\nCategory: `analysis`\nPhase: `biomedical-evidence`\nQuality tier: `evidence-gated`\nReasoning demand: `heavy`\n\nQuality bar:\n\n- Require observed source receipts and verified helper output hashes, not a mock result or health-only check.\n- Retain contradictory source assertions and date\u002Fidentity gaps without deriving a clinical consensus.\n\nRequired inputs:\n\n- public gene\u002Fvariant and disease query\n- bounded BioMCP capture workspace\n- intended entity identifiers and source scope\n\nExpert clarification questions:\n- `public gene\u002Fvariant and disease query`\n  - English: Which public gene, exact allele if any, disease label and intended IDs should remain distinct?\n  - Korean: 어떤 공개 유전자, 정확한 변이, 질환명과 식별자를 구분해서 확인할까요?\n\nExpected outputs:\n\n- biomedical_evidence_matrix\u002Fv1\n- biomedical_reconciliation_manifest\u002Fv1\n\nArtifact expectations:\n\n- Authored file contracts, not registered OMH RPC artifacts: evidence-matrix.json and manifest.json plus external raw capture\u002Freceipt references.\n- Raw responses remain outside the package; the matrix preserves source assertions with JSON-pointer paths, accessions\u002FNCT IDs, review\u002Fsubmitter context and retrieval\u002Fsource times.\n\nSafety rules:\n\n- No patient data, clinical eligibility determination, treatment recommendation or pathogenicity adjudication; source assertions are not medical advice.\n- No network or subprocess from the shipped helper, registration, discovery or install; BioMCP runs only via explicit bounded host invocation in an isolated optional environment.\n- Keep germline\u002Fsomatic and disease\u002Fpopulation contexts separate; recruitment and text matches never establish eligibility or variant relevance.\n- Preserve raw bytes and exact queries; mark source failure, missing dates and unresolved identity as partial instead of inventing biological findings.\n\nProcedure: load `references\u002Fprocedure.md`.\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","# Biomedical Evidence\n\nThis is an OMH `biomedical-evidence` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).\n\n## Why This Exists\n\nPublic sources can disagree about a variant while describing different alleles, diseases or assertion domains. Preserve those differences and their provenance before any synthesis; a fetched record is not a clinical recommendation.\n\n## First Steps\n\n- Read `toolkit\u002FREADME.md` and `references\u002Fexecution-and-qa.md`; inspect the installed BioMCP version and help before any public retrieval.\n- Require public entities only; name exact identifiers, source terms, isolated workspace and a 40-second per-retrieval host timeout before capturing unmodified stdout\u002Fstderr.\n- Run `toolkit\u002Fscripts\u002Freconcile.py` only against a hash-checked local capture envelope; never execute provider text or install an upstream skill pack.\n\n## Do Not Use When\n\n- For explaining one supplied paper, use `omh-paper-learning`; for broad literature discovery, use `ulw-research`.\n- For generic server configuration and connection diagnostics, load the host's MCP setup guidance instead.\n- For sequence analysis or omics pipelines, select an available computational biology specialist instead; this method does not implement those analyses.\n- For a patient's diagnosis, care, trial eligibility or treatment choice, stop and refer to an appropriately qualified professional; this toolkit cannot provide that decision.\n\n## Examples\n\nGood example:\n\n- Prompt: Cross-check public BRAF V600E and melanoma records across ClinVar and ClinicalTrials.gov, retaining conflicting assertions and missing update dates.\n- Expected behavior: Capture exact public queries, reconcile raw JSON offline, and report identity\u002Fdate gaps with both source receipts.\n- Why: Source comparison is bounded and does not ask for patient care.\n\nBad example:\n\n- Prompt: Use these patient records to select a therapy and decide whether the patient can join a trial.\n- Expected behavior: Refuse patient-level processing and clinical decisions; offer only public-source provenance checking.\n- Why: Registry status and source annotations are not clinical eligibility or treatment evidence.\n\n## Completion Checklist\n\n- Both source attempts have raw hashes and exact receipts, or missing\u002Ffailing sources are explicitly partial with nonzero status.\n- Entity\u002Fbuild\u002Ftranscript, disease basis, original assertions, conflicts and absent source times remain visible; no eligibility or clinical inference appears.\n- Read both output files, verify hashes and report synthetic tests separately from real retrieval; do not claim distribution or live availability from preparation.\n\n## Recovery Notes\n\n- If BioMCP is unavailable, keep captures unobserved and prepare only the explicit isolated setup; never fabricate a source response.\n- If a source fails or JSON changes, preserve stdout\u002Fstderr and a partial report; audit an updated adapter before accepting unknown schemas.\n- If disease labels or allele aliases cannot be matched literally, preserve the mismatch and ask for authoritative identifiers rather than silently broadening.\n\n\n\n## When to Use\n\nUse when public gene\u002Fvariant and disease assertions must be cross-checked against ClinVar and trial registry records, preserving source failures and disagreements rather than inferring a clinical conclusion.\n\n    Strong routing signals: `biomedical-evidence`, `biomedical evidence reconciliation`, `ClinVar cross-check`, `variant evidence matrix`, `BioMCP capture reconciliation`\n\n## Catalog Metadata\n\nCategory: `analysis`\nPhase: `biomedical-evidence`\nQuality tier: `evidence-gated`\nReasoning demand: `heavy`\n\nQuality bar:\n\n- Require observed source receipts and verified helper output hashes, not a mock result or health-only check.\n- Retain contradictory source assertions and date\u002Fidentity gaps without deriving a clinical consensus.\n\nRequired inputs:\n\n- public gene\u002Fvariant and disease query\n- bounded BioMCP capture workspace\n- intended entity identifiers and source scope\n\nExpert clarification questions:\n- `public gene\u002Fvariant and disease query`\n  - English: Which public gene, exact allele if any, disease label and intended IDs should remain distinct?\n  - Korean: 어떤 공개 유전자, 정확한 변이, 질환명과 식별자를 구분해서 확인할까요?\n\nExpected outputs:\n\n- biomedical_evidence_matrix\u002Fv1\n- biomedical_reconciliation_manifest\u002Fv1\n\nArtifact expectations:\n\n- Authored file contracts, not registered OMH RPC artifacts: evidence-matrix.json and manifest.json plus external raw capture\u002Freceipt references.\n- Raw responses remain outside the package; the matrix preserves source assertions with JSON-pointer paths, accessions\u002FNCT IDs, review\u002Fsubmitter context and retrieval\u002Fsource times.\n\nSafety rules:\n\n- No patient data, clinical eligibility determination, treatment recommendation or pathogenicity adjudication; source assertions are not medical advice.\n- No network or subprocess from the shipped helper, registration, discovery or install; BioMCP runs only via explicit bounded host invocation in an isolated optional environment.\n- Keep germline\u002Fsomatic and disease\u002Fpopulation contexts separate; recruitment and text matches never establish eligibility or variant relevance.\n- Preserve raw bytes and exact queries; mark source failure, missing dates and unresolved identity as partial instead of inventing biological findings.\n\nProcedure: load `references\u002Fprocedure.md`.\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","analysis","biomedical-evidence","evidence-gated","main","4c174e06a831864e98c30f630a7aa6c04738b094","skills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-biomedical-evidence","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-biomedical-evidence",{"tool":44,"command":45},"bunx","bunx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill omh-biomedical-evidence",{"tool":47,"command":48},"pnpm","pnpm dlx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill omh-biomedical-evidence","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-biomedical-evidence\u002FSKILL.md",true,[52,58,62,66,70,76],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fexecution-and-qa.md","REFERENCE","参考文档",3131,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-biomedical-evidence\u002Freferences\u002Fexecution-and-qa.md",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Ffull-contract.md",3242,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-biomedical-evidence\u002Freferences\u002Ffull-contract.md",{"path":63,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fprocedure.md",3557,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-biomedical-evidence\u002Freferences\u002Fprocedure.md",{"path":67,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":68,"sourceHtmlUrl":69},"toolkit\u002FREADME.md",7790,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-biomedical-evidence\u002Ftoolkit\u002FREADME.md",{"path":71,"resourceType":72,"resourceTypeDesc":73,"sizeBytes":74,"sourceHtmlUrl":75},"toolkit\u002Fscripts\u002Freconcile.py","SCRIPT","脚本",19519,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-biomedical-evidence\u002Ftoolkit\u002Fscripts\u002Freconcile.py",{"path":77,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":78,"sourceHtmlUrl":79},"toolkit\u002Fupstream-manifest.json",3060,"https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-biomedical-evidence\u002Ftoolkit\u002Fupstream-manifest.json",[81,89,97,105,112,119],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":85,"sourceHtmlUrl":86,"categories":87,"keywords":88,"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":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":93,"sourceHtmlUrl":94,"categories":95,"keywords":96,"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":98,"name":99,"nameZh":6,"description":100,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":101,"sourceHtmlUrl":102,"categories":103,"keywords":104,"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":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"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":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"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":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"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",[],[]]