fix(skills): trim gnu + guile descriptions under the 1000-char cap

gnu-coding-standards (1002->993) and spacecraft-guile-guidelines (1002->988) were the only rendered descriptions over 1000 chars — still under the loader's 1024 hard limit, but over the repo's 1000-char working cap. Trim each without dropping any trigger keyword; rebuild both bundles. All skills are now <=1000.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: UnbreakableMJ

gnu-coding-standards.skill

@@ -4,7 +4,7 @@ description: >-
   Apply the GNU Coding Standards faithfully — including the free-software philosophy
   (GPL licensing, FSF copyright assignment, Texinfo-canonical documentation, the
   policy against promoting nonfree software) — extended so GNU's conventions are
-  expressed idiomatically in C, Rust, GNU Guile (Scheme), Go, and Python. The gate
+  expressed idiomatically in C, Rust, GNU Guile, Go, and Python. The gate
   is GNU intent: consult this skill whenever the user is writing, reviewing,
   planning, or auditing software meant to be GNU-compliant, GNU-targeted, or a GNU
   package. Triggers include "GNU coding standards", "make this

gnu-coding-standards.zip

@@ -1,6 +1,6 @@
 ---
 name: spacecraft-guile-guidelines
-description: Write idiomatic, functional, concurrent GNU Guile (Guile Scheme 3.x) code. Use this skill whenever the user is writing, reviewing, or debugging Guile Scheme — any .scm file, any mention of Guile, Scheme, fibers, Guile channels, SRFIs, syntax-rules/syntax-case macros, Guile-specific APIs (spawn-fiber, run-fibers, make-channel, put-message, get-message, choice-operation), or functional Scheme patterns. Trigger even when the request is implicit, e.g. "write a concurrent worker pool in Guile", "make this Scheme tail-recursive", "set up a CSP pipeline", or "port this to fibers." Covers functional style (pure functions, proper tail calls, SRFI-1 list processing, records, hygienic macros) AND concurrency (Fibers/CSP, Guile channels, POSIX threads, futures, promises, parameters). Do NOT trigger for Common Lisp, Python, Rust, or other languages — only Guile Scheme. Prefer this skill over generic Scheme/Lisp advice — Guile has specific modules, idioms, and pitfalls that generic advice gets wrong.
+description: Write idiomatic, functional, concurrent GNU Guile (Scheme 3.x) code. Use this skill whenever the user is writing, reviewing, or debugging Guile Scheme — any .scm file, any mention of Guile, Scheme, fibers, Guile channels, SRFIs, syntax-rules/syntax-case macros, Guile-specific APIs (spawn-fiber, run-fibers, make-channel, put-message, get-message, choice-operation), or functional Scheme patterns. Trigger even when the request is implicit, e.g. "write a concurrent worker pool in Guile", "make this Scheme tail-recursive", "set up a CSP pipeline", or "port this to fibers." Covers functional style (pure functions, proper tail calls, SRFI-1 list processing, records, hygienic macros) AND concurrency (Fibers/CSP, Guile channels, POSIX threads, futures, promises, parameters). Do NOT trigger for Common Lisp, Python, Rust, or other languages — only Guile Scheme. Prefer it over generic Scheme/Lisp advice — Guile has specific modules, idioms, and pitfalls that generic advice gets wrong.
 license: GPL-3.0-or-later
 maintainer: Mohamed Hammad <Mohamed.Hammad@SpacecraftSoftware.org>
 website: https://Construct.SpacecraftSoftware.org/