Loading...
Loading...
Found 890 Skills
This skill should be used when the user asks to "review my resume", "check my resume", "analyze my resume", "scan my resume for AI", "is my resume AI-sounding", "how does my resume look", or wants feedback on resume quality, structure, tone, or ATS readiness. Works for all resume and CV types: standard US, federal, academic, legal, medical, consulting, tech, executive, military transition, education, nonprofit, trades, creative, investment banking, and EU/Europass formats. Entry-level through executive.
Headless spreadsheet engine for financial modeling, data analysis, and scenario comparison. Use when: building financial models with ratios and what-if scenarios, computing derived values from tabular data with formulas, producing .xlsx files with live formulas (not static values) for human review, any task where the agent would otherwise write imperative code to manipulate numbers that a spreadsheet does naturally. Triggers: financial model, scenario analysis, ratio computation, balance sheet, P&L, what-if, sensitivity analysis, banking ratios, spreadsheet model, build a model, projection, forecast. Do NOT use for: simple CSV/Excel read/write (use the xlsx skill), chart-only tasks, or data volumes exceeding ~5000 rows.
ALWAYS `render inertia: { key: data }` to pass data as props — instance variables are NOT auto-passed (only alba-inertia does that). Rails controller patterns for Inertia.js: render inertia, prop types (defer, optional, merge, scroll), shared data, flash, PRG redirects, validation errors. Use when writing controllers that load data, display records, or serve Inertia responses. CRITICAL: external URLs (Stripe/OAuth) MUST use inertia_location, NEVER redirect_to.
Check and validate MTHDS bundles for issues. Use when user says "validate this", "check my workflow", "check my method", "does this .mthds make sense?", "review this pipeline", "any issues?", "is this correct?". Reports problems without modifying files. Read-only analysis.
Diagnoses and fixes Aptos Move compilation, runtime, and deployment errors. Triggers on: 'error', 'fix this', 'debug', 'troubleshoot', 'why is this failing', error codes like 'EOBJECT_DOES_NOT_EXIST', 'ABORTED', 'RESOURCE_NOT_FOUND', 'Type mismatch', 'ability constraint'.
Search and track grocery prices from Berlin supermarkets (Rewe, Lidl, Aldi). Stores best prices in a local database. Triggers on: /prices search <item>, /prices best <item>, /prices list, 'how much does X cost', 'cheapest X in Berlin', 'find price for', or when looking up grocery costs for meal planning.
Instant visual verification via screenshots. For quick checks like 'does button look blue', 'is layout centered', 'header look right on mobile'. Fast alternative to formal testing - just look and confirm. Use when user wants visual inspection without creating test files.
ALWAYS LOAD THIS SKILL when: something doesn't work as expected, documentation is unclear, need to understand library internals, debugging integration issues, or before making assumptions about how a library works. Contains opensrc repo paths, debugging workflows, and examples for Effect, TanStack, TRPC, Drizzle, Better Auth, OpenCode.
Goldsky Turbo pipeline YAML reference — the authoritative source for field names, required vs optional fields, and valid values. Use whenever the user asks about specific YAML fields: what does `start_at: earliest` vs `latest` do, what fields does a postgres/clickhouse/kafka sink require, what is the `from:` field in a sink, how does `checkpoint` work, what's the syntax for `batch_size` or `primary_key`. Also use for validation errors like 'unknown field' or 'missing required field'. For interactive pipeline building end-to-end, use /turbo-builder instead.
Generate a pedagogically-grounded study guide for learning an unfamiliar codebase. Use when the user wants to onboard onto a codebase, understand a project's architecture, create learning materials for a team, or asks things like "help me learn this codebase", "create an onboarding guide", "I'm new to this project", "how does this system work", "study guide for this repo", or "explain this codebase to me". Produces a structured document that builds understanding from purpose to systems to patterns, using evidence-based learning techniques (elaborative interrogation, concept mapping, threshold concepts, worked examples, progressive disclosure).
This skill should be used when the user asks about macOS/nix-darwin system settings, Dock/Finder configuration, Homebrew Cask management, Shottr setup, or Folder Actions. Triggers: "darwin-rebuild", Dock/Finder settings, "/etc/bashrc conflict", "/etc/zshrc conflict", "killall cfprefsd", "primary user does not exist", "shottr 설정", "shottr 단축키", "스크린샷 저장 경로", "shottr 라이센스", "Folder Actions", "폴더 감시", "compress-video", "compress-rar", "upload-immich". For iOS Shortcuts and Cherri DSL details use managing-shortcuts.
End-to-end workflow—review changes, create a Japanese commit per commit-jp, run pnpm lint && pnpm test, then push to origin per push. Use when the user wants to commit and publish in one go. Does not open or update PRs—use create-pr-jp for that.