Sammlung rust

Rust KI-Tools für System-Workflows und Engineering-Zuverlässigkeit | AI Agent Skills

Installierbare AI Agent Skills für rust systems reliability Developer Workflows in Claude Code, Cursor und Windsurf.

Diese Rust-Sammlung konzentriert sich auf systemnahe Entwickler-Workflows: verlässliches Tooling aufbauen, Performance optimieren, Reliability-Checks durchsetzen und Release-Pipelines sicher automatisieren. Statt eines Server-Rankings stehen praktische Engineering-Skills im Vordergrund, die Korrektheit, Observability und Betriebsstabilität in Produktion verbessern. MCP-kompatible Integrationen können ergänzend vorkommen, bleiben aber nachgeordnet gegenüber dem Hauptziel: zuverlässige und performante Softwarelieferung.

Page-Level Review Standard

This Page Is a Curated Decision Surface, Not Just a Themed List

A collection page should not just add more cards to the screen. It should explain why these skills belong together, how the next step moves into installation and validation, and which path should continue the decision afterwards.

Reviewed On

2026-04-17

Maintained By

Killer-Skills editorial review within the recovery-focused authority queue.

Verification

Validate installability, operator clarity, workflow fit, and maintainer trust before retaining or adding an entry.

Primary Audience

High-intent users who roughly know the direction and need a faster path to an installable shortlist.

Three Minimum Standards For This Collection

- A collection page must narrow users into a better shortlist instead of flattening more repositories onto the screen.
- The next click should continue into installation docs, CLI validation, or a better-fit solution page instead of resetting back to a broad directory.
- This page only becomes a real first-party judgment surface when its selection logic, maintenance posture, and delivery path are all visible.

Primary Install Bridge

Pick One Skill, Then Take the Install Path

This collection should not trap users in comparison mode or pretend to install the whole collection. Its job is to narrow the shortlist to one skill, then send the next click into installation, validation, and rollout. Installation happens on the skill path.

Step 1 / Primary Path

Step 1: Open the installation docs

Move from Rust discovery into the install flow, validation checklist, and first command path before comparing anything else.

Open the Install Path

Best-Fit Next Paths

The Next Click Should Keep Narrowing, Not Reset Back To A Generic Directory

Once the install path is clear, move into the solution, CLI, or editorial surface that best matches this collection. That keeps platform, framework, and operations demand narrowing into a more verifiable high-intent journey.

P1 solution

Process Automation Solution

A solution page for teams turning SOPs, handoffs, and operations into repeatable AI-assisted execution paths.

Operational intent deserves a stronger bridge than generic tooling lists can provide.

P1 solution

Data Extraction Solution

A solution page for ETL, structured output, reporting pipelines, and data-heavy automation work.

Data-heavy search demand is easier to recover through focused solution pages than through generic directories.

Editorial Proof & Trust Signals

Why This Collection Deserves Priority Attention

Reviewed on 2026-04-17 against Rust workflow fit, installation clarity, operator handoff, and systems engineering usefulness. This page is now positioned as an install-first Rust entry point instead of a broad language roundup.

We prioritize this page because Rust-intent users usually need a shortlist they can install, validate, and carry into real reliability and release loops quickly.

Trust Signals

- Entries are chosen for practical Rust workflow value such as reliability checks, performance-sensitive delivery, release automation, and operational clarity.
- Selection favors tools with public documentation and clear setup paths that teams can validate before wider rollout.
- The page is curated for repeatable systems engineering, not for vague language keyword coverage or generic repository popularity.

Grouping Logic

- Lead with tools that can enter a Rust-centered workflow without adding heavy setup ambiguity.
- Keep the shortlist compact enough for quick comparison while still covering reliability, release, review, and performance support.
- Use installation as the bridge from Rust discovery into validated daily execution.

Maintenance & Review

Last Reviewed: 2026-04-17
Cadence: Re-check when install flow, maintainer posture, or Rust workflow relevance changes upstream; otherwise review monthly.
Maintained By: Killer-Skills editorial review within the recovery-focused authority queue.
Verification: Validate installability, operator clarity, workflow fit, and maintainer trust before retaining or adding an entry.

Execution Examples

How These Skills Work Together In Practice

Install one Rust workflow tool first

Use this page when you want one Rust companion that can enter real systems work without turning evaluation into another endless toolchain comparison.

1. Open the installation docs before opening more Rust-related repositories.
2. Choose one tool that best supports reliability, release, review, or performance-sensitive work.
3. Install it and verify the CLI write path, sync behavior, and first operator checkpoint.
4. Only after the base path works, expand the setup across the wider Rust workflow.

