This skill should be used when the user asks to 'audit for JSR', 'check JSR readiness', 'review JSR config', 'verify package for JSR', 'publish to JSR', 'prepare for JSR publishing', 'JSR compliance check', 'run JSR audit', or wants to ensure their Deno/TypeScript package meets JSR standards before publishing.
View on GitHubjsr-audit/skills/jsr-audit/SKILL.md
January 21, 2026
Select agents to install to:
npx add-skill https://github.com/jahanson/cc-plugins/blob/main/jsr-audit/skills/jsr-audit/SKILL.md -a claude-code --skill jsr-auditInstallation paths:
.claude/skills/jsr-audit/# JSR Publishing Audit Comprehensive audit guide for JSR (JavaScript Registry) compliance and scoring optimization. --- ## Understanding the JSR Score JSR assigns packages a quality score from 0-100%, displayed with color coding: - **Red**: Below 60% - **Orange**: 60-90% - **Green**: 90%+ (target this) The score directly influences search ranking. View any package's breakdown at `jsr.io/@scope/package/score`. ### The 9 Scoring Factors | Category | Factor | Impact | |----------|--------|--------| | **Documentation** | Has README or module doc | High | | | Has examples in README/module doc | High | | | Has module docs in all entrypoints | High | | | Has docs for most symbols | High | | **Best Practices** | No slow types | Medium | | | Has provenance (SLSA attestation) | Medium | | **Discoverability** | Has description (≤250 chars) | Low | | **Compatibility** | At least one runtime marked compatible | Low | | | At least two runtimes compatible | Low | **Key insight**: Documentation carries the heaviest weight. Comprehensive JSDoc + README + `@module` tags will score higher than perfect types with minimal docs. --- ## Audit Checklist | Check | Command/Location | What to Look For | |-------|------------------|------------------| | Required metadata | `deno.json` | `name`, `version`, `exports` fields | | Scoped package name | `name` field | Format: `@scope/package-name` | | Package description | `description` field | ≤250 characters for discoverability | | Valid exports | `exports` field | Entry points exist and are correct | | No slow types | `deno publish --dry-run` | No slow type warnings | | Clean file list | `deno publish --dry-run` | Only intended files included | | ESM only | Source files | No CommonJS (`module.exports`, `require()`) | | Module documentation | Entry point files | `@module` JSDoc tag present | | Symbol documentation | Exported symbols | JSDoc with `@param`, `@returns`, `@example` | --- ## Audit Process ### Step 1: Check Required Metada