Agent skill

Style Neobrutalism

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

Install Style Neobrutalism

skills CLI

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

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

GitHub CLI

$ gh skill install pnp/sharepoint-skills style-neobrutalism --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-neobrutalism/style-neobrutalism .claude/skills/style-neobrutalism && 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-neobrutalism" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/style-neobrutalism/style-neobrutalism into .claude/skills/style-neobrutalism/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-neobrutalism", 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-neobrutalism/style-neobrutalism

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-neobrutalism -a codex

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

GitHub CLI

$ gh skill install pnp/sharepoint-skills style-neobrutalism --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-neobrutalism/style-neobrutalism .agents/skills/style-neobrutalism && 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-neobrutalism" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/style-neobrutalism/style-neobrutalism into .agents/skills/style-neobrutalism/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-neobrutalism", 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-neobrutalism -a cursor

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

GitHub CLI

$ gh skill install pnp/sharepoint-skills style-neobrutalism --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-neobrutalism/style-neobrutalism .cursor/skills/style-neobrutalism && 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-neobrutalism" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/style-neobrutalism/style-neobrutalism into .cursor/skills/style-neobrutalism/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-neobrutalism", 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-neobrutalism/style-neobrutalism

--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-neobrutalism -a gemini-cli

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

GitHub CLI

$ gh skill install pnp/sharepoint-skills style-neobrutalism --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-neobrutalism/style-neobrutalism .gemini/skills/style-neobrutalism && 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-neobrutalism" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/style-neobrutalism/style-neobrutalism into .gemini/skills/style-neobrutalism/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-neobrutalism", 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-neobrutalism

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-neobrutalism -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-neobrutalism/style-neobrutalism .github/skills/style-neobrutalism && 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-neobrutalism" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/style-neobrutalism/style-neobrutalism into .github/skills/style-neobrutalism/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-neobrutalism", 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-neobrutalism -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-neobrutalism --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-neobrutalism/style-neobrutalism .opencode/skills/style-neobrutalism && 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-neobrutalism" agent skill from https://github.com/pnp/sharepoint-skills/tree/main/Skills/style-neobrutalism/style-neobrutalism into .opencode/skills/style-neobrutalism/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "style-neobrutalism", 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-neobrutalism
GitHub stars: 133
Token cost: ~3.9k tokens
SKILL.md length: 829 words
Files: 1
Skills in repo: 52
Repo updated: Oct 9, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

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

Works in 4 steps: Document/Item name — bold, 15px, black → Status badge — styled per badge tokens… → Progress section — label "Progress" +… → …
The user says neobrutalism
SKILL.md covers Badge Tokens, Progress Bar Tokens, Deadline Tokens and Row Card Tokens, plus 5 more sections
Reaches developer.microsoft.com

What it does

Style Neobrutalism is an agent skill from pnp/sharepoint-skills. Neobrutalism style tokens and row template for the list-styling skill. Bold black borders, saturated colors, uppercase text, chunky progress bars, sharp edges, card-based row layout with sidebar metadata panel. The row template replaces the entire row with a two-panel card. Use when the user says "neobrutalism," "brutalist," "bold borders," "chunky style," or similar.

Its SKILL.md is about 3.9k 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 neobrutalism
Tasks that involve Design tokens

Example prompts

“neobrutalism,”
“brutalist,”
“bold borders,”
“/style-neobrutalism”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Document/Item name — bold, 15px, black
Status badge — styled per badge tokens (black border, uppercase, saturated color)
Progress section — label "Progress" + bar + percentage (large, bold)
Deadline section — 📅 icon + date + DEADLINE/OVERDUE sublabel

What it can do on your machine

Read from SKILL.md and the folder at commit 69712d2. 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 Neobrutalism loads about 3.9k tokens when it runs. Until then it costs about 97 tokens; SKILL.md has 829 words of instructions outside code blocks.

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

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 69712d2, republished under its MIT licence (© pnp). 829 words, ~3,865 tokens.

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

name: style-neobrutalism
description: Neobrutalism style tokens and row template for the list-styling skill. Bold black borders, saturated colors, uppercase text, chunky progress bars, sharp edges, card-based row layout with sidebar metadata panel. The row template replaces the entire row with a two-panel card. Use when the user says "neobrutalism," "brutalist," "bold borders," "chunky style," or similar.

Neobrutalism — Style Tokens + Row Template

Bold, graphic, raw. Thick black borders. Saturated colors. Uppercase. Card-based row layout with metadata sidebar.

This style uses a full rowFormatter — it replaces the entire row layout, not just individual columns.

Badge Tokens

padding: 4px 12px
border-radius: 3px
font-size: 11px
font-weight: 700
text-transform: uppercase

status_colors

