# AI use cases for Skills (juliobsz/skills)

Repo: [juliobsz/skills](https://github.com/juliobsz/skills) | Use cases: 4 | Page: https://dedupedai.com/use-cases/juliobsz-skills/

A set of agent skills, /awwwards and /jury, that build award-style websites from a one-line brief and score existing sites the way an Awwwards jury would.

This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL.

- Build a distinctive portfolio site from one line: https://dedupedai.com/use-cases/juliobsz-skills/build-portfolio-from-one-line/
- Score a live website like an Awwwards jury: https://dedupedai.com/use-cases/juliobsz-skills/score-live-site-like-awwwards-jury/
- Compare your site against a competitor's: https://dedupedai.com/use-cases/juliobsz-skills/compare-two-sites-with-jury/
- Redesign an existing landing page in your project: https://dedupedai.com/use-cases/juliobsz-skills/redesign-landing-page-in-project/

## How to build a distinctive portfolio site from one line with Skills

Repo: [juliobsz/skills](https://github.com/juliobsz/skills) | Difficulty: Intermediate | Time: 1 hour | Basis: From the README

Get a designed, browser-checked portfolio site from a single sentence instead of a template.

**Who it is for:** A freelancer or creative who needs a personal site fast and does not want the generic purple-gradient, three-card default an agent usually produces.

**The problem:** Asking an agent for a portfolio usually returns the same bland layout, with placeholder copy and no design direction.

**The outcome:** A built site with a written concept, a DESIGN.md design system, semantic HTML, screenshots checked on desktop and mobile, and a list of placeholders you still need to replace.

### Steps

1. Run `npx skills add juliobsz/skills -g` in a terminal.
2. Open a new agent session so it loads the skill.
3. Type `make me a portfolio, my name is <your name>` or ask for a website in one line. (inferred, check the README)
4. Read the assumptions the agent writes down, and the DESIGN.md it produces.
5. Replace every placeholder listed at the end of the run with your real projects, photos and copy.
6. Confirm before the agent deploys to Vercel, Netlify or Cloudflare.

### Prompt to paste into your agent

```text
Using the juliobsz/skills repo, run the /awwwards skill with the brief 'make me a portfolio, my name is <name>, I work as <craft>'. Expect a built site folder, a DESIGN.md file and a list of placeholder copy. Verify that no placeholder text remains in the final HTML before you report the site as done.
```

### Caveat

The README gives no run time, so the 1 hour figure is an estimate, and it notes a full run is long with heavy token use.

Risk, credentials: Deploying to Vercel, Netlify or Cloudflare requires your own account login, so only grant deploy access you are comfortable with.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/juliobsz-skills/build-portfolio-from-one-line/

## How to score a live website like an Awwwards jury with Skills

Repo: [juliobsz/skills](https://github.com/juliobsz/skills) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Get a scorecard with screenshots and measurements for any reachable site.

**Who it is for:** A designer or developer who wants an honest, evidence-based review of a live site before showing it to a client or submitting it.

**The problem:** Opinions about a site's design, speed and accessibility are hard to compare, and most reviews do not cite evidence.

**The outcome:** A .jury/ folder with a scorecard.md, screenshots and reports, where every number cites a screenshot or measurement, and fixes ranked by how much score they would gain.

### Steps

1. Run `npx skills add juliobsz/skills -g` in a terminal.
2. Open a new agent session so it loads the skill.
3. Type `/jury https://your-site.com` with the URL of the live site.
4. Open .jury/scorecard.md and read the ranked fix list first.
5. Check the jury estimate band against the critic score before you act on it.

### Prompt to paste into your agent

```text
Using the juliobsz/skills repo, run the /jury skill on <target URL>. Expect a .jury/scorecard.md file with screenshots, Core Web Vitals measurements and a ranked fix list. Verify that each score in the scorecard links to a screenshot or measurement in the .jury folder.
```

### Caveat

The jury estimate rests on two winning sites and is not affiliated with Awwwards, and pages behind a login cannot be scored.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/juliobsz-skills/score-live-site-like-awwwards-jury/

## How to compare your site against a competitor's with Skills

Repo: [juliobsz/skills](https://github.com/juliobsz/skills) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README

Score two sites side by side with the same rubric and evidence.

**Who it is for:** A product or marketing lead who wants to see where their site falls short of a competitor's on design, usability and content.

**The problem:** Judging your own site against a rival by eye is subjective, and it is easy to miss accessibility or performance gaps.

**The outcome:** Two scored reports under the same rubric, showing where each site leads or trails, with evidence you can share.

### Steps

1. Run `npx skills add juliobsz/skills -g` in a terminal.
2. Open a new agent session so it loads the skill.
3. Type `/jury https://mine.com vs https://theirs.com` with both URLs.
4. Open the scorecard for each site in the .jury/ folder.
5. Compare the categories where the gap is largest and start with the top ranked fixes.

### Prompt to paste into your agent

```text
Using the juliobsz/skills repo, run /jury on <your URL> vs <competitor URL>. Expect two scorecards in the .jury/ folder with the same categories. Verify that both sites were scored with the same rubric and that each score cites its screenshots.
```

### Caveat

Both URLs must be reachable without a login, and the critic scores only stills and measurements, so motion and sound are not part of the result.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/juliobsz-skills/compare-two-sites-with-jury/

## How to redesign an existing landing page in your project with Skills

Repo: [juliobsz/skills](https://github.com/juliobsz/skills) | Difficulty: Advanced | Time: 1 hour | Basis: From the README

Rebuild a landing page inside your own project and check it before shipping.

**Who it is for:** A developer or founder with an existing site who wants a stronger visual design and a pre-launch quality check.

**The problem:** A working landing page often looks generic, and checking every breakpoint and reduced motion state by hand takes time.

**The outcome:** A redesigned page in the project, a DESIGN.md design system, real-browser screenshots, and a score from the same blind critic used by /awwwards.

### Steps

1. Run `npx skills add juliobsz/skills -g` in a terminal.
2. Open a new agent session inside your project folder.
3. Type `/awwwards` and ask: redesign this landing page so it could win site of the day.
4. If the agent reports Playwright missing, run `npm i -D playwright` in the project, then `npx playwright install chromium` once.
5. Review the new screenshots and the DESIGN.md before accepting the changes.

### Prompt to paste into your agent

```text
Using the juliobsz/skills repo, run /awwwards inside <project folder> to redesign the landing page at <page path>. Expect updated page files, a DESIGN.md and screenshots for desktop, mobile and reduced motion. Verify that the production build still succeeds before you report the redesign as complete.
```

### Caveat

The README says the skill installs Playwright as a dev dependency in your project, so expect changes to package.json, and the 1 hour figure is an estimate.

Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/

URL: https://dedupedai.com/use-cases/juliobsz-skills/redesign-landing-page-in-project/