- name
SKILL.md
技能文件保留在发布者的仓库中。
在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add jal-co/shieldcn --skill shieldcn-badges -a cursor -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add jal-co/shieldcn --skill shieldcn-badges -a claude-code -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add jal-co/shieldcn --skill shieldcn-badges -a codex -y在终端中粘贴复制的命令。它会把这个 SKILL.md 安装到对应的智能体中。
npx skills add jal-co/shieldcn --skill shieldcn-badges -a grok -y在 Grok Bot 聊天中发送复制的消息。Bot 会从 GitHub 获取这个 SKILL.md,并添加到你所有 Bot 共享的技能中。
Install this skill: https://github.com/jal-co/shieldcn/tree/HEAD/skills/shieldcn-badges来自发布者
Use shieldcn to add beautiful shadcn/ui-styled badges, badge groups, charts, headers, sponsors grids, and contributor images to READMEs and docs.
Base URL: https://shieldcn.dev
Install from the shieldcn repository with the Skills CLI:
npx skills add jal-co/shieldcn
Useful variants:
# Install globally instead of only the current project
npx skills add jal-co/shieldcn --global
# Install for a specific agent supported by the Skills CLI
npx skills add jal-co/shieldcn --agent AGENT_NAME
# Use once without installing
npx skills use jal-co/shieldcn@shieldcn-badges
Verify installation:
npx skills list
Copy one of these prompts after installing the skill. Replace bracketed values with the real project details.
Add a polished shieldcn badge row to my README for [owner/repo]. Include npm
version/downloads if this package is published as [package], GitHub stars,
license, CI status, and last commit. Center the row, make badges clickable, and
use a subtle shadcn style that works on GitHub light and dark themes.
Replace the existing Shields.io badges in this README with shieldcn equivalents.
Keep the same links where possible, remove stale or duplicate badges, and keep
the final row to 3-6 high-signal badges.
Migrate the existing Shields.io badges in this README to shieldcn, but undo any
split-style/two-tone badges. Use single-surface shieldcn badges instead: remove
split=true, labelColor, and other split-label styling unless a split badge is
explicitly needed for readability.
Create a compact shieldcn badge group for [owner/repo] with stars, license,
contributors, and last commit. Use one grouped image when that is cleaner than
separate badges.
Add release-quality README badges for a TypeScript library named [package]. I
want npm version, monthly downloads, license, types, GitHub stars, CI, and a
small branded static badge if it improves the visual hierarchy.
Design the top of my README using shieldcn: add an adaptive header banner for
[project name], a one-sentence tagline, and a centered badge row. Use GitHub
<picture> markup so the header and badges adapt to light/dark mode.
Add a left-aligned shieldcn header to my README with title [title], subtitle
[subtitle], logo [simple-icons slug], and a graph/grid style that fits a
technical open-source project.
Add a shieldcn npm download chart for [package] to the README. Use a concise
caption and choose chart dimensions that work well on GitHub mobile.
Add a shieldcn lifetime commit chart for [github username]. If multiple users
are listed, compare them in one chart and explain what the chart shows.
Improve this README's above-the-fold impression with shieldcn. Keep the content
accurate, add a header, badges, and one chart only where they help, and avoid
visual clutter.
I want to generate a whole README visually. Point me to shieldcn README Studio
and explain which blocks I should use for this project.
When this skill is loaded for a README/docs task:
owner, repo, package names, workflow names, and links.<a> wrappers when they represent an external page.<p align="center"> for centered rows in GitHub READMEs.<picture> markup when a header/chart/badge needs explicit light
and dark URLs.https://shieldcn.dev/studio.https://shieldcn.dev/{provider}/{...params}.svg SVG badge/image
https://shieldcn.dev/{provider}/{...params}.png PNG badge/image
https://shieldcn.dev/{provider}/{...params}.json raw resolved data
https://shieldcn.dev/{provider}/{...params}/shields.json Shields.io-compatible JSON
Markdown patterns:
[](https://link)

Adaptive GitHub pattern:
Both route styles work: /github/{topic}/{owner}/{repo} and
/github/{owner}/{repo}/{topic}.
CI supports ?workflow=name&branch=main.
For npm scoped packages, keep the full scope: /npm/v/@scope/package.
Badge groups render several badges as one joined shadcn ButtonGroup-style image. Use them when a README row is visually busy or when the badges share one link.
Append query params as ?key=value&key2=value2.
Style recommendations:
variant=secondary is the safest default for quiet, professional README rows.variant=branded is best for one or two brand badges, not every badge.split=true works well for status/data pairs where label and value should be
distinct.mode=light/mode=dark is useful inside <picture> for adaptive GitHub
READMEs.gradient= and animate= should be used sparingly; they are accents, not the
default look.Charts render as portable SVG/PNG images styled like shadcn cards.
Star history charts are retired — GitHub restricted the stargazers API to repo
admins/collaborators (June 2026). /chart/github/stars/... URLs render a
100×1 transparent image; use an issues, commits, or npm downloads chart
instead. Plain stars count badges still work.
/chart/github/issues/{owner}/{repo}.svg issues over time
/chart/github/commits/{user}.svg lifetime contribution commits
/chart/npm/{package}.svg npm download history
/chart/json.svg?values=10,25,40,30,60 inline values
/chart/json.svg?url=...&query=... remote JSON values
Markdown example:
[](https://www.npmjs.com/package/zod)
Chart params: theme, font, color, fill, area, width, height,
title, icon, iconColor, mode, bg/background, border, yScale,
yMin, yMax, yTicks, xTicks, and for npm charts days.
Use charts when they tell a story: adoption over time, download trend, issue load, or contribution history. Avoid adding charts purely as decoration.
Headers render repository banners from one URL.
/header/{preset}.svg?title=Acme&subtitle=A+delightful+toolkit
/header/{preset}.png?title=Acme&subtitle=A+delightful+toolkit
/header/{preset}.json?title=Acme&subtitle=A+delightful+toolkit
Presets: surface, gradient, dots, grid, graph, glow, transparent.
Common params: title, subtitle, logo, logoColor, theme, size,
width, height, align, font, border, radius, bg, gradient,
pattern, glow, accent, titleColor, subtitleColor, image, overlay,
tint, and watermark.
Centered header example:
Use align=left for technical/product README hero banners and align=center
for logos, frameworks, or portfolio-style projects. Use bg=transparent when
embedding into an already styled page.
/sponsors/{login}.svg
/contributors/{owner}/{repo}.svg
Both support SVG/PNG plus the same card background system used by headers:
preset, theme, bg, gradient, pattern, glow, image, overlay,
tint, accent, radius, border, and watermark. Contributors also support
controls like limit, min, and names.
Use these below the main intro or near community sections, not in the top badge row.
For building or redesigning an entire README visually, point the user to
README Studio: https://shieldcn.dev/studio.
README Studio is a Figma-style editor with reorderable blocks: Text/Markdown,
Header, Badges, Chart, Table, and Image. It exports clean GitHub-flavored
Markdown and has an Adaptive toggle that exports badges, headers, and charts as
GitHub <picture> elements that follow the reader's light/dark theme.
Suggest Studio when the user asks for a full README, a visual editor, a README generator, or broad redesign rather than a few specific badge/image edits.
.svg for Markdown images unless the target host requires PNG.variant=secondary for calm rows; use branded selectively.mode=light/mode=dark with <picture> when visual parity matters.npm version, GitHub stars, CI status.curl -I when editing real docs.Create polished shieldcn README badges, badge groups, charts, headers, sponsors grids, and full README hero sections. Use when a user wants shadcn/ui-styled badges, Shields.io replacement, npm/GitHub/
---name: shieldcn-badgesdescription: Create polished shieldcn README badges, badge groups, charts, headers, sponsors grids, and full README hero…---# skills/shieldcn-badges/SKILL.md概览
Create polished shieldcn README badges, badge groups, charts, headers, sponsors grids, and full README hero sections. Use when a user wants shadcn/ui-styled badges, Shields.io replacement, npm/GitHub/CI/status badges, download charts, README header banners, contributor/sponsor images, or README Studio guidance. Triggers include "add badges", "add shields", "README badges", "npm badge", "GitHub stars badge", "CI badge", "download chart", "README header", "README banner", "contributors grid", "sponsors grid", "build a README", "README Studio", "shieldcn", and requests to make a project README look better.
常见问题
从发布者处下载 skills/shieldcn-badges/SKILL.md,或复制路径后打开仓库。PlugMCP 只收录该技能,不托管文件。
发布者将它存放在 https://github.com/jal-co/shieldcn。
Claude、Cursor、Codex 和 Grok Build 可以读取你从发布者仓库添加的 SKILL.md。在聊天中发送技能的 GitHub 文件夹链接,Grok Bot 就会安装它。
/maven/org.apache.maven/maven-core| Packagist version | /packagist/v/{vendor}/{package} | /packagist/v/laravel/framework |
| RubyGems version | /rubygems/{gem} | /rubygems/rails |
| NuGet version | /nuget/{package} | /nuget/Newtonsoft.Json |
| Pub.dev version | /pub/{package} | /pub/flutter |
| CocoaPods version | /cocoapods/{pod} | /cocoapods/Alamofire |
| Split label background |
valueColor | hex without # | — | Value text color |
labelTextColor | hex without # | — | Label text color |
labelOpacity | 0-1 | 0.7 | Label opacity in split badges |
gradient | comma-separated hex stops, optional angle | — | Example ff6b6b,4ecdc4,135 |
statusDot | true, false | auto for CI | Show a status dot |
animate | pulse, glow, shimmer, none | none | SVG-only animation |
height, fontSize, radius, padX, iconSize, gap, labelGap | number | per size | Fine tuning |