tutorials

Guide gatOS tutorial authoring with style, dual-transport, and snippets.

13|1|Updated Jun 12, 2026
One-click install
npx skills add https://github.com/meow-sci/gatOS --skill tutorials
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tutorials
Source: https://github.com/meow-sci/gatOS/tree/main/.claude/skills/tutorials
Command: npx skills add https://github.com/meow-sci/gatOS --skill tutorials

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires starlight, astro, purrTTY, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill solves the problem of creating clear, informative, and effective tutorial content for the gatOS documentation. It provides the structure, style, and tools needed to write tutorials that are easy to understand and follow.

Core Features & Use Cases

  • Structured Authoring Guide: Offers a step-by-step guide to creating high-quality tutorials following the gatOS style guide.
  • Dual-Transport Convention: Ensures tutorials cover both filesystem and HTTP APIs, making them applicable in various scenarios.
  • Reusable Code Snippets: Provides a library of code snippets to streamline the writing process and maintain consistency across tutorials.
  • Use Case: If you need to write a tutorial that demonstrates how to control a vessel's attitude in gatOS using the filesystem or HTTP API, this skill helps you structure the tutorial, provide examples, and link to relevant resources.

Quick Start

Run the 'tutorials' skill and follow the guide to write a new tutorial about a specific gatOS feature or workflow.

Frequently Asked Questions about tutorials

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I write a gatOS tutorial that covers both the filesystem and HTTP API?

To write a gatOS tutorial covering both APIs, use the dual-transport convention outlined in the authoring guide. This approach structures your content to demonstrate filesystem and HTTP API interactions side-by-side, ensuring readers understand both methods.

What is the best way to structure technical writing for gatOS documentation?

The best way to structure gatOS technical writing is by following a specific tutorial progression and style guide. This ensures your documentation maintains a clear, informative flow with reusable code snippets that integrate seamlessly into the gatOS ecosystem.

Do I need to understand the gatOS filesystem API before authoring a guide?

Yes, understanding the gatOS filesystem and HTTP API is required before authoring a guide. The skill is optimized for the gatOS documentation ecosystem and assumes prerequisite knowledge to properly utilize the structured authoring guide and code snippets.

Can I use Astro and Starlight to build gatOS tutorials?

Yes, you can use Astro and Starlight to build gatOS tutorials, as they are listed as core dependencies. The skill utilizes these frameworks alongside the purrTTY tool to support the authoring process and manage the documentation assets effectively.

How do I include reusable code snippets when writing a gatOS guide?

To include reusable code snippets when writing a gatOS guide, access the library provided by this skill. It streamlines the writing process by offering pre-built examples that maintain consistency across the filesystem and HTTP API demonstrations in your tutorials.

Why does my gatOS tutorial need a dual-transport convention?

Your gatOS tutorial needs a dual-transport convention to ensure it covers both filesystem and HTTP APIs, making it applicable in various scenarios. This convention guarantees that readers can follow the workflow regardless of their preferred interaction method.