Website review
This review may include AI-generated content and is not individually verified. Domain, certificate and other facts come from the observed data on this page.
What is Skillry?
Skillry is a curated library of reusable "Agent Skills" — packaged workflows that you install into AI coding agents such as Claude Code, Codex and Cursor. Instead of prompting an agent from scratch each time, you pick a skill and the agent runs it end to end to produce a specific artifact: slides, web pages, images or video. The site describes itself as "Agent Skills with taste," and the catalogue is organised around those four creation categories.
How it fits into a working setup
You connect your agent to Skillry, browse or search the library, and install a skill. From then on the workflow lives with your agent, so the same instructions and design decisions get reused rather than re-explained. Skills shown on the page include items like a visual canvas deck, a marketing landing page, an OG image style, a logo reveal and a chart-based web component.
Who it suits
- Designers and marketers who want presentable output (decks, landing pages, social images) without hand-building templates.
- Developers already using Claude Code, Codex or Cursor who want repeatable generation steps rather than ad-hoc prompts.
- Small teams producing launch assets — announcement films, capability reels, product pages — where consistency across a set matters.
Free versus paid
The page separates "Free Agent Skills" from the wider catalogue. Free entries are described as installable and runnable end to end with no card and no trial timer, which makes them a sensible way to test whether a skill's output style matches what you need before committing further. A pricing page exists, but treat the free tier as your evaluation path rather than assuming paid skills differ only in quantity.
A practical next step
Pick one narrow task you repeat often — a weekly deck or a product-page hero — find the closest matching skill in that category, and run it once on real content. Judge it on how much editing the output needs, not on how impressive the demo looks; that ratio is what determines whether a library like this saves you time.
How do I install a Skillry Agent Skill in Claude Code, Codex, or Cursor?
Skillry is a curated library of reusable Agent Skills — packaged SKILL.md workflows for tasks like slides, web pages, images, and video. You browse the library, pick a skill, and install it into your agent so it can run that workflow end to end. The site lists support for Claude Code, Codex, Cursor, and "more supported agents."
What installing involves
A Skillry Agent Skill is a folder containing at least a SKILL.md file (plus any supporting assets). Installing means placing that folder where your agent looks for skills, then restarting or reloading the agent so it picks up the new skill. The exact path differs by tool, so follow the install instructions shown on the skill's page rather than a generic path.
Typical flow
- Open the skill's page on Skillry and note its category (Web, Image, Slides, Video) and whether it's marked Free.
- Use the install action on that page — it should give you the skill folder or a command tailored to your agent.
- Drop the folder into your agent's skills directory (or run the provided command).
- Reload the agent and confirm the skill appears in its skill list.
- Run it once on a small test prompt to check the output before using it on real work.
Tool-by-tool notes
- Claude Code: add the skill folder to your project or user-level skills location, then start a new session so Claude Code scans it.
- Codex: place the skill where your Codex setup reads skills, and reload.
- Cursor: install into the skills directory your Cursor agent uses, then restart the agent.
The page shows a "Connect your agent" section, which is the most reliable place to get the correct path or command for your specific tool.
Practical next step
Start with a Free skill in the format you need — for example the Free "Editable Visual Deck" (Slides) or "Activity Calendar Chart" (Web). Install it, run it once, and check the output quality before committing to a paid skill. If the install path in the site's instructions doesn't match your agent version, check the agent's own documentation for its current skills directory.
Which Skillry skills are free and which require payment?
Skillry separates its catalog into free and paid Agent Skills, and the free ones are clearly labeled in the listings. Based on the page, the free skills shown are:
- GrokBot Avatar (Image)
- Velocity-Matched UI Sting (Video)
- Editable Visual Deck (Slides)
- Activity Calendar Chart (Web)
- Hand-Drawn Visual Notes (Image)
- Agent-Chorus Capability Reel (Video)
- Image Narrative Deck (Slides)
- Sage Sneaker Store (Web)
- Liquid-Rupture Logo Reveal (Video)
Paid skills appear in the same categories without the free tag, including Collage Creative Portfolio, Procreate Style OG Image, Obsidian Cinema Landing, Starlit Deck, Goodnotes Style OG Image, Cadence Marketing Landing, Cobalt Serif Freelancer Site, Cut-Paper Collective Site, Dark Stat Hero, Paired Column Chart, Summary Line Chart, Project Knowledge Graph, Interactive System Map, Visual Canvas Deck, Article Brief Deck, Red Black Zine Deck, Brand Story Deck, Academic Argument Deck, Architectural Project Deck, Pain-Gag Reveal Launch Film, Partnership Announcement Film, and Texture-Swatch Kinetic Launch.
A practical way to decide: if you want to test whether a skill fits your workflow before committing, start with the free version of the same format (for example, Editable Visual Deck for slides or Velocity-Matched UI Sting for video). If the free skill produces output you can actually use, the paid skills in that category are the natural next step. If you only need a one-off asset, the free tier is often enough on its own.
Skillry lists a pricing page at Skillry if you want to check current paid options directly.
Are Skillry's Agent Skills compatible with my AI coding agent?
Skillry's skills are built to be agent-agnostic. Its library is described as working with Claude Code, Codex, and Cursor, and the page shows a "Works with + 6" badge alongside an "And more supported agents" note — so compatibility is the norm rather than the exception.
What you're actually installing is a SKILL.md file: a reusable, text-based workflow definition. That format is the reason portability is plausible — the skill describes a task and its process, and your agent supplies the model and tools.
How to check before you commit
- Confirm your agent is listed. Look for your specific tool among the supported agents on the skill page rather than relying on the general claim.
- Start with a free skill. The library marks a good number of entries as Free, covering slides, web pages, images, and video. That's the cheapest way to test the fit on your own setup.
- Read the skill's requirements. Skills that produce slides, web pages, images, or video may depend on tools your agent can reach. A text-only agent will handle a deck outline differently than one with file and image access.
A quick test scenario
Pick one free skill in the format you care about most — say a chart or landing-page skill — install it, and run it end to end on a small real task. If the output lands close to what you'd ship, the rest of the library is likely to behave the same way.
Where compatibility gets fuzzy
"Works with" usually means the skill's instructions are portable, not that every agent will produce identical results. Agents differ in how much they can do autonomously, how they handle files, and how they render visual output. Treat the badge as a starting signal and your own test run as the verdict.
If you want a second reference point on the underlying skill format, the documentation for Anthropic's Claude documentation and Cursor covers how each agent consumes custom instructions.
How can I find the right Skillry skill for a specific task like slides, video, or images?
Start with the category filters, not the search box. Skillry organizes its library around the artifact you want to produce — Web, Slides, Image, and Video — and each skill listing names a concrete output (for example, "Starlit Deck" under Slides or "Velocity-Matched UI Sting" under Video). Match your task to the category first, then judge the individual skill by its output name and install count.
H3 How to narrow it down
- Pick the category that matches your deliverable. Slides, video, images and web pages are the four groupings shown on the page, so decide what you are actually handing over before browsing.
- Read the skill name as a promise about the result. Names like "Academic Argument Deck," "Editable Visual Deck," or "Liquid-Rupture Logo Reveal" tell you the format and the intended effect better than any generic label would.
- Use the curated lists as shortcuts. The site surfaces Featured, Free, Trending and Top-rated sections. Trending is useful when you want something that other people are actively installing; Top-rated is useful when you want a proven option; Free is useful when you want to try one skill end to end before committing.
- Check the install count as a rough popularity signal. A skill with more installs has been run by more people, which is weak evidence but better than none when two options look similar.
- Confirm your agent is supported. The page lists Claude Code, Codex and Cursor as targets and notes additional supported agents, so check that your tool appears before you invest time.
H3 A concrete example
Suppose you need a conference talk deck rather than a marketing landing page. Go to Slides, scan for names that describe argument structure ("Academic Argument Deck," "Article Brief Deck") rather than visual style alone, then compare against the Trending Slides list. If two candidates fit, prefer the one whose name matches your content type — an argument-driven deck for a research talk, a brand story deck for a client pitch.
H3 Decision criteria when two skills look equally good
| If you care most about… | Lean toward |
|---|---|
| Trying before paying | The Free section |
| Broad adoption | Higher install counts |
| Current momentum | Trending lists |
| Proven quality | Top-rated lists |
| A specific visual register | The skill name's style words (zine, cinematic, hand-drawn) |
If you want a second opinion on a design-heavy skill, compare it against what the same category offers on a general marketplace such as GitHub or a design reference like Dribbble before installing.
Your next step: open the category page for your deliverable, shortlist two or three skills by name, and install the free one first to see whether its output style matches what you had in mind.
What do the install counts and ratings on Skillry skills mean?
On Skillry, the numbers shown on each skill card are simple popularity and quality signals, not a guarantee of fit for your project.
Install counts show how many times a skill has been installed. Higher numbers suggest more people have tried it and it has survived real use. Low counts are common on a young library and don't mean a skill is bad — it may just be new.
Ratings reflect user scores. A rating with very few installs is weak evidence; a rating backed by many installs is more meaningful. Treat a 5-star skill with 1 install as interesting, not proven.
| Signal | What it tells you | What it does not tell you |
|---|---|---|
| Install count | Adoption and rough reliability | Whether it fits your stack or output style |
| Rating | User satisfaction | Whether reviewers had your use case |
| "Free" tag | No card or trial timer needed | That paid skills are better |
| Category (Web, Slides, Image, Video) | Output type | Quality within that category |
The page's own framing — "Install one, run it end to end, keep what it makes" — points to the real test: run a skill on a small real task and judge the output yourself.
For example, if you need a launch video, the free "Velocity-Matched UI Sting" shows 11 installs and 2 ratings, while "Liquid-Rupture Logo Reveal" shows 5 installs and no rating. The first has more social proof, but the second might match your brand better. Install both, run each on a short clip, and compare.
As a decision rule: use installs and ratings to shortlist, then use output quality to decide. For more context on how skills are organized, see Skillry.
User reviews (0)