Borrowing it
Nothing to install: this file belongs to Synerise/synerise-design. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/Synerise/synerise-design/master/.claude/skills/publish-ready/SKILL.mdgit clone --depth 1 https://github.com/Synerise/synerise-designWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/synerise/synerise-design/publish-ready)<a href="https://agentmods.dev/skills/synerise/synerise-design/publish-ready"><img src="https://agentmods.dev/badge/skills/synerise/synerise-design/publish-ready/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/synerise/synerise-design/publish-ready"><img src="https://agentmods.dev/badge/skills/synerise/synerise-design/publish-ready.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00033 | $0.02464 |
| Opus 5 | $0.00016 | $0.01232 |
| Sonnet 5 | $0.00007 | $0.00493 |
| Haiku 4.5 | $0.00003 | $0.00246 |
Grade A, and why
publish-ready scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 7d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 228 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Overview
Run a pre-publish readiness check on a single component package. This skill orchestrates verification across documentation (CLAUDE.md, README.md), Storybook completeness (argTypes, code tabs, overview MDX), unit test coverage for new functionality, and interaction tests for complex components. It produces a pass/fail checklist with actionable items for anything that needs attention before publishing.
Arguments
The user must provide:
- Package name — e.g.,
modal,button,progress-bar(kebab-case directory name underpackages/components/)
The user may optionally provide:
- A git ref or branch to diff against for identifying "new functionality" (defaults to
origin/master)
If the package name was not provided, ask: "Which package would you like to check for publish readiness? (e.g. modal, button, progress-bar)"
Workflow
Step 1 — Locate the package and gather context
Find all relevant files:
packages/components/<package-name>/src/ ← component source
packages/components/<package-name>/CLAUDE.md ← AI reference doc
packages/components/<package-name>/README.md ← user-facing docs
packages/components/<package-name>/package.json ← package metadata
packages/storybook/stories/components/<PascalName>/ ← stories directory
Derive <PascalName> from the kebab-case name (e.g., progress-bar → ProgressBar). If the stories directory uses a different casing, search with:
packages/storybook/stories/components/**/<PascalName>*.stories.tsx
Read all source files, types files, stories, tests, and documentation before forming any judgements.
Step 2 — Identify new and changed functionality
Run a diff against the base branch to understand what has changed:
git diff origin/master -- packages/components/<package-name>/src/
From the diff, extract:
- New props added to types files
- New components or sub-components added
- New hooks added
- Changed behaviour in existing components (modified logic, new branches)
- New exports added to
index.ts
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 7d ago First seen · 228 lines · 33 tokens per session scan A c126ef599a31
publish-ready is a skill published in the GitHub repository Synerise/synerise-design (96 stars, last pushed yesterday), licensed MIT. It adds 33 tokens to every session and 2,464 once invoked, about $0.0002 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-04.
Other skills, from other repositories
compiler-commit
Use when you want to verify compiler changes and commit with the correct convention. Runs tests, lint, and format, then commits with the [compiler] or [rust-compiler] prefix.
compiler-port
Port a compiler pass from TypeScript to Rust. Gathers context, plans the port, implements in a subagent with test-fix loop, then reviews.
compiler-verify
Use when you need to run all compiler checks (tests, lint, format) before committing. Detects whether TS or Rust code changed and runs the appropriate checks.
storybook-mcp-integration
Reference for the Storybook MCP server itself (@storybook/addon-mcp): 6 tools across 3 toolsets (dev, docs, testing), availability detection, and per-agent toolset filtering. Use when setting up the server or calling these tools directly against components that already exist. For the end-to-end pipeline that turns a…
angular-testing
Write Angular component tests using TestBed, ComponentHarness, and HttpTestingController with proper signal input handling. Use when writing component tests, mocking HTTP calls, or testing signal inputs.
appbuilder-testing
Generate and run tests for Adobe App Builder actions and UI components. Scaffolds Jest unit tests, integration tests against deployed actions, contract tests for Adobe API interactions, and React component tests using Testing Library. Provides mock helpers for State, Files, Events SDKs, @adobe/aio-lib- clients, ExC…