open-images-for-free-use — Claude Code skill: free images, license
The skill picks an image from a curated catalog and confirms its license from the file's own embedded metadata. Handy when you need a picture for a UI, article or deck.
npx skills add peter-duffy95/open-images-for-free-use-skill --skill open-images-for-free-use -a claude-codeWhat open-images-for-free-use does
Two stages: pick an image, then verify its license. The catalog ships inside the skill as ./index.json; read it whole with jq . ./index.json and choose an entry by its keywords, judging what the image is for — hero banner, blog header, portrait — rather than matching substrings. If nothing fits, the skill takes the closest option and tells you the match is approximate.
The file is fetched from a pinned commit, e40900d, and the license identifier in its metadata is checked against a fixed allow-list of eight known IDs. Only then does the skill print the matching license file bundled with it. The verdict comes from the image itself, not the catalog, so a catalog entry proves nothing on its own.
You still have to read the license. An NC tag rules out commercial use, ND forbids cropping and text overlays, SA obliges you to license derivatives the same way. For a commercial project where the image gets edited, a good chunk of the list is out — worth checking before the URL lands in your layout.
What it helps with
- find a landing page image without breaking its license
- check whether a photo is usable in a commercial project
- learn if cropping or overlaying text is allowed
- get an illustration for a blog post or slide deck
- grab an image URL with the license already confirmed
Example prompts for the agent
- find me an image for the hero banner on the landing page
- I need an illustration for a blog post, license must allow commercial use
- pick a picture for my presentation and show me its license
How to install open-images-for-free-use
1Skills CLI (Vercel)
npx skills add peter-duffy95/open-images-for-free-use-skill --skill open-images-for-free-use -a claude-code2Manually: put the files in place
~/.claude/skills/open-images-for-free-use/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/open-images-for-free-use/
1Skills CLI (Vercel)
npx skills add peter-duffy95/open-images-for-free-use-skill --skill open-images-for-free-use -a codex2Manually: put the files in place
.agents/skills/open-images-for-free-use/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add peter-duffy95/open-images-for-free-use-skill --skill open-images-for-free-use -a cursor2Manually: put the files in place
.cursor/skills/open-images-for-free-use/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install peter-duffy95/open-images-for-free-use-skill open-images-for-free-use2Manually: put the files in place
.github/skills/open-images-for-free-use/SKILL.md1Skills CLI (Vercel)
npx skills add peter-duffy95/open-images-for-free-use-skill --skill open-images-for-free-use -a gemini-cli2Platform CLI
gemini skills install https://github.com/peter-duffy95/open-images-for-free-use-skillManually: put the files in place
.devin/skills/open-images-for-free-use/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add peter-duffy95/open-images-for-free-use-skill --skill open-images-for-free-use -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about open-images-for-free-use
How do I install open-images-for-free-use in Claude?
Run npx skills add peter-duffy95/open-images-for-free-use-skill --skill open-images-for-free-use -a claude-code. It lands at ~/.claude/skills/open-images-for-free-use/SKILL.md.
What does open-images-for-free-use do?
It picks an image from a curated catalog and confirms the license from the file's own embedded metadata. You get a URL whose licensing question is already answered.
Can I use these images in a commercial project?
It depends on the license of the specific file. An NC tag blocks commercial use, ND blocks modification, and SA requires derivatives to carry the same license.
