Document the current static web-app behavior, local-only save flow, shallow installer path, and maintainer-only sync controls.\n\nAlign maintainer guides with the active audit-to-risk-sync workflow, canonical artifact bot contract, release/coverage requirements, and updated security triage context so the docs match the repository's real operating model.
Add a When to Use section for akf-trust-metadata so release validation stays within the current warning budget.\n\nRefresh the generated plugin-safe and catalog artifacts produced by the maintainer sync after the PR batch landed.
Document the new Claude Code and Codex plugin distributions and explain how root plugins, bundle plugins, and plugin-safe filtering relate to the full library install.\n\nSync the catalog, plugin compatibility artifacts, and generated plugin-safe subsets so main stays consistent before the v9.0.0 release flow.
Add Codex marketplace metadata and a repo-local plugin scaffold so the repository can be installed as a Codex plugin without duplicating the skills catalog.
Document the new integration path and cover it with a regression test to keep the marketplace entry and plugin manifest in sync.
Add visible FAQ and concepts content, strengthen tool-specific integration
guides, and publish a dedicated skills-vs-MCP explainer.
Extend homepage SEO metadata and JSON-LD so the GitHub Pages catalog
better reflects the repository's real positioning and common user
questions.
Add fourteen skills from Dimillian/Skills, integrate the merged Snowflake and WordPress updates into the maintainer sync, and refresh registry metadata, attributions, walkthrough notes, and the 8.9.0 release notes while keeping validation warnings within budget.
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
Add a Unix activation script, Antigravity-specific installer guidance,
and cross-platform recovery documentation so users can reduce the
live skill set when truncation or context overload appears.
Regenerate the canonical bundle/catalog artifacts after merging the
stale goldrush-api removal so main stays release-ready.
Refs #381
Tighten the web app ESLint scope so TypeScript source is checked
without crawling bundled skill assets, and remove unused markdown and
debounce dependencies.
Clarify the security reporting flow and split code vs content
licensing to reduce ambiguity for users and contributors.
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.
Update the maintainer and user walkthroughs so they reflect the
completed 8.2.0 release publication instead of the pre-release ready
state.
Capture the final PR merge set, issue closure state, and the exact
release commands that were executed on main.
Add the 8.2.0 changelog entry and align the release-facing user docs
with the current maintenance sweep so the release workflow has the
required notes and public version references in place.
Refresh README release messaging and contributor acknowledgements ahead
of the automated release commit and tag creation.
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
Consolidate the repository into clearer apps, tools, and layered docs areas so contributors can navigate and maintain it more reliably. Align validation, metadata sync, and CI around the same canonical workflow to reduce drift across local checks and GitHub Actions.
