Refresh maintainer-owned artifacts after the PR merge batch, convert the\nJetski loader example to a directly importable Node ESM module, and add\nthe 8.7.0 changelog entry before release preparation.\n\nRefs #382\nRefs #388
Align public docs and maintainer guidance with the current 1,304-skill catalog state and v8.4.0 release copy.
Refresh README credits for newly imported external sources, update user-facing count references, and document the post-release docs realignment in the changelog and walkthrough.
* chore: implement ESM standardization and security attestation
Aligning root infrastructure with Node.js v24.14.0 standards.
- Set type: module in package.json to eliminate re-parsing overhead.
- Migrated Jetski Loader tests to .cjs to maintain legacy security audit compatibility.
- Verified path traversal and symlink protections with clean attestation.
* chore(ci): update pr_preflight path to .cjs for ESM compatibility
* feat(infra): surgical ESM modernization for Gemini suite
Resolved Codex P1 by reverting global root ESM shift to preserve installer stability.
- Implemented scoped 'type: module' in /docs/integrations/jetski-gemini-loader/ to eliminate re-parsing overhead.
- Updated test runner (run-test-suite.js) and CI (ci.yml) to track .cjs transitions.
- Verified zero-warning execution in Node v24.14.0.
Harden batch activation, dev refresh gating, Microsoft sync path
handling, and Jetski skill loading against command injection,
symlink traversal, and client-side star tampering.
Add regression coverage for the security-sensitive paths and
update the internal triage addendum for the Jetski loader fix.
This commit adds documentation and a reference implementation for
integrating antigravity-awesome-skills with Jetski/Cortex agents
without hitting the context window truncation error (issue #269).
Changes:
- New integration guide: docs/integrations/jetski-cortex.md
- Example loader: examples/jetski-gemini-loader/loader.ts
- Example README: examples/jetski-gemini-loader/README.md
- Updated FAQ: docs/users/faq.md (added context overflow section)
- Updated usage: docs/users/usage.md (added "Can I load all skills?" FAQ)
The solution follows a manifest + lazy-loading pattern:
- Use data/skills_index.json as lightweight manifest
- Only load SKILL.md files for @skill-id references in messages
- Enforce maxSkillsPerTurn limit to prevent overflow
