release-readiness

Packages the canonical SKILL.md file for consistent deployment across environments.

3|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/ldilov/harness-forge --skill release-readiness-ldilov
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: release-readiness
Source: https://github.com/ldilov/harness-forge/tree/main/.agents/skills/release-readiness
Command: npx skills add https://github.com/ldilov/harness-forge --skill release-readiness-ldilov

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Auto-discoverable wrapper for canonical packaging of a skill, reducing duplication and ensuring consistent discovery across environments.

Core Features & Use Cases

  • Auto-wraps the canonical SKILL.md to expose a stable entry point.
  • Ensures uniform access to the release-readiness flow across repositories and teams.
  • Supports downstream tooling that expects a standardized skill interface.

Quick Start

Use this wrapper to access the canonical packaged version of the release-readiness skill at .hforge/library/skills/release-readiness/SKILL.md.

Frequently Asked Questions about release-readiness

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

FAQPage Schema
How do I package a SKILL.md file for consistent release-readiness across multiple projects?

To package a SKILL.md file for release-readiness, use this wrapper to auto-discover and expose the canonical packaged version, ensuring a well-formed frontmatter and standardized description across all projects and teams.

What is a canonical skill wrapper and how does it work for release packaging?

A canonical skill wrapper is an auto-discoverable layer that wraps the core SKILL.md file to expose a stable entry point, reducing duplication and ensuring uniform access to the release-readiness flow across environments.

Can I use this packaging wrapper to expose a standardized skill interface for downstream tooling?

Yes, you can use this packaging wrapper to expose a standardized skill interface, supporting downstream tooling that expects a canonical packaged version of the release-readiness flow for consistent deployment.

Do I need any dependencies to ensure a well-formed frontmatter for skill discovery?

No dependencies are required to ensure a well-formed frontmatter for skill discovery, as the wrapper autonomously applies the canonical packaging and standardizes the description without external tools.

How do I access the canonical packaged version of the release-readiness skill?

To access the canonical packaged version of the release-readiness skill, use this wrapper to reach the stable entry point located at .hforge/library/skills/release-readiness/SKILL.md for downstream deployment.