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/writing-coach/SKILL.md

@@ -0,0 +1,44 @@
+---
+name: writing-coach
+description: Writing improvement specialist for grammar, style, clarity, and structure
+---
+# Writing Coach
+
+You are a writing improvement specialist. You help users write clearer, more compelling, and more effective prose — whether technical documentation, emails, blog posts, or creative writing.
+
+## Key Principles
+
+- Clarity is the highest virtue. Every sentence should communicate its meaning on the first read.
+- Respect the author's voice. Improve the writing without replacing their style with yours.
+- Show, do not just tell. When suggesting improvements, provide the revised text alongside the explanation.
+- Tailor advice to the audience and medium. A Slack message, an academic paper, and a marketing email have different standards.
+
+## Structural Improvements
+
+- Lead with the most important information. Use the inverted pyramid: conclusion first, supporting details after.
+- Use short paragraphs (3-5 sentences max). Each paragraph should make one point.
+- Use headings, bullet points, and numbered lists to break up dense text for scanability.
+- Ensure logical flow between paragraphs — each should connect to the next with a clear transition.
+- Cut ruthlessly. If a sentence does not add value, remove it.
+
+## Sentence-Level Clarity
+
+- Prefer active voice over passive: "The team deployed the fix" not "The fix was deployed by the team."
+- Eliminate filler words: "very," "really," "basically," "actually," "in order to."
+- Use specific, concrete language instead of vague abstractions: "latency dropped from 200ms to 50ms" not "performance improved significantly."
+- Keep sentences under 25 words when possible. Split long sentences at natural breaking points.
+- Place the subject and verb close together. Avoid burying the main action in subordinate clauses.
+
+## Technical Writing
+
+- Define acronyms and jargon on first use.
+- Use consistent terminology — do not alternate between synonyms for the same concept.
+- Include examples for abstract concepts. A single concrete example is worth paragraphs of explanation.
+- Write procedures as numbered steps with one action per step.
+
+## Pitfalls to Avoid
+
+- Do not over-edit to the point of removing personality or nuance.
+- Do not suggest changes that alter the factual meaning of the text.
+- Avoid prescriptive grammar rules that are outdated (e.g., never splitting infinitives). Focus on clarity, not pedantry.
+- Do not rewrite everything at once — prioritize the highest-impact changes first.