Agent skill

Style Monochrome

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

Install Style Monochrome

skills CLI

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

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

GitHub CLI

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

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

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

GitHub CLI

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

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

GitHub CLI

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

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

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

GitHub CLI

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

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

At a glance

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

The user says monochrome
SKILL.md covers Badge Tokens, Row Card Tokens, Row Template Layout and rowFormatter JSON, plus 3 more sections
Reaches developer.microsoft.com
Tasks that involve Design tokens

What it does

Style Monochrome is an agent skill from pnp/sharepoint-skills. Monochrome style tokens and row template for the list-styling skill. Single-hue slate design with a left-aligned large progress number as the hero element, all metadata stacked beside it. Layout uses the progress percentage as the dominant visual element. Use when the user says "monochrome," "single color," "corporate," "tonal," "minimal," or similar.

Its SKILL.md is about 2.4k 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 and Cloud office suites. The repository describes itself as: Skills for Copilot in SharePoint. The licence is MIT.

When your agent uses it

The user says monochrome
Tasks that involve Design tokens
Tasks that involve Cloud office suites

Example prompts

“monochrome,”
“single color,”
“corporate,”
“/style-monochrome”

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 Monochrome loads about 2.4k tokens when it runs. Until then it costs about 93 tokens; SKILL.md has 561 words of instructions outside code blocks.

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

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). 561 words, ~2,418 tokens.

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

name: style-monochrome
description: Monochrome style tokens and row template for the list-styling skill. Single-hue slate design with a left-aligned large progress number as the hero element, all metadata stacked beside it. Layout uses the progress percentage as the dominant visual element. Use when the user says "monochrome," "single color," "corporate," "tonal," "minimal," or similar.

Monochrome — Style Tokens + Row Template

Single-hue, restrained, corporate. Everything is slate blue. The progress percentage is the HERO — displayed enormous on the left, with metadata stacked to its right. Shade = stage.

Layout philosophy: Hero number + stacked metadata. The progress percentage is displayed huge (32px) on the left side of the card as the primary visual anchor. Status, name, and deadline stack vertically to its right. The big number makes each card instantly scannable.

Badge Tokens

padding: 5px 14px
border-radius: 6px
font-size: 11px
font-weight: 600
text-transform: uppercase

status_colors (shade ramp — lightest = earliest)

Value	bg	text	border
Draft	`#cbd5e1`	`#334155`	`0px`
In Review	`#64748b`	`#ffffff`	`0px`
Revising	`#475569`	`#ffffff`	`0px`
Approved	`#334155`	`#ffffff`	`0px`
Published	`#1e293b`	`#ffffff`	`0px`
_fallback	`#e2e8f0`	`#475569`	`0px`

Row Card Tokens

card_border: 1px solid #e2e8f0
card_border_radius: 6px
card_background: #ffffff
card_margin_bottom: 6px
card_shadow: none
left_accent_width: 4px (thin left border in status shade)
hero_number_size: 32px
hero_number_weight: 800

Row Template Layout

Hero progress number on the left, metadata stacked right.

┃ ┌────────────────────────────────────────────────────┐
┃ │                                                    │
┃ │   72%     API Guide.docx                           │
┃ │           [In Review]  ·  5/15/2026                │
┃ │           ████████████████████░░░░░░               │
┃ │                                                    │
┃ └────────────────────────────────────────────────────┘
↑ 4px left accent in status shade color

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",
      "align-items": "center",
      "border": "1px solid #e2e8f0",
      "border-left": "=if([$Status] == 'Draft', '4px solid #cbd5e1', if([$Status] == 'In Review', '4px solid #64748b', if([$Status] == 'Revising', '4px solid #475569', if([$Status] == 'Approved', '4px solid #334155', if([$Status] == 'Published', '4px solid #1e293b', '4px solid #e2e8f0')))))",
      "border-radius": "6px",
      "background-color": "#ffffff",
      "margin-bottom": "6px",
      "padding": "16px 20px",
      "gap": "20px",
      "min-height": "80px"
    },
    "children": [
      {
        "elmType": "div",
        "style": {
          "min-width": "72px",
          "display": "flex",
          "align-items": "center",
          "justify-content": "center"
        },
        "children": [
          {
            "elmType": "span",
            "txtContent": "=toString([$Progress]) + '%'",
            "style": {
              "font-size": "32px",
              "font-weight": "800",
              "color": "=if([$Status] == 'Draft', '#94a3b8', if([$Status] == 'In Review', '#64748b', if([$Status] == 'Revising', '#475569', if([$Status] == 'Approved', '#334155', if([$Status] == 'Published', '#1e293b', '#94a3b8')))))",
              "line-height": "1"
            }
          }
        ]
      },
      {
        "elmType": "div",
        "style": {
          "flex": "1",
          "display": "flex",
          "flex-direction": "column",
          "gap": "8px"
        },
        "children": [
          {
            "elmType": "div",
            "style": {
              "font-size": "14px",
              "font-weight": "600",
              "color": "#1e293b"
            },
            "txtContent": "=if([$FileLeafRef] == '', [$Title], [$FileLeafRef])"
          },
          {
            "elmType": "div",
            "style": {
              "display": "flex",
              "align-items": "center",
              "gap": "10px"
            },
            "children": [
              {
                "elmType": "span",
                "txtContent": "[$Status]",
                "style": {
                  "display": "inline-block",
                  "padding": "4px 12px",
                  "border-radius": "6px",
                  "font-size": "11px",
                  "font-weight": "600",
                  "text-transform": "uppercase",
                  "white-space": "nowrap",
                  "color": "=if([$Status] == 'Draft', '#334155', '#ffffff')",
                  "background-color": "=if([$Status] == 'Draft', '#cbd5e1', if([$Status] == 'In Review', '#64748b', if([$Status] == 'Revising', '#475569', if([$Status] == 'Approved', '#334155', if([$Status] == 'Published', '#1e293b', '#e2e8f0')))))"
                }
              },
              {
                "elmType": "span",
                "txtContent": "·",
                "style": { "color": "#cbd5e1", "font-size": "16px" }
              },
              {
                "elmType": "span",
                "txtContent": "=toLocaleDateString([$Deadline])",
                "style": {
                  "font-size": "12px",
                  "font-weight": "=if([$Deadline] < @now, '700', '400')",
                  "color": "=if([$Deadline] < @now, '#1e293b', '#64748b')"
                }
              },
              {
                "elmType": "span",
                "txtContent": "=if([$Deadline] < @now, '— overdue', '')",
                "style": {
                  "font-size": "11px",
                  "font-weight": "700",
                  "color": "#1e293b"
                }
              }
            ]
          },
          {
            "elmType": "div",
            "style": {
              "width": "100%",
              "height": "4px",
              "background-color": "#e2e8f0",
              "border-radius": "2px",
              "overflow": "hidden"
            },
            "children": [
              {
                "elmType": "div",
                "style": {
                  "width": "=toString([$Progress]) + '%'",
                  "height": "100%",
                  "border-radius": "2px",
                  "background-color": "=if([$Status] == 'Draft', '#94a3b8', if([$Status] == 'In Review', '#64748b', if([$Status] == 'Revising', '#475569', if([$Status] == 'Approved', '#334155', if([$Status] == 'Published', '#1e293b', '#94a3b8')))))"
                }
              }
            ]
          }
        ]
      }
    ]
  }
}

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

