@laitszkin/apollo-toolkit 2.11.0 → 2.11.1

package/CHANGELOG.md

@@ -4,6 +4,13 @@ All notable changes to this repository are documented in this file.
 
 ## [Unreleased]
 
+## [v2.11.1] - 2026-03-23
+
+### Changed
+- Add a dedicated GitHub Actions validation job for `SKILL.md` description length checks.
+- Enforce a maximum `description` length of 1024 characters in `scripts/validate_skill_frontmatter.py`.
+- Shorten `enhance-existing-features` metadata so its `description` stays within the loader limit without changing intent.
+
 ## [v2.11.0] - 2026-03-23
 
 ### Added

package/enhance-existing-features/SKILL.md

@@ -1,21 +1,15 @@
 ---
 name: enhance-existing-features
 description: >-
-  Build and extend brownfield features in an existing codebase. Always explore
-  the codebase first, then decide from the user's requested change whether
-  specs (`spec.md`/`tasks.md`/`checklist.md`) are required before coding. When
-  specs are required, depend on `generate-spec` for the shared planning,
-  clarification, approval, and backfill workflow. If a spec set exists and is
-  approved, complete all planned tasks and applicable checklist items before
-  yielding unless the user changes scope or an external blocker prevents safe
-  completion. Even when specs are not
-  required, still add and run related tests for
-  unit/property-based/user-critical integration chain/E2E coverage. Tests must
-  not stop at happy-path validation: for business-logic changes require
-  property-based testing unless explicitly `N/A` with reason, design
-  adversarial/regression/authorization/idempotency/concurrency coverage where
-  relevant, use mocks for external services in logic chains, and verify
-  meaningful business outcomes rather than smoke-only success.
+  Extend brownfield features by exploring the codebase first, then deciding
+  whether shared specs (`spec.md`/`tasks.md`/`checklist.md`) are required
+  before coding. When specs are needed, use `generate-spec` for planning,
+  clarification, approval, and backfill, and complete approved in-scope tasks
+  before yielding unless scope changes or an external blocker prevents safe
+  completion. With or without specs, add and run relevant unit,
+  property-based, regression, integration, E2E, and adversarial tests as
+  applicable, use mocks for external services in logic chains, and verify
+  meaningful business outcomes instead of smoke-only success.
 ---
 
 # Enhance Existing Features

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@laitszkin/apollo-toolkit",
-  "version": "2.11.0",
+  "version": "2.11.1",
   "description": "Apollo Toolkit npm installer for managed skill copying across Codex, OpenClaw, and Trae.",
   "license": "MIT",
   "author": "LaiTszKin",

package/scripts/validate_skill_frontmatter.py

@@ -11,6 +11,7 @@ import yaml
 
 NAME_PATTERN = re.compile(r"^[a-z0-9]+(?:-[a-z0-9]+)*$")
 REQUIRED_KEYS = {"name", "description"}
+MAX_DESCRIPTION_LENGTH = 1024
 
 
 def repo_root() -> Path:
@@ -81,6 +82,11 @@ def validate_skill(skill_dir: Path) -> list[str]:
     description = frontmatter.get("description")
     if not isinstance(description, str) or not description.strip():
         errors.append(f"{skill_md}: 'description' must be a non-empty string.")
+    elif len(description) > MAX_DESCRIPTION_LENGTH:
+        errors.append(
+            f"{skill_md}: invalid description: exceeds maximum length of "
+            f"{MAX_DESCRIPTION_LENGTH} characters"
+        )
 
     return errors