[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75K2ZF5K0BP8VG4ZFXWPJ4D":3,"skill-same:01M75K2ZF5K0BP8VG4ZFXWPJ4D":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M75K2ZF5K0BP8VG4ZFXWPJ4D","docs-sync",null,"Audit or update public documentation against current code, covering changed behavior, defaults, examples, and navigation. Use for documentation coverage or as the documentation stage of authorized implementation work.","yasik\u002Fskills","yasik","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F127702?v=4","01M75K27120Z0BWE7GMCBQ21M8","Andrii Yasinetsky","01M75K2722ZQ7HH0WKE61XDHD1",3,"MIT","https:\u002F\u002Fgithub.com\u002Fyasik\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering\u002Fskills\u002Fdocs-sync\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: docs-sync\ndescription: Audit or update public documentation against current code, covering changed behavior, defaults, examples, and navigation. Use for documentation coverage or as the documentation stage of authorized implementation work.\n---\n\n# Docs sync\n\nKeep public documentation accurate in its existing home. This skill owns coverage\nand content; `dev-docs` supplies writing guidance and `docs-portal` runs checks.\n\n## Resolve scope and authority\n\nUse the requested feature, directory, or diff against its actual base. Perform a\nfull public-doc audit only when requested. Discover canonical sources and navigation\nfrom the target repository; `docs\u002F` is an example, not a required layout. Exclude\ninternal plans and rollout tracking from public pages, navigation, and search.\n\nAn audit-only request produces findings without edits or a rebuild. A request to\nsync\u002Fupdate docs, or a development task that includes the affected documentation,\nauthorizes those in-scope edits. Proceed without a separate approval report. Honor\nan explicit draft-only or review-before-editing constraint.\n\n## Compare and update\n\n1. Read the actual public exports, defaults, guarantees, configuration, and supported\n   examples in scope. Reuse current implementation evidence from the calling task.\n2. Compare those facts with relevant pages. Look for missing behavior, obsolete\n   names or semantics, broken examples, misplaced information, and internal plans\n   leaking into public content. Keep evidence to file, symbol\u002Fsetting, and mismatch.\n3. Update existing pages where possible. Add a page only when the topic has no\n   suitable home; adjust the index or navigation when pages move, appear, or vanish.\n   No documentation change is a valid result when the public contract is unchanged.\n4. Apply `dev-docs` to the changed prose, using the bundled sibling when native\n   skill discovery is unavailable. Preserve terminology and established structure.\n   Use plain technical English, short realistic examples, and current behavior.\n   Avoid rhetoric, slang, jokes, and contrastive-negation phrasing.\n5. Use `docs-portal` for applicable checks after edits. Preserve one canonical\n   source; do not add a website or second content copy to satisfy the workflow.\n   Reuse valid writing\u002Fbuild results when inputs have not changed.\n\n## Return the result\n\nFor an audit, report consequential gaps with evidence and proposed file-level\ncorrections. For an update, report changed pages, behavior documented, checks,\nand material limits. Omit empty categories. In a development cycle, return these\nfacts to the coordinating task for its integrated report; no separate pre-edit\nreport or approval checkpoint is needed.\n","# Docs sync\n\nKeep public documentation accurate in its existing home. This skill owns coverage\nand content; `dev-docs` supplies writing guidance and `docs-portal` runs checks.\n\n## Resolve scope and authority\n\nUse the requested feature, directory, or diff against its actual base. Perform a\nfull public-doc audit only when requested. Discover canonical sources and navigation\nfrom the target repository; `docs\u002F` is an example, not a required layout. Exclude\ninternal plans and rollout tracking from public pages, navigation, and search.\n\nAn audit-only request produces findings without edits or a rebuild. A request to\nsync\u002Fupdate docs, or a development task that includes the affected documentation,\nauthorizes those in-scope edits. Proceed without a separate approval report. Honor\nan explicit draft-only or review-before-editing constraint.\n\n## Compare and update\n\n1. Read the actual public exports, defaults, guarantees, configuration, and supported\n   examples in scope. Reuse current implementation evidence from the calling task.\n2. Compare those facts with relevant pages. Look for missing behavior, obsolete\n   names or semantics, broken examples, misplaced information, and internal plans\n   leaking into public content. Keep evidence to file, symbol\u002Fsetting, and mismatch.\n3. Update existing pages where possible. Add a page only when the topic has no\n   suitable home; adjust the index or navigation when pages move, appear, or vanish.\n   No documentation change is a valid result when the public contract is unchanged.\n4. Apply `dev-docs` to the changed prose, using the bundled sibling when native\n   skill discovery is unavailable. Preserve terminology and established structure.\n   Use plain technical English, short realistic examples, and current behavior.\n   Avoid rhetoric, slang, jokes, and contrastive-negation phrasing.\n5. Use `docs-portal` for applicable checks after edits. Preserve one canonical\n   source; do not add a website or second content copy to satisfy the workflow.\n   Reuse valid writing\u002Fbuild results when inputs have not changed.\n\n## Return the result\n\nFor an audit, report consequential gaps with evidence and proposed file-level\ncorrections. For an update, report changed pages, behavior documented, checks,\nand material limits. Omit empty categories. In a development cycle, return these\nfacts to the coordinating task for its integrated report; no separate pre-edit\nreport or approval checkpoint is needed.\n",{"name":5,"description":7},"main","befb9ad4042bc8bc52cff51625619434b95d5598","plugins\u002Fengineering\u002Fskills\u002Fdocs-sync",1,"https:\u002F\u002Fgithub.com\u002Fyasik\u002Fskills","https:\u002F\u002Fgithub.com\u002Fyasik","http:\u002F\u002Fwww.yasik.org","CTO at @diadia-ai, also co-founder  @mnemonic-labs. Previously (self-driving, marketplace dynamics, ML) @uber eng @google; \r\n","2026-11-08 05:33:50",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add yasik\u002Fskills --skill docs-sync",{"tool":39,"command":40},"bunx","bunx skills add yasik\u002Fskills --skill docs-sync",{"tool":42,"command":43},"pnpm","pnpm dlx skills add yasik\u002Fskills --skill docs-sync","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fyasik\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering\u002Fskills\u002Fdocs-sync\u002FSKILL.md",true,[47],{"path":48,"resourceType":49,"resourceTypeDesc":50,"sizeBytes":51,"sourceHtmlUrl":52},"agents\u002Fopenai.yaml","REFERENCE","参考文档",280,"https:\u002F\u002Fgithub.com\u002Fyasik\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering\u002Fskills\u002Fdocs-sync\u002Fagents\u002Fopenai.yaml",[54,61,68,75,82,89],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M75K4ANG19T1AX8WHCZ3DDJR","terminal-report","Produce beautiful, structured terminal output for a CLI or analysis tool — ANSI colors, aligned data tables, inline bar charts, diverging\u002Fcentered bars, tagged progress logs, sparklines, and section headers. Use this skill whenever you are building a command-line tool, analysis script, report generator, data dashboard, or status\u002Fprogress display that prints to a terminal, OR whenever the user wants output to look \"polished\", \"colored\", \"styled\", \"like a dashboard\", or shows a screenshot of a pretty terminal and asks how to make one. Applies even when the user just says \"print the results nicely\" or \"make a little CLI for this\" without naming colors or charts explicitly.","https:\u002F\u002Fgithub.com\u002Fyasik\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fterminal-report\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M75K47031HBRZBHX3KDWA4G4","technical-prose","Write and revise technical explanations, design docs, reviews, reports, and progress updates in clear, connected prose. Use when the reader needs to understand a mechanism or decision, or when a draft feels dense, choppy, jargon-heavy, or like compressed implementation notes. Preserve technical meaning while making the reasoning easy to follow.","https:\u002F\u002Fgithub.com\u002Fyasik\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Ftechnical-prose\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M75K3Y1SYYF6DF7BW5P6EPQS","teach","Teach a complex topic as one complete, self-paced written lesson — chaptered sections the learner reads top to bottom, a deep-dive that slows down on the single hardest concept and breaks it into steps with worked examples, diagrams only where they actually clarify, and real citations for going deeper. Works from an explicit topic (\"teach me how Raft consensus works\") or from one or more links\u002Fpapers\u002Fdocs the user wants to be brought up to speed on — it fetches them, falling back to a browser when a page is paywalled, JavaScript-rendered, or only partially retrievable. Use this whenever the user wants to *understand* something rather than just get an answer: \"teach me X\", \"explain this \u003Clink>\", \"help me understand \u003Ctopic>\", \"I want to learn \u003Cthing>\", \"break this down for me\", \"ELI5 but properly \u002F but deep\", or when they drop a URL and ask to be walked through it like a class. Distinct from a quick factual lookup or a terse summary — reach for this when the goal is durable understanding, not a TL;DR.","https:\u002F\u002Fgithub.com\u002Fyasik\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fteach\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M75K3RJR4Q8DWR819CYMQ6TZ","mermaid-render","Render a Mermaid diagram as a beautiful, optionally animated SVG (and PNG) in a calm editorial style, instead of stock Mermaid output. Supports flowchart, stateDiagram, and sequenceDiagram. Use whenever the user wants to render, draw, beautify, restyle, or \"make nice\" a Mermaid \u002F flowchart \u002F sequence \u002F state diagram, add animated data-flow to a diagram, or turn a described process or architecture into a polished diagram for a doc, README, or slide. All styling — colors, fonts, shapes, borders, animation — is configurable in one theme file.","https:\u002F\u002Fgithub.com\u002Fyasik\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fmermaid-render\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M75K3K0XAQT3A9G6DA5SK0RT","dev-docs","Write, rewrite, or review developer documentation to a complete, packaged technical-writing style guide: tone, grammar, punctuation, formatting, procedures, code samples, placeholders, UI text, linking, naming, and a word list of about 700 terms, plus an index of every rule. Use whenever the user asks for developer docs, technical docs, a README, API reference, quickstart, how-to, tutorial, concept page, release notes, docstrings or reference comments, or a docs style review, or wants docs that read like a major platform's documentation. Also use to check a draft against the style guide or to look up a term in the word list.","https:\u002F\u002Fgithub.com\u002Fyasik\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fdev-docs\u002FSKILL.md",[],[],{"skillNo":90,"name":91,"nameZh":6,"description":92,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":93,"categories":94,"keywords":95,"publishedAt":19},"01M75K3F33HE2YFN6PQA0ETNRF","unit-test-coverage","Select, write, and review meaningful tests of public functions and interfaces. Use when adding behavior, fixing a regression, reviewing test quality, or diagnosing failing tests. Every test must protect a critical behavior or flow; never add tests only to increase coverage.","https:\u002F\u002Fgithub.com\u002Fyasik\u002Fskills\u002Fblob\u002Fmain\u002Fplugins\u002Fengineering\u002Fskills\u002Funit-test-coverage\u002FSKILL.md",[],[]]