jsr-audit

Validate Deno/TypeScript packages against JSR standards before publishing.

Updated Jun 4, 2026
One-click install
npx skills add https://github.com/rickylabs/netscript --skill jsr-audit-rickylabs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jsr-audit
Source: https://github.com/rickylabs/netscript/tree/main/.agents/skills/jsr-audit
Command: npx skills add https://github.com/rickylabs/netscript --skill jsr-audit-rickylabs

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This skill helps ensure that Deno/TypeScript packages meet JSR standards before publishing, improving their quality and discoverability.

Core Features & Use Cases

  • Compliance Check: Audits packages for JSR readiness, configuration, and documentation quality.
  • Score Optimization: Provides guidelines for achieving high scores in JSR's quality assessment.
  • Use Case: Before publishing a package, use this skill to review its configuration, verify exports, and ensure it meets JSR's documentation and best practices standards.

Quick Start

Run the jsr-audit skill to perform a dry-run audit on your package.

Frequently Asked Questions about jsr-audit

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check if my Deno package is ready for publishing to the JavaScript Registry?

To check Deno package readiness for the JavaScript Registry, run an audit against JSR standards to validate configuration, verify exports, and ensure documentation quality compliance before publishing.

What does the JSR score evaluate in a TypeScript package?

The JSR score evaluates a TypeScript package based on metadata, exports, and documentation quality, providing guidelines to optimize readiness and achieve high marks in the registry's quality assessment.

Can I use an audit to improve my package documentation for JSR?

Yes, you can use an audit to improve package documentation for JSR by reviewing configuration and verifying that your package meets the registry's best practices and documentation quality standards.

Why does my package configuration fail JSR compliance checks?

Package configuration fails JSR compliance checks when it lacks required metadata, has incorrect exports, or does not meet the documentation guidelines mandated by the JavaScript Registry standards.

Do I need to run a dry-run audit before publishing a Deno package to JSR?

Running a dry-run audit before publishing a Deno package to JSR is recommended to review configuration, verify exports, and ensure full compliance with JavaScript Registry documentation and quality standards.