[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72S8VAD2PTW30ASEQQE7S12":3,"skill-same:01M72S8VAD2PTW30ASEQQE7S12":51},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M72S8VAD2PTW30ASEQQE7S12","fsdocs-build",null,"This skill should be used when the user asks to \"build docs\", \"build documentation\", \"run fsdocs\", \"preview docs\", \"watch docs\", \"fsdocs build errors\", \"fix doc build\", or needs to build, preview, or troubleshoot an FSharp.Formatting documentation site. Covers build commands, watch mode, common errors, and build flags.","EHotwagner\u002FFS-Skia-UI","EHotwagner","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F1645484?v=4","01M72S7CTBDPQDQHQJKKHY87K9","01M72S7CVFD0JN82RVX21NFEVC",2,"MIT","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffsdocs-build\u002FSKILL.md",[],[],"2026-11-10 22:39:42",false,"---\nname: fsdocs-build\ndescription: This skill should be used when the user asks to \"build docs\", \"build documentation\", \"run fsdocs\", \"preview docs\", \"watch docs\", \"fsdocs build errors\", \"fix doc build\", or needs to build, preview, or troubleshoot an FSharp.Formatting documentation site. Covers build commands, watch mode, common errors, and build flags.\nversion: 0.1.0\n---\n\n# Build and Preview FSharp.Formatting Documentation\n\nBuild a documentation site with `dotnet fsdocs`, preview it locally, and troubleshoot common build issues.\n\n**Key capabilities:**\n- Build documentation with appropriate flags for the situation\n- Launch watch mode for live preview during authoring\n- Diagnose and fix common fsdocs build errors\n- Handle eval mode for literate scripts with executable output\n\n## Overview\n\nFSharp.Formatting builds static HTML from three inputs: API docs (from compiled assemblies and XML doc comments), Markdown files in `docs\u002F`, and literate `.fsx` scripts in `docs\u002F`. The build process compiles projects, extracts documentation, and renders everything into `output\u002F`.\n\n## Workflow\n\n### 1. Verify Tool Installation\n\nConfirm `fsdocs-tool` is available:\n\n```\ndotnet tool restore\ndotnet fsdocs --help\n```\n\nIf not installed, use the `fsdocs-setup` skill first.\n\n### 2. Build Projects in Release Mode\n\nAPI documentation is generated from compiled assemblies. Build in Release mode to ensure the output matches what users will see:\n\n```\ndotnet build -c Release\n```\n\nThis step is essential — fsdocs reads the compiled DLLs and their XML doc files.\n\n### 3. Run fsdocs Build\n\nStandard build:\n\n```\ndotnet fsdocs build --clean\n```\n\nBuild with script evaluation (for literate `.fsx` files that use `include-output`, `include-it`, or `include-value`):\n\n```\ndotnet fsdocs build --clean --eval\n```\n\n### 4. Check Build Output\n\nReview the build output for:\n- **Errors** — compilation failures, missing references, broken cross-references\n- **Warnings** — missing doc comments, unresolved `cref` links\n- **Generated pages** — confirm expected files appear in `output\u002F`\n\n### 5. Report Results\n\nSummarize what was generated: number of API pages, content pages, any errors or warnings that need attention.\n\n## Build Flags Reference\n\n| Flag | Purpose | When to Use |\n|---|---|---|\n| `--clean` | Remove previous output before building | Always on first build or when changing structure |\n| `--eval` | Evaluate `.fsx` scripts and capture output | When literate scripts use output directives |\n| `--strict` | Treat warnings as errors | CI builds, pre-release verification |\n| `--noapidocs` | Skip API doc generation | When only editing content pages |\n| `--nonpublic` | Include non-public members in API docs | Internal documentation builds |\n| `--nodefaultcontent` | Skip default content generation | When using fully custom content |\n| `--input \u003Cdir>` | Override input directory | Non-standard project layouts |\n| `--output \u003Cdir>` | Override output directory | Custom deployment paths |\n| `--properties \u003Cprops>` | Pass MSBuild properties | Override `Directory.Build.props` values |\n\n## Watch Mode\n\nFor live preview during authoring:\n\n```\ndotnet fsdocs watch\n```\n\nThis starts a local server (default port 8901) and rebuilds on file changes. Open `http:\u002F\u002Flocalhost:8901` in a browser.\n\nWatch mode options:\n- `--port \u003Cn>` — use a different port\n- `--eval` — evaluate scripts on each rebuild (slower but shows output)\n- `--noapidocs` — skip API regeneration for faster content iteration\n\nTypical authoring workflow: run `dotnet fsdocs watch --noapidocs` for fast content iteration, then do a full `dotnet fsdocs build --clean --eval` before committing.\n\n## Common Errors and Fixes\n\n### Missing XML Documentation File\n**Symptom:** API pages are empty or missing.\n**Cause:** `GenerateDocumentationFile` not set to `true` in project properties.\n**Fix:** Add `\u003CGenerateDocumentationFile>true\u003C\u002FGenerateDocumentationFile>` to `Directory.Build.props`.\n\n### Compilation Failure During Build\n**Symptom:** `fsdocs build` fails with compile errors.\n**Cause:** Projects don't compile in Release mode, or a dependency is missing.\n**Fix:** Run `dotnet build -c Release` separately to isolate the issue.\n\n### Broken Cross-References\n**Symptom:** Warnings about unresolved `cref` links in build output.\n**Cause:** Incorrect `cref` syntax or referencing non-public members.\n**Fix:** Use fully qualified names: `cref:T:Namespace.TypeName` for types, `cref:M:Namespace.TypeName.MethodName` for methods.\n\n### Script Evaluation Failures\n**Symptom:** `.fsx` files fail during `--eval`.\n**Cause:** Missing `#r` references, runtime errors in scripts, or scripts depending on external state.\n**Fix:** Ensure all assembly references are present. Use `(*** do-not-eval ***)` for scripts that cannot be evaluated.\n\n### Missing Assembly References in .fsx\n**Symptom:** `Type not found` or `Namespace not opened` during eval.\n**Cause:** Literate scripts need explicit assembly references.\n**Fix:** Add `#r \"..\u002Fsrc\u002FMyProject\u002Fbin\u002FRelease\u002Fnet8.0\u002FMyProject.dll\"` at the top of the script.\n\n### Stale Output\n**Symptom:** Changes don't appear in the built site.\n**Cause:** Cached build output.\n**Fix:** Use `--clean` to force a fresh build.\n\n## Best Practices\n\n**DO:**\n- ✅ Always build projects in Release mode before running fsdocs\n- ✅ Use `--clean` when structure or navigation has changed\n- ✅ Use `--noapidocs` during content-only authoring for faster iteration\n- ✅ Run a full `--eval` build before committing to verify all scripts work\n- ✅ Check build output for warnings — they often indicate broken cross-references\n\n**DON'T:**\n- ❌ Skip the Release build step — fsdocs needs compiled assemblies\n- ❌ Use `--eval` in watch mode unless actively working on script output\n- ❌ Ignore cross-reference warnings — they produce broken links in the site\n- ❌ Commit the `output\u002F` directory — it is a build artifact\n- ❌ Run fsdocs from a subdirectory — always run from the solution root\n\n## Additional Resources\n\n### Utility Scripts\n- **`scripts\u002Ffsdocs-build.sh`** — Build wrapper with error handling, Release compilation, and result reporting\n\n## Implementation Workflow\n\n1. Verify `fsdocs-tool` is installed (`dotnet tool restore`)\n2. Build all projects in Release mode (`dotnet build -c Release`)\n3. Run `dotnet fsdocs build` with appropriate flags for the situation\n4. Review build output for errors and warnings\n5. Report results — pages generated, issues found, suggested fixes\n\nFocus on producing a successful build and clear diagnostics when issues arise.\n\n## Scope \u002F when to use\n\nUse this skill to **build, preview, or troubleshoot** an existing FSharp.Formatting\nsite — running `dotnet fsdocs build`, watch-mode previews, choosing flags, and\ndiagnosing build\u002Feval errors. If the project has no fsdocs setup yet, run\n[[fsdocs-setup]] first. To create the content that this skill builds, use\n[[fsdocs-api-doc]] (XML doc comments), [[fsdocs-examples]] (literate `.fsx`), or\n[[fsdocs-technical]] (Markdown). This skill is the build\u002Fdiagnose loop, not a\ncontent authoring skill.\n\n## Driven-library API\n\nThis skill drives the external **FSharp.Formatting** `dotnet fsdocs` CLI — there is\nno FS.Skia.UI backing `.fsi` surface. The driven contract is the CLI verb +\nflag surface: `build` and `watch`, with `--clean`, `--eval`, `--strict`,\n`--noapidocs`, `--nonpublic`, `--nodefaultcontent`, `--input`, `--output`,\n`--properties`, and (watch) `--port`. It depends on compiled assemblies plus their\nemitted XML doc files, so `dotnet build -c Release` is a precondition of every\nbuild.\n\n## Persistent-problem mandate\n\nfsdocs CLI flags and error messages change across tool versions, and broken\n`cref` cross-references fail silently. Consult the **official online docs first**\nfor the pinned tool version before relying on a flag documented here, and re-read\nthe live docs when a build error does not match the troubleshooting table — this is\na recurring, version-sensitive surface.\n\n## Related\n\n- [[fsdocs-setup]] — install `fsdocs-tool` and scaffold `docs\u002F` before building\n- [[fsdocs-api-doc]] — author the `\u002F\u002F\u002F` comments that become API pages\n- [[fsdocs-examples]] — literate `.fsx` scripts built with `--eval`\n- [[fsdocs-technical]] — Markdown pages picked up by the build\n\n## Sources\n\n- FSharp.Formatting documentation: https:\u002F\u002Ffsprojects.github.io\u002FFSharp.Formatting\u002F\n- Command-line \u002F `fsdocs` CLI reference: https:\u002F\u002Ffsprojects.github.io\u002FFSharp.Formatting\u002Fcommandline.html\n- FSharp.Formatting repository: https:\u002F\u002Fgithub.com\u002Ffsprojects\u002FFSharp.Formatting\n","# Build and Preview FSharp.Formatting Documentation\n\nBuild a documentation site with `dotnet fsdocs`, preview it locally, and troubleshoot common build issues.\n\n**Key capabilities:**\n- Build documentation with appropriate flags for the situation\n- Launch watch mode for live preview during authoring\n- Diagnose and fix common fsdocs build errors\n- Handle eval mode for literate scripts with executable output\n\n## Overview\n\nFSharp.Formatting builds static HTML from three inputs: API docs (from compiled assemblies and XML doc comments), Markdown files in `docs\u002F`, and literate `.fsx` scripts in `docs\u002F`. The build process compiles projects, extracts documentation, and renders everything into `output\u002F`.\n\n## Workflow\n\n### 1. Verify Tool Installation\n\nConfirm `fsdocs-tool` is available:\n\n```\ndotnet tool restore\ndotnet fsdocs --help\n```\n\nIf not installed, use the `fsdocs-setup` skill first.\n\n### 2. Build Projects in Release Mode\n\nAPI documentation is generated from compiled assemblies. Build in Release mode to ensure the output matches what users will see:\n\n```\ndotnet build -c Release\n```\n\nThis step is essential — fsdocs reads the compiled DLLs and their XML doc files.\n\n### 3. Run fsdocs Build\n\nStandard build:\n\n```\ndotnet fsdocs build --clean\n```\n\nBuild with script evaluation (for literate `.fsx` files that use `include-output`, `include-it`, or `include-value`):\n\n```\ndotnet fsdocs build --clean --eval\n```\n\n### 4. Check Build Output\n\nReview the build output for:\n- **Errors** — compilation failures, missing references, broken cross-references\n- **Warnings** — missing doc comments, unresolved `cref` links\n- **Generated pages** — confirm expected files appear in `output\u002F`\n\n### 5. Report Results\n\nSummarize what was generated: number of API pages, content pages, any errors or warnings that need attention.\n\n## Build Flags Reference\n\n| Flag | Purpose | When to Use |\n|---|---|---|\n| `--clean` | Remove previous output before building | Always on first build or when changing structure |\n| `--eval` | Evaluate `.fsx` scripts and capture output | When literate scripts use output directives |\n| `--strict` | Treat warnings as errors | CI builds, pre-release verification |\n| `--noapidocs` | Skip API doc generation | When only editing content pages |\n| `--nonpublic` | Include non-public members in API docs | Internal documentation builds |\n| `--nodefaultcontent` | Skip default content generation | When using fully custom content |\n| `--input \u003Cdir>` | Override input directory | Non-standard project layouts |\n| `--output \u003Cdir>` | Override output directory | Custom deployment paths |\n| `--properties \u003Cprops>` | Pass MSBuild properties | Override `Directory.Build.props` values |\n\n## Watch Mode\n\nFor live preview during authoring:\n\n```\ndotnet fsdocs watch\n```\n\nThis starts a local server (default port 8901) and rebuilds on file changes. Open `http:\u002F\u002Flocalhost:8901` in a browser.\n\nWatch mode options:\n- `--port \u003Cn>` — use a different port\n- `--eval` — evaluate scripts on each rebuild (slower but shows output)\n- `--noapidocs` — skip API regeneration for faster content iteration\n\nTypical authoring workflow: run `dotnet fsdocs watch --noapidocs` for fast content iteration, then do a full `dotnet fsdocs build --clean --eval` before committing.\n\n## Common Errors and Fixes\n\n### Missing XML Documentation File\n**Symptom:** API pages are empty or missing.\n**Cause:** `GenerateDocumentationFile` not set to `true` in project properties.\n**Fix:** Add `\u003CGenerateDocumentationFile>true\u003C\u002FGenerateDocumentationFile>` to `Directory.Build.props`.\n\n### Compilation Failure During Build\n**Symptom:** `fsdocs build` fails with compile errors.\n**Cause:** Projects don't compile in Release mode, or a dependency is missing.\n**Fix:** Run `dotnet build -c Release` separately to isolate the issue.\n\n### Broken Cross-References\n**Symptom:** Warnings about unresolved `cref` links in build output.\n**Cause:** Incorrect `cref` syntax or referencing non-public members.\n**Fix:** Use fully qualified names: `cref:T:Namespace.TypeName` for types, `cref:M:Namespace.TypeName.MethodName` for methods.\n\n### Script Evaluation Failures\n**Symptom:** `.fsx` files fail during `--eval`.\n**Cause:** Missing `#r` references, runtime errors in scripts, or scripts depending on external state.\n**Fix:** Ensure all assembly references are present. Use `(*** do-not-eval ***)` for scripts that cannot be evaluated.\n\n### Missing Assembly References in .fsx\n**Symptom:** `Type not found` or `Namespace not opened` during eval.\n**Cause:** Literate scripts need explicit assembly references.\n**Fix:** Add `#r \"..\u002Fsrc\u002FMyProject\u002Fbin\u002FRelease\u002Fnet8.0\u002FMyProject.dll\"` at the top of the script.\n\n### Stale Output\n**Symptom:** Changes don't appear in the built site.\n**Cause:** Cached build output.\n**Fix:** Use `--clean` to force a fresh build.\n\n## Best Practices\n\n**DO:**\n- ✅ Always build projects in Release mode before running fsdocs\n- ✅ Use `--clean` when structure or navigation has changed\n- ✅ Use `--noapidocs` during content-only authoring for faster iteration\n- ✅ Run a full `--eval` build before committing to verify all scripts work\n- ✅ Check build output for warnings — they often indicate broken cross-references\n\n**DON'T:**\n- ❌ Skip the Release build step — fsdocs needs compiled assemblies\n- ❌ Use `--eval` in watch mode unless actively working on script output\n- ❌ Ignore cross-reference warnings — they produce broken links in the site\n- ❌ Commit the `output\u002F` directory — it is a build artifact\n- ❌ Run fsdocs from a subdirectory — always run from the solution root\n\n## Additional Resources\n\n### Utility Scripts\n- **`scripts\u002Ffsdocs-build.sh`** — Build wrapper with error handling, Release compilation, and result reporting\n\n## Implementation Workflow\n\n1. Verify `fsdocs-tool` is installed (`dotnet tool restore`)\n2. Build all projects in Release mode (`dotnet build -c Release`)\n3. Run `dotnet fsdocs build` with appropriate flags for the situation\n4. Review build output for errors and warnings\n5. Report results — pages generated, issues found, suggested fixes\n\nFocus on producing a successful build and clear diagnostics when issues arise.\n\n## Scope \u002F when to use\n\nUse this skill to **build, preview, or troubleshoot** an existing FSharp.Formatting\nsite — running `dotnet fsdocs build`, watch-mode previews, choosing flags, and\ndiagnosing build\u002Feval errors. If the project has no fsdocs setup yet, run\n[[fsdocs-setup]] first. To create the content that this skill builds, use\n[[fsdocs-api-doc]] (XML doc comments), [[fsdocs-examples]] (literate `.fsx`), or\n[[fsdocs-technical]] (Markdown). This skill is the build\u002Fdiagnose loop, not a\ncontent authoring skill.\n\n## Driven-library API\n\nThis skill drives the external **FSharp.Formatting** `dotnet fsdocs` CLI — there is\nno FS.Skia.UI backing `.fsi` surface. The driven contract is the CLI verb +\nflag surface: `build` and `watch`, with `--clean`, `--eval`, `--strict`,\n`--noapidocs`, `--nonpublic`, `--nodefaultcontent`, `--input`, `--output`,\n`--properties`, and (watch) `--port`. It depends on compiled assemblies plus their\nemitted XML doc files, so `dotnet build -c Release` is a precondition of every\nbuild.\n\n## Persistent-problem mandate\n\nfsdocs CLI flags and error messages change across tool versions, and broken\n`cref` cross-references fail silently. Consult the **official online docs first**\nfor the pinned tool version before relying on a flag documented here, and re-read\nthe live docs when a build error does not match the troubleshooting table — this is\na recurring, version-sensitive surface.\n\n## Related\n\n- [[fsdocs-setup]] — install `fsdocs-tool` and scaffold `docs\u002F` before building\n- [[fsdocs-api-doc]] — author the `\u002F\u002F\u002F` comments that become API pages\n- [[fsdocs-examples]] — literate `.fsx` scripts built with `--eval`\n- [[fsdocs-technical]] — Markdown pages picked up by the build\n\n## Sources\n\n- FSharp.Formatting documentation: https:\u002F\u002Ffsprojects.github.io\u002FFSharp.Formatting\u002F\n- Command-line \u002F `fsdocs` CLI reference: https:\u002F\u002Ffsprojects.github.io\u002FFSharp.Formatting\u002Fcommandline.html\n- FSharp.Formatting repository: https:\u002F\u002Fgithub.com\u002Ffsprojects\u002FFSharp.Formatting\n",{"name":5,"version":23,"description":7},"0.1.0","main","f943406829a9218b2882e09eb88d4ddb539c5e72",".agents\u002Fskills\u002Ffsdocs-build",0,"https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI","https:\u002F\u002Fgithub.com\u002FEHotwagner","2026-06-16 16:16:52",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add EHotwagner\u002FFS-Skia-UI --skill fsdocs-build",{"tool":37,"command":38},"bunx","bunx skills add EHotwagner\u002FFS-Skia-UI --skill fsdocs-build",{"tool":40,"command":41},"pnpm","pnpm dlx skills add EHotwagner\u002FFS-Skia-UI --skill fsdocs-build","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffsdocs-build\u002FSKILL.md",true,[45],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"scripts\u002Ffsdocs-build.sh","SCRIPT","脚本",3377,"https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Ffsdocs-build\u002Fscripts\u002Ffsdocs-build.sh",[52,59,66,73,80,87],{"skillNo":53,"name":54,"nameZh":6,"description":55,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":56,"categories":57,"keywords":58,"publishedAt":18},"01M72SGYR4T02T1HTS175E0V86","fs-skia-ui-widgets","Generated product guidance for Skia-rendered FS.Skia.UI Controls, rich text, chart controls, graph controls, DataGrid, and custom wrappers.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-ui-widgets\u002FSKILL.md",[],[],{"skillNo":60,"name":61,"nameZh":6,"description":62,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":63,"categories":64,"keywords":65,"publishedAt":18},"01M72SGVZJR1B117QK7TCC6E0J","fs-skia-testing","Assert generated-product expectations and evidence in a governed FS.Skia.UI product.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-testing\u002FSKILL.md",[],[],{"skillNo":67,"name":68,"nameZh":6,"description":69,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M72SGTC5HZYEVVVZT4X51AZ3","fs-skia-skiaviewer","Wire a generated FS.Skia.UI product to the desktop viewer host.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-skiaviewer\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M72SGS47RPYPC9JTC39CC6EF","fs-skia-scene","Build pure scene descriptions in a generated FS.Skia.UI product.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-scene\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M72SGQF4G76C4NGSF69KZRRF","fs-skia-keyboard-input","Map keyboard input to product commands in a generated FS.Skia.UI product.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-keyboard-input\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M72SGNJP3PMSS2VRP98G7Z42","fs-skia-elmish","Drive a generated FS.Skia.UI product through the pure Elmish adapter.","https:\u002F\u002Fgithub.com\u002FEHotwagner\u002FFS-Skia-UI\u002Fblob\u002Fmain\u002Ftemplate\u002Fproduct-skills\u002Ffs-skia-elmish\u002FSKILL.md",[],[]]