rust-worker

Coordinate Rust-based CLI migrations with cargo tests and Go verification workflows.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/Mario-pereyra/mapj --skill rust-worker
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: rust-worker
Source: https://github.com/Mario-pereyra/mapj/tree/main/.factory/skills/rust-worker
Command: npx skills add https://github.com/Mario-pereyra/mapj --skill rust-worker

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Rust implementation worker for mapj CLI migration coordinates the end-to-end shift from Go to Rust, enabling improved performance, maintainability, and consistent worker behavior across the CLI project.

Core Features & Use Cases

  • Project structure setup
  • CLI commands with clap
  • Output formatters (LLM, TOON, Auto)
  • Authentication and credential storage
  • TDN search and Confluence export
  • Protheus SQL query and connection management
  • Preset system with parameter handling

Quick Start

Read the feature description, review the Go implementation for reference, write tests first, then implement the Rust code to satisfy all features.

Frequently Asked Questions about rust-worker

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

FAQPage Schema
How do I migrate a Go CLI application to Rust?

To migrate a Go CLI to Rust, use a structured worker to coordinate setup, execution, and verification. The process requires writing tests first, implementing Rust code incrementally, and verifying behavior against the existing Go reference implementation.

What is the best way to structure a Rust CLI migration using cargo?

The best way to structure a Rust CLI migration with cargo is to follow a feature workflow: read the feature description, review the Go implementation, write tests first, then implement the Rust code to satisfy all features and run cargo checks.

Does the Rust worker migration support CLI commands with clap and output formatters?

Yes, the Rust worker migration supports CLI commands with clap and includes output formatters for LLM, TOON, and Auto formats. It also handles authentication, credential storage, and parameter handling within the preset system.

Why should I use a test-first approach when shifting CLI tooling from Go to Rust?

A test-first approach is required when shifting CLI tooling from Go to Rust to ensure consistent worker behavior and maintainability. Writing tests before implementation allows you to verify the new Rust code directly against the existing Go reference behavior.

Do I need the Rust toolchain and cargo test to verify CLI component migration?

Yes, the Rust toolchain and cargo test are required to verify CLI component migration. The worker coordinates setup, execution, and verification by applying cargo checks and running tests to ensure the new Rust implementation matches the Go behavior.