dist-channel-selection
Skill2 starsChanged 11 days agoMITView on GitHub
Guide for selecting the correct distribution channel (npm, Cargo, etc.) based on artifact type and target audience. Use this skill when preparing to publish or release a new version of a package — even if they just say "publish this" or "release it". Not for cicd-pipeline.
In this repository63 other files it gives its agents.
- AGENTS.mdAGENTS.md
- .agents/skills/avoid-ai-writing/AGENTS.mdAGENTS.md
- .agents/skills/do-web-doc-resolver/AGENTS.mdAGENTS.md
- .agents/skills/skill-evaluator/AGENTS.mdAGENTS.md
- scripts/AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- llms-full.txtllms.txt
- llms.txtllms.txt
- accessibility-auditorSkill
- agent-browserSkill
- agentic-abstentionSkill
- agents-mdSkill
- api-design-firstSkill
- architecture-diagramSkill
- avoid-ai-writingSkill
- cicd-pipelineSkill
- cloudflare-worker-apiSkill
- codacySkill
- codeberg-apiSkill
- code-review-assistantSkill
- css-render-performanceSkill
- database-devopsSkill
- debuggerSkill
- delegateSkill
- dependency-upgradesSkill
- docs-hookSkill
- document-rendering-and-locatorsSkill
- dogfoodSkill
- dora-reportSkill
- do-web-doc-resolverSkill
- durable-objectsSkill
- eu-ai-act-complianceSkill
- git-github-workflowSkill
- goap-agentSkill
- implementerSkill
- intent-classifierSkill
- iterative-refinementSkill
- jules-delegatorSkill
- learnSkill
- lifecycle-managementSkill
- local-context-sanitizationSkill
- memory-contextSkill
- migration-refactoringSkill
- nested-build-isolationSkill
- privacy-firstSkill
- progressive-deliverySkill
- pwa-offline-syncSkill
- reader-ui-uxSkill
- readme-best-practicesSkill
- secrets-managementSkill
- secure-invite-and-accessSkill
- security-code-auditorSkill
- shell-script-qualitySkill
- skill-creatorSkill
- skill-evaluatorSkill
- static-analysisSkill
- testing-strategySkill
- test-runnerSkill
- triz-solverSkill
- turso-dbSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Ensure artifacts are published to the correct channels with appropriate verification.
- Distinctive: line 39
Run the domain-specific verification tools (e.g., WASM size gates, LOC enforcement).
- Distinctive: line 43
Always perform a dry run before the final publish to catch packaging issues.
- Distinctive: line 47
Use the official toolchain for the selected channel.
≈ “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.
Files
Distribution Channel Selection
Ensure artifacts are published to the correct channels with appropriate verification.
When to Use
- User asks to publish or release a new version of a package
- Need to select the correct distribution channel (npm, Cargo, etc.)
- Even if they just say "publish this" or "release it"
Decision Matrix
| Artifact Type | Channel | Primary Verification | Dry Run Command |
| Rust library | crates.io | cargo test | cargo publish --dry-run |
| WASM library | npm | scripts/wasm_size_gate.sh | npm pack --dry-run |
| CLI (Node) | npm | npm test | npm pack --dry-run |
| CLI (Rust) | GitHub/npm | scripts/quality_gate.sh | cargo build --release |
Preconditions
- Version bumped in
VERSIONfile. CHANGELOG.mdupdated with new version details../scripts/quality_gate.shpasses locally.- All CI checks are green.
Publishing Process
1. Verification
Run the domain-specific verification tools (e.g., WASM size gates, LOC enforcement).
2. Dry Run
Always perform a dry run before the final publish to catch packaging issues.
3. Final Publish
Use the official toolchain for the selected channel.
Common Pitfalls
- Publishing WASM binaries without size verification.
- Forgetting to sync the
VERSIONfile across sub-packages. - Incomplete CHANGELOG leading to consumer confusion.
See Also
cicd-pipeline— CI/CD pipeline for publishinggit-github-workflow— Git workflow for releases
Rationalizations
| Rationalization | Reality |
| "I'll skip the dry run — the publish always works." | Dry runs catch packaging errors, missing files, and metadata issues that silently corrupt published artifacts. |
| "The VERSION file doesn't need to match package.json." | Version mismatches confuse consumers, break CI/CD pipelines, and invalidate changelog entries. |
Red Flags
- Publishing without running the dry-run command first
- Forgetting to update CHANGELOG.md before publishing
- Skipping quality gate checks prior to release
References
AGENTS.md- Version management policyscripts/wasm_size_gate.sh- WASM size enforcement
Voice & Context
- Default:
professional+blog - Reference:
voice-profilesskill for definitions and auto-detection.
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
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.