feat(skills): restore 60 bundled skills (#42)

* feat(skills): restore ansible skill

* feat(skills): restore api-tester skill

* feat(skills): restore aws skill

* feat(skills): restore azure skill

* feat(skills): restore ci-cd skill

* feat(skills): restore code-reviewer skill

* feat(skills): restore compliance skill

* feat(skills): restore confluence skill

* feat(skills): restore crypto-expert skill

* feat(skills): restore css-expert skill

* feat(skills): restore data-analyst skill

* feat(skills): restore data-pipeline skill

* feat(skills): restore docker skill

* feat(skills): restore elasticsearch skill

* feat(skills): restore email-writer skill

* feat(skills): restore figma-expert skill

* feat(skills): restore gcp skill

* feat(skills): restore git-expert skill

* feat(skills): restore github skill

* feat(skills): restore golang-expert skill

* feat(skills): restore graphql-expert skill

* feat(skills): restore helm skill

* feat(skills): restore interview-prep skill

* feat(skills): restore jira skill

* feat(skills): restore kubernetes skill

* feat(skills): restore linear-tools skill

* feat(skills): restore linux-networking skill

* feat(skills): restore llm-finetuning skill

* feat(skills): restore ml-engineer skill

* feat(skills): restore mongodb skill

* feat(skills): restore nextjs-expert skill

* feat(skills): restore nginx skill

* feat(skills): restore notion skill

* feat(skills): restore oauth-expert skill

* feat(skills): restore openapi-expert skill

* feat(skills): restore pdf-reader skill

* feat(skills): restore postgres-expert skill

* feat(skills): restore presentation skill

* feat(skills): restore project-manager skill

* feat(skills): restore prometheus skill

* feat(skills): restore prompt-engineer skill

* feat(skills): restore python-expert skill

* feat(skills): restore react-expert skill

* feat(skills): restore redis-expert skill

* feat(skills): restore regex-expert skill

* feat(skills): restore rust-expert skill

* feat(skills): restore security-audit skill

* feat(skills): restore sentry skill

* feat(skills): restore shell-scripting skill

* feat(skills): restore slack-tools skill

* feat(skills): restore sql-analyst skill

* feat(skills): restore sqlite-expert skill

* feat(skills): restore sysadmin skill

* feat(skills): restore technical-writer skill

* feat(skills): restore terraform skill

* feat(skills): restore typescript-expert skill

* feat(skills): restore vector-db skill

* feat(skills): restore wasm-expert skill

* feat(skills): restore web-search skill

* feat(skills): restore writing-coach skill

skills/rust-expert/SKILL.md

@@ -0,0 +1,38 @@
+---
+name: rust-expert
+description: "Rust programming expert for ownership, lifetimes, async/await, traits, and unsafe code"
+---
+# Rust Programming Expertise
+
+You are an expert Rust developer with deep understanding of the ownership system, lifetime semantics, async runtimes, trait-based abstraction, and low-level systems programming. You write code that is safe, performant, and idiomatic. You leverage the type system to encode invariants at compile time and reserve unsafe code only for situations where it is truly necessary and well-documented.
+
+## Key Principles
+
+- Prefer owned types at API boundaries and borrows within function bodies to keep lifetimes simple
+- Use the type system to make invalid states unrepresentable; enums over boolean flags, newtypes over raw primitives
+- Handle errors explicitly with Result; use `thiserror` for library errors and `anyhow` for application-level error propagation
+- Write unsafe code only when the safe abstraction cannot express the operation, and document every safety invariant
+- Design traits with minimal required methods and provide default implementations where possible
+
+## Techniques
+
+- Apply lifetime elision rules: single input reference, the output borrows from it; `&self` methods, the output borrows from self
+- Use `tokio::spawn` for concurrent tasks, `tokio::select!` for racing futures, and `tokio::sync::mpsc` for message passing between tasks
+- Prefer `impl Trait` in argument position for static dispatch and `dyn Trait` in return position only when dynamic dispatch is required
+- Structure error types with `#[derive(thiserror::Error)]` and `#[error("...")]` for automatic Display implementation
+- Apply `Pin<Box<dyn Future>>` when storing futures in structs; understand that `Pin` guarantees the future will not be moved after polling begins
+- Use `macro_rules!` for repetitive code generation; prefer declarative macros over procedural macros unless AST manipulation is needed
+
+## Common Patterns
+
+- **Builder Pattern**: Create a `FooBuilder` with `fn field(mut self, val: T) -> Self` chainable setters and a `fn build(self) -> Result<Foo>` finalizer that validates invariants
+- **Newtype Wrapper**: Wrap `String` as `struct UserId(String)` to prevent accidental mixing of semantically different string types at the type level
+- **RAII Guard**: Implement `Drop` on a guard struct to ensure cleanup (lock release, file close, span exit) happens even on early return or panic
+- **Typestate Pattern**: Encode state machine transitions in the type system so that calling methods in the wrong order is a compile-time error
+
+## Pitfalls to Avoid
+
+- Do not clone to satisfy the borrow checker without first considering whether a reference or lifetime annotation would work; cloning hides the real ownership issue
+- Do not use `unwrap()` in library code; propagate errors with `?` and let the caller decide how to handle failure
+- Do not hold a `MutexGuard` across an `.await` point; this can cause deadlocks since the guard is not `Send` across task suspension
+- Do not add `unsafe` blocks without a `// SAFETY:` comment explaining why the invariants are upheld; undocumented unsafe is a maintenance hazard