87 skills · sorted by relevance
Use when proofreading, copy-editing, or verifying English in any docs/**/*.mdx chapter or code comment in this repo. Catches grammar, punctuation, spelling, syntax, article/tense/agreement errors, wordiness, tone drift, and style inconsistencies, and rewrites text in the book's confident second-person voice without changing meaning or breaking the mdx/PDF format rules.
The English summary is being prepared. Showing the original description.
Use whenever creating, renaming, or editing any file under docs/ in this repo, or when asked to compile/build the book PDF. Enforces the exact .mdx frontmatter, ID scheme, and heading-depth rules required by the go-pretty-pdf tool (https://github.com/sazardev/go-pretty-pdf) so the whole book keeps compiling.
The English summary is being prepared. Showing the original description.
Use when building content-heavy sites with Astro, deciding between SSG/SSR/hybrid, choosing client directives (idle/visible/load/media), structuring content collections with type-safe schemas, integrating React/Vue/Solid/Svelte components in the same project, or migrating from Next.js for marketing/docs. Triggers: client:idle vs client:load tradeoffs, content collections schema with zod, image optimization via @astrojs/image, view transitions, server islands, MDX layouts. NOT for SPA-style apps that need full interactivity (use Next/Remix), Astro internals/plugin authoring, or non-content sites where islands provide no benefit.
The English summary is being prepared. Showing the original description.
Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support.
The English summary is being prepared. Showing the original description.
Reference for Astro — the core web framework the gatOS docs site (under site/) is built on. Use this when authoring or editing pages in site/, working with .astro/.md/.mdx files, content collections, the astro.config.mjs, or component/JSX-in-Markdown mechanics. Covers Astro component anatomy, using components in MDX, content collections, frontmatter, imports, expressions, and the build/dev commands — enough to work the site without leaving the repo. Pair with the `starlight` skill (the docs theme + its components) and the `tutorials` skill (the gatOS house style).
The English summary is being prepared. Showing the original description.
Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support.
The English summary is being prepared. Showing the original description.
Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support.
The English summary is being prepared. Showing the original description.
Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support.
The English summary is being prepared. Showing the original description.
Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support.
The English summary is being prepared. Showing the original description.
Use when building content-heavy sites with Astro, deciding between SSG/SSR/hybrid, choosing client directives (idle/visible/load/media), structuring content collections with type-safe schemas, integrating React/Vue/Solid/Svelte components in the same project, or migrating from Next.js for marketing/docs. Triggers: client:idle vs client:load tradeoffs, content collections schema with zod, image optimization via @astrojs/image, view transitions, server islands, MDX layouts. NOT for SPA-style apps that need full interactivity (use Next/Remix), Astro internals/plugin authoring, or non-content sites where islands provide no benefit.
The English summary is being prepared. Showing the original description.
Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support.
The English summary is being prepared. Showing the original description.
Reorganize existing OpenClaw documentation while checking behavior against source code, schemas, and tests. Preserve accurate details, move reference material to suitable pages, and verify formatting and links so readers can follow the main workflow.
Review, improve, rewrite, or draft Storybook documentation in /docs. Assess each page’s purpose, audience, structure, and examples, then make suitable edits or provide a content plan, with formatting checks after changes.
Maintain visual snapshot tests, which compare rendered images, for Remotion’s web renderer. Update existing tests after implementation changes, or add explicitly requested tests with sample components, preview registration, and documentation updates for supported properties.
Find the relevant guidance for writing Remotion animations that agents can understand and that remain editable in Studio’s Visual Mode. It points to resources for scene structure, editable styles and animations, and interactive custom components.
Add a text-to-speech engine to Voicebox through dependency research, backend implementation, interface updates, and packaging. The workflow covers development checks and verification of the packaged application before handing the build over for local testing.
Keep the CopilotKit Intelligence documentation landing page aligned with feature and guide changes. It coordinates feature cards, links, navigation, and related tests so readers can find current guides after additions, moves, renames, or removals.
Close a NemoClaw maintenance day by consolidating documentation and changelog updates, reviewing merged and unfinished work, and preparing a release handoff. When requested, pass the version to the dedicated skill that verifies and creates the release tag.
Review recent Git commits to find changes that affect users, then update the relevant documentation pages. Identify missing pages, explain changed behavior or migration steps, and validate the resulting documentation with the project's build tools.
Update documentation to match source changes on the current branch. Map changed files to existing pages, verify behavior against the code, revise affected references and examples, and report missing documentation using repository-specific mapping rules.
Write, review, and edit developer documentation for SDKs, libraries, and frameworks. Organize guides, API references, and code examples around readers’ tasks, checking technical claims against source code and official documentation while following the destination site’s conventions.
Authoritative agent-runtime contract for working inside an OpenKnowledge project — a markdown-CRDT knowledge base exposed over MCP. Use whenever reading, listing, searching, editing, or linting any `.md` or `.mdx` file in the project, and before any `mcp__open-knowledge*` tool call (`exec`, `search`, `write`, `edit`, `lint`, and the rest). Installed by `ok init`, so its presence means this is an OpenKnowledge project and it governs every markdown file here. Covers the read/write tool surface, grounding and linking rules, folder/template conventions, the live browser preview, and the rule that OK's MCP tools — never native file tools — handle in-scope markdown.
The English summary is being prepared. Showing the original description.
Guides for writing and editing Remotion documentation. Use when adding docs pages, editing MDX files in packages/docs, or writing documentation content.
The English summary is being prepared. Showing the original description.
Write documentation following Metabase's conversational, clear, and user-focused style. Use when creating or editing documentation files (markdown, MDX, etc.).
The English summary is being prepared. Showing the original description.