skills.rest
Lsogod
LsogodCOMMUNITY
Explore all skills by this author →
GitHub

plugin-package-check

Audit compaction-debugger plugins for release-readiness gaps before publishing.

Updated Apr 5, 2026
Search Tags:#plugin#publish#manifest#quality-assurance#open-source#release-check#clawhub
One-click install
npx skills add https://github.com/Lsogod/compaction-debugger --skill plugin-package-check
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: plugin-package-check
Source: https://github.com/Lsogod/compaction-debugger/tree/main/skills/plugin-package-check
Command: npx skills add https://github.com/Lsogod/compaction-debugger --skill plugin-package-check

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a pre-release audit for compaction-debugger plugins, ensuring packaging and metadata are correct before publishing to ClawHub or public repositories.

Core Features & Use Cases

  • Validates manifest completeness: id, name, kind: "context-engine", skills, configSchema.
  • Checks for release-readiness artifacts: absence of logs/ and cache directories or other build remnants.
  • Verifies documentation and open-source basics: README clarity, existence of LICENSE and .gitignore, and proper naming/organization of skills.
  • Useful for pre-release workflows: ensures a consistent, trustworthy package before publishing to ClawHub or public repositories.

Quick Start

Run the plugin-package-check on your repository to generate a release-readiness report.

Frequently Asked Questions about plugin-package-check

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

FAQPage Schema
How do I check if my plugin manifest is ready for publishing to ClawHub?▼

To check plugin manifest readiness, validate that required fields id, name, kind, skills, and configSchema are present and correctly defined. A release-readiness audit enforces these manifest fields, ensuring your compaction-debugger plugin packaging is complete before open-source distribution.

What do I need in my plugin repository before running a release-readiness check?▼

Before a release-readiness check, ensure your plugin repository contains a complete manifest, a clear README, a LICENSE file, and a .gitignore. The audit reviews these open-source basics to confirm your package meets distribution standards.

How do I clean up build artifacts before publishing an open-source plugin?▼

To clean up build artifacts before publishing, remove residual logs and cache directories from your package. The release-readiness audit flags these build remnants to ensure a consistent, trustworthy plugin distribution.

Does the plugin package check work for open-source distribution outside of ClawHub?▼

Yes, the release-readiness check works for open-source distribution outside of ClawHub. It audits manifest completeness, artifact cleanup, and documentation basics to ensure your plugin packaging is correct for any public repository.

Related Skills

Explore More Software Engineering Skills→
Securability-EngineeringSecurability-Engineering
2

your-skill-name

Define a Skill unit manifest with YAML frontmatter for the securable-claude-plugin repository.

Official
Basic
chrono-metachrono-meta
7

marketplace-gate

Audit repositories against a 5-point marketplace inclusion checklist.

Community
Intermediate
Mathews-TomMathews-Tom
310

repo-sentinel

Audit Git repositories for security and public-release readiness across attack surfaces.

Community
Advanced
IndianOldTurtledoveIndianOldTurtledove
45

codex-oss-maintainer-toolkit

Embed automated repository workflows for issue triage, review, and release tasks.

Community
Intermediate