Agent skill

Style Retro

Retro Memphis style tokens and row template for the list-styling skill.

Install Style Retro

skills CLI

$ npx skills add pnp/sharepoint-skills --skill style-retro -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install pnp/sharepoint-skills style-retro --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/Skills/style-retro/style-retro .claude/skills/style-retro && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "style-retro" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/style-retro/style-retro into .claude/skills/style-retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-retro", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/pnp/sharepoint-skills/tree/main/Skills/style-retro/style-retro

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add pnp/sharepoint-skills --skill style-retro -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install pnp/sharepoint-skills style-retro --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/Skills/style-retro/style-retro .agents/skills/style-retro && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "style-retro" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/style-retro/style-retro into .agents/skills/style-retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-retro", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add pnp/sharepoint-skills --skill style-retro -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install pnp/sharepoint-skills style-retro --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/Skills/style-retro/style-retro .cursor/skills/style-retro && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "style-retro" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/style-retro/style-retro into .cursor/skills/style-retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-retro", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/pnp/sharepoint-skills.git --path Skills/style-retro/style-retro

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add pnp/sharepoint-skills --skill style-retro -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install pnp/sharepoint-skills style-retro --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/Skills/style-retro/style-retro .gemini/skills/style-retro && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "style-retro" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/style-retro/style-retro into .gemini/skills/style-retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-retro", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install pnp/sharepoint-skills style-retro

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add pnp/sharepoint-skills --skill style-retro -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/Skills/style-retro/style-retro .github/skills/style-retro && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "style-retro" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/style-retro/style-retro into .github/skills/style-retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-retro", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add pnp/sharepoint-skills --skill style-retro -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install pnp/sharepoint-skills style-retro --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/pnp/sharepoint-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/Skills/style-retro/style-retro .opencode/skills/style-retro && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "style-retro" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/style-retro/style-retro into .opencode/skills/style-retro/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-retro", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: style-retro
GitHub stars: 132
Token cost: ~3.5k tokens
SKILL.md length: 851 words
Files: 1
Skills in repo: 51
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

Retro Memphis style tokens and row template for the list-styling skill.

The user says retro
SKILL.md covers Badge Tokens, Progress Bar Tokens, Deadline Tokens and Row Card Tokens, plus 5 more sections
Reaches developer.microsoft.com
Tasks that involve Design tokens

What it does

Style Retro is an agent skill from pnp/sharepoint-skills. Retro Memphis style tokens and row template for the list-styling skill. Bright contrasting colors, colored shadows, playful stacked card with a status-colored top banner and large progress number. Layout is a stacked vertical card with a bold colored header strip — NOT a sidebar layout. Use when the user says "retro," "memphis," "80s," "90s," "colorful," "playful," "fun style," or similar.

Its SKILL.md is about 3.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Frontend & Design, covering Design tokens. The repository describes itself as: Skills for Copilot in SharePoint. The licence is MIT.

When your agent uses it

The user says retro
Tasks that involve Design tokens

Example prompts

“retro,”
“memphis,”
“colorful,”
“/style-retro”

What it can do on your machine

Read from SKILL.md and the folder at commit aa9eb14. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are json).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Hosts in commands or code, which the agent is likely to contact:
- developer.microsoft.com
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Style Retro loads about 3.5k tokens when it runs. Until then it costs about 101 tokens; SKILL.md has 851 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~101
When it runs · the whole SKILL.md, loaded when a task matches: ~3.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from pnp/sharepoint-skills at commit aa9eb14, republished under its MIT licence (© pnp). 851 words, ~3,545 tokens.

