Install
npx skills add sleekdotdesign/agent-skillsWho this is for
This guide is for people who need mobile-app interfaces and want an agent to create design drafts directly inside Sleek. Sleek is the officially named AI-driven mobile-app design tool, at
https://sleek.design/
The repository is
https://github.com/designed-by-ai/skills
Current materials record only one skill: design-mobile-apps, used to design mobile apps, create screens, and manage Sleek projects. The skill directory is
https://github.com/designed-by-ai/skills/blob/main/skills/design-mobile-apps
It fits when you already have a Sleek account, a key ready, and an agent that can read skill files in the working directory. It does not fit anyone without a key or anyone not planning to use Sleek. Do not infer extra skills that this material never wrote.
Finish a first try in 3 minutes
Follow only the one official recommended path.
Precondition: this machine can run npx, and the key is already in the environment variable SLEEK_API_KEY. Create the key on this page:
https://sleek.design/agents/setup
Do not put the key into chat or the repository. Before install, confirm the current working directory is the project where you want the skill.
Install location: official text says npx skills add puts the skill into the working directory’s .agents/skills/. If the agent will not discover skills there, point it at the installed SKILL.md.
Copy and run:
npx skills add sleekdotdesign/agent-skills
Official notes call this interactive browse-to-install. Success: .agents/skills/ appears in the working directory and you can see the installed SKILL.md. First do a read-only check: ask the agent how it would create one mobile-app screen and which Sleek project facts it would use, but do not call an API or change the project yet. If it can point to design-mobile-apps and mention that SLEEK_API_KEY is required, the skill has been found.
Creating a screen or changing a project writes on the Sleek side and is an external action with side effects. Do not authorize a real call until the project and screen scope are confirmed.
Usage cases
Case 1: Create a mobile-app screen. This matches “create design screens” written for design-mobile-apps. Fits when the key is set and the skill already appears under .agents/skills/. First have the agent write the screen structure and copy in chat; authorize a Sleek write only after you confirm. Success: the matching screen appears in the Sleek project. The materials do not expand concrete UI fields or commands; do not fill in anything beyond “can create a screen.”
Case 2: Manage an existing Sleek project. This matches “manage Sleek projects” in the same skill. Fits when the project already exists and you only want the agent to inspect or tidy, not create a design at once. Confirm the project identity first and ask for a read-only account of what it can do now. If the agent does not find .agents/skills/, point it at the installed SKILL.md path as the official note says. Success: it matches that project, rather than creating an unauthorized new screen. The materials do not give details of a project-list API.
Usage limits
The install command points at sleekdotdesign/agent-skills, which is not the same string as the repository URL; do not rewrite it as an install source that never appeared. The materials do not name any required client, and they give no second-marketplace install steps.
Do not call without SLEEK_API_KEY. Keep the key only in an environment variable; do not use placeholder example keys. Current materials prove only this one skill folder; do not invent other skill names or paths.
Creating screens and managing projects both change data in Sleek. Preview first, then authorize. For more, follow the official repository:
https://github.com/designed-by-ai/skills