recoup-cover-art
Create square cover art for a release — single, EP, or album artwork sized for DSPs (Spotify, Apple Music). Use when the user says "cover art", "album art", "single artwork", "artwork for [release]", "make a cover for [song]", or "DSP artwork". Produces brand-defining 1:1 art with no clickbait text. Distinct from a YouTube thumbnail (use recoup-thumbnail). Works with or without artist context.
What this skill does
# Cover Art
Square release artwork for DSPs. This is **brand-defining, durable** art — the image that
represents the release everywhere it streams. It is NOT a clickbait thumbnail: cover art
carries at most the artist/title set cleanly, never hooky overlay text or arrows. For
YouTube/video CTR art, use `recoup-thumbnail`.
Read `references/content-api.md` (image gen, upscale, async) and
`references/analyze-gate.md` (verify before delivery). Both ship alongside this skill.
## DSP requirements
- **Square 1:1**, high resolution (aim ≥ 3000×3000 for store acceptance) — generate then
`upscale` (`type: image`) if needed.
- **Legible at thumbnail size** — it'll appear tiny in a queue; test the concept small.
- Keep text minimal and on-brand; no streaming logos, no URLs, no "explicit"-style badges.
## Steps
1. **Gather direction.** Context mode: aesthetic + any palette/motifs from
`context/artist.md`, release theme from `releases/{slug}/RELEASE.md`. Generic mode: the
user's concept/prompt. Optionally seed with a supplied photo as `reference_image_url`.
2. **Generate** the 1:1 image (`POST $BASE/content/image`, poll). Offer 2–3 directions.
3. **Upscale** the chosen one to DSP resolution.
4. **Verify** with the analyze gate — composition reads at small size, no garbled text, no
artifacts, title/name legible if included.
## Persist
Workspace → `artists/{slug}/releases/{release-slug}/cover.png` and record the URL in that
release's `RELEASE.md` (Section 18, visuals). Commit `{what}: {why}`. See
`references/workspace-context.md`. No workspace → return the image URL.
## Guardrails
- **Cover art ≠ thumbnail.** No hooky overlay text, arrows, or shocked faces.
- **Square + high-res**, or DSPs reject it.
- **Likeness:** if seeding with a real face, use the artist's own reference; image models
may 422 on celebrity likeness.
Related in Ads & Marketing
ads
IncludedMulti-platform paid advertising audit and optimization skill. Analyzes Google, Meta, YouTube, LinkedIn, TikTok, Microsoft, and Apple Ads. 250+ checks with scoring, parallel agents, industry templates, and AI creative generation.
banana
IncludedAI image generation Creative Director powered by Google Gemini Nano Banana models. Use this skill for ANY request involving image creation, editing, visual asset production, or creative direction. Triggers on: generate an image, create a photo, edit this picture, design a logo, make a banner, visual for my anything, and all /banana commands. Handles text-to-image, image editing, multi-turn creative sessions, batch workflows, and brand presets.
rpg-migration-analyzer
IncludedAnalyzes legacy RPG (Report Program Generator) programs from AS/400 and IBM i systems for migration to modern Java applications. Extracts business logic from RPG III/IV/ILE source code, identifies data structures (D-specs), file operations (F-specs), program dependencies (CALLB/CALLP), and converts RPG constructs to Java equivalents. Generates migration reports, complexity estimates, and Java implementation strategies with POJO classes, JPA entities, and service methods. Use when modernizing AS/400 or IBM i legacy systems, analyzing RPG source files (.rpg, .rpgle, .RPGLE), converting RPG to Java, mapping data specifications to Java classes, planning legacy system migration, or when user mentions RPG analysis, Report Program Generator, RPG III/IV/ILE, AS/400 modernization, IBM i migration, packed decimal conversion, or mainframe application rewrite.
brand-library-architect
IncludedBuild a complete brand library for a product — visual asset render pipeline, brand documentation set (BRAND, COPY, MANIFESTO, BIOS, FAQ, GLOSSARY, TONE, PRICING), open-source convention files (README, CONTRIBUTING, SECURITY, CODE_OF_CONDUCT), and a self-contained press kit. This skill should be used when the user asks to "build a brand library / brand kit / press kit / brand assets" for a product, "set up a brand library workflow," "create a positioning manifesto plus visual identity," or any combination of brand documentation + visual asset pipeline. Apply phase-by-phase or run end-to-end. Templates are product-agnostic and use {{TOKEN}} placeholders the skill prompts the user to fill.
writing-tech-post
IncludedAuthors engineering blog posts end-to-end: launch deep-dives, incident postmortems, architecture migrations, performance case studies, tutorials, AI/agent system writeups, security disclosures, and research-to-product translations. Picks the correct archetype, plans the abstraction ladder, enforces an evidence cadence (diagrams, benchmarks, profiles, traces, code, ablations), tunes voice against publisher house styles (Datadog, Vercel, GitHub, AWS, Meta, Cloudflare, Jane Street), and runs a pre-publish gate for narrative momentum and disclosure ethics. Use when drafting a new engineering post, restructuring a draft that feels flat, deciding which evidence form belongs where, validating that depth and product context are balanced, or preparing a postmortem, migration, or performance narrative for external publication. Do not use for API reference documentation, README authoring, marketing copy, release notes, generic SEO content, ghost-written executive thought leadership, or non-engineering long-form essays.
blog-google
IncludedGoogle API integration for blog performance: PageSpeed Insights, CrUX Core Web Vitals with 25-week history, Search Console performance, URL Inspection, Indexing API, GA4 organic traffic, NLP entity analysis for E-E-A-T, YouTube video search for embedding, and Google Ads Keyword Planner. Progressive feature availability based on credential tier (API key, OAuth/service account, GA4, Ads). Shares config with claude-seo at ~/.config/claude-seo/google-api.json. Use when user says "google data", "page speed", "core web vitals", "search console", "indexation", "GA4", "keyword research", "nlp entities", "blog performance", "youtube search", "google api setup".