agentleFS
leafyoungleafyoung/shared_skills/rust-harden/SKILL.md

rust-harden

Skill2 starsChanged 2 months agoNo licenceView on GitHub

This skill should be used when the user asks to "harden Rust code for production", "make Rust production-ready", "prevent Rust panics in production", "set up panic hooks", "configure panic = abort", "harden a Rust web service", "secure Rust Docker images", "add Landlock sandboxing", "drop privileges in Rust", "add circuit breakers", "set resource limits on Rust services", "add health checks and readiness probes", "graceful shutdown in Rust", "audit Rust dependencies", "use mimalloc secure allocator", "run Miri on Rust code", "test Rust release builds", "prevent stack overflows in Rust", or mentions production hardening, runtime resilience, failure modes, supply-chain security, or operational robustness for Rust programs. Use this skill whenever the user wants to make Rust code resilient at runtime, reduce its attack surface, or prepare it for production deployment.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 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.

  • 0

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “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.

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.