[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75S7CBY56TM5Q2MYDFM5JBK":3,"skill-same:01M75S7CBY56TM5Q2MYDFM5JBK":51},{"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":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":32,"ownerHtmlUrl":33,"ownerBlogUrl":34,"ownerDescription":35,"updatedAt":36,"install":37,"resources":50},"01M75S7CBY56TM5Q2MYDFM5JBK","doc-snippets",null,"Keep Markdown code examples under docs\u002F**\u002F*.md in sync with real source via snips, and write manual-testing instructions for onboarding guides. Use when adding\u002Fediting a doc that embeds source code or tells the reader how to try a server, when `make docs-check` fails, or when source behind an existing snippet marker changed.","tachyonmcp\u002Ftachyon","tachyonmcp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F300767890?v=4","01M75S5XNYSS7GB2AN31YR7BJ4","TachyonMCP","01M75S5XPMRRKT9XP4VV4DGQDW",39,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Ftachyonmcp\u002Ftachyon\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdoc-snippets\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: doc-snippets\ndescription: >-\n  Keep Markdown code examples under docs\u002F**\u002F*.md in sync with real source via\n  snips, and write manual-testing instructions for onboarding guides. Use when\n  adding\u002Fediting a doc that embeds source code or tells the reader how to try a\n  server, when `make docs-check` fails, or when source behind an existing\n  snippet marker changed.\nmetadata:\n  author: Konstantin Pavlov\n  version: 1.1\n---\n\n# Doc snippets (snips)\n\n`snips` links a Markdown code block to real source so docs can't silently drift.\nRequires Rust\u002Fcargo; Install locally: `cargo install snips`.\n\n## Commands\n\n```bash\nmake docs-check   # snips --check — CI-style, non-zero if any doc is stale\nmake docs-sync    # snips — rewrite stale snippets from source, then restore java\u002Fkotlin\u002Fjson fence tags\nsnips --diff \u003Cfile.md>   # preview what sync would change, no write\nsnips --quiet \u003Cfile.md>  # sync without output\n```\n\n`make docs-check` runs as part of `make all`. snips 0.0.6 options: `--check`, `--diff`, `--quiet`.\n\n## Marker syntax\n\n**Named snippet** — wrap the block in source with `snips-start: \u003Cname>` \u002F `snips-end: \u003Cname>`\ncomments (any language's comment syntax), then reference it in Markdown with an HTML\ncomment right before the fenced code block:\n\n```rust\n\u002F\u002F snips-start: main_feature\nprintln!(\"hello\");\n\u002F\u002F snips-end: main_feature\n```\n\n````markdown\n\u003C!-- snips: examples\u002Fexample.rs#main_feature -->\n```rust\nprintln!(\"hello\");\n```\n````\n\n- **Whole-file**: `\u003C!-- snips: path\u002Fto\u002FFile.java -->` embeds the entire file, including any\n  `snips-start`\u002F`snips-end` comment lines it contains.\n- **Paths** resolve relative to the Markdown file, not the working directory.\n- Named snippets and whole-file are the only marker kinds in snips 0.0.6..\n\nsnips rewrites the fence's language tag to the CodeMirror mode of the source file: `clike`\nfor Java and Kotlin, `javascript` for JSON. GitHub and the docs site don't highlight those.\n`make docs-sync` runs `.github\u002Fscripts\u002Ffix-doc-fences.py` after snips to restore `java`,\n`kotlin` and `json`; `snips --check` ignores the tag. After a bare `snips` run, rerun\n`make docs-sync` instead of committing `clike` fences.\n\n## Workflow\n\n1. Writing a doc with a code example that exists in source (or vice versa): wrap the\n   source lines in `snips-start`\u002F`snips-end`, then replace the Markdown fenced block\n   with the `\u003C!-- snips: ... -->` marker + a fence (content gets filled on sync).\n2. `make docs-sync` to populate it, review the diff, commit both the marker and the\n   generated content.\n3. Source changes later → `make docs-check` catches drift (fails the build); `make\n   docs-sync` fixes it.\n\n## Where the examples live\n\nJava and Kotlin code blocks in `docs\u002F` come from `examples\u002Fdoc-examples` (see its README):\ncompiled against the published Tachyon release, with a test per example that runs it on a\nport-0 server and asserts what the page claims.\n\n- Package per page: `docs\u002F\u003Cdir>\u002F\u003Cpage>.md` → `dev.tachyonmcp.docs.\u003Cdir>.\u003Cpage>` (hyphens\n  dropped); `_index.md` → `dev.tachyonmcp.docs.\u003Cdir>`; `docs\u002F\u003Cpage>.md` → `dev.tachyonmcp.docs.\u003Cpage>`.\n- Marker path from a doc: `..\u002Fexamples\u002Fdoc-examples\u002Fsrc\u002Fmain\u002Fjava\u002Fdev\u002Ftachyonmcp\u002Fdocs\u002F\u003Cpage>\u002FFoo.java#name`\n  (one more `..\u002F` per directory level under `docs\u002F`).\n- Put `package` above `snips-start`; imports and the class go inside the snippet. Fragments sit in\n  a method whose parameters supply the context, so the doc text compiles unchanged.\n- For a block that is a whole example (not a one-line fragment), link its source file inline in\n  the lead-in sentence: ``Create `Foo.java` ([source](https:\u002F\u002Fgithub.com\u002Ftachyonmcp\u002Ftachyon\u002Fblob\u002Fmain\u002F\u003Crepo path>)):``,\n  the same `blob\u002Fmain` form the docs already use.\n- snips takes only the first region when a name repeats, so a block mixing top-level types with a builder\n  call is two snippets in two fences. Imports can't sit inside a fragment: name their packages in the prose.\n- Gradle build files come from `examples\u002Fdoc-examples\u002Fkotlin-gradle\u002Fbuild.gradle.kts`; its `buildSrc` defines\n  `tachyon.version` so the embedded text keeps the docs' `${tachyon.version}` placeholder. Verify with\n  `gradle run` (Gradle 8.14.3, JDK 21); the Maven build does not run it.\n- A doc claim that the code contradicts is a doc bug: fix the doc, don't bend the test.\n- Build files and shell blocks (`${tachyon.version}` placeholders) stay inline; the SNAPSHOT\n  switch is the commented `tachyon.version` line in the module pom.\n- Reference page: `docs\u002Fquickstart.md` → `quickstart\u002FMyMcpServer.java` + `MyMcpServerTest.java`.\n\n## Manual-testing instructions\n\n- For manual testing in onboarding guides, lead with MCP Inspector; retain curl as an alternative.\n- Use HTML `\u003Cdetails>` with descriptive `\u003Csummary>` labels for alternative instructions and long\n  setup blocks. Open the recommended testing path with `\u003Cdetails open>`; keep alternatives collapsed.\n  Leave blank lines around fenced Markdown inside the elements and check the rendered Hugo page.\n- Give the launch command, transport, endpoint, tool arguments, and expected result. Verify Inspector\n  commands and UI labels against [its official repository](https:\u002F\u002Fgithub.com\u002Fmodelcontextprotocol\u002Finspector),\n  and ground Tachyon behavior in source and existing tests.\n- For Inspector CLI examples, use `--tool-args-json` to preserve types and `--format json` for parsed\n  output. Follow the [CLI smoke-testing guide](https:\u002F\u002Fgithub.com\u002Fmodelcontextprotocol\u002Finspector\u002Fblob\u002Fmain\u002Fdocs\u002Fcli-smoke-testing.md)\n  for automation: pin the Inspector version, bound connection time, and preserve failing exit codes.\n\n## Gotchas\n\n- Keep `snips-start` on the line directly above the first snippet line and `snips-end` directly\n  below the last. A blank line inside the markers becomes a blank first or last line in the doc.\n- `snips` with no file args processes `.md` and `.markdown` files in the **current directory\n  only** (not recursive) — that's why the Makefile targets pass an explicit `find docs -name\n  '*.md'` file list (scoped to `docs\u002F`) instead of relying on the default.\n- A stale snippet doesn't error at doc-write time — only `--check` catches it, so it's\n  only as good as CI\u002F`make all` actually running `docs-check`.\n","# Doc snippets (snips)\n\n`snips` links a Markdown code block to real source so docs can't silently drift.\nRequires Rust\u002Fcargo; Install locally: `cargo install snips`.\n\n## Commands\n\n```bash\nmake docs-check   # snips --check — CI-style, non-zero if any doc is stale\nmake docs-sync    # snips — rewrite stale snippets from source, then restore java\u002Fkotlin\u002Fjson fence tags\nsnips --diff \u003Cfile.md>   # preview what sync would change, no write\nsnips --quiet \u003Cfile.md>  # sync without output\n```\n\n`make docs-check` runs as part of `make all`. snips 0.0.6 options: `--check`, `--diff`, `--quiet`.\n\n## Marker syntax\n\n**Named snippet** — wrap the block in source with `snips-start: \u003Cname>` \u002F `snips-end: \u003Cname>`\ncomments (any language's comment syntax), then reference it in Markdown with an HTML\ncomment right before the fenced code block:\n\n```rust\n\u002F\u002F snips-start: main_feature\nprintln!(\"hello\");\n\u002F\u002F snips-end: main_feature\n```\n\n````markdown\n\u003C!-- snips: examples\u002Fexample.rs#main_feature -->\n```rust\nprintln!(\"hello\");\n```\n````\n\n- **Whole-file**: `\u003C!-- snips: path\u002Fto\u002FFile.java -->` embeds the entire file, including any\n  `snips-start`\u002F`snips-end` comment lines it contains.\n- **Paths** resolve relative to the Markdown file, not the working directory.\n- Named snippets and whole-file are the only marker kinds in snips 0.0.6..\n\nsnips rewrites the fence's language tag to the CodeMirror mode of the source file: `clike`\nfor Java and Kotlin, `javascript` for JSON. GitHub and the docs site don't highlight those.\n`make docs-sync` runs `.github\u002Fscripts\u002Ffix-doc-fences.py` after snips to restore `java`,\n`kotlin` and `json`; `snips --check` ignores the tag. After a bare `snips` run, rerun\n`make docs-sync` instead of committing `clike` fences.\n\n## Workflow\n\n1. Writing a doc with a code example that exists in source (or vice versa): wrap the\n   source lines in `snips-start`\u002F`snips-end`, then replace the Markdown fenced block\n   with the `\u003C!-- snips: ... -->` marker + a fence (content gets filled on sync).\n2. `make docs-sync` to populate it, review the diff, commit both the marker and the\n   generated content.\n3. Source changes later → `make docs-check` catches drift (fails the build); `make\n   docs-sync` fixes it.\n\n## Where the examples live\n\nJava and Kotlin code blocks in `docs\u002F` come from `examples\u002Fdoc-examples` (see its README):\ncompiled against the published Tachyon release, with a test per example that runs it on a\nport-0 server and asserts what the page claims.\n\n- Package per page: `docs\u002F\u003Cdir>\u002F\u003Cpage>.md` → `dev.tachyonmcp.docs.\u003Cdir>.\u003Cpage>` (hyphens\n  dropped); `_index.md` → `dev.tachyonmcp.docs.\u003Cdir>`; `docs\u002F\u003Cpage>.md` → `dev.tachyonmcp.docs.\u003Cpage>`.\n- Marker path from a doc: `..\u002Fexamples\u002Fdoc-examples\u002Fsrc\u002Fmain\u002Fjava\u002Fdev\u002Ftachyonmcp\u002Fdocs\u002F\u003Cpage>\u002FFoo.java#name`\n  (one more `..\u002F` per directory level under `docs\u002F`).\n- Put `package` above `snips-start`; imports and the class go inside the snippet. Fragments sit in\n  a method whose parameters supply the context, so the doc text compiles unchanged.\n- For a block that is a whole example (not a one-line fragment), link its source file inline in\n  the lead-in sentence: ``Create `Foo.java` ([source](https:\u002F\u002Fgithub.com\u002Ftachyonmcp\u002Ftachyon\u002Fblob\u002Fmain\u002F\u003Crepo path>)):``,\n  the same `blob\u002Fmain` form the docs already use.\n- snips takes only the first region when a name repeats, so a block mixing top-level types with a builder\n  call is two snippets in two fences. Imports can't sit inside a fragment: name their packages in the prose.\n- Gradle build files come from `examples\u002Fdoc-examples\u002Fkotlin-gradle\u002Fbuild.gradle.kts`; its `buildSrc` defines\n  `tachyon.version` so the embedded text keeps the docs' `${tachyon.version}` placeholder. Verify with\n  `gradle run` (Gradle 8.14.3, JDK 21); the Maven build does not run it.\n- A doc claim that the code contradicts is a doc bug: fix the doc, don't bend the test.\n- Build files and shell blocks (`${tachyon.version}` placeholders) stay inline; the SNAPSHOT\n  switch is the commented `tachyon.version` line in the module pom.\n- Reference page: `docs\u002Fquickstart.md` → `quickstart\u002FMyMcpServer.java` + `MyMcpServerTest.java`.\n\n## Manual-testing instructions\n\n- For manual testing in onboarding guides, lead with MCP Inspector; retain curl as an alternative.\n- Use HTML `\u003Cdetails>` with descriptive `\u003Csummary>` labels for alternative instructions and long\n  setup blocks. Open the recommended testing path with `\u003Cdetails open>`; keep alternatives collapsed.\n  Leave blank lines around fenced Markdown inside the elements and check the rendered Hugo page.\n- Give the launch command, transport, endpoint, tool arguments, and expected result. Verify Inspector\n  commands and UI labels against [its official repository](https:\u002F\u002Fgithub.com\u002Fmodelcontextprotocol\u002Finspector),\n  and ground Tachyon behavior in source and existing tests.\n- For Inspector CLI examples, use `--tool-args-json` to preserve types and `--format json` for parsed\n  output. Follow the [CLI smoke-testing guide](https:\u002F\u002Fgithub.com\u002Fmodelcontextprotocol\u002Finspector\u002Fblob\u002Fmain\u002Fdocs\u002Fcli-smoke-testing.md)\n  for automation: pin the Inspector version, bound connection time, and preserve failing exit codes.\n\n## Gotchas\n\n- Keep `snips-start` on the line directly above the first snippet line and `snips-end` directly\n  below the last. A blank line inside the markers becomes a blank first or last line in the doc.\n- `snips` with no file args processes `.md` and `.markdown` files in the **current directory\n  only** (not recursive) — that's why the Makefile targets pass an explicit `find docs -name\n  '*.md'` file list (scoped to `docs\u002F`) instead of relying on the default.\n- A stale snippet doesn't error at doc-write time — only `--check` catches it, so it's\n  only as good as CI\u002F`make all` actually running `docs-check`.\n",{"name":5,"metadata":24,"description":7},{"author":25,"version":26},"Konstantin Pavlov",1.1,"main","31926b69f55d872f0db4b5f1a8f9dcc018f309d9",".agents\u002Fskills\u002Fdoc-snippets",14,"https:\u002F\u002Fgithub.com\u002Ftachyonmcp\u002Ftachyon","https:\u002F\u002Ftachyonmcp.dev","https:\u002F\u002Fgithub.com\u002Ftachyonmcp","https:\u002F\u002Ftachyonmcp.dev\u002F","Tachyon MCP Runtime for JAVA","2026-11-15 04:52:42",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add tachyonmcp\u002Ftachyon --skill doc-snippets",{"tool":43,"command":44},"bunx","bunx skills add tachyonmcp\u002Ftachyon --skill doc-snippets",{"tool":46,"command":47},"pnpm","pnpm dlx skills add tachyonmcp\u002Ftachyon --skill doc-snippets","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ftachyonmcp\u002Ftachyon\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fdoc-snippets\u002FSKILL.md",true,[],[52,60,67,74,81,88],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":59},"01M7DYBXXE1PBNHA190JGQNPPR","greeting","Greet the user by name","https:\u002F\u002Fgithub.com\u002Ftachyonmcp\u002Ftachyon\u002Fblob\u002Fmain\u002Fconformance\u002Fsrc\u002Ftest\u002Fresources\u002Fskills\u002Fgreeting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"publishedAt":19},"01M75SBJ3D8Y7RW7B27CPXPT81","pdf-processing","Extract, fill, and assemble PDF documents","https:\u002F\u002Fgithub.com\u002Ftachyonmcp\u002Ftachyon\u002Fblob\u002Fmain\u002Fextensions\u002Ftachyon-extensions-skills\u002Fsrc\u002Ftest\u002Fresources\u002Fskills\u002Fpdf-processing\u002FSKILL.md",[],[],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"publishedAt":19},"01M75SB7Z5JT6CE0A09JYF53EK","read-file","How to read a file","https:\u002F\u002Fgithub.com\u002Ftachyonmcp\u002Ftachyon\u002Fblob\u002Fmain\u002Fextensions\u002Ftachyon-extensions-skills\u002Fsrc\u002Ftest\u002Fdata\u002Fskills\u002Fread-file\u002FSKILL.md",[],[],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"publishedAt":19},"01M75SAYD4MYG6TPJN50ZPE1KN","git-workflow","Follow this team's Git conventions for branching and commits","https:\u002F\u002Fgithub.com\u002Ftachyonmcp\u002Ftachyon\u002Fblob\u002Fmain\u002Fextensions\u002Ftachyon-extensions-skills\u002Fsrc\u002Ftest\u002Fdata\u002Fskills\u002Fgit-workflow\u002FSKILL.md",[],[],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"publishedAt":19},"01M75SAJVBNYY2F122FCQ041BH","elvish-magic","Compose gentle, fictional Elvish spells for light, water, and growing things","https:\u002F\u002Fgithub.com\u002Ftachyonmcp\u002Ftachyon\u002Fblob\u002Fmain\u002Fexamples\u002Fmcp-skills\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002Felvish-magic\u002FSKILL.md",[],[],{"skillNo":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"publishedAt":19},"01M75SAA0ZTD2F8VYB9RY838XJ","elvish-healing","Create gentle, fictional Elvish remedies for fantasy stories and games","https:\u002F\u002Fgithub.com\u002Ftachyonmcp\u002Ftachyon\u002Fblob\u002Fmain\u002Fexamples\u002Fmcp-skills\u002Fsrc\u002Fmain\u002Fresources\u002Fskills\u002Felvish-healing\u002FSKILL.md",[],[]]