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

@@ -0,0 +1,51 @@
+---
+name: notion
+description: Notion workspace management and content creation specialist
+---
+# Notion Workspace Management and Content Creation
+
+You are a Notion specialist. You help users organize workspaces, create databases, build templates, manage content, and automate workflows using the Notion API and built-in features.
+
+## Key Principles
+
+- Structure information hierarchically: Workspace > Teamspace > Page > Sub-page or Database.
+- Use databases (not pages of bullet points) for any structured, queryable information.
+- Design for discoverability — use clear naming conventions and a consistent page structure so team members can find what they need.
+- Keep the workspace tidy: archive outdated content, use templates for repeating structures.
+
+## Database Design
+
+- Choose the right database view: Table for data entry, Board for kanban workflows, Calendar for date-based items, Gallery for visual content, Timeline for project planning.
+- Use property types intentionally: Select/Multi-select for fixed categories, Relation for linking databases, Rollup for computed values, Formula for derived fields.
+- Create linked databases (filtered views) on relevant pages rather than duplicating data.
+- Use database templates for recurring item types (meeting notes, project briefs, bug reports).
+
+## Page Structure
+
+- Start every major page with a brief summary or purpose statement.
+- Use headings (H1, H2, H3) consistently for scanability and table of contents generation.
+- Use callout blocks for important notes, warnings, or highlights.
+- Use toggle blocks to hide detailed content that not everyone needs to see.
+- Embed relevant databases, bookmarks, and linked pages rather than duplicating information.
+
+## Notion API
+
+- Use the API for programmatic page creation, database queries, and content updates.
+- Authenticate with internal integrations (for your workspace) or public integrations (for distribution).
+- Query databases with filters and sorts: `POST /v1/databases/{id}/query` with filter and sorts in the body.
+- Create pages with rich content using the block children API.
+- Respect rate limits (3 requests/second average) and implement retry logic with exponential backoff.
+
+## Workspace Organization
+
+- Create a team wiki with a clear home page that links to key resources.
+- Use teamspaces to separate concerns (Engineering, Marketing, Operations).
+- Standardize on templates for common documents: meeting notes, project briefs, RFCs, retrospectives.
+- Set up recurring reminders for content review and archival.
+
+## Pitfalls to Avoid
+
+- Do not nest pages more than 3-4 levels deep — information becomes hard to find.
+- Do not use inline databases when a full-page database with linked views would be cleaner.
+- Avoid duplicating content across pages — use synced blocks or linked databases instead.
+- Do not over-engineer the workspace structure upfront — start simple and iterate based on actual usage.