opencode-skills-collection 2.0.37 → 2.0.39

package/README.md

@@ -184,9 +184,6 @@ The old `opencode-skills-antigravity` package on npm is deprecated and re-export
 Issues and pull requests are welcome
 at [github.com/FrancoStino/opencode-skills-collection](https://github.com/FrancoStino/opencode-skills-collection/issues).
 
-If you'd like to contribute new skills to the collection, open a PR adding a new folder inside `bundled-skills/` — it
-will be automatically picked up on next sync.
-
 ---
 
 ## Beta Releases

package/bundled-skills/.antigravity-install-manifest.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "updatedAt": "2026-04-11T17:33:11.670Z",
+  "updatedAt": "2026-04-11T19:36:06.899Z",
   "entries": [
     "00-andruia-consultant",
     "007",
@@ -1008,6 +1008,7 @@
     "protect-mcp-governance",
     "protocol-reverse-engineering",
     "pubmed-database",
+    "puzzle-activity-planner",
     "pydantic-ai",
     "pydantic-models-py",
     "pypict-skill",
@@ -1025,6 +1026,8 @@
     "radix-ui-design-system",
     "rag-engineer",
     "rag-implementation",
+    "rayden-code",
+    "rayden-use",
     "react-best-practices",
     "react-component-performance",
     "react-flow-architect",
@@ -1165,6 +1168,7 @@
     "skill-developer",
     "skill-improver",
     "skill-installer",
+    "skill-optimizer",
     "skill-rails-upgrade",
     "skill-router",
     "skill-scanner",

package/bundled-skills/docs/integrations/jetski-cortex.md

@@ -1,9 +1,9 @@
 ---
 title: Jetski/Cortex + Gemini Integration Guide
-description: "Use antigravity-awesome-skills with Jetski/Cortex without hitting context-window overflow with 1.397+ skills."
+description: "Use antigravity-awesome-skills with Jetski/Cortex without hitting context-window overflow with 1.401+ skills."
 ---
 
-# Jetski/Cortex + Gemini: safe integration with 1,1.397+ skills
+# Jetski/Cortex + Gemini: safe integration with 1,1.401+ skills
 
 This guide shows how to integrate the `antigravity-awesome-skills` repository with an agent based on **Jetski/Cortex + Gemini** (or similar frameworks) **without exceeding the model context window**.
 
@@ -23,7 +23,7 @@ Never do:
 - concatenate all `SKILL.md` content into a single system prompt;
 - re-inject the entire library for **every** request.
 
-With over 1,1.397 skills, this approach fills the context window before user messages are even added, causing truncation.
+With over 1,1.401 skills, this approach fills the context window before user messages are even added, causing truncation.
 
 ---
 

package/bundled-skills/docs/integrations/jetski-gemini-loader/README.md

@@ -20,7 +20,7 @@ This example shows one way to integrate **antigravity-awesome-skills** with a Je
 - How to enforce a **maximum number of skills per turn** via `maxSkillsPerTurn`.
 - How to choose whether to **truncate or error** when too many skills are requested via `overflowBehavior`.
 
-This pattern avoids context overflow when you have 1,397+ skills installed.
+This pattern avoids context overflow when you have 1,401+ skills installed.
 
 ---
 

package/bundled-skills/docs/maintainers/repo-growth-seo.md

@@ -6,7 +6,7 @@ This document keeps the repository's GitHub-facing discovery copy aligned with t
 
 Preferred positioning:
 
-> Installable GitHub library of 1,397+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and other AI coding assistants.
+> Installable GitHub library of 1,401+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and other AI coding assistants.
 
 Key framing:
 
@@ -20,7 +20,7 @@ Key framing:
 
 Preferred description:
 
-> Installable GitHub library of 1,397+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and more. Includes installer CLI, bundles, workflows, and official/community skill collections.
+> Installable GitHub library of 1,401+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and more. Includes installer CLI, bundles, workflows, and official/community skill collections.
 
 Preferred homepage:
 
@@ -28,7 +28,7 @@ Preferred homepage:
 
 Preferred social preview:
 
-- use a clean preview image that says `1,397+ Agentic Skills`;
+- use a clean preview image that says `1,401+ Agentic Skills`;
 - mention Claude Code, Cursor, Codex CLI, and Gemini CLI;
 - avoid dense text and tiny logos that disappear in social cards.
 

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

@@ -69,7 +69,7 @@ For manual updates, you need:
 The update process refreshes:
 - Skills index (`skills_index.json`)
 - Web app skills data (`apps\web-app\public\skills.json`)
-- All 1,397+ skills from the skills directory
+- All 1,401+ skills from the skills directory
 
 ## When to Update
 

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

@@ -673,4 +673,4 @@ Found a skill that should be in a bundle? Or want to create a new bundle? [Open
 
 ---
 
-_Last updated: March 2026 | Total Skills: 1,397+ | Total Bundles: 37_
+_Last updated: March 2026 | Total Skills: 1,401+ | Total Bundles: 37_

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,397+ skills instead of a narrow single-domain starter pack.
+- It includes 1,401+ 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,397+ files.
+- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,401+ 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 (V9.11.0)
+# Getting Started with Antigravity Awesome Skills (V9.12.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,397+ specialized areas
+- **Domain expertise** across 1,401+ 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,397+ skill files** to your computer (default: `~/.gemini/antigravity/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)  
+✅ **Downloaded 1,401+ skill files** to your computer (default: `~/.gemini/antigravity/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,397+ tools (✅ done)
+- You installed a toolbox with 1,401+ 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,397+ skills at once. Here's a sensible approach:
+Don't try to use all 1,401+ 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,397+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
+No. Even though you have 1,401+ 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,397+ skills live here
+├── 📁 skills/                          ← 1,401+ skills live here
 │   │
 │   ├── 📁 brainstorming/
 │   │   └── 📄 SKILL.md                 ← Skill definition
@@ -47,7 +47,7 @@ antigravity-awesome-skills/
 │   │   └── 📁 2d-games/
 │   │       └── 📄 SKILL.md             ← Nested skills also supported
 │   │
-│   └── ... (1,397+ total)
+│   └── ... (1,401+ total)
 │
 ├── 📁 apps/
 │   └── 📁 web-app/                     ← Interactive browser
@@ -100,7 +100,7 @@ antigravity-awesome-skills/
 
 ```
                     ┌─────────────────────────┐
-                    │  1,397+ SKILLS          │
+                    │  1,401+ 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,397+ total)                │
+│   └── ... (1,401+ total)                │
 └─────────────────────────────────────────┘
 ```
 

package/bundled-skills/puzzle-activity-planner/SKILL.md

@@ -0,0 +1,71 @@
+---
+name: puzzle-activity-planner
+description: "Plan puzzle-based activities for classrooms, parties, and events with pre-configured generator links"
+category: education
+risk: safe
+source: community
+source_repo: fruitwyatt/puzzle-activity-planner
+source_type: community
+date_added: "2026-04-11"
+author: fruitwyatt
+tags: [education, puzzle, classroom, activity-planning, event]
+tools: [claude, cursor, gemini, codex]
+---
+
+# Puzzle Activity Planner
+
+## Overview
+
+Plans engaging puzzle-based activities for classrooms, parties, team-building sessions, and events. Given an event description, audience, and goal, produces a structured activity plan with pre-configured generator links that include URL parameters for one-click ready-to-use puzzles.
+
+## When to Use This Skill
+
+- Planning a classroom lesson with puzzle activities
+- Organizing party games involving puzzles
+- Creating team-building sessions with multiple puzzle types
+- Preparing educational activities for kids, students, or adults
+
+## Process
+
+1. **Understand the event** - audience, group size, duration, theme
+2. **Select puzzle types** - match difficulty and format to the audience
+3. **Build timeline** - minute-by-minute flow with transitions
+4. **Generate links** - pre-configured URLs with theme content baked in
+5. **Create prep checklist** - print quantities and materials needed
+
+## Puzzle Types Supported
+
+- **Word Search** - vocabulary building, warm-ups, brain training
+- **Crossword** - vocabulary review, test prep, party games
+- **Sudoku** - math warm-ups, logic training, focus time
+- **Bingo** - group games, classroom review, holiday celebrations
+- **Jigsaw** - ice-breakers, collaborative activities, crafts
+
+## URL Parameters
+
+All generator links include pre-filled parameters so users get ready-to-use puzzles in one click. The skill generates theme-appropriate content (words, clues, items) and embeds them directly in the URL.
+
+Example:
+```
+https://jigsawmake.com/word-search-maker?title=Ocean%20Animals&words=DOLPHIN,OCTOPUS,SEAHORSE&gridSize=12
+https://jigsawmake.com/crossword-puzzle-maker?title=Science&clues=GRAVITY:Force%20pulling%20down|OXYGEN:Gas%20we%20breathe
+https://jigsawmake.com/bingo-card-generator?title=Party%20Bingo&items=Dance,Laugh,Sing&cardCount=25
+```
+
+## Output Format
+
+Each plan includes:
+- Activity header (occasion, audience, duration, difficulty)
+- Objectives (2-3 learning or engagement goals)
+- Puzzle menu table with generator links
+- Minute-by-minute timeline
+- Materials and prep checklist with print quantities
+- Differentiation tips (easier/harder adaptations)
+
+## Rules
+
+- Match puzzle difficulty to the audience
+- Suggest 2-3 puzzle types per activity for variety
+- Include timing buffers for transitions
+- Apply the user's theme consistently across all puzzles
+- Always use URL parameters with pre-filled content

package/bundled-skills/rayden-code/SKILL.md

@@ -0,0 +1,104 @@
+---
+name: rayden-code
+description: Generate React code with Rayden UI components using correct props, tokens, and premium layout patterns
+category: development
+risk: safe
+source: https://github.com/playbookTV/rayden-ui-design-skill
+source_type: community
+date_added: 2026-04-10
+author: Leslie Williams
+tags: react, tailwind, design-system, ui, components, vibe-coding, rayden, rayna-ui, code-generation
+tools: Read, Write, Edit, Bash, Glob, Grep
+---
+
+# Rayden Code Skill
+
+## Overview
+
+Generate production-quality React + Tailwind CSS code using the Rayden UI component library (34 components). The skill loads a complete API reference with every component, every prop, design tokens, layout patterns, and an explicit anti-pattern ban list — preventing hallucinated components and generic AI output. Built on the Rayna UI design system.
+
+## When to Use This Skill
+
+- You're building a new page or feature using Rayden UI components
+- You want to scaffold a dashboard, landing page, auth screen, settings page, or data table
+- You need to generate React code that follows a specific design system precisely
+- You want to prototype UI quickly with correct component usage and premium aesthetics
+- You're vibe coding and want design-system-compliant output
+
+## How It Works
+
+1. **Parses the request** — Identifies page type, required components, and data model
+2. **Loads RAYDEN_RULES.md** — Complete reference: 34 components with full props, design philosophy, token classes, layout patterns, anti-patterns, and accessibility rules
+3. **Plans the layout** — Decides page structure, component selection, spacing, color, and elevation strategy
+4. **Generates code** — Writes React + Tailwind CSS using only documented components and token classes
+5. **Self-validates** — Runs a 16-point checklist covering correctness (valid components/props, token usage, nesting) and design quality (whitespace, hierarchy, restraint, responsiveness)
+
+## Examples
+
+### Vibe code a SaaS dashboard
+
+```
+/rayden-code a dashboard with KPI cards, a recent orders table, and an activity feed
+```
+
+**Use case:** You're building an internal analytics tool and need a full dashboard page with MetricsCard grid, sortable Table, and ActivityFeed sidebar — all with correct Rayden imports and token classes.
+
+### Scaffold a login page
+
+```
+/rayden-code login page with email and password
+```
+
+**Use case:** You need a centered auth form with Input components, a primary Button, and proper visual hierarchy — following Rayden's "Auth / Focused Form" pattern.
+
+### Build an admin settings page
+
+```
+/rayden-code settings page with profile section, notification toggles, and danger zone
+```
+
+**Use case:** You're adding a settings area to your app and need form sections with Toggle components, a destructive action zone, and a single-column constrained layout.
+
+### Create a pricing page
+
+```
+/rayden-code pricing page with 3 tiers and a feature comparison table
+```
+
+**Use case:** You need a marketing pricing section with Card components for each tier, Badge for the recommended plan, and a Table for feature comparison.
+
+### Build an e-commerce product grid
+
+```
+/rayden-code product catalog with filters, search, and a card grid
+```
+
+**Use case:** You're building a storefront and need a responsive product grid with Chip filters, Input search, Pagination, and Cards with images — all using Rayden's layout and spacing rules.
+
+## Best Practices
+
+- Describe what you want in plain language — the skill maps your request to the right components
+- Install `@raydenui/ui` in your project first (`npm install @raydenui/ui`)
+- Import `@raydenui/ui/styles.css` in your app entry point for design tokens to work
+- Review generated code for business logic — the skill handles UI, not data fetching
+- Use alongside `/rayden-use` if you also want the same design built in Figma
+
+## Security & Safety Notes
+
+- This skill only reads its bundled rules file and writes code to your project
+- No external network requests
+- No secrets or credentials involved
+- Generated code uses standard React patterns with no eval or dynamic code execution
+
+## Common Pitfalls
+
+| Problem | Solution |
+|---------|----------|
+| Components not rendering correctly | Ensure `@raydenui/ui/styles.css` is imported in your app entry |
+| "Component doesn't exist" error | The skill only uses documented components — check if you're asking for something Rayden doesn't have |
+| Colors look wrong | Use token classes (`bg-primary-500`) not hex values. Ensure the Rayden CSS is loaded |
+| Layout not responsive | The skill generates responsive code by default — check that your viewport meta tag is set |
+
+## Related Skills
+
+- `rayden-use` — Build Rayden UI components and screens in Figma via MCP (included in the same package)

package/bundled-skills/rayden-use/SKILL.md

@@ -0,0 +1,107 @@
+---
+name: rayden-use
+description: Build and maintain Rayden UI components and screens in Figma via Figma MCP with full design token enforcement
+category: design
+risk: safe
+source: https://github.com/playbookTV/rayden-ui-design-skill
+source_type: community
+date_added: 2026-04-10
+author: Leslie Williams
+tags: figma, design-system, ui, components, mcp, rayden, rayna-ui
+tools: mcp__claude_ai_Figma__use_figma, mcp__claude_ai_Figma__get_screenshot, mcp__claude_ai_Figma__whoami, Read
+---
+
+# Rayden UI Design Skill
+
+## Overview
+
+Build and maintain Rayden UI components and screens directly in Figma using the Figma MCP. The skill enforces the Rayna UI design system — resolved design tokens, craft rules, anti-pattern detection, and visual validation — so every output is mechanically correct and visually premium. Supports three style modes (conservative, balanced, expressive) and includes a dedicated subagent for full-page screen composition.
+
+## When to Use This Skill
+
+- You need to build a new Rayden UI component with all its variants in Figma
+- You're composing a full screen (dashboard, landing page, auth form, settings, data table) from Rayden patterns
+- You want to audit an existing Figma file for design system compliance
+- You need to add new variants to an existing Figma component
+- You're syncing React component updates back to Figma
+
+## How It Works
+
+1. **Verifies environment** — Checks Figma MCP connection and write access via `whoami`
+2. **Loads component data** — Reads Rayden component specs, anatomy, and tokens from the `@raydenui/ai` MCP server or installed package
+3. **Loads craft rules** — Reads supporting files: resolved token values, craft rules, anti-patterns, and screen layout patterns
+4. **Identifies task type** — Determines if building a single component, composing a screen, auditing, or adding variants
+5. **Applies style mode** — Adjusts spacing, shadow, typography, and visual weight based on conservative/balanced/expressive mode
+6. **Builds with helpers** — Generates Figma Plugin API code using mandatory helper functions (hexToRgb, loadFonts, applyShadow, applyBorder) with auto layout on every frame
+7. **Visual validation** — Takes screenshots after each build stage and validates against 8 acceptance criteria (alignment, spacing, color accuracy, hierarchy, radius, shadow, primary action count)
+
+## Examples
+
+### Build a component with all variants
+
+```
+/rayden-use Button https://figma.com/file/abc123
+```
+
+**Use case:** You're starting a new design system file and need the Button component with all variants (primary, secondary, grey, destructive) in solid and outlined appearances across SM and LG sizes.
+
+### Design a SaaS dashboard
+
+```
+/rayden-use dashboard-screen balanced https://figma.com/file/abc123
+```
+
+**Use case:** You're designing an analytics dashboard and need a sidebar layout with KPI cards, a data table, and an activity feed — all using consistent Rayden tokens and spacing.
+
+### Build a marketing landing page
+
+```
+/rayden-compose landing expressive https://figma.com/file/abc123
+```
+
+**Use case:** You need a high-impact landing page with bolder typography, stronger shadows, and asymmetric layouts that avoid the generic "AI-generated" look.
+
+### Audit an existing design for compliance
+
+```
+/rayden-use audit https://figma.com/file/abc123
+```
+
+**Use case:** You have an existing Figma file and want to check that all colors match Rayden tokens, spacing is on the 4px grid, and radius is concentric.
+
+### Add variants to an existing component
+
+```
+/rayden-use add-variants Input https://figma.com/file/abc123
+```
+
+**Use case:** The Input component exists in your Figma file but is missing error and success states — the skill reads the existing structure and extends it.
+
+## Best Practices
+
+- Always provide a Figma file URL as the last argument
+- Use `balanced` mode (default) for most use cases; `conservative` for dense admin UIs, `expressive` for marketing pages
+- Let the skill take screenshots between build stages — this is how it validates output quality
+- Install `@raydenui/ai` as an MCP server for the richest component data access
+- Review the generated output in Figma after completion — the skill validates mechanically but human judgment on aesthetics is still valuable
+
+## Security & Safety Notes
+
+- This skill only reads local supporting files and calls the Figma MCP — no external network requests beyond Figma's API
+- Requires Figma Dev or Full seat with write access to the target file
+- Does not modify files outside of the target Figma document
+- All design tokens are bundled in the skill's supporting files — no secrets or credentials involved
+
+## Common Pitfalls
+
+| Problem | Solution |
+|---------|----------|
+| "Font not found" error | The skill falls back to Roboto if Inter is unavailable — ensure Inter is loaded in your Figma file for best results |
+| Components don't combine as variants | All components must share the same parent frame before calling `combineAsVariants` |
+| Colors look wrong | Verify you're using resolved token hex values from tokens.md, not approximations |
+| Figma permission denied | Check that your Figma seat is Dev or Full (not Viewer) and the file isn't view-only |
+
+## Related Skills
+
+- `rayden-code` — Generate React code with Rayden UI components (included in the same package)
+- `rayden-compose` — Dedicated subagent for composing full-page Figma screens (included in this skill package)

package/bundled-skills/sales-automator/SKILL.md

@@ -1,12 +1,6 @@
 ---
 name: sales-automator
-description: 'Draft cold emails, follow-ups, and proposal templates. Creates
-
-  pricing pages, case studies, and sales scripts. Use PROACTIVELY for sales
-
-  outreach or lead nurturing.
-
-  '
+description: 'Draft cold emails, follow-ups, and proposal templates. Creates pricing pages, case studies, and sales scripts. Use PROACTIVELY for sales outreach or lead nurturing. '
 risk: unknown
 source: community
 date_added: '2026-02-27'

package/bundled-skills/skill-optimizer/SKILL.md

@@ -0,0 +1,266 @@
+---
+name: skill-optimizer
+description: "Diagnose and optimize Agent Skills (SKILL.md) with real session data and research-backed static analysis. Works with Claude Code, Codex, and any Agent Skills-compatible agent."
+risk: safe
+source: hqhq1025/skill-optimizer (MIT)
+date_added: "2026-04-11"
+---
+
+## When to Use This Skill
+
+- Use when skills are not triggering as expected or seem broken
+- Use when you want to audit and improve your skill library's quality
+- Use when you want to understand which skills are underperforming or wasting context tokens
+
+## Rules
+
+- **Read-only**: never modify skill files. Only output report.
+- **All 8 dimensions**: do not skip any. If data is insufficient, report "N/A — insufficient session data" rather than omitting.
+- **Quantify**: "you had 12 research tasks last week but the skill never triggered" beats "you often do research".
+- **Suggest, don't prescribe**: give specific wording suggestions for description improvements, but frame as suggestions.
+- **Show evidence**: for undertrigger claims, quote the actual user message that should have triggered the skill.
+- **Evidence-based suggestions**: when suggesting description rewrites, cite the specific research finding that motivates the change (e.g., "front-load trigger keywords — MCP study shows 3.6x selection rate improvement").
+
+## Overview
+
+Analyze skills using **historical session data + static quality checks**, output a diagnostic report with P0/P1/P2 prioritized fixes. Scores each skill on a 5-point composite scale across 8 dimensions.
+
+CSO (Claude/Agent Search Optimization) = writing skill descriptions so agents select the right skill at the right time. This skill checks for CSO violations.
+
+## Usage
+
+- `/optimize-skill` → scan all skills
+- `/optimize-skill my-skill` → single skill
+- `/optimize-skill skill-a skill-b` → multiple specified skills
+
+## Data Sources
+
+Auto-detect the current agent platform and scan the corresponding paths:
+
+| Source | Claude Code | Codex | Shared |
+|--------|------------|-------|--------|
+| Session transcripts | `~/.claude/projects/**/*.jsonl` | `~/.codex/sessions/**/*.jsonl` | — |
+| Skill files | `~/.claude/skills/*/SKILL.md` | `~/.codex/skills/*/SKILL.md` | `~/.agents/skills/*/SKILL.md` |
+
+**Platform detection:** Check which directories exist. Scan all available sources — a user may have both Claude Code and Codex installed.
+
+## Workflow
+
+```
+Identify target skills
+        ↓
+Collect session data (python3 scripts scan JSONL transcripts)
+        ↓
+Run 8 analysis dimensions
+        ↓
+Compute composite scores
+        ↓
+Output report with P0/P1/P2
+```
+
+### Step 1: Identify Target Skills
+
+Scan skill directories in order: `~/.claude/skills/`, `~/.codex/skills/`, `~/.agents/skills/`. Deduplicate by skill name (same name in multiple locations = same skill). For each, read `SKILL.md` and extract:
+- name, description (from YAML frontmatter)
+- trigger keywords (from description field)
+- defined workflow steps (Step 1/2/3... or ### sections under Workflow)
+- word count
+
+If user specified skill names, filter to only those.
+
+### Step 2: Collect Session Data
+
+Use python3 scripts via Bash to scan session JSONL files. Extract:
+
+**Claude Code sessions** (`~/.claude/projects/**/*.jsonl`):
+- `Skill` tool_use calls (which skills were invoked)
+- User messages (full text)
+- Assistant messages after skill invocation (for workflow tracking)
+- User messages after skill invocation (for reaction analysis)
+
+**Codex sessions** (`~/.codex/sessions/**/*.jsonl`):
+- `session_meta` events → extract `base_instructions` for skill loading evidence
+- `response_item` events → assistant outputs (workflow tracking)
+- `event_msg` events → tool execution and skill-related events
+- User messages from `turn_context` events (for reaction analysis)
+
+**Note:** Codex injects skills via context rather than explicit `Skill` tool calls. Skill loading (present in `base_instructions`) does NOT equal active invocation. To detect actual use, search for skill-specific workflow markers (step headers, output formats) in `response_item` content within that session. A skill is "invoked" only if the agent produced output following the skill's defined workflow.
+
+**Aggregated:**
+- Per-skill: invocation count, trigger keyword match count
+- Per-skill: user reaction sentiment after invocation
+- Per-skill: workflow step completion markers
+
+### Step 3: Run 8 Analysis Dimensions
+
+**You MUST run ALL 8 dimensions.** The baseline behavior without this skill is to skip dimensions 4.2, 4.3, 4.5b, and 4.8. These are the most valuable dimensions — do not skip them.
+
+#### 4.1 Trigger Rate
+
+Count how many times each skill was actually invoked vs how many times its trigger keywords appeared in user messages.
+
+**Claude Code:** count `Skill` tool_use calls in transcripts.
+**Codex:** count sessions where the agent produced output following the skill's workflow markers (not merely loaded in context).
+
+**Diagnose:**
+- Never triggered → skill may be useless or trigger words wrong
+- Keywords match >> actual invocations → undertrigger problem, description needs work
+- High frequency → core skill, worth optimizing
+
+#### 4.2 Post-Invocation User Reaction
+
+**This dimension is critical and easy to skip. Do not skip it.**
+
+After a skill is invoked in a session, read the user's next 3 messages. Classify:
+- **Negative**: "no", "wrong", "never mind", "not what I wanted", user interrupts
+- **Correction**: user re-describes their intent, manually overrides skill output
+- **Positive**: "good", "ok", "continue", "nice", user follows the workflow
+- **Silent switch**: user changes topic entirely (likely false positive trigger)
+
+Report per-skill satisfaction rate.
+
+#### 4.3 Workflow Completion Rate
+
+**This dimension is critical and easy to skip. Do not skip it.**
+
+For each skill invocation found in session data:
+1. Extract the skill's defined steps from SKILL.md
+2. Search the assistant messages in that session for step markers (Step N, specific output formats defined in the skill)
+3. Calculate: how far did execution get?
+
+Report: `{skill-name} (N steps): avg completed Step X/N (Y%)`
+
+If a specific step is frequently where execution stops, flag it.
+
+#### 4.4 Static Quality Analysis
+
+Check each SKILL.md against these 14 rules:
+
+| Check | Pass Criteria |
+|-------|--------------|
+| Frontmatter format | Only `name` + `description`, total < 1024 chars |
+| Name format | Letters, numbers, hyphens only |
+| Description trigger | Starts with "Use when..." or has explicit trigger conditions |
+| Description workflow leak | Description does NOT summarize the skill's workflow steps (CSO violation) |
+| Description pushiness | Description actively claims scenarios where it should be used, not just passive |
+| Overview section | Present |
+| Rules section | Present |
+| MUST/NEVER density | Count ALL-CAPS directive words; >5 per 100 words = flag |
+| Word count | < 500 words (flag if over) |
+| Narrative anti-pattern | No "In session X, we found..." storytelling |
+| YAML quoting safety | description containing `: ` must be wrapped in double quotes |
+| Critical info position | Core trigger conditions and primary actions must be in the first 20% of SKILL.md |
+| Description 250-char check | Primary trigger keywords must appear within the first 250 characters of description |
+| Trigger condition count | ≤ 2 trigger conditions in description is ideal |
+
+#### 4.5a False Positive Rate (Overtrigger)
+
+Skill was invoked but user immediately rejected or ignored it.
+
+#### 4.5b Undertrigger Detection
+
+**This is the highest-value dimension.** For each skill, extract its **capability keywords** (not just trigger keywords — what the skill CAN do). Then scan user messages for tasks that match those capabilities but where the skill was NOT invoked.
+
+Report: which user messages SHOULD have triggered the skill but didn't, and suggest description improvements.
+
+**Compounding Risk Assessment:**
+For skills with chronic undertriggering (0 triggers across 5+ sessions where relevant tasks appeared), flag as "compounding risk" — undertriggered skills cannot self-improve through usage feedback, causing the gap to widen over time. Recommend immediate description rewrite as P0.
+
+#### 4.6 Cross-Skill Conflicts
+
+Compare all skill pairs:
+- Trigger keyword overlap (same keywords in two descriptions)
+- Workflow overlap (two skills teach similar processes)
+- Contradictory guidance
+
+#### 4.7 Environment Consistency
+
+For each skill, extract referenced:
+- File paths → check if they exist (`test -e`)
+- CLI tools → check if installed (`which`)
+- Directories → check if they exist
+
+Flag any broken references.
+
+#### 4.8 Token Economics
+
+**This dimension is critical and easy to skip. Do not skip it.**
+
+For each skill:
+- Word count (from Step 1)
+- Trigger frequency (from 4.1)
+- Cost-effectiveness = trigger count / word count
+- Flag: large + never-triggered skills as candidates for removal or compression
+
+**Progressive Disclosure Tier Check:**
+Evaluate each skill against the 3-tier loading model:
+- Tier 1 (frontmatter): ~100 tokens. Check: is description ≤ 1024 chars?
+- Tier 2 (SKILL.md body): <500 lines recommended. Check: word count.
+- Tier 3 (reference files): loaded on demand. Check: does skill use reference files for detailed content, or cram everything into SKILL.md?
+
+Flag skills that put 500+ words in SKILL.md without using reference files as "poor progressive disclosure".
+
+### Step 4: Composite Score
+
+Rate each skill on a 5-point scale:
+
+| Score | Meaning |
+|-------|---------|
+| 5 | Healthy: high trigger rate, positive reactions, complete workflows, clean static |
+| 4 | Good: minor issues in 1-2 dimensions |
+| 3 | Needs attention: significant gap in 1 dimension or minor gaps in 3+ |
+| 2 | Problematic: never triggered, or negative user reactions, or major static issues |
+| 1 | Broken: doesn't work, references missing, or fundamentally misaligned |
+
+**Scored dimensions** (weighted average):
+- Trigger rate: 25%
+- User reaction: 20%
+- Workflow completion: 15%
+- Static quality: 15%
+- Undertrigger: 15%
+- Token economics: 10%
+
+**Qualitative dimensions** (reported but not scored):
+- 4.5a Overtrigger: reported as count + examples
+- 4.6 Cross-Skill Conflicts: reported as conflict pairs
+- 4.7 Environment Consistency: reported as pass/fail per reference
+
+## Report Format
+
+```markdown
+# Skill Optimization Report
+**Date**: {date}
+**Scope**: {all / specified skills}
+**Session data**: {N} sessions, {date range}
+
+## Overview
+| Skill | Triggers | Reaction | Completion | Static | Undertrigger | Token | Score |
+|-------|----------|----------|------------|--------|--------------|-------|-------|
+| example-skill | 2 | 100% | 86% | B+ | 1 miss | 486w | 4/5 |
+
+## P0 Fixes (blocking usage)
+1. ...
+
+## P1 Improvements (better experience)
+1. ...
+
+## P2 Optional Optimizations
+1. ...
+
+## Per-Skill Diagnostics
+### {skill-name}
+#### 4.1 Trigger Rate
+...
+#### 4.2 User Reaction
+...
+(all 8 dimensions)
+```
+
+## Research Background
+
+The analysis dimensions in this report are grounded in the following research:
+- **Undertrigger detection**: Memento-Skills (arXiv:2603.18743) — skills as structured files require accurate routing; unrouted skills cannot self-improve via the read-write learning loop
+- **Description quality**: MCP Description Quality (arXiv:2602.18914) — well-written descriptions achieve 72% tool selection rate vs. 20% random baseline (3.6x improvement)
+- **Information position**: Lost in the Middle (Liu et al., TACL 2024) — U-shaped LLM attention curve
+- **Format impact**: He et al. (arXiv:2411.10541) — format changes alone can cause 9-40% performance variance
+- **Instruction compliance**: IFEval (arXiv:2311.07911) — LLMs struggle with multi-constraint prompts

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "opencode-skills-collection",
-  "version": "2.0.37",
+  "version": "2.0.39",
   "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

@@ -22158,6 +22158,28 @@
       "reasons": []
     }
   },
+  {
+    "id": "puzzle-activity-planner",
+    "path": "skills/puzzle-activity-planner",
+    "category": "education",
+    "name": "puzzle-activity-planner",
+    "description": "Plan puzzle-based activities for classrooms, parties, and events with pre-configured generator links",
+    "risk": "safe",
+    "source": "community",
+    "date_added": "2026-04-11",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    }
+  },
   {
     "id": "pydantic-ai",
     "path": "skills/pydantic-ai",
@@ -22532,6 +22554,50 @@
       "reasons": []
     }
   },
+  {
+    "id": "rayden-code",
+    "path": "skills/rayden-code",
+    "category": "development",
+    "name": "rayden-code",
+    "description": "Generate React code with Rayden UI components using correct props, tokens, and premium layout patterns",
+    "risk": "safe",
+    "source": "https://github.com/playbookTV/rayden-ui-design-skill",
+    "date_added": "2026-04-10",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    }
+  },
+  {
+    "id": "rayden-use",
+    "path": "skills/rayden-use",
+    "category": "design",
+    "name": "rayden-use",
+    "description": "Build and maintain Rayden UI components and screens in Figma via Figma MCP with full design token enforcement",
+    "risk": "safe",
+    "source": "https://github.com/playbookTV/rayden-ui-design-skill",
+    "date_added": "2026-04-10",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    }
+  },
   {
     "id": "react-best-practices",
     "path": "skills/react-best-practices",
@@ -23395,7 +23461,7 @@
     "path": "skills/sales-automator",
     "category": "business",
     "name": "sales-automator",
-    "description": "Draft cold emails, follow-ups, and proposal templates. Creates\npricing pages, case studies, and sales scripts. Use PROACTIVELY for sales\noutreach or lead nurturing.\n",
+    "description": "Draft cold emails, follow-ups, and proposal templates. Creates pricing pages, case studies, and sales scripts. Use PROACTIVELY for sales outreach or lead nurturing. ",
     "risk": "unknown",
     "source": "community",
     "date_added": "2026-02-27",
@@ -25530,6 +25596,30 @@
       "reasons": []
     }
   },
+  {
+    "id": "skill-optimizer",
+    "path": "skills/skill-optimizer",
+    "category": "meta",
+    "name": "skill-optimizer",
+    "description": "Diagnose and optimize Agent Skills (SKILL.md) with real session data and research-backed static analysis. Works with Claude Code, Codex, and any Agent Skills-compatible agent.",
+    "risk": "safe",
+    "source": "hqhq1025/skill-optimizer (MIT)",
+    "date_added": "2026-04-11",
+    "plugin": {
+      "targets": {
+        "codex": "blocked",
+        "claude": "blocked"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": [
+        "target_specific_home_path"
+      ]
+    }
+  },
   {
     "id": "skill-rails-upgrade",
     "path": "skills/skill-rails-upgrade",