Owl-Listener/designer-skills: what the plugin marketplace actually installs

The problem this pack is aimed at

Design work in an AI coding assistant tends to arrive as a blank prompt. You type a request, the agent improvises a structure, and the next session improvises a different one. Owl-Listener/designer-skills addresses that by shipping the structure as files: 273 skills and 76 commands across 33 plugins, grouped into five collections. The README describes the intent plainly, calling them "design skills for the agent era, written so an AI agent can actually use them."

The audience is not only designers. The getting-started section says the three-step install needs no coding and no terminal, which suggests the author expects people who use Claude Code as an application rather than as a command-line tool. The skills themselves span research, design systems, UX strategy, UI, interaction, prototyping and testing, design ops, a general toolkit, and visual critique. That range is the point: a person who runs a usability study and a person who maintains a token set pull from the same marketplace but install different plugins.

One structural detail matters more than the counts. This repository is the front door. Nine design-practice plugins ship from here. The other four collections (AI product design, UX program management, design leadership, inclusive design) live in separate repositories, and the marketplace pulls their plugins in. So the single install command exposes 33 plugins, but only nine of them have their source in this repository.

How the marketplace, plugins and skills fit together

There are three layers. A marketplace is a repository Claude Code knows how to read. A plugin is a named bundle inside it. A skill or command is a file inside a plugin. The README's step 2 adds the marketplace and notes that "nothing installs yet", which is accurate: adding a marketplace only registers where plugins live. Step 3 is where selection happens, through the Discover tab of the `/plugin` interface, where you tick collections with the space bar and press enter.

The repository layout reflects this. The top level holds one directory per design-practice plugin (design-research, design-systems, ux-strategy, ui-design, interaction-design, prototyping-testing, design-ops, designer-toolkit, visual-critique) alongside `.claude-plugin/` and `.gemini/`. The `.gemini/extensions/` path is what the Gemini CLI instructions copy from, which is how the same plugin set is exposed to a second host.

Commands are namespaced by plugin. The README lists entries such as `/design-ops:handoff`, which the table describes as producing "a developer-ready package" of specs, measurements, assets, states and a QA checklist, and `/design-research:discover`, described as a full research cycle covering persona creation, empathy mapping and journey mapping. The namespace prefix is the plugin name, so you can tell from a command which plugin has to be installed for it to exist.

Governing files sit at the root: SKILL_TEMPLATE.md and COMMAND_TEMPLATE.md for authoring new entries, CONTRIBUTING.md for contributions, and INDEX.md, which the README recommends when you do not know which skill you need. INDEX.md arranges skills by situation and, according to the README, lists "the pairs most often mistaken for each other", which is a more useful artifact than a flat catalogue.

Installing the pack in Claude Code

The README's path assumes Claude Code is already installed and signed in. The first command registers the marketplace. Run it inside Claude Code, not in a shell:

/plugin marketplace add Owl-Listener/designer-skills

Nothing is installed by this step. To choose plugins, open the plugin interface and switch to the Discover tab:

/plugin

The README says you move with the arrow keys, tick with the space bar, and press enter to install. If you want only the design-practice plugins, tick design-research, design-systems, ui-design, interaction-design and the rest, and leave the other collections alone. A single plugin can also be installed directly by name, using the plugin and the marketplace:

/plugin install ux-strategy@designer-skills

For a narrower door, each collection has its own marketplace repository. Substituting the command below registers only the inclusive-design collection, after which the Discover step works the same way:

/plugin marketplace add Owl-Listener/inclusive-design-skills

When you are unsure where to begin, the README points at a starting command that asks what you are working on and names your stage, one command to run now, and the two that follow:

/designer-toolkit:start-here

For Gemini CLI, the README gives a different route from your project root: clone the repository to a temporary directory, create `.gemini/extensions`, and copy the extension files into place.

