Agent skill · Content & Marketing

blog-cover-generator

Use when the user asks to generate a blog cover image, thumbnail, or article header. Automatically uses modern typography, brand logos, and Google Search grounding to create beautiful 16:9 images with Gemini 3.1 Flash Image Preview.

Varnan-Techgithub.com/Varnan-TechGitHub ↗
claude-codeMIT
Install
npx skills add Varnan-Tech/opendirectory --skill blog-cover-image-cli --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 4 KB
Bundled scripts: none
Path: skills/blog-cover-image-cli/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 571
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Blog Cover Generator Skill This skill provides AI agents with the ability to generate stunning, minimalist, technical blog cover images using the `blog-cover-image-cli`. The CLI leverages Gemini 3.1 Flash Image Preview, automatically fetches brand logos from domains, uses local aesthetic reference images, and employs Google Search grounding to inject real-time context. ## Setup & Configuration **Agent Pre-requisites:** Before using this tool, verify it is installed. If `blog-cover-cli --help` fails, install it globally: ```bash npm install -g blog-cover-image-cli ``` If the user wants you to generate an image and you haven't set up the API key yet, you must first configure the CLI using a Gemini API Key. The CLI stores this securely via the `conf` package. ```bash # 1. Set your Gemini API Key (Required for image generation) npx -p blog-cover-image-cli blog-cover-cli config set-key <YOUR_GEMINI_API_KEY> # 2. Set your Brandfetch Client ID (Required to fetch high-res logos) npx -p blog-cover-image-cli blog-cover-cli config set-brandfetch-id <YOUR_BRANDFETCH_CLIENT_ID> # Check your keys (masked) npx -p blog-cover-image-cli blog-cover-cli config get-key npx -p blog-cover-image-cli blo

What's inside
Steps it walks through
  1. Setup & Configuration
  2. Usage: Generating an Image
  3. Arguments
  4. Examples
  5. How It Works Under the Hood
  6. Edge Cases / Troubleshooting
Ships with 1 file
  • README.md
Commands it runs
npm install -g blog-cover-image-cli
npx -p blog-cover-image-cli blog-cover-cli config set-key <YOUR_GEMINI_API_KEY>
npx -p blog-cover-image-cli blog-cover-cli config set-brandfetch-id <YOUR_BRANDFETCH_CLIENT_ID>
Check your keys (masked)
npx -p blog-cover-image-cli blog-cover-cli config get-key
npx -p blog-cover-image-cli blog-cover-cli config get-brandfetch-id
npx -p blog-cover-image-cli blog-cover-cli generate -t "The Title of the Blog Post" -l "example.com"
npx -p blog-cover-image-cli blog-cover-cli generate -t "Why Cursor is the Ultimate AI Code Editor" -l "cursor.com"
npx -p blog-cover-image-cli blog-cover-cli generate -t "Building Apps in Minutes with Lovable" -l "lovable.dev"
npx -p blog-cover-image-cli blog-cover-cli generate -t "Mastering React in 2026" -l "reactjs.org" -o "./assets/react-cover.png"
More from opendirectory
All skills →
About this skill
What does the blog-cover-generator skill do?

Use when the user asks to generate a blog cover image, thumbnail, or article header. Automatically uses modern typography, brand logos, and Google Search grounding to create beautiful 16:9 images with Gemini 3.1 Flash Image Preview.

How do I install it?

Run `npx skills add Varnan-Tech/opendirectory --skill blog-cover-image-cli --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From Varnan-Tech/opendirectory, a repository with 571 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going