[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EV2J9B1GW35C1THMRCSP1G":3,"skill-same:01M7EV2J9B1GW35C1THMRCSP1G":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},"01M7EV2J9B1GW35C1THMRCSP1G","omh-paper-learning",null,"[omh] Paper or paper PDF to understand: explain a supplied paper or paper\u002FPDF at a selected level while preserving full section coverage and source evidence boundaries. Use when the user says: paper-learning, paper learning, paper-explainer, paper explainer, paper explanation, explain this paper, explain this arxiv paper, paper walkthrough.","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-paper-learning\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: \"omh-paper-learning\"\ndescription: \"[omh] Paper or paper PDF to understand: explain a supplied paper or paper\u002FPDF at a selected level while preserving full section coverage and source evidence boundaries. Use when the user says: paper-learning, paper learning, paper-explainer, paper explainer, paper explanation, explain this paper, explain this arxiv paper, paper walkthrough.\"\nlicense: MIT\nmetadata:\n  hermes:\n    tags: [workflow, oh-my-hermes, research]\n    category: research\n    phase: paper-learning\n    role: researcher\n    quality_tier: paper-learning-gated\n---\n\n# Paper Learning\n\nThis is an OMH `paper-learning` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).\n\n## Why This Exists\n\n`paper-learning` exists so Hermes can act like a strong human tutor for papers: choose the right explanation level, walk through the full paper section by section, and keep PDF extraction and validation evidence honest.\n\n## Do Not Use When\n\n- The request asks to export, convert, render, or package a file; use `omh-materials-package`.\n- The request asks for daily\u002Fweekly paper monitoring, digest, source inbox, or Scout\u002FAnalyst\u002FBriefer operations.\n- The request asks to find current papers or sources when no supplied paper exists; use `ulw-research`.\n- The request asks for a visual\u002Fimage card; use `omh-image-cards`.\n- The request asks to implement or reproduce the paper's code; prepare a coding handoff only after a paper learning or reproduction plan is accepted.\n\n## Examples\n\nGood example:\n\n- Prompt: paper-learning 이 논문 PDF를 아주 쉽게 설명해줘. 내용은 줄이지 말고 섹션별로.\n- Expected behavior: Prepare paper_learning_card\u002Fv1, ask or record level=very_easy, mark PDF extraction\u002Fsource_state evidence, then explain section-by-section with a coverage ledger.\n- Why: The user supplied a paper\u002FPDF explanation intent with an explicit level and coverage-preserving constraint.\n\nBad example:\n\n- Prompt: paper-learning 이 PDF를 PPT로 변환해서 공유용 파일 만들어줘.\n- Expected behavior: Route to `materials-package` because the user wants file conversion\u002Fexport, not conceptual paper explanation.\n- Why: PDF file output and render QA are material packaging work, not paper learning evidence.\n\n## Completion Checklist\n\n- The selected explanation level is one of: very_easy, moderate, expert, choose.\n- The source_state is recorded and scoped to observed text or extraction evidence.\n- The coverage ledger lists observed, missing, or prepared sections before claiming completion.\n- The explanation is section-aware and does not compress away claims, equations, figures, limitations, or reproducibility notes.\n- Not-observed boundaries remain visible: full_pdf_extraction, figure_ocr, external_citation_check, math_proof_validation, code_or_benchmark_reproduction, peer_review_or_claim_correctness.\n\n## Recovery Notes\n\n- If no paper text is observed, prepare the learning card from metadata only and ask for an attachment, excerpt, or extraction evidence.\n- If only an abstract or excerpt is supplied, label the result as excerpt explanation and list missing sections.\n- If context is too long, continue section-by-section and keep covered \u002F next \u002F missing state in the ledger.\n- If the paper is longer than one read window, plan numbered page or line ranges in a durable host-owned ledger before reading, walk them in order, and mark each covered; the native OMH plan tool is unavailable in this projection.\n- If the user asks for validation, citation checking, math proof review, or reproduction, create a separate observed-evidence or coding handoff path.\n\n\n\n## When to Use\n\nUse when Hermes should explain a supplied paper, arXiv entry, paper PDF, pasted excerpt, or extracted paper text at a selected level while keeping a coverage ledger instead of shrinking the paper into a lossy summary.\n\n    Strong routing signals: `paper-learning`, `paper learning`, `paper-explainer`, `paper explainer`, `paper explanation`, `explain this paper`, `explain this arxiv paper`, `paper walkthrough`, `research paper explanation`, `arxiv paper explain`, `pdf paper explain`, `paper pdf explanation`, `explain the attached paper`, `explain this pdf paper`, `without dropping details`, `very easy paper explanation`, `moderate paper explanation`, `expert paper explanation`, `논문 설명`, `논문 해설`, `논문 쉽게 설명`, `논문 아주 쉽게`, `논문 적당한 난이도`, `논문 전문가급`, `이 논문 설명해줘`, `이 논문 PDF 설명해줘`, `논문 PDF 쉽게 설명`, `논문 내용 줄이지 말고`\n\n## Catalog Metadata\n\nCategory: `research`\nPhase: `paper-learning`\nQuality tier: `paper-learning-gated`\nReasoning demand: `standard`\n\nQuality bar:\n\n- Ask for or state the explanation level before drafting: very easy, moderate, or expert.\n- Record source_state as one of: metadata_only, excerpt_text_observed, file_text_extraction_observed, full_text_observed, unknown_or_missing.\n- Preserve the coverage policy `coverage_preserving_not_lossy_summary` through a section-by-section ledger.\n- Explain by chunks when the source is long; keep each chunk linked to coverage_ledger status.\n- Set source_state from how the paper was acquired, not from the request. An entry that Hermes' bundled `arxiv` skill returned (search or id lookup) is `metadata_only` until paper text is read. Text that the bundled `pdf` skill's `pdf_read.py \u003Cfile> --text` run returned is `file_text_extraction_observed` for the pages that came back with text, and a page that came back empty is listed as missing. Without those skills, the state is whatever the supplied text supports.\n- For a paper past one read budget, plan numbered page ranges before reading, and map each covered range onto the coverage ledger's sections.\n- List missing sections and not-observed claims before presenting the explanation as complete.\n\nRequired inputs:\n\n- paper identity or attachment reference\n- observed text scope or extraction evidence\n- explanation level: very_easy, moderate, expert, or choose\n- coverage scope: full paper, selected sections, or supplied excerpt\n- output language when different from the source\n\nExpected outputs:\n\n- paper_learning_card\u002Fv1\n- explanation level metadata\n- source_state boundary\n- coverage ledger\n- section-by-section explanation outline\n- missing-section and not-observed list\n\nArtifact expectations:\n\n- record the card with `omh paper plan --title \u003Ctitle> --source \u003Cpath or url> --level \u003Clevel> --source-state \u003Cstate>`, which writes paper_learning_card\u002Fv1 to `$OMH_HOME\u002Fpaper-learning\u002F\u003Cpaper_id>\u002Fcard.json` and hashes a local source file without parsing it\n- record each explained chunk with `omh paper progress \u003Cpaper_id> --covered \u003Csection> --next \u003Csection> [--missing \u003Csection>] [--note \u003Ctext>]`, which updates the coverage ledger and appends one line to `ledger.jsonl`; `omh paper validate` checks the store\n\nSafety rules:\n\n- Do not claim full PDF extraction, figure OCR, external citation checking, math validation, code reproduction, peer review, or full-paper coverage without observed evidence.\n- A pasted abstract or excerpt supports only excerpt explanation until the remaining sections are observed.\n- Level changes may change scaffolding, vocabulary, analogies, and critique depth, but must not drop substantive content.\n- End each chunk with covered \u002F next \u002F missing rather than done unless the coverage ledger is complete.\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","# Paper Learning\n\nThis is an OMH `paper-learning` workflow skill, projected for Agent Skills hosts (Claude Code, Codex, Cursor, opencode, OpenClaw, pi).\n\n## Why This Exists\n\n`paper-learning` exists so Hermes can act like a strong human tutor for papers: choose the right explanation level, walk through the full paper section by section, and keep PDF extraction and validation evidence honest.\n\n## Do Not Use When\n\n- The request asks to export, convert, render, or package a file; use `omh-materials-package`.\n- The request asks for daily\u002Fweekly paper monitoring, digest, source inbox, or Scout\u002FAnalyst\u002FBriefer operations.\n- The request asks to find current papers or sources when no supplied paper exists; use `ulw-research`.\n- The request asks for a visual\u002Fimage card; use `omh-image-cards`.\n- The request asks to implement or reproduce the paper's code; prepare a coding handoff only after a paper learning or reproduction plan is accepted.\n\n## Examples\n\nGood example:\n\n- Prompt: paper-learning 이 논문 PDF를 아주 쉽게 설명해줘. 내용은 줄이지 말고 섹션별로.\n- Expected behavior: Prepare paper_learning_card\u002Fv1, ask or record level=very_easy, mark PDF extraction\u002Fsource_state evidence, then explain section-by-section with a coverage ledger.\n- Why: The user supplied a paper\u002FPDF explanation intent with an explicit level and coverage-preserving constraint.\n\nBad example:\n\n- Prompt: paper-learning 이 PDF를 PPT로 변환해서 공유용 파일 만들어줘.\n- Expected behavior: Route to `materials-package` because the user wants file conversion\u002Fexport, not conceptual paper explanation.\n- Why: PDF file output and render QA are material packaging work, not paper learning evidence.\n\n## Completion Checklist\n\n- The selected explanation level is one of: very_easy, moderate, expert, choose.\n- The source_state is recorded and scoped to observed text or extraction evidence.\n- The coverage ledger lists observed, missing, or prepared sections before claiming completion.\n- The explanation is section-aware and does not compress away claims, equations, figures, limitations, or reproducibility notes.\n- Not-observed boundaries remain visible: full_pdf_extraction, figure_ocr, external_citation_check, math_proof_validation, code_or_benchmark_reproduction, peer_review_or_claim_correctness.\n\n## Recovery Notes\n\n- If no paper text is observed, prepare the learning card from metadata only and ask for an attachment, excerpt, or extraction evidence.\n- If only an abstract or excerpt is supplied, label the result as excerpt explanation and list missing sections.\n- If context is too long, continue section-by-section and keep covered \u002F next \u002F missing state in the ledger.\n- If the paper is longer than one read window, plan numbered page or line ranges in a durable host-owned ledger before reading, walk them in order, and mark each covered; the native OMH plan tool is unavailable in this projection.\n- If the user asks for validation, citation checking, math proof review, or reproduction, create a separate observed-evidence or coding handoff path.\n\n\n\n## When to Use\n\nUse when Hermes should explain a supplied paper, arXiv entry, paper PDF, pasted excerpt, or extracted paper text at a selected level while keeping a coverage ledger instead of shrinking the paper into a lossy summary.\n\n    Strong routing signals: `paper-learning`, `paper learning`, `paper-explainer`, `paper explainer`, `paper explanation`, `explain this paper`, `explain this arxiv paper`, `paper walkthrough`, `research paper explanation`, `arxiv paper explain`, `pdf paper explain`, `paper pdf explanation`, `explain the attached paper`, `explain this pdf paper`, `without dropping details`, `very easy paper explanation`, `moderate paper explanation`, `expert paper explanation`, `논문 설명`, `논문 해설`, `논문 쉽게 설명`, `논문 아주 쉽게`, `논문 적당한 난이도`, `논문 전문가급`, `이 논문 설명해줘`, `이 논문 PDF 설명해줘`, `논문 PDF 쉽게 설명`, `논문 내용 줄이지 말고`\n\n## Catalog Metadata\n\nCategory: `research`\nPhase: `paper-learning`\nQuality tier: `paper-learning-gated`\nReasoning demand: `standard`\n\nQuality bar:\n\n- Ask for or state the explanation level before drafting: very easy, moderate, or expert.\n- Record source_state as one of: metadata_only, excerpt_text_observed, file_text_extraction_observed, full_text_observed, unknown_or_missing.\n- Preserve the coverage policy `coverage_preserving_not_lossy_summary` through a section-by-section ledger.\n- Explain by chunks when the source is long; keep each chunk linked to coverage_ledger status.\n- Set source_state from how the paper was acquired, not from the request. An entry that Hermes' bundled `arxiv` skill returned (search or id lookup) is `metadata_only` until paper text is read. Text that the bundled `pdf` skill's `pdf_read.py \u003Cfile> --text` run returned is `file_text_extraction_observed` for the pages that came back with text, and a page that came back empty is listed as missing. Without those skills, the state is whatever the supplied text supports.\n- For a paper past one read budget, plan numbered page ranges before reading, and map each covered range onto the coverage ledger's sections.\n- List missing sections and not-observed claims before presenting the explanation as complete.\n\nRequired inputs:\n\n- paper identity or attachment reference\n- observed text scope or extraction evidence\n- explanation level: very_easy, moderate, expert, or choose\n- coverage scope: full paper, selected sections, or supplied excerpt\n- output language when different from the source\n\nExpected outputs:\n\n- paper_learning_card\u002Fv1\n- explanation level metadata\n- source_state boundary\n- coverage ledger\n- section-by-section explanation outline\n- missing-section and not-observed list\n\nArtifact expectations:\n\n- record the card with `omh paper plan --title \u003Ctitle> --source \u003Cpath or url> --level \u003Clevel> --source-state \u003Cstate>`, which writes paper_learning_card\u002Fv1 to `$OMH_HOME\u002Fpaper-learning\u002F\u003Cpaper_id>\u002Fcard.json` and hashes a local source file without parsing it\n- record each explained chunk with `omh paper progress \u003Cpaper_id> --covered \u003Csection> --next \u003Csection> [--missing \u003Csection>] [--note \u003Ctext>]`, which updates the coverage ledger and appends one line to `ledger.jsonl`; `omh paper validate` checks the store\n\nSafety rules:\n\n- Do not claim full PDF extraction, figure OCR, external citation checking, math validation, code reproduction, peer review, or full-paper coverage without observed evidence.\n- A pasted abstract or excerpt supports only excerpt explanation until the remaining sections are observed.\n- Level changes may change scaffolding, vocabulary, analogies, and critique depth, but must not drop substantive content.\n- End each chunk with covered \u002F next \u002F missing rather than done unless the coverage ledger is complete.\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},"researcher",[27,28,29],"workflow","oh-my-hermes","research","paper-learning","paper-learning-gated","main","4c174e06a831864e98c30f630a7aa6c04738b094","skills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-paper-learning","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-paper-learning",{"tool":44,"command":45},"bunx","bunx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill omh-paper-learning",{"tool":47,"command":48},"pnpm","pnpm dlx skills add mhyahya854\u002FAI-Second-Brain_Universal-Rules --skill omh-paper-learning","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmhyahya854\u002FAI-Second-Brain_Universal-Rules\u002Fblob\u002Fmain\u002Fskills\u002F_intake\u002Fgithub\u002Frlaope\u002Foh-my-hermes\u002Fomh-paper-learning\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",[],[]]