cleanup-tags
Clean up Docker Hub tags for stellars-jupyterlab-ds
Best use case
cleanup-tags is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Clean up Docker Hub tags for stellars-jupyterlab-ds
Teams using cleanup-tags should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/cleanup-tags/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How cleanup-tags Compares
| Feature / Agent | cleanup-tags | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Clean up Docker Hub tags for stellars-jupyterlab-ds
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Clean Up Docker Hub Tags Manage and remove old or unwanted tags from Docker Hub for the `stellars/stellars-jupyterlab-ds` repository. ## Current Tags !`curl -s "https://hub.docker.com/v2/repositories/stellars/stellars-jupyterlab-ds/tags?page_size=100" | jq -r '.results[].name' | sort -V` ## Workflow 1. Show the user the current tags listed above 2. Ask which tags to delete using AskUserQuestion with options: - Delete all tags below version X.Y (e.g., "Delete all 3.4.x and lower") - Delete specific version range (e.g., "Delete 3.3.x only") - Delete tags matching a pattern - Custom selection 3. Authenticate using Docker credential helper (see AUTH.md) 4. Delete selected tags via Docker Hub API (see API.md) 5. Report results showing which tags were deleted successfully
Related Skills
repo-cleanup
Use when a repository needs cleanup of dead code, build artifacts, unused dependencies, outdated docs, or stale tests - provides safe cleanup workflows, validation steps, and reporting templates for code, deps, docs, tests, and sprint archives.
branch-cleanup
Clean up local branches after PR merges. Syncs main with origin, identifies branches with merged PRs, and proposes safe deletion. Use when the user asks to 'clean up branches', 'delete merged branches', 'sync branches', or mentions branch cleanup.
skills-cleanup
How to clean up duplicate/untracked skills in the skills repo
meeting-cleanup
Batch process multiple meetings from a single day. Consolidates action items and insights across meetings.
code-coverage-orphan-class-cleanup
Use when an org's overall Apex coverage is sliding toward 75% because of orphaned (uncovered, unreferenced) classes inflating the denominator. Triggers: 'production deploy blocked at 74% coverage', 'find apex classes with 0% coverage', 'orphan apex class report', 'org coverage dropping despite green test runs'. NOT for writing tests on actively used classes (use apex/test-class-standards) or for raising coverage on partially-covered classes.
batch-data-cleanup-patterns
Use when scheduling automated deletion of temporary records, enforcing data retention policies, running nightly cleanup jobs, reclaiming org storage, managing recycle bin, or performing async bulk deletion of aged records. Trigger keywords: batch delete, retention policy, purge records, cleanup job, recycle bin, emptyRecycleBin, hard delete, nightly purge, storage optimization. NOT for data archival to external storage (use data-archival-strategies).
org-cleanup-and-technical-debt
Use when executing admin-level cleanup in a Salesforce org: deleting unused fields, removing inactive Flow versions, deactivating legacy automation, running Salesforce Optimizer or Org Check, and performing destructive metadata deploys. Triggers: 'clean up unused fields', 'delete inactive flows', 'run Optimizer', 'org has too many custom fields', 'remove old workflow rules', 'Flow version limit'. NOT for assessing or reporting on technical debt (use architect/technical-debt-assessment). NOT for code-level refactoring or Apex cleanup (use apex/ skills).
cleanup-agent-worktree
Remove Agent Worktree
markdown-lint-cleanup
Fix markdown lint warnings by enforcing headings, blank lines around lists, and language-tagged code fences for clean documentation.
mole-mac-cleanup
Mac cleanup & optimization tool combining CleanMyMac, AppCleaner, DaisyDisk features. Deep cleaning, smart uninstaller, disk insights, and project artifact purge.
meta-tags-optimizer
Use when the user asks to "optimize title tag", "write meta description", "improve CTR", "Open Graph tags", "social.
codebase-cleanup-tech-debt
You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti