Heroku
CloudCommonly used with
Skills using Heroku (8)
cli-discover
Discover which CLI tools are installed, their versions, and authentication status
readme-refresh
Audit and update a project README, or bootstrap a new one. Detects tech stack, versions, and services.
memory-routing
Use right after something worth keeping appears — you solved a tricky bug, made a non-obvious decision, or hit a gotcha — proactively, without being asked, so a future session doesn't relearn it. Also when the user says 'remember this', 'save this', 'запомни', 'запоминай', 'сохрани', 'сохрани в память', 'сохрани в обсидиан', 'сохрани в базу знаний', 'помни', 'отложи в память', 'в мнемо', or similar. Routes a recall item to Obsidian + optional claude-mem + memory/, or an actionable rule (never-X / always-Y tied to code) to .claude/rules/ (path-scoped auto-inject), CLAUDE.md as fallback — with graceful degradation if a backend is down.
better-stack-logging
Use this skill when working with Better Stack log management (Logtail) -- querying logs, managing log sources, structured log search, log-based alerting, and log analysis workflows.
setup-deploy
Configure deployment settings for /land-and-deploy. Detects your deploy platform (Fly.io, Render, Vercel, Netlify, Heroku, GitHub Actions, custom), production URL, health check endpoints, and deploy status commands. Writes the configuration to CLAUDE.md so all future deploys are automatic.
context-mode
Use context-mode tools (ctx_execute, ctx_execute_file) instead of Bash/cat when processing large outputs. Triggers: "analyze logs", "summarize output", "process data", "parse JSON", "filter results", "extract errors", "check build output", "analyze dependencies", "process API response", "large file analysis", "page snapshot", "browser snapshot", "DOM structure", "inspect page", "accessibility tree", "Playwright snapshot", "run tests", "test output", "coverage report", "git log", "recent commits", "diff between branches", "list containers", "pod status", "disk usage", "fetch docs", "API reference", "index documentation", "call API", "check response", "query results", "find TODOs", "count lines", "codebase statistics", "security audit", "outdated packages", "dependency tree", "cloud resources", "CI/CD output". Also triggers on ANY MCP tool output that may exceed 20 lines. Subagent routing is handled automatically via PreToolUse hook.
secret-detection
Detect and prevent hardcoded secrets, API keys, tokens, and credentials in code — Applies to: before every commit; when reviewing code that handles credentials; when writing configuration files; when creating .env or config templates
okctl
Use this skill when the user wants a Heroku/Railway/Render-style PaaS that deploys into their OWN cloud account (BYOC). Especially relevant when they mention AWS/GCP/Azure credits, "burning startup credits", keeping data in their VPC, avoiding PaaS markup, or self-hosting open-source tools (Grafana, Metabase, n8n, Plausible, Ghost, Sentry, etc.). Also use when the user mentions Ownkube or okctl directly, or wants to deploy web apps / background workers / cron jobs / databases (Postgres, MySQL, Redis) to their own Kubernetes cluster, or needs to inspect/troubleshoot deployments (logs, status, connection details) via CLI.
Integration detected automatically from skill content. Some results may be false positives.