Value	bg	text	border
Draft	`#9ca3af`	`#000000`	`2px solid #000000`
In Review	`#2563eb`	`#ffffff`	`2px solid #000000`
Revising	`#f59e0b`	`#000000`	`2px solid #000000`
Approved	`#16a34a`	`#ffffff`	`2px solid #000000`
Published	`#16a34a`	`#ffffff`	`2px solid #000000`
_fallback	`#e5e7eb`	`#000000`	`2px solid #000000`

Progress Bar Tokens

progress_track_height: 10px
progress_track_bg: #e5e7eb
progress_track_border: 2px solid #000000
progress_track_radius: 2px
progress_fill_radius: 0px
progress_color_low: #ef4444
progress_color_mid: #f59e0b
progress_color_high: #22c55e
progress_label_font_size: 14px
progress_label_font_weight: 800
progress_label_color: #1f2937

Deadline Tokens

deadline_icon: 📅
date_font_size: 13px
date_normal_color: #1f2937
date_normal_weight: 700
date_overdue_color: #dc2626
date_overdue_weight: 800
date_sublabel: DEADLINE
date_sublabel_color: #6b7280
date_sublabel_font_size: 10px

Row Card Tokens

card_border: 3px solid #000000
card_border_radius: 0px
card_background: #ffffff
card_margin_bottom: 8px
card_shadow: 4px 4px 0px #000000
sidebar_width: 280px
sidebar_border_right: 3px solid #000000
sidebar_background: #f9fafb
sidebar_padding: 16px
main_padding: 16px
overdue_card_border_color: #dc2626
overdue_card_shadow: 4px 4px 0px #dc2626

Row Template Layout

The Neobrutalism rowFormatter creates a two-panel card for each item:

┌──────────────────────────────────────────────────────────┐
│ ┌─────────────┐ ┌──────────────────────────────────────┐ │
│ │  SIDEBAR     │ │  MAIN CONTENT                        │ │
│ │              │ │                                      │ │
│ │  Doc Name    │ │  (Weekly tracking columns,           │ │
│ │  [Status]    │ │   additional metadata,               │ │
│ │              │ │   or detail content)                  │ │
│ │  Progress    │ │                                      │ │
│ │  ████░░ 72%  │ │                                      │ │
│ │              │ │                                      │ │
│ │  📅 5/15/26  │ │                                      │ │
│ │  DEADLINE    │ │                                      │ │
│ └─────────────┘ └──────────────────────────────────────┘ │
└──────────────────────────────────────────────────────────┘
   ↑ 3px black border + hard offset shadow (4px 4px 0px black)

Document/Item name — bold, 15px, black
Status badge — styled per badge tokens (black border, uppercase, saturated color)
Progress section — label "Progress" + bar + percentage (large, bold)
Deadline section — 📅 icon + date + DEADLINE/OVERDUE sublabel

Main content contains:

Whatever additional columns exist (weekly tracking, notes, owner, etc.)
If no additional columns, the main area shows the item description or remains minimal

Overdue treatment:

