Skills
Skills are packaged workflows an agent loads on demand. They ship in the hermoso npm package and drive the CLI over Bash, so they work in any client that supports skills without adding a tool manifest to your context.
Why a skill and not just tools
A tool tells an agent what it can do. A skill tells it what to do in what order, and what not to do — which of two similar tools fits the ask, how to sequence research before creative, when to stop and confirm. Each of ours is explicit about its boundary; hermoso-research says outright that it is not for generating creative, and points at the skill that is.
The four skills
hermoso-research
Competitor and ad-library intelligence: find a brand's competitors, pull their real running ads across Meta, Google and LinkedIn, and surface the hooks and angles worth copying.
Triggers on asks like “find my competitors”, “pull brand's ads”, “what ads are working in my niche”, “research the longest-running ads”. Not for generating creative.
hermoso-ad-from-brand
A finished, on-brand ad end to end: onboard the brand, write the concept and copy, then render the image or video.
Triggers on “make an ad for company”, “build a launch ad for my brand”, or a domain plus what to advertise. Not for pulling competitor ads, and not for rendering a prompt you already have.
hermoso-generate
Render creative from a prompt you already have, against the raw model catalog.
hermoso-product-photoshoot
Turn a real product photo into a set of usable shots — the product composited into scenes rather than a model's guess at what your packaging looks like.
Installing
The skills live under skills/ in the published package. Copy the ones you want into your client's skills directory — for Claude Code that is .claude/skills/ in a project, or ~/.claude/skills/ for every project:
npm install -g hermoso
cp -r "$(npm root -g)/hermoso/skills/hermoso-research" ~/.claude/skills/Each skill is a single SKILL.md with YAML front matter (name, description, argument-hint, allowed-tools) and its instructions below. They are plain text — read one before installing it, and edit it if your workflow differs.
Skills need the CLI authenticated (hermoso auth login, or HERMOSO_TOKEN in the environment). They spend the same credits as any other surface — a skill is a script, not a discount.
Writing your own
Nothing about ours is privileged. A skill that shells out to hermoso … --json and parses the result has the full surface available to it, and the workspace's brand context applies automatically. If you build one worth sharing, request_feature reaches us from inside your agent.