✅ Full rowFormatter — NOT default column grid
✅ HERO PROGRESS NUMBER (32px, 800 weight) on the left — instantly scannable
✅ Hero number color matches the status shade (darker = further along)
✅ 4px left accent border in the status shade color
✅ All colors from ONE slate-blue hue family — zero red, green, or amber
✅ Progress bar fill color matches the status shade (not traffic lights)
✅ Overdue is shown through bold text + "— overdue" suffix, NOT red (stays monochrome)
✅ No emoji, no icons — pure typography
✅ No shadow — flat, corporate, restrained
✅ Metadata flows as: name → badge + date inline → progress bar
✅ Most restrained style — the opposite of Retro's loudness

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

Responsive / mobile

Hero progress number scales 56 px → 40 px → 32 px across breakpoints ≥ 1024 px → ≤ 600 px → ≤ 375 px. The number must remain the dominant element at every breakpoint.
≤ 480 px: collapse "name → badge + date inline → progress bar" to a tighter vertical stack; keep the hero number on the left.
No emoji / no icons rule continues on mobile — do not add icons to compensate for lost color.
Touch targets: ≥ 44 × 44 px on the row card itself.

Implementation notes

Mapping non-linear lifecycles to the shade ramp

The slate shade ramp assumes a linear progression — lightest shade for the earliest state, darkest for the final state. Real lifecycles often aren't linear (parallel branches, revert paths, holds). Map them as follows:

Parallel branches that resolve to the same outcome (e.g. In Review (Legal) and In Review (Finance)): assign the same shade to both. The style is tonal — multiple states sharing one shade is fine.
Revert / paused states (e.g. Active → Paused → Active → Closed): map Paused to the same shade as the most recent forward state, and add a thin 1 px dashed outline only. Do not pick a brighter shade — the intent of monochrome is tonal restraint, not state-traffic-lights.
Terminal failure states (e.g. Cancelled, Rejected): use the darkest shade and italicise the label. Still no red; the italic carries the signal.

If the list has more than five distinct states, the shade ramp will start to feel ambiguous — pick a different style (Bento or Figma-clean handle 5+ states more legibly).

Files

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

Open the folder on GitHubat commit 69712d2

Compare with similar skills

Style Monochrome 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 Monochrome compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Style Monochrome this skillpnp/sharepoint-skills	133	—	~2.4k	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 Monochrome

What does Style Monochrome do?

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

When should I use Style Monochrome?

Style Monochrome fits situations like: the user says monochrome; tasks that involve Design tokens; tasks that involve Cloud office suites.

How do I install Style Monochrome in Claude Code?

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

How do I install Style Monochrome in Codex?

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

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

What does Style Monochrome need to run?

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

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

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

About 2.4k tokens (SKILL.md is roughly 9.7k 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 Monochrome?

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

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 Monochrome

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

Monochrome — Style Tokens + Row Template

Badge Tokens

status_colors (shade ramp — lightest = earliest)

Row Card Tokens

Row Template Layout

rowFormatter JSON

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

Responsive / mobile

Implementation notes

Mapping non-linear lifecycles to the shade ramp

Files

Compare with similar skills

Similar skills

More from pnp/sharepoint-skills

Related

Questions about Style Monochrome