gumroad-upload-management
Automate Gumroad product image uploads and listing maintenance with Selenium and Chrome profile sessions. Use when users ask to upload or replace Gumroad product images, map local image files to product pages, run `gumroad_image_uploader.py`, troubleshoot Chrome/Selenium session failures, or verify upload results from logs.
Best use case
gumroad-upload-management is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Automate Gumroad product image uploads and listing maintenance with Selenium and Chrome profile sessions. Use when users ask to upload or replace Gumroad product images, map local image files to product pages, run `gumroad_image_uploader.py`, troubleshoot Chrome/Selenium session failures, or verify upload results from logs.
Teams using gumroad-upload-management 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/gumroad-upload-management/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How gumroad-upload-management Compares
| Feature / Agent | gumroad-upload-management | 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?
Automate Gumroad product image uploads and listing maintenance with Selenium and Chrome profile sessions. Use when users ask to upload or replace Gumroad product images, map local image files to product pages, run `gumroad_image_uploader.py`, troubleshoot Chrome/Selenium session failures, or verify upload results from logs.
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
# Gumroad Upload Management ## Run Workflow 1. Ensure image files exist in `C:\Users\issda\OneDrive\Downloads` or `C:\Users\issda\Downloads`. 2. Prefer a preview first with `--dry-run`. 3. Run the real upload after preview confirms product-image matches. 4. Confirm success using `gumroad_upload.log`. ## Commands Use these commands in order. ```powershell # Start Chrome with remote debugging for stable attach mode Start-Process -FilePath "C:\Program Files\Google\Chrome\Application\chrome.exe" -ArgumentList "--remote-debugging-port=9222","https://app.gumroad.com/products" # Dry-run preview (no upload) python C:\Users\issda\.codex\skills\gumroad-upload-management\scripts\gumroad_image_uploader.py --debugger-address 127.0.0.1:9222 --images-dir "C:\Users\issda\OneDrive\Downloads" --dry-run # Real upload python C:\Users\issda\.codex\skills\gumroad-upload-management\scripts\gumroad_image_uploader.py --debugger-address 127.0.0.1:9222 --images-dir "C:\Users\issda\OneDrive\Downloads" ``` ## Match Rules - Match images to products by filename token overlap. - Skip unmatched products instead of guessing. - Rename files with product-identifying words when matching fails. ## Troubleshooting Read `references/troubleshooting.md` when Selenium or Gumroad page automation fails. ## Artifacts - Script: `scripts/gumroad_image_uploader.py` - Log file output: `gumroad_upload.log`
Related Skills
scbe-document-management
Consolidate overlapping docs, classify files by authority, and keep SCBE repo documents aligned with runtime truth. Use when the repo has drift between canonical docs, public docs, proposal notes, research branches, and generated evidence.
cloud-storage-local-storage-management
Audit, sort, route, and back up large Windows workspaces across local disks and cloud-sync folders without recursive mirror failures. Use when the user wants the filesystem cleaned up, cloud storage organized, backup targets chosen by free space and route quality, or hardware/storage bottlenecks identified before moving data.
shopify-management-ops
Run Shopify management from terminal with audit-first checks, product sync, storefront gate control, and optional live publish. Use when the user asks to manage Shopify products, storefront state, or monetization operations.
scbe-self-improvement-skill-management
Run the SCBE self-improvement loop by documenting completed work, creating new skills, updating existing skills, and propagating SCBE knowledge to other AI systems via context documents and structured knowledge files. Use when users ask to create/update skills, formalize repeated SCBE workflows, enforce skill approval gates, generate transfer prompts for Claude/Gemini/custom agents, or publish SCBE knowledge artifacts to Hugging Face datasets.
scbe-training-pair-authoring
Create prompt and response and metadata training pairs from SCBE documents, repair traces, terminal sessions, and operational workflows using the repository's canonical dataset contract and provenance rules.
scbe-spin-conversation-engine
Generate SFT training data via radial matrix conversation pivots with D&D-style combat research mode. Produces diverse, cost-effective training pairs with Sacred Tongue encoding, golden spiral problem distribution, and harmonic re-attunement.
scbe-research-training-bridge
Stage arXiv evidence and Obsidian markdown into source-grounded Hugging Face training bundles for research, review, and later SFT runs.
scbe-colab-bridge
Control Google Colab notebooks from Claude Code via Chrome extension. Execute cells, run terminal commands, read outputs, and manage GPU compute remotely.
scbe-claim-to-code-evidence
Map SCBE Notion technical claims, proof pages, and patent-facing architecture notes to concrete repository evidence such as code paths, tests, demos, and docs. Use when Codex needs to build a due-diligence packet, claim-to-code audit, implementation crosswalk, patent support note, or proof summary from local Notion exports and repo artifacts.
scbe-autonomous-worker-productizer
Turn SCBE automation, autonomous worker, and revenue-system notes into concrete offers, workflow packs, pilot plans, or SaaS-facing product packets. Use when Codex needs to package Notion automation pages into buyer-ready offerings, n8n/Zapier workflow designs, flock-backed worker systems, or implementation roadmaps tied to existing SCBE repo surfaces.
multi-agent-cloud-offload
Deterministically sort, bundle, verify, and offshore local files through multiple AI/model lanes while capturing training rows and method evidence. Use when Codex needs to inventory folders, batch-process files, upload them to cloud targets such as rclone-backed Google Drive, Hugging Face, or GitHub, and only delete sources after the configured number of verified targets succeed.
long-form-work-orchestrator
Run long-form engineering work in checkpointed phases with deterministic artifacts, resilience handling, and end-of-run reliability reporting.