Card border changes from black to red (#dc2626)
Card shadow changes from black to red
Creates an unmistakable "this is overdue" signal without needing to read the date

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",
      "border": "=if([$Deadline] < @now, '3px solid #dc2626', '3px solid #000000')",
      "border-radius": "0px",
      "background-color": "#ffffff",
      "margin-bottom": "8px",
      "box-shadow": "=if([$Deadline] < @now, '4px 4px 0px #dc2626', '4px 4px 0px #000000')",
      "overflow": "hidden",
      "min-height": "120px"
    },
    "children": [
      {
        "elmType": "div",
        "style": {
          "width": "280px",
          "min-width": "280px",
          "border-right": "3px solid #000000",
          "background-color": "#f9fafb",
          "padding": "16px",
          "display": "flex",
          "flex-direction": "column",
          "gap": "10px"
        },
        "children": [
          {
            "elmType": "div",
            "style": {
              "font-size": "15px",
              "font-weight": "800",
              "color": "#000000",
              "line-height": "1.2"
            },
            "txtContent": "=if([$FileLeafRef] == '', [$Title], [$FileLeafRef])"
          },
          {
            "elmType": "div",
            "style": {
              "display": "flex",
              "align-items": "center",
              "gap": "8px"
            },
            "children": [
              {
                "elmType": "span",
                "txtContent": "[$Status]",
                "style": {
                  "display": "inline-block",
                  "padding": "4px 12px",
                  "border-radius": "3px",
                  "font-size": "11px",
                  "font-weight": "700",
                  "text-transform": "uppercase",
                  "white-space": "nowrap",
                  "border": "2px solid #000000",
                  "color": "=if([$Status] == 'Draft', '#000000', if([$Status] == 'In Review', '#ffffff', if([$Status] == 'Revising', '#000000', if([$Status] == 'Approved', '#ffffff', if([$Status] == 'Published', '#ffffff', '#000000')))))",
                  "background-color": "=if([$Status] == 'Draft', '#9ca3af', if([$Status] == 'In Review', '#2563eb', if([$Status] == 'Revising', '#f59e0b', if([$Status] == 'Approved', '#16a34a', if([$Status] == 'Published', '#16a34a', '#e5e7eb')))))"
                }
              },
              {
                "elmType": "span",
                "txtContent": "=if([$Deadline] < @now, '⚠️ AT RISK', '✅ ON TRACK')",
                "style": {
                  "font-size": "11px",
                  "font-weight": "700",
                  "color": "=if([$Deadline] < @now, '#dc2626', '#16a34a')"
                }
              }
            ]
          },
          {
            "elmType": "div",
            "style": {
              "display": "flex",
              "flex-direction": "column",
              "gap": "4px"
            },
            "children": [
              {
                "elmType": "div",
                "style": {
                  "display": "flex",
                  "justify-content": "space-between",
                  "align-items": "center"
                },
                "children": [
                  {
                    "elmType": "span",
                    "txtContent": "Progress",
                    "style": {
                      "font-size": "11px",
                      "font-weight": "600",
                      "color": "#6b7280",
                      "text-transform": "uppercase"
                    }
                  },
                  {
                    "elmType": "span",
                    "txtContent": "=toString([$Progress]) + '%'",
                    "style": {
                      "font-size": "14px",
                      "font-weight": "800",
                      "color": "=if([$Progress] < 30, '#dc2626', if([$Progress] < 66, '#f59e0b', '#16a34a'))"
                    }
                  }
                ]
              },
              {
                "elmType": "div",
                "style": {
                  "width": "100%",
                  "height": "10px",
                  "background-color": "#e5e7eb",
                  "border": "2px solid #000000",
                  "border-radius": "2px",
                  "overflow": "hidden"
                },
                "children": [
                  {
                    "elmType": "div",
                    "style": {
                      "width": "=toString([$Progress]) + '%'",
                      "height": "100%",
                      "border-radius": "0px",
                      "background-color": "=if([$Progress] < 30, '#ef4444', if([$Progress] < 66, '#f59e0b', '#22c55e'))"
                    }
                  }
                ]
              }
            ]
          },
          {
            "elmType": "div",
            "style": {
              "display": "flex",
              "flex-direction": "column",
              "gap": "2px"
            },
            "children": [
              {
                "elmType": "div",
                "style": {
                  "display": "flex",
                  "align-items": "center",
                  "gap": "4px"
                },
                "children": [
                  {
                    "elmType": "span",
                    "txtContent": "📅",
                    "style": { "font-size": "13px" }
                  },
                  {
                    "elmType": "span",
                    "txtContent": "=toLocaleDateString([$Deadline])",
                    "style": {
                      "font-size": "13px",
                      "font-weight": "=if([$Deadline] < @now, '800', '700')",
                      "color": "=if([$Deadline] < @now, '#dc2626', '#1f2937')"
                    }
                  }
                ]
              },
              {
                "elmType": "span",
                "txtContent": "=if([$Deadline] < @now, '⚠️ OVERDUE', 'DEADLINE')",
                "style": {
                  "font-size": "10px",
                  "font-weight": "=if([$Deadline] < @now, '700', '400')",
                  "color": "=if([$Deadline] < @now, '#dc2626', '#6b7280')",
                  "text-transform": "uppercase"
                }
              }
            ]
          }
        ]
      },
      {
        "elmType": "div",
        "style": {
          "flex": "1",
          "padding": "16px",
          "display": "flex",
          "align-items": "center",
          "justify-content": "center",
          "min-height": "100px"
        },
        "children": [
          {
            "elmType": "div",
            "style": {
              "display": "flex",
              "flex-direction": "column",
              "gap": "4px",
              "align-items": "center"
            },
            "children": [
              {
                "elmType": "button",
                "txtContent": "Open Item →",
                "customRowAction": { "action": "defaultClick" },
                "style": {
                  "background-color": "#000000",
                  "color": "#ffffff",
                  "border": "2px solid #000000",
                  "border-radius": "3px",
                  "padding": "8px 20px",
                  "font-size": "12px",
                  "font-weight": "700",
                  "text-transform": "uppercase",
                  "cursor": "pointer"
                }
              }
            ]
          }
        ]
      }
    ]
  }
}

Adapting the rowFormatter

For document libraries: Use [$FileLeafRef] for the file name. The template above handles both lists ([$Title]) and libraries ([$FileLeafRef]) with a conditional.

For lists with additional columns: Replace the "Open Item" button area with actual column content. For example, if there's an Owner column, add it to the sidebar. If there are weekly tracking columns, render them as cards in the main content area.

For weekly tracking columns: If the list has multi-line text columns for weekly updates (e.g., "Mar 23 - Mar 29"), render them as mini-cards in the main content area with tinted backgrounds, following this pattern:

