# Heroku Addons > Manage Heroku add-on resources and attachments safely. Use when the agent needs to create, inspect, plan, attach, detach, upgrade, wait on, open, or destroy Heroku add-ons, or reason about attachment aliases, shared resources, config-var side effects, and add-on lifecycle guardrails. - Skill: `dsouzaanush/heroku-addons` (Agent Skill, multi-file: 5 files) - Install (CLI): `npx skillmds add dsouzaanush/heroku-addons` - Raw SKILL.md: https://api.skillmd.com/api/skills/dsouzaanush/heroku-addons/raw - Safety review: pending (external: skill-scanner PASS, skillspector PASS) - Works with: Claude Code, Claude.ai, OpenAI Codex - Category: AI & ML - Author: dsouzaAnush (https://skillmd.com/u/dsouzaanush) - Updated: 2026-08-19 - Page: https://skillmd.com/skills/dsouzaanush/heroku-addons --- # Heroku Add-ons Use this skill for generic add-on lifecycle management that is broader than any one specialized service. ## Read-only-first flow Start with: - `heroku addons:info ` - `heroku addons:plans ` - `heroku addons:open ` when the user needs vendor console access Use inspection to determine: - which resource is being managed - which app attachments already exist - whether the operation should happen at the resource level or attachment level ## Resource and attachment model Keep these distinctions explicit: - `addons:create` creates a resource - `addons:attach` attaches an existing resource to an app, often creating config vars - `addons:detach` removes an attachment but may leave the underlying resource running - `addons:destroy` destroys the resource itself Prefer attachments and aliases when the goal is controlled sharing rather than a new resource. ## Confirm-first operations Ask for confirmation before: - `addons:create` - `addons:attach` - `addons:detach` - `addons:upgrade` - `addons:destroy` Call out config-var side effects and aliasing behavior before executing attachment changes. ## References - Read `references/addons-lifecycle.md` for aliasing, sharing behavior, and source links.