One-click install
npx skills add https://github.com/commontoolsinc/labs --skill ct
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ct
Source: https://github.com/commontoolsinc/labs/tree/main/.claude/skills/ct
Command: npx skills add https://github.com/commontoolsinc/labs --skill ct

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Interacting with a distributed computing platform like CommonTools, managing deployed instances (charms), and orchestrating data flows can be complex. This skill provides a comprehensive guide to the ct command-line interface, simplifying deployment, management, and debugging of reactive recipes and charms.

Core Features & Use Cases

  • Charm Lifecycle Management: Deploy new recipes, update existing charms, and inspect their state with clear commands.
  • Reactive Data Linking: Establish dynamic data flows between charms, enabling complex, automated workflows.
  • Local Recipe Testing: Rapidly iterate and debug recipes locally using ct dev before deployment.
  • Use Case: A developer has built a new recipe and needs to deploy it to a CommonTools space, link its output to another existing charm, and then inspect the data flow. This skill provides the exact ct commands and best practices to achieve this efficiently.

Quick Start

Type check and execute a recipe locally:

./dist/ct dev ./recipe.tsx

Frequently Asked Questions about ct

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

FAQPage Schema
How do I deploy a recipe as a charm using the CommonTools CLI?

Deploy a recipe as a charm using `ct charm new` to create a new charm from your recipe, then use `ct charm set` to update its configuration. The `ct` CLI automates deployment and management of recipes to your CommonTools space with JSON-based configuration values.

How do I link charms to create reactive data flows between them?

Establish reactive data flows by using `ct charm link` to connect the output of one charm to the input of another. This enables automated, distributed computing workflows where data updates propagate dynamically across linked charms in your CommonTools space.

What commands are available in the ct CLI for managing deployed charms?

Core ct commands include `charm ls` to list deployed charms, `charm get` to retrieve values, `charm call` to invoke operations, `charm inspect` to view charm state, and `charm map` to visualize charm relationships and data flows within your deployment.

How do I test and debug a recipe locally before deploying it?

Use `ct dev ./recipe.tsx` to type-check and execute a recipe locally in your development workflow. This enables rapid iteration and debugging of recipes before deployment to CommonTools, reducing deployment failures and validation errors.

What setup is required to use the ct CLI with CommonTools?

Initialize the ct CLI with `deno task ct setup`, providing an identity key (claude.key), API URL, and target space. This prerequisite configuration establishes authentication and connection parameters required for all charm lifecycle and data-linking operations.

Does the ct CLI enforce JSON values for charm configuration?

Yes, the ct CLI requires JSON values for charm configuration and includes built-in `--help` guidance to validate and format inputs correctly. This ensures consistent, machine-readable charm state across your distributed computing platform.