git clone https://github.com/Owl-Listener/designer-skills /tmp/designer-skills
mkdir -p .gemini/extensions
cp -r /tmp/designer-skills/.gemini/extensions/. .gemini/extensions/

That is the whole documented setup. There is no build step, no package manager, and no configuration file to edit.

Where the documentation stops

The README is a good on-ramp and a thin reference. It lists every command in a table, but the table is truncated in the version available, and the descriptions are one line each. For a command like `/design-ops:plan-sprint`, you learn that it runs a design sprint end to end with challenge framing, schedule, exercises and a prototype test plan, but not what inputs it expects, what it writes, or where the output lands. You will find that out by running it.

The repository has no releases. None are listed, so there are no version tags to pin, no changelog entries to read by version, and no upgrade path documented as such. A CHANGELOG.md exists at the top level, and that is the only place a change would surface. If your team needs to know what changed between two points in time before rolling an update into a shared workflow, this pack does not give you that in a structured form.

There is also a boundary in the install model itself. These are files consumed by Claude Code or Gemini CLI. The README states that plainly rather than pretending otherwise, but it means the pack is useless to anyone who does not already run one of those two hosts. A designer who works in Figma and nothing else gets no value from the marketplace command.

The counts are another place to read carefully. The headline figure of 273 skills and 76 commands covers all five collections, while this repository carries 111 skills and 34 commands across its nine plugins. The larger number is real, but it depends on four external repositories that this one does not control.

Compared with writing your own skills

The obvious alternative is not another plugin pack. It is authoring your own skills inside your own repository. Claude Code reads skill and command files from a project, so a team can write exactly the three prompts it repeats every week and skip the other 270.

The difference is scope and maintenance. A hand-written skill set is small, specific to your product vocabulary, and yours to version. This pack is broad, generic by necessity, and maintained by someone else. Its 111 design-practice skills cover situations you may never hit (card sorting, service blueprints, localization, motion) and cannot know your component names, your research repository, or your review gates.

The repository does lower the cost of the middle path. SKILL_TEMPLATE.md and COMMAND_TEMPLATE.md exist so contributors can add entries in the expected shape, and CONTRIBUTING.md describes the process. If you like the structure of a plugin such as design-systems but not its content, the templates are the sanctioned way to build a variant. What you cannot do is edit the installed copy and expect it to survive, because the marketplace pulls from the upstream repository.

Licence, maintenance and the real upgrade cost

The repository is MIT licensed, and the LICENSE file sits at the top level. MIT permits commercial use, modification and redistribution provided the copyright notice and permission notice are kept. That matters here because skills are text you may want to fork and adapt; MIT does not stand in the way. This is a description of the licence text, not legal advice, and the four sibling collections carry their own licences in their own repositories, which this one does not restate.

On maintenance: the last push to the default branch was on 2026-09-05. There are no releases, so the practical upgrade mechanism is pulling whatever the marketplace serves at the moment you install. That is convenient and slightly opaque. A skill you installed last month may read differently today, and the CHANGELOG.md is the only record.

The cost that is easiest to underestimate is review. Every skill and command is a prompt that shapes an agent's behaviour, and the pack ships over a hundred of them in this repository alone. Reading all of them before use is unrealistic. Reading the handful you install is not, and the INDEX.md situation grouping plus the note about commonly confused pairs is the fastest way to narrow that set.

Editorial conclusion

Adopt it if you already work inside Claude Code or Gemini CLI and want design tasks to follow named workflows instead of ad hoc prompts; the design-practice plugins ship from this repository, so there is nothing to clone. Skip it if you need a standalone design tool, a Figma plugin, or anything that runs without an agent host, and skip it if you need versioned release notes, because the repository has none. Before installing, open INDEX.md and confirm a skill matches your situation, then check whether the plugin you want lives in this repository or in one of the four sibling collections, since the marketplace pulls those in from elsewhere.

Frequently asked questions

Official sources

1. Issues
2. License: MIT
3. Owl-Listener/designer-skills on GitHub
4. README