agentleFS
cosmonic-labscosmonic-labs/skills/wash/SKILL.md

wash

Skill21 starsChanged 31 days agoApache-2.0View on GitHub

Expert in wasmCloud Shell (wash) CLI tool for building, running, and managing WebAssembly components and wasmCloud applications. Use this skill when working with wasmCloud, WebAssembly components, WIT (WebAssembly Interface Types) definitions, or wash commands.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 1 is distinctive, and 6 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Verify version with: wash --version

    line 14
  2. Very specific:

    Use wash build or wash dev for building components

    line 19
  3. Very specific:

    Use wash dev for local development and build loop.

    line 26
  4. Very specific:

    Use wash wit update when there are mismatched WIT (WebAssembly Interface Types) definitions.

    line 38
  5. Very specific:

    Run wash build to build the code

    line 54
  6. Distinctive:

    If you encounter errors about mismatched WIT definitions:

    line 79
  7. Very specific:

    Run wash wit update to synchronize definitions

    line 81

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

wash - wasmCloud Shell

This skill provides expertise in using the wasmCloud Shell (wash) CLI tool for developing and managing WebAssembly components and wasmCloud applications.

Prerequisites

  • wash version 2.0.0 or later
  • Verify version with: wash --version

Important Notes

Do not use cargo component commands (like cargo component build) when working with wasmCloud projects. Always use wash commands instead:

  • Use wash build or wash dev for building components
  • For plugins, build with wash build --skip-fetch (since wasmcloud:wash interface isn't published)

Core Commands

wash dev

Use wash dev for local development and build loop. This command:

  • Automatically rebuilds your component on file changes
  • Provides a fast iteration cycle during development
  • Watches for changes and recompiles as needed

Example:

wash dev

wash wit update

Use wash wit update when there are mismatched WIT (WebAssembly Interface Types) definitions. This command:

  • Updates WIT dependencies to resolve conflicts
  • Synchronizes WIT definitions across your project
  • Fixes version mismatches in component interfaces

Example:

wash wit update

Common Workflows

Starting a New Project using the HTTP Hello World template

  1. wash new https://github.com/wasmCloud/wasmCloud.git --name http-hello-world --subfolder templates/http-hello-world
  2. cd my-project
  3. Run wash build to build the code
  4. Make changes to your code

Expected Component Structure

A modern wash new Rust HTTP component can follow this structure:

|
|-- .wash/
|   -- config.yaml
|-- manifests/
|   -- workloaddeployment.yaml
|-- src/
|   -- lib.rs
|-- wit/
|   -- world.wit
|-- Cargo.toml
|-- Cargo.lock
|-- wkg.lock
|-- README.md

Fixing WIT Definition Conflicts

If you encounter errors about mismatched WIT definitions:

  1. Run wash wit update to synchronize definitions
  2. Review the updated WIT files
  3. Continue with wash build

Additional Resources

  • wash is the primary CLI tool for the wasmCloud ecosystem
  • It handles component building, testing, and deployment
  • Supports both local development and production workflows

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.