The Problem
Design teams need a quick way to generate mobile‑app UI screens without manually laying out each component. Without automation, designers spend hours on repetitive layout work, delaying product iteration.
What This Does
The repository provides a Sleek Agent skill that lets the Sleek AI‑design platform create mobile‑app screens on demand. The skill is defined in skills/design-mobile-apps/SKILL.md, which describes the prompts and API calls required to drive Sleek’s backend. The top‑level README.md lists the skill, shows a hero image (assets/hero.png), and supplies the npm‑based installation commands. No source code beyond markdown is shipped; the runtime logic lives inside Sleek’s own agent framework, not in this repo.
How It Is Wired
Because the repo contains only documentation (README.md, LICENSE, SKILL.md) and a static image, there is no executable code to trace. The wiring therefore consists of:
| File | Role |
|---|---|
skills/design-mobile-apps/SKILL.md | Declares the skill’s name, description, required parameters, and the HTTP request that the Sleek agent will issue to the Sleek API. |
README.md | Provides the user‑facing install instructions (npx skills add …). The command copies the SKILL.md into the consumer’s .agents/skills/ directory, where Sleek’s runtime loads it. |
LICENSE | Legal wrapper, no runtime effect. |
assets/hero.png | Visual branding only. |
The actual execution flow is handled by the external Sleek agent runtime:
- User runs
npx skills add sleekdotdesign/agent-skills -s sleek-design-mobile-apps. - The
npxtool fetches this repo, extractsSKILL.md, and writes it to<project>/.agents/skills/design-mobile-apps/. - When a Sleek‑enabled agent starts, it scans
.agents/skills/forSKILL.mdfiles, parses the YAML/JSON payload inside, and registers the skill. - At runtime, a request to the skill triggers the agent to call the Sleek API using the
SLEEK_API_KEYenvironment variable, returning generated screen assets.
No internal call graph exists in this repository; the only “code” is the declarative skill definition consumed by external tooling.
How To Use It
# Clone the repo (optional, for inspection)
git clone https://github.com/moses-y/agent-skillz
# Install the skill into your project
npx skills add sleekdotdesign/agent-skills # interactive picker
# or install the specific skill directly
npx skills add sleekdotdesign/agent-skills -s sleek-design-mobile-apps
Prerequisites
- A Sleek account (free trial or Pro).
SLEEK_API_KEYset in the environment. The README points to Sleek’s key‑generation UI.
Running After installation, invoke the skill from any Sleek‑compatible agent (e.g., a chatbot or CLI that loads .agents/skills/). The agent will forward the request to Sleek’s API and return generated mockups.
Real‑World Use
A product team integrates the skill into its internal design bot. When a product manager types “Create a login screen for our new health app,” the bot loads SKILL.md, sends the prompt to Sleek, and posts the resulting mockup back to the Slack channel. The workflow eliminates manual sketching and accelerates UI review cycles.
Code Health & Issues
- Medium – No tests – repository-wide – No test files are present, so code paths (the skill definition) are unverified.
- Medium – No CI/CD – repository-wide – No
.github/workflows, Dockerfile, or other pipeline configuration. - Low – License present – root –
LICENSEexists (MIT), satisfying legal distribution. - Low – No lockfile – root – No
package-lock.jsonor similar, which could lead to nondeterministic dependency resolution for thenpxinstall step.
All findings are derived from the static analysis output; no additional issues were inferred.
The Bottom Line
The repo supplies a ready‑to‑install Sleek skill that offloads mobile‑app UI generation to Sleek’s AI service. It is well‑documented but contains only declarative assets, leaving the actual execution to external tooling. Lack of tests and CI means the skill definition is unvalidated, so teams should treat it as a prototype and add their own verification before production use. Suitable for developers already invested in the Sleek ecosystem who need a quick, low‑code UI generation shortcut.