dist-channel-selection

Select distribution channels for Rust crates, WASM npm, and CLI npm artifacts.

4|Updated Feb 15, 2026
One-click install
npx skills add https://github.com/d-o-hub/chaotic_semantic_memory --skill dist-channel-selection
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dist-channel-selection
Source: https://github.com/d-o-hub/chaotic_semantic_memory/tree/main/.agents/skills/dist-channel-selection
Command: npx skills add https://github.com/d-o-hub/chaotic_semantic_memory --skill dist-channel-selection

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Artifact-aware decision logic for selecting the correct distribution channel (cargo crate vs WASM npm vs CLI npm). Use when validating, installing, or publishing.

Core Features & Use Cases

  • Matrix-driven channel selection across crates.io, npm WASM, and npm CLI
  • Canonical artifact paths and recommended workflows for each channel
  • Real-world scenarios: validating a release, publishing a new artifact, installing across environments

Quick Start

Identify the target artifact and apply the decision matrix to select the correct distribution channel.

Frequently Asked Questions about dist-channel-selection

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

FAQPage Schema
How do I choose the right distribution channel for a Rust crate or WASM npm package?

Choosing the right distribution channel requires applying a decision matrix that checks artifact types and maps Rust outputs to crates.io, while routing WASM and CLI packages to the appropriate npm registries for publishing.

What is the best way to publish multi-artifact projects across Rust and npm?

The best way to publish multi-artifact projects is using explicit artifact-type checks to route Rust binaries to crates.io and CLI or WASM outputs to npm, applying canonical paths during the installation workflow.

When do I need to select between crates.io and npm for my artifact release?

You need to select between crates.io and npm when validating a release or setting up environments for multi-artifact projects, using artifact-aware decision logic to match the build output with its correct registry.

How does artifact-aware channel selection work for WASM and CLI npm distributions?

Artifact-aware channel selection works by implementing explicit artifact-type checks that distinguish WASM targets from CLI packages, mapping each build output to the correct npm distribution channel with environment setup guidance.

Can I use a single decision matrix for validating and installing both Rust and WASM artifacts?

Yes, you can use a single matrix-driven channel selection process for validating and installing both Rust and WASM artifacts, providing canonical paths and recommended workflows for each specific registry.