Download SKILL.mdSave it as .claude/skills/style-retro/SKILL.md (or your agent's skills folder).

name: style-retro
description: Retro Memphis style tokens and row template for the list-styling skill. Bright contrasting colors, colored shadows, playful stacked card with a status-colored top banner and large progress number. Layout is a stacked vertical card with a bold colored header strip — NOT a sidebar layout. Use when the user says "retro," "memphis," "80s," "90s," "colorful," "playful," "fun style," or similar.

Retro Memphis — Style Tokens + Row Template

Bright, playful, LOUD. Every status is a different color. Colored shadows. Stacked vertical card with a bold colored banner. This is the fun one.

Layout philosophy: Stacked vertical card with colored banner. The top third of the card is a bold status-colored banner containing the document name in large white text. Below it, a white content area with the status badge, a large progress percentage, and deadline info. The banner color changes per status — the card's personality changes with every item. This is structurally different from Neobrutalism's horizontal sidebar split.

Badge Tokens

padding: 5px 14px
border-radius: 20px (full pill — playful, round, fun)
font-size: 12px
font-weight: 700
text-transform: uppercase

status_colors

Value	bg	text	border	banner_color
Draft	`#fbbf24`	`#1f2937`	`2px solid #d97706`	`#fbbf24`
In Review	`#3b82f6`	`#ffffff`	`2px solid #7c3aed`	`#3b82f6`
Revising	`#f472b6`	`#ffffff`	`2px solid #db2777`	`#f472b6`
Approved	`#2dd4bf`	`#1f2937`	`2px solid #0d9488`	`#2dd4bf`
Published	`#a78bfa`	`#ffffff`	`2px solid #7c3aed`	`#a78bfa`
_fallback	`#e5e7eb`	`#374151`	`2px solid #9ca3af`	`#e5e7eb`

CRITICAL: The banner_color IS the status bg color — the entire top of the card floods with the status hue. Draft cards have a yellow top. In Review cards have a blue top. Revising cards have a hot pink top. Every card in the list is a different color.

Progress Bar Tokens

progress_track_height: 10px
progress_track_bg: #fef3c7 (warm yellow tint)
progress_track_border: 2px solid #d97706
progress_track_radius: 5px
progress_fill_radius: 3px
progress_color_low: #f472b6 (HOT PINK — not red)
progress_color_mid: #3b82f6 (ELECTRIC BLUE — not amber)
progress_color_high: #2dd4bf (TEAL — not green)
progress_label_font_size: 28px (HUGE — the hero element)
progress_label_font_weight: 800
progress_label_color: #7c3aed (PURPLE)

Deadline Tokens

deadline_icon: 🗓️
date_font_size: 13px
date_normal_color: #374151
date_normal_weight: 600
date_overdue_color: #db2777 (HOT PINK — not red)
date_overdue_weight: 800
date_sublabel_color: #7c3aed (PURPLE)
overdue_label: 🔥 OVERDUE

Row Card Tokens

card_border: 3px solid (color matches status shadow_color)
card_border_radius: 12px (rounded — playful)
card_background: #ffffff
card_margin_bottom: 12px
card_shadow: 6px 6px 0px (large hard offset — COLORED per status)
banner_height: (auto — wraps content with padding)
banner_padding: 16px 20px
content_padding: 16px 20px
overdue_border_color: #db2777
overdue_shadow_color: #db2777

Row Template Layout

Stacked vertical card with a status-colored banner on top.

    ╭──────────────────────────────────────────────────╮
    │▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│
    │▓▓  API Guide.docx                             ▓▓│ ← status-colored
    │▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓│   banner
    │                                                  │
    │  [IN REVIEW]  🎯 ON TRACK     72%    🗓️ 5/15/26 │ ← white content
    │                                                  │
    │  ░░████████████████████████████████░░░░░░░░░░░   │ ← warm yellow
    │                                                  │   track + amber
    ╰──────────────────────────────────────────────────╯   border
       ▓▓▓▓▓▓ ← 6px colored offset shadow

Key difference from Neobrutalism: Neobrutalism is a HORIZONTAL split (sidebar left, content right). Retro is a VERTICAL split (banner top, content bottom). Even the silhouettes are different.

rowFormatter JSON

Adapt before applying. The column names below ([$Status], [$Progress], [$Deadline]) are example placeholders — replace them with the actual internal column names from the user's list. Also update every status value string ('Draft', 'In Review', 'Revising', etc.) to match the user's actual Choice values. Follow list-styling Step 3.

json

{
  "$schema": "https://developer.microsoft.com/json-schemas/sp/v2/view-formatting.schema.json",
  "hideSelection": false,
  "hideColumnHeaders": true,
  "rowFormatter": {
    "elmType": "div",
    "style": {
      "display": "flex",
      "flex-direction": "column",
      "border": "=if([$Deadline] < @now, '3px solid #db2777', if([$Status] == 'Draft', '3px solid #d97706', if([$Status] == 'In Review', '3px solid #7c3aed', if([$Status] == 'Revising', '3px solid #db2777', if([$Status] == 'Approved', '3px solid #0d9488', if([$Status] == 'Published', '3px solid #7c3aed', '3px solid #9ca3af'))))))",
      "border-radius": "12px",
      "background-color": "#ffffff",
      "margin-bottom": "12px",
      "box-shadow": "=if([$Deadline] < @now, '6px 6px 0px #db2777', if([$Status] == 'Draft', '6px 6px 0px #d97706', if([$Status] == 'In Review', '6px 6px 0px #7c3aed', if([$Status] == 'Revising', '6px 6px 0px #db2777', if([$Status] == 'Approved', '6px 6px 0px #0d9488', if([$Status] == 'Published', '6px 6px 0px #7c3aed', '6px 6px 0px #9ca3af'))))))",
      "overflow": "hidden"
    },
    "children": [
      {
        "elmType": "div",
        "style": {
          "padding": "16px 20px",
          "background-color": "=if([$Deadline] < @now, '#db2777', if([$Status] == 'Draft', '#fbbf24', if([$Status] == 'In Review', '#3b82f6', if([$Status] == 'Revising', '#f472b6', if([$Status] == 'Approved', '#2dd4bf', if([$Status] == 'Published', '#a78bfa', '#e5e7eb'))))))",
          "display": "flex",
          "align-items": "center",
          "gap": "10px"
        },
        "children": [
          {
            "elmType": "div",
            "style": {
              "font-size": "16px",
              "font-weight": "800",
              "color": "=if([$Status] == 'Draft', '#1f2937', if([$Status] == 'Approved', '#1f2937', '#ffffff'))",
              "flex": "1",
              "line-height": "1.3"
            },
            "txtContent": "=if([$FileLeafRef] == '', [$Title], [$FileLeafRef])"
          },
          {
            "elmType": "span",
            "txtContent": "=if([$Deadline] < @now, '🔥', '✨')",
            "style": {
              "font-size": "20px"
            }
          }
        ]
      },
      {
        "elmType": "div",
        "style": {
          "padding": "16px 20px",
          "display": "flex",
          "flex-direction": "column",
          "gap": "12px"
        },
        "children": [
          {
            "elmType": "div",
            "style": {
              "display": "flex",
              "align-items": "center",
              "gap": "14px",
              "flex-wrap": "wrap"
            },
            "children": [
              {
                "elmType": "span",
                "txtContent": "[$Status]",
                "style": {
                  "display": "inline-block",
                  "padding": "5px 14px",
                  "border-radius": "20px",
                  "font-size": "12px",
                  "font-weight": "700",
                  "text-transform": "uppercase",
                  "white-space": "nowrap",
                  "border": "=if([$Status] == 'Draft', '2px solid #d97706', if([$Status] == 'In Review', '2px solid #7c3aed', if([$Status] == 'Revising', '2px solid #db2777', if([$Status] == 'Approved', '2px solid #0d9488', if([$Status] == 'Published', '2px solid #7c3aed', '2px solid #9ca3af')))))",
                  "color": "=if([$Status] == 'Draft', '#1f2937', if([$Status] == 'In Review', '#ffffff', if([$Status] == 'Revising', '#ffffff', if([$Status] == 'Approved', '#1f2937', if([$Status] == 'Published', '#ffffff', '#374151')))))",
                  "background-color": "=if([$Status] == 'Draft', '#fbbf24', if([$Status] == 'In Review', '#3b82f6', if([$Status] == 'Revising', '#f472b6', if([$Status] == 'Approved', '#2dd4bf', if([$Status] == 'Published', '#a78bfa', '#e5e7eb')))))"
                }
              },
              {
                "elmType": "span",
                "txtContent": "=if([$Deadline] < @now, '🔥 AT RISK', '🎯 ON TRACK')",
                "style": {
                  "font-size": "11px",
                  "font-weight": "700",
                  "color": "=if([$Deadline] < @now, '#db2777', '#0d9488')"
                }
              },
              {
                "elmType": "span",
                "txtContent": "=toString([$Progress]) + '%'",
                "style": {
                  "font-size": "28px",
                  "font-weight": "800",
                  "color": "#7c3aed",
                  "margin-left": "auto"
                }
              }
            ]
          },
          {
            "elmType": "div",
            "style": {
              "width": "100%",
              "height": "10px",
              "background-color": "#fef3c7",
              "border": "2px solid #d97706",
              "border-radius": "5px",
              "overflow": "hidden"
            },
            "children": [
              {
                "elmType": "div",
                "style": {
                  "width": "=toString([$Progress]) + '%'",
                  "height": "100%",
                  "border-radius": "3px",
                  "background-color": "=if([$Progress] < 30, '#f472b6', if([$Progress] < 66, '#3b82f6', '#2dd4bf'))"
                }
              }
            ]
          },
          {
            "elmType": "div",
            "style": {
              "display": "flex",
              "align-items": "center",
              "gap": "6px"
            },
            "children": [
              {
                "elmType": "span",
                "txtContent": "🗓️",
                "style": { "font-size": "13px" }
              },
              {
                "elmType": "span",
                "txtContent": "=toLocaleDateString([$Deadline])",
                "style": {
                  "font-size": "13px",
                  "font-weight": "=if([$Deadline] < @now, '800', '600')",
                  "color": "=if([$Deadline] < @now, '#db2777', '#374151')"
                }
              },
              {
                "elmType": "span",
                "txtContent": "=if([$Deadline] < @now, '🔥 OVERDUE', 'DEADLINE')",
                "style": {
                  "font-size": "10px",
                  "font-weight": "=if([$Deadline] < @now, '700', '500')",
                  "color": "=if([$Deadline] < @now, '#db2777', '#7c3aed')",
                  "text-transform": "uppercase"
                }
              }
            ]
          }
        ]
      }
    ]
  }
}

Checklist — "I Can't Believe That's SharePoint"

✅ Full rowFormatter — NOT default column grid
✅ VERTICAL STACKED layout with colored banner on top — NOT a sidebar (structurally different from Neobrutalism)
✅ Banner background FLOODS with the status color — yellow, blue, pink, teal, or lavender
✅ Document name is white-on-color in the banner — bold and prominent
✅ ✨ sparkle emoji in banner (🔥 for overdue) — playful decorative element
✅ Card border AND shadow color change per status — colored, NEVER black
✅ 6px hard offset colored shadows (bigger than Neobrutalism's 4px)
✅ Rounded corners (12px) — playful, not sharp
✅ Pill-shaped status badges (20px radius) with colored borders
✅ Progress percentage is HUGE (28px) and PURPLE — pushed to the right
✅ Progress bar track is warm yellow (#fef3c7) with amber border
✅ Progress fills are PINK → BLUE → TEAL (not red → amber → green)
✅ Deadline sublabel is PURPLE, overdue is HOT PINK with 🔥
✅ Every status gets its own distinct hue — no repeats
✅ Overdue cards: banner turns hot pink, border/shadow turn hot pink, 🔥 replaces ✨
✅ The list looks like a bag of candy exploded — in a good way
✅ Silhouette test: banner-on-top looks NOTHING like sidebar-on-left (Neobrutalism)

Show full SKILL.md (266 more words)Show less

Responsive / mobile

≤ 600 px: drop the colored box-shadow offset from 4 px to 2 px so it doesn't clip the next card.
≤ 480 px: the banner stays full-width — it carries the identity. Stack the metadata (progress + deadline) vertically below it.
Hero text: the large progress percentage below the banner steps 32 px → 24 px on mobile. Do not go below 24 px.
Touch targets: ≥ 44 × 44 px on the row card.

Implementation notes

Status-tinted shadows render inconsistently

The colored box-shadow (hot pink for overdue, banner color elsewhere) is not portable:

Chrome / Edge: render the offset and color correctly.
Safari: occasionally mutes saturation on box-shadow colors, so the pink reads more salmon than hot.
Older SharePoint themes: strip multi-layer or colored box-shadow entirely.

Provide a fallback that does not depend on the shadow: the colored top banner must always render — it is the primary identity element. The shadow is decoration. When QA shows the shadow is missing in a target environment, do not add a different decoration; let the banner do the work.

The pink/blue/teal progress palette is intentional — explain it once

Consumers used to traffic-light progress (red < 30% → amber → green ≥ 70%) will see a 95 % card filled in teal and assume the style is broken. It is not. Retro Memphis progress goes pink → blue → teal by design — each value gets its own distinct hue, the way 80s Memphis palettes worked.

When applying this style for the first time in a tenant, surface this fact in a single sentence to the user: "Progress in Retro Memphis uses pink → blue → teal instead of red → amber → green — that's intentional."

Files

Just SKILL.md in Skills/style-retro/style-retro of pnp/sharepoint-skills.

Open the folder on GitHubat commit aa9eb14

Compare with similar skills

Style Retro next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Style Retro compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Style Retro this skillpnp/sharepoint-skills	132	—	~3.5k	Automated safety check: Pass	MIT	3 days ago
Figma Design System Builderwarpdotdev/warp	65k	2 repos	~4.4k	Automated safety check: Pass	AGPL-3.0	today
Figma use_figma Plugin API Ruleswarpdotdev/warp	65k	4 repos	~4.4k	Automated safety check: Pass	AGPL-3.0	today
MCP Developmentcoollabsio/coolify	63k	1 repos	~949	Automated safety check: Pass	MIT	today
Design SystemOhh-889/skyroc	795	11 repos	~1.7k	Automated safety check: Pass	MIT	1 mo ago
Design Dnazanwei/design-dna	1.9k	1 repos	~2.1k	Automated safety check: Pass	MIT	1 mo ago

Similar skills

Figma Design System Builder
warpdotdev/warp
Builds or updates a design system in Figma from a codebase in ordered phases: discovery, variables and tokens, components, theming and documentation, with checkpoints.
65k GitHub starsUsed in 2 repos~4.4k tokens
Frontend & DesignAuto-check passed
Figma use_figma Plugin API Rules
warpdotdev/warp
Required groundwork before any use_figma call: the rules and reference files for running JavaScript in a Figma file through the Plugin API without common failures.
65k GitHub starsUsed in 4 repos~4.4k tokens
Frontend & DesignAuto-check passed
MCP Development
coollabsio/coolify
A skill your agent uses for Laravel MCP development. An agent skill from coollabsio/coolify.
63k GitHub starsUsed in 1 repo~949 tokens
Frontend & DesignAuto-check passed
Design System
Ohh-889/skyroc
Token architecture, component specifications, and slide generation.
795 GitHub starsUsed in 11 repos~1.7k tokens
Frontend & DesignAuto-check passed
Design Dna
zanwei/design-dna
Extract, define, and apply design DNA across three dimensions: design system (tokens), design style (qualitative feel), and visual effects (Canvas, WebGL, 3D, particles, shaders, scroll effects…
1.9k GitHub starsUsed in 1 repo~2.1k tokens
Frontend & DesignAuto-check passed
Figma Design to Code
warpdotdev/warp
Turns a Figma frame or component into production code that matches the design, using the Figma MCP server and the project's own design system.
65k GitHub starsUsed in 4 repos~2.9k tokens
Frontend & DesignAuto-check passed

More from pnp/sharepoint-skills

All 51 skills in this repo

Scorecard Matrix
pnp/sharepoint-skills
Generates a polished, self-contained HTML heatmap scorecard — a weighted comparison matrix where entities (rows) are scored across dimensions (columns), with computed totals, rank badges, and a…
132 GitHub stars~1.9k tokensUpdated 3 days ago
Auto-check passed
Analyze Document Library
pnp/sharepoint-skills
Analyze the current SharePoint document library in read-only mode and produce a structured summary of files, folders, file types, recent activity, naming issues, and organization recommendations.
132 GitHub stars~899 tokensUpdated 3 days ago
Auto-check passed
Broken Link Auditor
pnp/sharepoint-skills
Audits SharePoint pages, news posts, and hyperlink fields for broken or risky links and saves a self-contained HTML link-health report to the site.
132 GitHub stars~2.5k tokensUpdated 3 days ago
Auto-check passed
Custom Image Tagger
pnp/sharepoint-skills
Analyze selected construction images, create missing object metadata columns, and write concise visual metadata back to SharePoint columns using explicit image-analysis, list-schema, list-update…
132 GitHub stars~1.2k tokensUpdated 3 days ago
Auto-check passed
Dossier
pnp/sharepoint-skills
Renders a polished, self-contained HTML briefing from any data source — SharePoint lists, uploaded documents, or a verbal description.
132 GitHub stars~1.9k tokensUpdated 3 days ago
Auto-check passed
Exec Report
pnp/sharepoint-skills
Generates a polished, self-contained HTML executive report or dashboard from any data source — SharePoint lists, CSV exports, or a user description.
132 GitHub stars~2k tokensUpdated 3 days ago
Auto-check passed

Questions about Style Retro

What does Style Retro do?

Retro Memphis style tokens and row template for the list-styling skill. Style Retro is an agent skill from pnp/sharepoint-skills. Retro Memphis style tokens and row template for the list-styling skill.

When should I use Style Retro?

Style Retro fits situations like: the user says retro; tasks that involve Design tokens.

How do I install Style Retro in Claude Code?

Run `npx skills add pnp/sharepoint-skills --skill style-retro -a claude-code`. Or copy the skill folder (Skills/style-retro/style-retro in pnp/sharepoint-skills) into .claude/skills/style-retro in your project. Claude Code loads it when a task matches its description.

How do I install Style Retro in Codex?

Run `npx skills add pnp/sharepoint-skills --skill style-retro -a codex`. Or copy the skill folder (Skills/style-retro/style-retro in pnp/sharepoint-skills) into .agents/skills/style-retro in your project. Codex loads it when a task matches its description.

Can I use Style Retro in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add pnp/sharepoint-skills --skill style-retro -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/style-retro, .gemini/skills/style-retro, .github/skills/style-retro and .opencode/skills/style-retro in your project.

What does Style Retro need to run?

SKILL.md names no scripts, command-line tools or credentials: Style Retro is instructions for the agent only.

Does Style Retro access the network?

SKILL.md names 1 domain. In commands or code: developer.microsoft.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

Is Style Retro safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Style Retro use?

Style Retro is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Style Retro use?

About 3.5k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Style Retro?

Skills that share tags, products or a category with Style Retro: Figma Design System Builder (warpdotdev/warp, 65k stars), Figma use_figma Plugin API Rules (warpdotdev/warp, 65k stars), MCP Development (coollabsio/coolify, 63k stars) and Design System (Ohh-889/skyroc, 795 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Style Retro?

pnp (a GitHub organization) maintains it in pnp/sharepoint-skills, which has 132 GitHub stars. The repository holds 51 skills in this directory. The repository was last updated on October 6, 2026.

Source: pnp/sharepoint-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Style Retro

Facts

At a glance

What it does

When your agent uses it

Example prompts

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Retro Memphis — Style Tokens + Row Template

Badge Tokens

status_colors

Progress Bar Tokens

Deadline Tokens

Row Card Tokens

Row Template Layout

rowFormatter JSON

Checklist — "I Can't Believe That's SharePoint"

Responsive / mobile

Implementation notes

Status-tinted shadows render inconsistently

The pink/blue/teal progress palette is intentional — explain it once

Files

Compare with similar skills

Similar skills

More from pnp/sharepoint-skills

Related

Questions about Style Retro