Card background: #fef9c3 (light yellow tint)
Card border: 2px solid #000000
Card border-radius: 0px
Header text: bold, showing the progress change
Detail text: bulleted items from the column value

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

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

✅ Full rowFormatter card layout — NOT default column grid
✅ Two-panel design: metadata sidebar + main content
✅ 3px solid black border on the card
✅ Hard offset box-shadow (4px 4px 0px black) — NO diffused shadows
✅ Shadow and border turn RED for overdue items
✅ Status badge with black border inside the sidebar
✅ ON TRACK / AT RISK indicator next to status
✅ Full-width progress bar with black border in sidebar
✅ Progress percentage is LARGE (14px) and color-coded
✅ Composed deadline with 📅 icon + date + DEADLINE/OVERDUE sublabel
✅ "Open Item" button in main area (or weekly tracking cards)
✅ Every text element is UPPERCASE or BOLD — nothing is lightweight
✅ The overall card design is immediately recognizable as Neobrutalism
✅ Someone seeing this would say "that can't be SharePoint"

Responsive / mobile

≤ 720 px: the 280 px metadata sidebar collapses below the main content. Switch the row container to flex-direction: column and set both panels to width: 100%. The hard black border stays continuous around the full card.
≤ 480 px: drop the uppercase ON TRACK / AT RISK sublabel beside the status badge — the badge alone carries the state. Keep the progress percentage large; this style needs at least one big number visible on mobile.
Hero text step-down: status badge from 14 px → 12 px is acceptable; do not go smaller or the uppercase loses readability.
Touch targets: the "Open Item" button must be ≥ 44 × 44 px on mobile — widen its padding rather than shrinking text.

Implementation notes

Hard-shadow clipping at row edges

The signature hard 4 px offset box-shadow is fragile in two situations:

Adjacent rows with tight spacing: when list row spacing drops below 8 px, the shadow of row N clips into the border of row N + 1. Require list row spacing ≥ 12 px when applying this style.
SharePoint's table-style row containers: some Modern view variants clip the right and bottom shadow at the row container edge. Two fixes — use whichever the renderer allows:
1. Set overflow: visible on the row wrapper (preferred).
2. Drop the shadow offset to 3 px so it fits inside the row's default padding (acceptable trade-off).

Do not remove the shadow — it carries the style identity. Soft-shadow fallback is not a neobrutalism solution; pick a different style if the renderer refuses hard offsets.

Files

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

Open the folder on GitHubat commit 69712d2

Compare with similar skills

Style Neobrutalism 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 Neobrutalism compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Style Neobrutalism this skillpnp/sharepoint-skills	133	—	~3.9k	Automated safety check: Pass	MIT	yesterday
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	yesterday
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 52 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…
133 GitHub stars~1.9k tokensUpdated yesterday
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.
133 GitHub stars~899 tokensUpdated yesterday
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.
133 GitHub stars~2.5k tokensUpdated yesterday
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…
133 GitHub stars~1.2k tokensUpdated yesterday
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.
133 GitHub stars~1.9k tokensUpdated yesterday
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.
133 GitHub stars~2k tokensUpdated yesterday
Auto-check passed

Questions about Style Neobrutalism

What does Style Neobrutalism do?

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

When should I use Style Neobrutalism?

Style Neobrutalism fits situations like: the user says neobrutalism; tasks that involve Design tokens.

How do I install Style Neobrutalism in Claude Code?

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

How do I install Style Neobrutalism in Codex?

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

Can I use Style Neobrutalism 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-neobrutalism -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-neobrutalism, .gemini/skills/style-neobrutalism, .github/skills/style-neobrutalism and .opencode/skills/style-neobrutalism in your project.

What does Style Neobrutalism need to run?

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

Does Style Neobrutalism 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 Neobrutalism 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 Neobrutalism use?

Style Neobrutalism 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 Neobrutalism use?

About 3.9k tokens (SKILL.md is roughly 15k 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 Neobrutalism?

Skills that share tags, products or a category with Style Neobrutalism: 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 Neobrutalism?

pnp (a GitHub organization) maintains it in pnp/sharepoint-skills, which has 133 GitHub stars. The repository holds 52 skills in this directory. The repository was last updated on October 9, 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 Neobrutalism

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Neobrutalism — Style Tokens + Row Template

Badge Tokens

status_colors

Progress Bar Tokens

Deadline Tokens

Row Card Tokens

Row Template Layout

Sidebar contains:

Main content contains:

Overdue treatment:

rowFormatter JSON

Adapting the rowFormatter

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

Responsive / mobile

Implementation notes

Hard-shadow clipping at row edges

Files

Compare with similar skills

Similar skills

More from pnp/sharepoint-skills

Related

Questions about Style Neobrutalism