galileo-stud
9 skills with substantive source documentation and an official publisher or observed installation demand. Read each skill’s original documentation through its card.
galileo-studio-devdesigning-error-handling
Decides where and how failures are handled. Use when writing or reviewing code that can fail — database, HTTP, queue, file, payment or auth provider calls, webhooks, background jobs, parsing of external input — and when deciding whether to add a try/catch, fallback, default value, retry, or timeout. Also use when a reviewer flags swallowed exceptions, silent failures, or defensive checks for states that cannot happen.
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 5
galileo-studio-devexecuting-plans
Use when you have a written implementation plan to execute in a separate session with review checkpoints
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 5
galileo-studio-devfinishing-a-development-branch
Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 5
galileo-studio-devgrill-me
Interview the user relentlessly about a plan or design until reaching shared understanding, resolving each branch of the decision tree. Use when user wants to stress-test a plan, get grilled on their design, or mentions "grill me".
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 5
galileo-studio-devinstrumenting-for-observability
Adds logging, metrics, tracing, and error reporting that let someone else diagnose a failure. Use when instrumenting a new handler, job, or integration, wiring Sentry or a logger, deciding what to log, or when a log line might include request bodies, tokens, emails, or other personal data. Also use when a failure investigation finds no useful trace.
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 5
galileo-studio-devlearning-codebase-conventions
Discovers and follows the conventions of the codebase being changed. Use before writing or changing code in an existing repository, especially in an area not yet read this session — before creating a file, naming anything, choosing an error-handling or logging idiom, writing a test, or adding a utility. Also use when generated code looks foreign to the codebase or duplicates something that already exists.
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 5
galileo-studio-devowasp-security
Use when reviewing code for security vulnerabilities, implementing authentication/authorization, handling user input, or discussing web application security. Covers OWASP Top 10:2025, ASVS 5.0, LLM Top 10 (2025), and Agentic AI security (2026).
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 5
galileo-studio-devponytail
Forces the laziest solution that actually works, simplest, shortest, most minimal. Channels a senior dev who has seen everything: question whether the task needs to exist at all (YAGNI), reach for the standard library before custom code, native platform features before dependencies, one line before fifty. Supports intensity levels: lite, full (default), ultra. Use whenever the user says "ponytail", "be lazy", "lazy mode", "simplest solution", "minimal solution", "yagni", "do less", or "shortest
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 5
galileo-studio-devsemgrep
- Run Semgrep static analysis scan on a codebase using parallel subagents. Supports two scan modes — "run all" (full ruleset coverage) and "important only" (high-confidence security vulnerabilities). Automatically detects and uses Semgrep Pro for cross-file taint analysis when available. Use when asked to scan code for vulnerabilities, run a security audit with Semgrep, find bugs, or perform static analysis. Spawns parallel workers for multi-language codebases.
- installs
- 1
- GitHub stars
- 0
- Updated
- Oct 5