opencode-skills-antigravity 0.0.2 → 0.0.4

package/README.md

@@ -1,16 +1,15 @@
 # opencode-skills-antigravity
 
-An [OpenCode CLI](https://opencode.ai/) plugin that automatically downloads and keeps the [Antigravity Awesome Skills](https://github.com/sickn33/antigravity-awesome-skills) repository up to date every time you start OpenCode.
+An [OpenCode CLI](https://opencode.ai/) plugin that bundles and manages the [Antigravity Awesome Skills](https://github.com/sickn33/antigravity-awesome-skills) repository for instant use.
 
 ## ✨ How it works
 
-Every time OpenCode starts, this plugin runs silently in the background:
+This plugin ensures you always have the latest skills without any network latency at startup.
 
-- **First run:** clones the full `antigravity-awesome-skills` repo into `~/.config/opencode/skills/antigravity-awesome-skills`
-- **Subsequent runs:** runs `git pull origin main` to silently fetch any new skills
-- **Offline:** if no network is available, a warning is shown and OpenCode continues normally
+- **Automated Updates:** A GitHub Action checks for updates in the [Antigravity Awesome Skills](https://github.com/sickn33/antigravity-awesome-skills) repository every hour. If new skills are found, it automatically bundles them and publishes a new version of the NPM package.
+- **Instant Deployment:** When you start OpenCode, the plugin instantly copies the pre-bundled skills to your local machine. This process works perfectly offline and ensures zero network latency during startup.
 
-OpenCode will then automatically detect all skills inside that folder and make them available to the AI agent.
+OpenCode automatically detects all skills and makes them available to the AI agent.
 
 You can then invoke any skill explicitly in your prompt:
 
@@ -41,7 +40,7 @@ OpenCode will automatically download the npm package on next startup via Bun. No
 Skills are stored at:
 
 ```
-~/.config/opencode/skills/
+~/.config/opencode/.agents/skills/
 ```
 
 OpenCode scans this directory automatically at startup.

package/bundled-skills/astro/SKILL.md

@@ -0,0 +1,359 @@
+---
+name: astro
+description: "Build content-focused websites with Astro — zero JS by default, islands architecture, multi-framework components, and Markdown/MDX support."
+category: frontend
+risk: safe
+source: community
+date_added: "2026-03-18"
+author: suhaibjanjua
+tags: [astro, ssg, ssr, islands, content, markdown, mdx, performance]
+tools: [claude, cursor, gemini]
+---
+
+# Astro Web Framework
+
+## Overview
+
+Astro is a web framework designed for content-rich websites — blogs, docs, portfolios, marketing sites, and e-commerce. Its core innovation is the **Islands Architecture**: by default, Astro ships zero JavaScript to the browser. Interactive components are selectively hydrated as isolated "islands." Astro supports React, Vue, Svelte, Solid, and other UI frameworks simultaneously in the same project, letting you pick the right tool per component.
+
+## When to Use This Skill
+
+- Use when building a blog, documentation site, marketing page, or portfolio
+- Use when performance and Core Web Vitals are the top priority
+- Use when the project is content-heavy with Markdown or MDX files
+- Use when you want SSG (static) output with optional SSR for dynamic routes
+- Use when the user asks about `.astro` files, `Astro.props`, content collections, or `client:` directives
+
+## How It Works
+
+### Step 1: Project Setup
+
+```bash
+npm create astro@latest my-site
+cd my-site
+npm install
+npm run dev
+```
+
+Add integrations as needed:
+
+```bash
+npx astro add tailwind        # Tailwind CSS
+npx astro add react           # React component support
+npx astro add mdx             # MDX support
+npx astro add sitemap         # Auto sitemap.xml
+npx astro add vercel          # Vercel SSR adapter
+```
+
+Project structure:
+
+```
+src/
+  pages/          ← File-based routing (.astro, .md, .mdx)
+  layouts/        ← Reusable page shells
+  components/     ← UI components (.astro, .tsx, .vue, etc.)
+  content/        ← Type-safe content collections (Markdown/MDX)
+  styles/         ← Global CSS
+public/           ← Static assets (copied as-is)
+astro.config.mjs  ← Framework config
+```
+
+### Step 2: Astro Component Syntax
+
+`.astro` files have a code fence at the top (server-only) and a template below:
+
+```astro
+---
+// src/components/Card.astro
+// This block runs on the server ONLY — never in the browser
+interface Props {
+  title: string;
+  href: string;
+  description: string;
+}
+
+const { title, href, description } = Astro.props;
+---
+
+<article class="card">
+  <h2><a href={href}>{title}</a></h2>
+  <p>{description}</p>
+</article>
+
+<style>
+  /* Scoped to this component automatically */
+  .card { border: 1px solid #eee; padding: 1rem; }
+</style>
+```
+
+### Step 3: File-Based Pages and Routing
+
+```
+src/pages/index.astro          → /
+src/pages/about.astro          → /about
+src/pages/blog/[slug].astro    → /blog/:slug (dynamic)
+src/pages/blog/[...path].astro → /blog/* (catch-all)
+```
+
+Dynamic route with `getStaticPaths`:
+
+```astro
+---
+// src/pages/blog/[slug].astro
+export async function getStaticPaths() {
+  const posts = await getCollection('blog');
+  return posts.map(post => ({
+    params: { slug: post.slug },
+    props: { post },
+  }));
+}
+
+const { post } = Astro.props;
+const { Content } = await post.render();
+---
+
+<h1>{post.data.title}</h1>
+<Content />
+```
+
+### Step 4: Content Collections
+
+Content collections give you type-safe access to Markdown and MDX files:
+
+```typescript
+// src/content/config.ts
+import { z, defineCollection } from 'astro:content';
+
+const blog = defineCollection({
+  type: 'content',
+  schema: z.object({
+    title: z.string(),
+    date: z.coerce.date(),
+    tags: z.array(z.string()).default([]),
+    draft: z.boolean().default(false),
+  }),
+});
+
+export const collections = { blog };
+```
+
+```astro
+---
+// src/pages/blog/index.astro
+import { getCollection } from 'astro:content';
+
+const posts = (await getCollection('blog'))
+  .filter(p => !p.data.draft)
+  .sort((a, b) => b.data.date.valueOf() - a.data.date.valueOf());
+---
+
+<ul>
+  {posts.map(post => (
+    <li>
+      <a href={`/blog/${post.slug}`}>{post.data.title}</a>
+      <time>{post.data.date.toLocaleDateString()}</time>
+    </li>
+  ))}
+</ul>
+```
+
+### Step 5: Islands — Selective Hydration
+
+By default, UI framework components render to static HTML with no JS. Use `client:` directives to hydrate:
+
+```astro
+---
+import Counter from '../components/Counter.tsx';  // React component
+import VideoPlayer from '../components/VideoPlayer.svelte';
+---
+
+<!-- Static HTML — no JavaScript sent to browser -->
+<Counter initialCount={0} />
+
+<!-- Hydrate immediately on page load -->
+<Counter initialCount={0} client:load />
+
+<!-- Hydrate when the component scrolls into view -->
+<VideoPlayer src="/demo.mp4" client:visible />
+
+<!-- Hydrate only when browser is idle -->
+<Analytics client:idle />
+
+<!-- Hydrate only on a specific media query -->
+<MobileMenu client:media="(max-width: 768px)" />
+```
+
+### Step 6: Layouts
+
+```astro
+---
+// src/layouts/BaseLayout.astro
+interface Props {
+  title: string;
+  description?: string;
+}
+const { title, description = 'My Astro Site' } = Astro.props;
+---
+
+<html lang="en">
+  <head>
+    <meta charset="utf-8" />
+    <title>{title}</title>
+    <meta name="description" content={description} />
+  </head>
+  <body>
+    <nav>...</nav>
+    <main>
+      <slot />  <!-- page content renders here -->
+    </main>
+    <footer>...</footer>
+  </body>
+</html>
+```
+
+```astro
+---
+// src/pages/about.astro
+import BaseLayout from '../layouts/BaseLayout.astro';
+---
+
+<BaseLayout title="About Us">
+  <h1>About Us</h1>
+  <p>Welcome to our company...</p>
+</BaseLayout>
+```
+
+### Step 7: SSR Mode (On-Demand Rendering)
+
+Enable SSR for dynamic pages by setting an adapter:
+
+```javascript
+// astro.config.mjs
+import { defineConfig } from 'astro/config';
+import vercel from '@astrojs/vercel/serverless';
+
+export default defineConfig({
+  output: 'hybrid',  // 'static' | 'server' | 'hybrid'
+  adapter: vercel(),
+});
+```
+
+Opt individual pages into SSR with `export const prerender = false`.
+
+## Examples
+
+### Example 1: Blog with RSS Feed
+
+```typescript
+// src/pages/rss.xml.ts
+import rss from '@astrojs/rss';
+import { getCollection } from 'astro:content';
+
+export async function GET(context) {
+  const posts = await getCollection('blog');
+  return rss({
+    title: 'My Blog',
+    description: 'Latest posts',
+    site: context.site,
+    items: posts.map(post => ({
+      title: post.data.title,
+      pubDate: post.data.date,
+      link: `/blog/${post.slug}/`,
+    })),
+  });
+}
+```
+
+### Example 2: API Endpoint (SSR)
+
+```typescript
+// src/pages/api/subscribe.ts
+import type { APIRoute } from 'astro';
+
+export const POST: APIRoute = async ({ request }) => {
+  const { email } = await request.json();
+
+  if (!email) {
+    return new Response(JSON.stringify({ error: 'Email required' }), {
+      status: 400,
+      headers: { 'Content-Type': 'application/json' },
+    });
+  }
+
+  await addToNewsletter(email);
+  return new Response(JSON.stringify({ success: true }), { status: 200 });
+};
+```
+
+### Example 3: React Component as Island
+
+```tsx
+// src/components/SearchBox.tsx
+import { useState } from 'react';
+
+export default function SearchBox() {
+  const [query, setQuery] = useState('');
+  const [results, setResults] = useState([]);
+
+  async function search(e: React.FormEvent) {
+    e.preventDefault();
+    const data = await fetch(`/api/search?q=${query}`).then(r => r.json());
+    setResults(data);
+  }
+
+  return (
+    <form onSubmit={search}>
+      <input value={query} onChange={e => setQuery(e.target.value)} />
+      <button type="submit">Search</button>
+      <ul>{results.map(r => <li key={r.id}>{r.title}</li>)}</ul>
+    </form>
+  );
+}
+```
+
+```astro
+---
+import SearchBox from '../components/SearchBox.tsx';
+---
+<!-- Hydrated immediately — this island is interactive -->
+<SearchBox client:load />
+```
+
+## Best Practices
+
+- ✅ Keep most components as static `.astro` files — only hydrate what must be interactive
+- ✅ Use content collections for all Markdown/MDX content — you get type safety and auto-validation
+- ✅ Prefer `client:visible` over `client:load` for below-the-fold components to reduce initial JS
+- ✅ Use `import.meta.env` for environment variables — prefix public vars with `PUBLIC_`
+- ✅ Add `<ViewTransitions />` from `astro:transitions` for smooth page navigation without a full SPA
+- ❌ Don't use `client:load` on every component — this defeats Astro's performance advantage
+- ❌ Don't put secrets in `.astro` frontmatter that gets used in client-facing templates
+- ❌ Don't skip `getStaticPaths` for dynamic routes in static mode — builds will fail
+
+## Security & Safety Notes
+
+- Frontmatter code in `.astro` files runs server-side only and is never exposed to the browser.
+- Use `import.meta.env.PUBLIC_*` only for non-sensitive values. Private env vars (no `PUBLIC_` prefix) are never sent to the client.
+- When using SSR mode, validate all `Astro.request` inputs before database queries or API calls.
+- Sanitize any user-supplied content before rendering with `set:html` — it bypasses auto-escaping.
+
+## Common Pitfalls
+
+- **Problem:** JavaScript from a React/Vue component doesn't run in the browser
+  **Solution:** Add a `client:` directive (`client:load`, `client:visible`, etc.) — without it, components render as static HTML only.
+
+- **Problem:** `getStaticPaths` data is stale after content updates during dev
+  **Solution:** Astro's dev server watches content files — restart if changes to `content/config.ts` are not reflected.
+
+- **Problem:** `Astro.props` type is `any` — no autocomplete
+  **Solution:** Define a `Props` interface or type in the frontmatter and Astro will infer it automatically.
+
+- **Problem:** CSS from a `.astro` component bleeds into other components
+  **Solution:** Styles in `.astro` `<style>` tags are automatically scoped. Use `:global()` only when intentionally targeting children.
+
+## Related Skills
+
+- `@sveltekit` — When you need a full-stack framework with reactive UI (vs Astro's content focus)
+- `@nextjs-app-router-patterns` — When you need a React-first full-stack framework
+- `@tailwind-patterns` — Styling Astro sites with Tailwind CSS
+- `@progressive-web-app` — Adding PWA capabilities to an Astro site

package/bundled-skills/browser-extension-builder/SKILL.md

@@ -34,9 +34,6 @@ Structure for modern browser extensions
 
 **When to use**: When starting a new extension
 
-```javascript
-## Extension Architecture
-
 ### Project Structure
 ```
 extension/
@@ -91,7 +88,6 @@ Popup ←→ Background (Service Worker) ←→ Content Script
               ↓
         chrome.storage
 ```
-```
 
 ### Content Scripts
 
@@ -99,9 +95,6 @@ Code that runs on web pages
 
 **When to use**: When modifying or reading page content
 
-```javascript
-## Content Scripts
-
 ### Basic Content Script
 ```javascript
 // content.js - Runs on every matched page
@@ -159,7 +152,6 @@ injectUI();
   }]
 }
 ```
-```
 
 ### Storage and State
 
@@ -167,9 +159,6 @@ Persisting extension data
 
 **When to use**: When saving user settings or data
 
-```javascript
-## Storage and State
-
 ### Chrome Storage API
 ```javascript
 // Save data
@@ -218,7 +207,6 @@ async function setStorage(data) {
 const { settings } = await getStorage(['settings']);
 await setStorage({ settings: { ...settings, theme: 'dark' } });
 ```
-```
 
 ## Anti-Patterns
 

package/bundled-skills/devcontainer-setup/SKILL.md

@@ -1,6 +1,9 @@
 ---
 name: devcontainer-setup
 description: Creates devcontainers with Claude Code, language-specific tooling (Python/Node/Rust/Go), and persistent volumes. Use when adding devcontainer support to a project, setting up isolated development environments, or configuring sandboxed Claude Code workspaces.
+risk: safe
+source: vibeship-spawner-skills (Apache 2.0)
+date_added: 2026-03-06
 ---
 
 # Devcontainer Setup Skill

package/bundled-skills/docs/contributors/skill-anatomy.md

@@ -45,6 +45,8 @@ The frontmatter is at the very top, wrapped in `---`:
 ---
 name: my-skill-name
 description: "Brief description of what this skill does"
+risk: safe
+source: community
 ---
 ```
 
@@ -59,9 +61,26 @@ description: "Brief description of what this skill does"
 #### `description`
 - **What it is:** One-sentence summary
 - **Format:** String in quotes
-- **Length:** Keep it under 150 characters
+- **Length:** Keep it under 200 characters
 - **Example:** `"Stripe payment integration patterns including checkout, subscriptions, and webhooks"`
 
+#### `risk`
+- **What it is:** The safety classification of the skill
+- **Values:** `none` | `safe` | `critical` | `offensive` | `unknown`
+- **Example:** `risk: safe`
+- **Guide:**
+  - `none` — pure text/reasoning, no commands or mutations
+  - `safe` — reads files, runs non-destructive commands
+  - `critical` — modifies state, deletes files, pushes to production
+  - `offensive` — pentesting/red-team tools; **must** include "Authorized Use Only" warning
+  - `unknown` — legacy or unclassified; prefer a concrete level for new skills
+
+#### `source`
+- **What it is:** Attribution for the skill's origin
+- **Format:** URL or a short label
+- **Examples:** `source: community`, `source: "https://example.com/original"`
+- **Use `"self"`** if you are the original author
+
 ### Optional Fields
 
 Some skills include additional metadata:
@@ -70,9 +89,11 @@ Some skills include additional metadata:
 ---
 name: my-skill-name
 description: "Brief description"
-version: "1.0.0"
-author: "Your Name"
+risk: safe
+source: community
+author: "your-name-or-handle"
 tags: ["react", "typescript", "testing"]
+tools: [claude, cursor, gemini]
 ---
 ```
 

package/bundled-skills/docs/users/faq.md

@@ -37,6 +37,9 @@ Start from:
 - ✅ **Cursor** (AI IDE)
 - ✅ **Antigravity IDE**
 - ✅ **OpenCode**
+- ✅ **Kiro CLI** (Amazon)
+- ✅ **Kiro IDE** (Amazon)
+- ✅ **AdaL CLI**
 - ⚠️ **GitHub Copilot** (partial support via copy-paste)
 
 ### Are these skills free to use?

package/bundled-skills/goldrush-api/SKILL.md

@@ -0,0 +1,109 @@
+---
+name: goldrush-api
+description: "Query blockchain data across 100+ chains: wallet balances, token prices, transactions, DEX pairs, and real-time OHLCV streams via the GoldRush API by Covalent."
+category: blockchain
+risk: safe
+source: community
+date_added: "2026-03-17"
+author: covalenthq
+tags: [blockchain, crypto, web3, api, defi, wallet, multi-chain]
+tools: [claude, cursor, gemini, codex, copilot]
+---
+
+# GoldRush API
+
+## Overview
+GoldRush by Covalent provides blockchain data across 100+ chains through a unified REST API, real-time WebSocket streams, a CLI, and an x402 pay-per-request proxy. This skill enables AI agents to query wallet balances, token prices, transaction history, NFT holdings, and DEX pair data without building chain-specific integrations.
+
+## When to Use This Skill
+- Retrieving wallet token balances or total portfolio value across any chain
+- Fetching transaction history or decoded event logs for an address
+- Getting current or historical token prices (USD or native)
+- Monitoring DEX pairs, liquidity events, and real-time OHLCV candles via WebSocket
+- Building block explorers, portfolio dashboards, tax tools, or DeFi analytics
+- Accessing on-chain data with no signup via x402 pay-per-request
+
+## How It Works
+
+### Step 1: Get credentials
+Sign up at https://goldrush.dev for a free API key. For agent-native no-signup access, use the x402 proxy instead.
+
+### Step 2: Set your API key
+```bash
+export GOLDRUSH_API_KEY="your_api_key_here"
+```
+
+### Step 3: Query data
+
+**REST API (most endpoints):**
+```bash
+# Wallet token balances on Ethereum
+curl -H "Authorization: Bearer $GOLDRUSH_API_KEY"   "https://api.covalenthq.com/v1/eth-mainnet/address/0xADDRESS/balances_v2/"
+```
+
+**CLI (quick terminal queries):**
+```bash
+npx @covalenthq/goldrush-cli balances --chain eth-mainnet --address 0xADDRESS
+```
+
+**SDK (in code):**
+```javascript
+import GoldRushClient from "@covalenthq/client-sdk";
+const client = new GoldRushClient(process.env.GOLDRUSH_API_KEY);
+const resp = await client.BalanceService.getTokenBalancesForWalletAddress(
+  "eth-mainnet", "0xADDRESS"
+);
+```
+
+## Examples
+
+### Example 1: Token Balances
+```bash
+curl -H "Authorization: Bearer $GOLDRUSH_API_KEY"   "https://api.covalenthq.com/v1/eth-mainnet/address/0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045/balances_v2/"
+```
+
+### Example 2: Token Price History
+```bash
+curl -H "Authorization: Bearer $GOLDRUSH_API_KEY"   "https://api.covalenthq.com/v1/pricing/historical_by_addresses_v2/eth-mainnet/USD/0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48/"
+```
+
+### Example 3: Transaction History
+```bash
+curl -H "Authorization: Bearer $GOLDRUSH_API_KEY"   "https://api.covalenthq.com/v1/eth-mainnet/address/0xADDRESS/transactions_v3/"
+```
+
+### Example 4: Real-time OHLCV via WebSocket
+```javascript
+// Stream live price candles for a token pair
+const ws = new WebSocket("wss://streaming.covalenthq.com/v1/eth-mainnet/ohlcv");
+ws.on("message", (data) => console.log(JSON.parse(data)));
+```
+
+## Best Practices
+✅ Use chain slugs: `eth-mainnet`, `matic-mainnet`, `base-mainnet`, `bsc-mainnet` — full list at https://goldrush.dev/docs/networks
+✅ Store API key in `GOLDRUSH_API_KEY` env var — never hardcode
+✅ Use WebSocket streams for real-time data rather than polling REST
+✅ Use SDK cursor pagination for large result sets
+❌ Don't use x402 for high-volume use cases — get a standard API key instead
+❌ Don't use chain IDs (e.g., `1`) — use chain slugs (e.g., `eth-mainnet`)
+
+## Security & Safety Notes
+- API key in `GOLDRUSH_API_KEY` environment variable only
+- x402 payments use USDC on Base — set spending limits before autonomous agent use
+- Read-only data API — no write operations, no transaction signing
+
+## Common Pitfalls
+
+**Problem:** 401 Unauthorized  
+**Solution:** Ensure API key is in `Authorization: Bearer` header, not query string
+
+**Problem:** `chain_name not found`  
+**Solution:** Use chain slug format — see https://goldrush.dev/docs/networks
+
+**Problem:** Empty results for new wallet  
+**Solution:** Some endpoints require on-chain activity; new wallets with no transactions return empty arrays, not errors
+
+## Related Skills
+- @goldrush-streaming-api — real-time WebSocket DEX pair and OHLCV streams
+- @goldrush-x402 — pay-per-request blockchain data without API key
+- @goldrush-cli — terminal-first blockchain data queries