opencode-skills-collection 3.1.8 → 3.1.10

package/bundled-skills/docs/maintainers/skills-update-guide.md

@@ -72,7 +72,7 @@ The update process refreshes:
 - Canonical skills index (`skills_index.json`)
 - Compatibility mirror (`data/skills_index.json`)
 - Web app skills data (`apps\web-app\public\skills.json`)
-- All 1,689+ skills from the skills directory
+- All 1,693+ skills from the skills directory
 
 ## When to Update
 

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

@@ -1061,4 +1061,4 @@ Found a skill that should be in a bundle? Or want to create a new bundle? [Open
 
 ---
 
-_Last updated: June 2026 | Total Skills: 1,689+ | Total Bundles: 59_
+_Last updated: June 2026 | Total Skills: 1,693+ | Total Bundles: 59_

package/bundled-skills/docs/users/claude-code-skills.md

@@ -12,7 +12,7 @@ Install the library into Claude Code, then invoke focused skills directly in the
 
 ## Why use this repo for Claude Code
 
-- It includes 1,689+ skills instead of a narrow single-domain starter pack.
+- It includes 1,693+ skills instead of a narrow single-domain starter pack.
 - It supports the standard `.claude/skills/` path and the Claude Code plugin marketplace flow.
 - It also ships generated bundle plugins so teams can install focused packs like `Essentials` or `Security Developer` from the marketplace metadata.
 - It includes onboarding docs, bundles, and workflows so new users do not need to guess where to begin.

package/bundled-skills/docs/users/gemini-cli-skills.md

@@ -12,7 +12,7 @@ Install into the Gemini skills path, then ask Gemini to apply one skill at a tim
 
 - It installs directly into the expected Gemini skills path.
 - It includes both core software engineering skills and deeper agent/LLM-oriented skills.
-- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,689+ files.
+- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,693+ files.
 - It is useful whether you want a broad internal skill library or a single repo to test many workflows quickly.
 
 ## Install Gemini CLI Skills

package/bundled-skills/docs/users/getting-started.md

@@ -1,4 +1,4 @@
-# Getting Started with Antigravity Awesome Skills (V13.3.0)
+# Getting Started with Antigravity Awesome Skills (V13.4.0)
 
 **New here? This guide will help you supercharge your AI Agent in 5 minutes.**
 

package/bundled-skills/docs/users/kiro-integration.md

@@ -18,7 +18,7 @@ Kiro is AWS's agentic AI IDE that combines:
 
 Kiro's agentic capabilities are enhanced by skills that provide:
 
-- **Domain expertise** across 1,689+ specialized areas
+- **Domain expertise** across 1,693+ specialized areas
 - **Best practices** from Anthropic, OpenAI, Google, Microsoft, and AWS
 - **Workflow automation** for common development tasks
 - **AWS-specific patterns** for serverless, infrastructure, and cloud architecture

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

@@ -14,7 +14,7 @@ If you came in through a **Claude Code** or **Codex** plugin instead of a full l
 
 When you ran `npx antigravity-awesome-skills` or cloned the repository, you:
 
-✅ **Downloaded 1,689+ skill files** to your computer (default: `~/.agents/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)
+✅ **Downloaded 1,693+ skill files** to your computer (default: `~/.agents/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)
 ✅ **Made them available** to your AI assistant  
 ❌ **Did NOT enable them all automatically** (they're just sitting there, waiting)
 
@@ -34,7 +34,7 @@ Bundles are **curated groups** of skills organized by role. They help you decide
 
 **Analogy:**
 
-- You installed a toolbox with 1,689+ tools (✅ done)
+- You installed a toolbox with 1,693+ tools (✅ done)
 - Bundles are like **labeled organizer trays** saying: "If you're a carpenter, start with these 10 tools"
 - You can either **pick skills from the tray** or install that tray as a focused marketplace bundle plugin
 
@@ -212,7 +212,7 @@ Let's actually use a skill right now. Follow these steps:
 
 ## Step 5: Picking Your First Skills (Practical Advice)
 
-Don't try to use all 1,689+ skills at once. Here's a sensible approach:
+Don't try to use all 1,693+ skills at once. Here's a sensible approach:
 
 If you want a tool-specific starting point before choosing skills, use:
 
@@ -343,7 +343,7 @@ Usually no, but if your AI doesn't recognize a skill:
 
 ### "Can I load all skills into the model at once?"
 
-No. Even though you have 1,689+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
+No. Even though you have 1,693+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
 
 The intended pattern is:
 

package/bundled-skills/docs/users/visual-guide.md

@@ -34,7 +34,7 @@ antigravity-awesome-skills/
 ├── 📄 CONTRIBUTING.md                  ← Contributor workflow
 ├── 📄 CATALOG.md                       ← Full generated catalog
 │
-├── 📁 skills/                          ← 1,689+ skills live here
+├── 📁 skills/                          ← 1,693+ skills live here
 │   │
 │   ├── 📁 brainstorming/
 │   │   └── 📄 SKILL.md                 ← Skill definition
@@ -47,7 +47,7 @@ antigravity-awesome-skills/
 │   │   └── 📁 2d-games/
 │   │       └── 📄 SKILL.md             ← Nested skills also supported
 │   │
-│   └── ... (1,689+ total)
+│   └── ... (1,693+ total)
 │
 ├── 📁 apps/
 │   └── 📁 web-app/                     ← Interactive browser
@@ -100,7 +100,7 @@ antigravity-awesome-skills/
 
 ```
                     ┌─────────────────────────┐
-                    │  1,689+ SKILLS          │
+                    │  1,693+ SKILLS          │
                     └────────────┬────────────┘
                                  │
         ┌────────────────────────┼────────────────────────┐
@@ -201,7 +201,7 @@ If you want a workspace-style manual install instead, cloning into `.agent/skill
 │   ├── 📁 brainstorming/                 │
 │   ├── 📁 stripe-integration/            │
 │   ├── 📁 react-best-practices/          │
-│   └── ... (1,689+ total)                │
+│   └── ... (1,693+ total)                │
 └─────────────────────────────────────────┘
 ```
 

package/bundled-skills/sql-sentinel/SKILL.md

@@ -0,0 +1,131 @@
+---
+name: sql-sentinel
+description: "Audit SQL for the cost & performance anti-patterns that burn warehouse credits. Scores warehouse health 0-100 and outputs a prioritized cost-reduction plan for BigQuery, Snowflake, Redshift, and Postgres."
+category: data
+risk: safe
+source: community
+source_repo: takeaseatventure/sql-sentinel
+source_type: community
+date_added: "2026-06-26"
+author: takeaseat
+tags: [sql, bigquery, snowflake, redshift, postgres, data-warehouse, cost-optimization, performance, audit, finops]
+tools: [claude, cursor, codex, gemini]
+license: "MIT"
+license_source: "https://github.com/takeaseatventure/sql-sentinel/blob/main/LICENSE"
+---
+
+# sql-sentinel
+
+## Overview
+
+A static-analysis skill that audits SQL for the cost & performance anti-patterns that dominate warehouse bills — `SELECT *`, full-table scans, non-sargable predicates, Cartesian joins, the `NOT IN` NULL trap, and 15 more. It scores warehouse query health 0-100 (A-F) and outputs a prioritized cost-reduction plan, each finding with a `why`, a concrete `fix`, and an estimated savings.
+
+Built for analytics engineers (dbt, Looker), data platform teams running FinOps / "reduce cloud spend" initiatives, and anyone reviewing a SQL pull request before it hits production. Works across BigQuery, Snowflake, Redshift, and Postgres. Zero dependencies, MIT licensed.
+
+The executable engine and full rule set live in the source repository: https://github.com/takeaseatventure/sql-sentinel
+
+## When to Use This Skill
+
+- A user writes or reviews a query for BigQuery, Snowflake, Redshift, Postgres, or Spark SQL.
+- A user asks "why is this query so slow?" or "why is my warehouse bill so high?"
+- A user is about to promote a dashboard query or dbt model to production.
+- A data engineer wants a second pair of eyes before a code review or a cost-optimization sweep.
+- A team is running a "reduce cloud spend" or FinOps initiative.
+
+## How It Works
+
+The engine splits a SQL script into statements (honoring quotes and comments), runs 20 rules over each statement, scores health 0-100 weighted by severity (critical 25, high 12, medium 5, low 1), and returns a prioritized cost-reduction plan.
+
+### Step 1: Run the audit
+
+Install or clone the source repository, then run the zero-dependency engine:
+
+```bash
+git clone https://github.com/takeaseatventure/sql-sentinel.git
+cd sql-sentinel
+node scripts/sql-sentinel.js path/to/query.sql
+```
+
+Or programmatically:
+
+```javascript
+const { auditSql } = require('./scripts/sql-sentinel');
+const report = auditSql(yourSqlString, { dialect: 'bigquery' });
+console.log(report.healthScore);      // 0-100
+console.log(report.grade);            // 'A' | 'B' | 'C' | 'D' | 'E' | 'F'
+console.log(report.prioritizedPlan);  // array, worst findings first
+```
+
+### Step 2: Read the prioritized plan
+
+The output leads with critical findings (Cartesian joins, mass DELETE) and descends to low-severity style issues. Each finding explains *why* it costs money and *how* to fix it.
+
+## Examples
+
+### Example 1: A messy dashboard query
+
+```sql
+SELECT DISTINCT *
+FROM user_events, raw_logs
+WHERE LOWER(event_name) LIKE '%signup%'
+  AND user_id NOT IN (SELECT id FROM deleted_users)
+ORDER BY created_at;
+```
+
+The audit scores this 17/100 (grade F) and flags 7 findings:
+- CRITICAL: comma-join produces a Cartesian product (can turn a $0.02 query into a $200 query)
+- HIGH: `SELECT *` forces full column scan (30-90% wasted bytes on wide tables)
+- HIGH: leading-wildcard `LIKE '%signup%'` defeats indexes
+- HIGH: `LOWER(event_name)` defeats indexes (non-sargable)
+- HIGH: `NOT IN (SELECT ...)` — NULL semantics hazard
+- MEDIUM: `SELECT DISTINCT` dedup cost
+- MEDIUM: `ORDER BY` without `LIMIT` sorts the full result
+
+### Example 2: A clean, sargable query
+
+```sql
+-- This scores 90+/100 (grade A) — no findings
+SELECT id, email, created_at
+FROM users
+WHERE created_at >= TIMESTAMP '2026-01-01'
+  AND created_at <  TIMESTAMP '2026-02-01'
+ORDER BY id
+LIMIT 100;
+```
+
+## The 20 rules (ruleset v1.0.0)
+
+| Rule | Severity | Catches |
+|---|---|---|
+| SQL001 | high | `SELECT *` full column scan |
+| SQL002 | critical | No `WHERE` → full table scan |
+| SQL003 | high | `LIKE '%term'` non-sargable |
+| SQL004 | high | Function on column kills index |
+| SQL005 | critical | `CROSS JOIN` / comma-join |
+| SQL006 | medium | `SELECT DISTINCT` dedup cost |
+| SQL007 | medium | `ORDER BY` without `LIMIT` |
+| SQL008 | high | `NOT IN (SELECT ...)` NULL trap |
+| SQL009 | medium | Implicit type cast |
+| SQL010 | low | Many `OR`s (use `IN`/`UNION`) |
+| SQL011 | medium | `COUNT(DISTINCT)` at scale (use HLL) |
+| SQL012 | low | `LIMIT` without `ORDER BY` |
+| SQL013 | medium | Scalar subquery in `SELECT` |
+| SQL014 | medium | 5+ JOINs broadcast/spill risk |
+| SQL015 | high | Fact table, no partition filter |
+| SQL017 | low | String concat in `SELECT` |
+| SQL018 | medium | Window `OVER ()` no `PARTITION` |
+| SQL020 | critical | `DELETE`/`UPDATE` without `WHERE` |
+| SQL021 | low | `SELECT *` in `EXISTS`/`IN` |
+| SQL022 | medium | `UNION` vs `UNION ALL` |
+
+Run the test suite to verify each rule fires on real SQL:
+
+```bash
+cd scripts && node test.js   # 26 tests, zero dependencies
+```
+
+## Limitations
+
+- This is a **static** analyzer. It finds anti-patterns in the *text* of SQL; it does not read query plans, row counts, or billing. A flagged query on a 100-row table is cheap; the same query on a billion-row table is the problem the rule exists to prevent.
+- The fact-table heuristic (SQL015) keys off table *names* (`*_events`, `*_log`) and is advisory, not definitive.
+- It does not execute SQL — safe to run on any `.sql` file.

package/bundled-skills/web-project-brainstorming/SKILL.md

@@ -0,0 +1,149 @@
+---
+name: web-project-brainstorming
+description: Masterclass framework for brainstorming web development projects and page designs. Outlines structural phases for concept, UX flow, styling aesthetics, technical architecture, and SEO.
+category: consulting
+risk: safe
+source: self
+source_type: self
+date_added: "2026-06-26"
+author: Rsmiyani
+tags: [brainstorming, project-planning, web-development, product-scoping, design-system, architecture]
+tools: [claude, cursor, gemini]
+---
+
+# Web Project Brainstorming
+
+## Overview
+
+This skill provides a structured, masterclass-level framework for brainstorming web projects, web applications, or individual page designs at their inception. It guides developers and designers through scoping the core product concept, mapping user flows, defining visual styling aesthetics, selecting the technical stack, and planning for search engine optimization (SEO) and performance.
+
+## When to Use This Skill
+
+- Use at the start of any new web development project or page redesign.
+- Use when scoping feature sets, user roles, and interaction patterns for web applications.
+- Use when establishing design systems, color tokens, and layout guidelines.
+- Use when evaluating tech stacks (e.g., Next.js vs. Vanilla JS, CSS Grid vs. Tailwind).
+
+## How It Works
+
+Execute web project brainstorming sequentially across six structured phases. Ask the user questions one phase at a time to maintain focus and ensure thorough alignment.
+
+### Phase 1: Core Concept & Scoping
+Define the product's primary value proposition and scope:
+- **Target Audience**: Who is using the website or application?
+- **Core Value**: What problem does it solve for users?
+- **Key Features**: What are the top 3–5 mandatory features?
+
+### Phase 2: User Experience (UX) & Information Architecture
+Map how users navigate and interact:
+- **Page Hierarchy**: What is the sitemap and page structure?
+- **User Journeys**: What step-by-step flows do users take to complete key goals?
+- **Responsive Layout**: Is the interface mobile-first, desktop-first, or balanced?
+
+### Phase 3: Visual Styling & Design System
+Establish the visual guidelines and aesthetic parameters:
+- **Design Aesthetic**: Modern, minimalist, brutalist, glassmorphism, or luxury?
+- **Color Palette**: What are the primary, secondary, and accent colors? (Prefer tailorable HSL/RGB models over static color keywords).
+- **Typography**: Which Google Fonts or system fonts fit the theme? (e.g., Inter, Outfit, Syne).
+- **Interactive States**: How do hovers, clicks, transitions, and loading states behave?
+
+### Phase 4: Technical Stack & Architecture
+Select the technologies and integration systems:
+- **Frontend Framework**: React, Next.js, Vite, Astro, Svelte, or Vanilla HTML/JS?
+- **Styling Method**: Vanilla CSS, Tailwind CSS, or CSS Modules?
+- **Data & Backend**: REST API, GraphQL, tRPC, Firebase, Supabase, or SQLite?
+- **State Management**: Zustand, Context API, Redux, or local React state?
+
+### Phase 5: SEO, Accessibility (A11y), and Performance
+Plan for discoverability and fast loading times:
+- **SEO Elements**: Title tag structure, meta descriptions, and semantic HTML tag hierarchy.
+- **Accessibility**: ARIA labels, semantic tags, keyboard navigation, and color contrast.
+- **Performance**: Preloading assets, lazy loading images, server-side rendering (SSR), and CDN delivery.
+
+### Phase 6: MVP Scope & Project Phases
+Break the work down into manageable increments:
+- **Phase 1 (MVP)**: The absolute minimum viable product needed to deploy.
+- **Phase 2 (Enhancements)**: Nice-to-have features, micro-animations, and advanced integrations.
+
+## Examples
+
+### Interactive Questionnaire Prompt Template
+Use this prompt layout when initiating a brainstorming session with a client or team member:
+
+```markdown
+👋 Let's brainstorm your new web project! We will walk through 6 quick phases.
+
+---
+### Phase 1: Core Concept & Scoping
+1. What is the main title or working name of this project?
+2. Who are the primary target users (e.g., tech-savvy professionals, shoppers, children)?
+3. What are the 3 core tasks a user must be able to perform?
+---
+```
+
+### Brainstorming Output Document Template
+Once all phases are complete, generate a markdown blueprint for the project using this template:
+
+```markdown
+# Project Blueprint: [Project Name]
+
+## 1. Product Concept
+- **Value Proposition**: [Summary]
+- **Key Features**:
+  1. [Feature 1]
+  2. [Feature 2]
+
+## 2. Information Architecture & UX
+- **Pages**: `/index.html`, `/dashboard.html`
+- **Primary User Flow**: User signs up -> completes onboarding -> views dashboard.
+
+## 3. Styling & Aesthetics
+- **Aesthetic**: Sleek Glassmorphism Dark Mode
+- **Color Tokens**:
+  - Background: `hsl(222, 47%, 11%)`
+  - Accent/Primary: `hsl(217, 91%, 60%)`
+- **Typography**: Inter (Body), Outfit (Headings)
+
+## 4. Technical Architecture
+- **Framework**: Next.js (App Router)
+- **Styling**: Tailwind CSS
+- **Database**: PostgreSQL with Prisma ORM
+
+## 5. SEO & Performance
+- **Primary Title**: "[Brand] | [Tagline]"
+- **Performance Strategy**: Dynamic image optimization, caching pages via Cloudflare.
+
+## 6. MVP vs Phase 2 Roadmap
+- **MVP**: Authentication + core dashboard view.
+- **Phase 2**: Real-time notifications and PDF reporting.
+```
+
+## Best Practices
+
+- ✅ Ask questions incrementally—never dump all six phases in a single response to avoid cognitive overload.
+- ✅ Propose logical defaults (e.g., recommending responsive Tailwind/CSS Grid and standard semantic HTML) if the user is unsure.
+- ✅ Ensure semantic HTML layout hierarchy (one `<h1>` per page, sequential `<section>`, `<article>`, `<header>`, `<footer>` elements) is planned from the start.
+- ✅ Document explicit non-goals to prevent feature creep.
+
+## Limitations
+
+- This skill focuses on conceptual mapping, architecture, and feature planning; it does not replace the writing of implementation code or system configuration.
+- Brainstorming outcomes should be treated as flexible blueprints and refined as technical constraints are discovered during development.
+
+## Security & Safety Notes
+
+- During Phase 4 (Architecture), flag any security requirements (e.g., SSL certificates, CORS policies, secure authentication storage, environment variables protection) early.
+- Do not store actual API tokens, passwords, or credentials in design or blueprint documents.
+
+## Common Pitfalls
+
+- **Problem**: Scope Creep (the project expands too quickly before building an MVP).
+  **Solution**: Enforce Phase 6 strictly. Push nice-to-have features into Phase 2.
+- **Problem**: Ignoring mobile design until late in development.
+  **Solution**: Brainstorm responsive patterns in Phase 2 before deciding on layout style in Phase 3.
+
+## Related Skills
+
+- `@writing-plans` - Organizing structural step-by-step engineering plans.
+- `@architecture-decision-records` - Documenting architectural decisions.
+- `@ux-flow` - Designing deep user experience flows and interaction details.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-skills-collection",
-  "version": "3.1.8",
+  "version": "3.1.10",
   "description": "OpenCode CLI plugin that automatically downloads and keeps skills up to date.",
   "main": "dist/index.js",
   "types": "dist/index.d.ts",

package/skills_index.json

@@ -1107,6 +1107,28 @@
       ]
     }
   },
+  {
+    "id": "ai-loop",
+    "path": "skills/ai-loop",
+    "category": "workflow",
+    "name": "ai-loop",
+    "description": "Runs a bounded spec-build-review development loop with explicit scope, stop conditions, and human approval gates for risky or ambiguous work.",
+    "risk": "safe",
+    "source": "community",
+    "date_added": "2026-06-27",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    }
+  },
   {
     "id": "ai-ml",
     "path": "skills/ai-ml",
@@ -10294,6 +10316,28 @@
       "reasons": []
     }
   },
+  {
+    "id": "cron-doctor",
+    "path": "skills/cron-doctor",
+    "category": "devops",
+    "name": "cron-doctor",
+    "description": "Diagnose and validate cron expressions before they ship. Catches the five silent death-traps: impossible dates that never fire, OR-semantics that fire too often, midnight spikes, uneven step drift, and leap-year February 29.",
+    "risk": "safe",
+    "source": "community",
+    "date_added": "2026-06-26",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    }
+  },
   {
     "id": "crossframe",
     "path": "skills/crossframe",
@@ -31369,6 +31413,28 @@
       "reasons": []
     }
   },
+  {
+    "id": "sql-sentinel",
+    "path": "skills/sql-sentinel",
+    "category": "data",
+    "name": "sql-sentinel",
+    "description": "Audit SQL for the cost & performance anti-patterns that burn warehouse credits. Scores warehouse health 0-100 and outputs a prioritized cost-reduction plan for BigQuery, Snowflake, Redshift, and Postgres.",
+    "risk": "safe",
+    "source": "community",
+    "date_added": "2026-06-26",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    }
+  },
   {
     "id": "sqlmap-database-pentesting",
     "path": "skills/sqlmap-database-pentesting",
@@ -35691,6 +35757,28 @@
       "reasons": []
     }
   },
+  {
+    "id": "web-project-brainstorming",
+    "path": "skills/web-project-brainstorming",
+    "category": "consulting",
+    "name": "web-project-brainstorming",
+    "description": "Masterclass framework for brainstorming web development projects and page designs. Outlines structural phases for concept, UX flow, styling aesthetics, technical architecture, and SEO.",
+    "risk": "safe",
+    "source": "self",
+    "date_added": "2026-06-26",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    }
+  },
   {
     "id": "web-scraper",
     "path": "skills/web-scraper",