Tighten a Rust release loop

Treat the collection as an editorial filter when you need Rust-adjacent tools that improve engineering confidence without overcomplicating the stack.

1. Check whether the tool has stable ownership and visible install guidance.
2. Review CLI behavior so operators know what will be written and synced.
3. Use one validated path before scaling it to more crates, services, or teammates.
4. Document the chosen Rust workflow baseline after the first clean rollout.

After Installation

Supporting Moves After The Install Path Is Clear

Step 2

Step 2: Check CLI write and sync behavior

Confirm what the CLI writes, how sync behaves, and what operators should validate after the install path is clear.

Step 3

Step 3: Cross-check with trusted tools

Use the official trusted collection to sanity-check workflow choices before you standardize a team stack.

declutter

wildcard

caro: fast Rust CLI that turns natural‑language tasks into a safe POSIX command. Built for macOS (MLX/Metal) with a built‑in model; supports vLLM/Ollama/LM Studio. JSON‑only output, safety checks, confirmation, multi‑step goals, devcontainer included.

★ 27

⑂ 0

Künstliche Intelligenz

fix-repo

Improve a specific repos corpus conformance by fixing its top diverging cops in parallel using worktree-isolated teammates.

★ 1

⑂ 0

Entwickler

mag123c

Session start - check progress, suggest next task

★ 55

⑂ 0

Entwickler

github-release

decentpaste

Create a GitHub release with auto-generated release notes from commits since the last tag. Uses conventional commits to categorize changes into Features, Bug Fixes, and maintenance sections.

★ 156

⑂ 0

Security

triage

Rank cops by FP+FN from the corpus oracle to find the next batch to fix

★ 1

⑂ 0

Entwickler

openlark-code-standards

foxzool

OpenLark 项目代码规范检查技能。用于快速审查仓库内的架构一致性、API 实现套路、参数校验、命名与导出规范，并输出可执行检查清单与证据路径。

★ 66

⑂ 0

Entwickler

Related Authority Collections

If This Page Is Close, Keep Narrowing With Related Authority Collections

Do not reset back to the generic directory. Move sideways through these adjacent high-intent collections to narrow the shortlist toward the install path that best matches your team.

P1 collection

DevOps Workflow Tools to Install First

An operations-first collection for platform teams choosing release, incident, and automation helpers.

Operational intent is high value and should be routed into curated workflow picks instead of generic tool sprawl.

P1 collection

Agent Framework Tools to Install First

A framework and SDK collection for teams building agent foundations, not just browsing vendor names.

Framework intent strengthens the site's product judgment and reduces the mirror-site posture.

P2 collection

Community Skills to Install First

A community-tested collection for builders who want reusable skills without falling back to unfiltered repository browsing.

Community demand can still look authoritative when it is filtered through explicit curation and rollout logic.

P1 collection

TypeScript Workflow Tools to Install First

A typed-development collection that helps product teams shortlist TypeScript workflow tools with clear next steps.

TypeScript intent is strong enough to support a dedicated authority page instead of another mixed language roundup.

Installation Questions

Answer These Three Questions Before You Install

This collection should not keep users browsing forever. These three questions explain how to shortlist, install, and validate the next step.

Für welche Workflows sind diese Sammlungen gedacht?

Diese Sammlungen sind rund um Workflow-Automatisierung, Prozessautomatisierung, Dokumentenoperationen, Datenworkflows und wiederverwendbare Skill-Stacks aufgebaut.

Was unterscheidet eine Sammlung vom Hauptverzeichnis?

Das Verzeichnis eignet sich besser für direkte Suche, während Sammlungen komplementäre Skills um einen vollständigen Workflow bündeln.

Kann ich diese Sammlungen für Claude Code oder Cursor installieren?

Ja. Die Skills in diesen Sammlungen funktionieren in der Regel in Claude Code, Cursor, Windsurf und anderen unterstützten Umgebungen über einen einheitlichen Installationsablauf.

Additional Next Paths

Use These Additional Paths If You Need One More Step To Narrow The Decision

These are the supporting surfaces for this collection after the install direction is clear and the primary next paths have already narrowed the decision.

P1 solution

Agent Workflows Solution

A scenario page for users who already know the workflow problem they need to solve.

High-intent solution pages are safer recovery surfaces than broad skill detail expansion.

P1 solution

Workflow Automation Solution

A use-case page for users searching for repeatable automation patterns instead of one-off tools.

Workflow automation demand is easier to satisfy with curated intent clusters than with flat directory coverage.