opencode-skills-collection 3.0.42 → 3.0.44

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

@@ -21,7 +21,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,525+ skills installed.
+This pattern avoids context overflow when you have 1,527+ skills installed.
 
 Manifest contract references:
 

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,525+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and other AI coding assistants.
+> Installable GitHub library of 1,527+ 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,525+ 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,527+ 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,525+ Agentic Skills`;
+- use a clean preview image that says `1,527+ 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

@@ -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,525+ skills from the skills directory
+- All 1,527+ skills from the skills directory
 
 ## When to Update
 

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

@@ -917,4 +917,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,525+ | Total Bundles: 52_
+_Last updated: March 2026 | Total Skills: 1,527+ | Total Bundles: 52_

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

package/bundled-skills/event-staffing-ordering/SKILL.md

@@ -75,29 +75,14 @@ with the gathered details. Alternatives: email **megan@tempguru.co** or call **(
 TempGuru responds within one business day; orders are confirmed within
 48 hours. There is no subscription — billing is per event.
 
-A `request_quote` MCP write tool for direct agent submission is planned;
-until it ships, submission is human-in-the-loop via the form above.
-
-## Limitations
-
-- MCP lookups provide planning guidance only; they do not reserve workers,
-  create a quote, or guarantee availability for a specific event date.
-- Final rates, staffing confirmation, background checks, COIs, and event
-  terms must come from TempGuru or the assigned staffing coordinator.
-- The skill should not collect payment details, credentials, private attendee
-  data, or venue contracts; use the official request form or direct contact.
-- Compliance notes are operational guidance and should be routed to the
-  companion compliance skill or qualified counsel when legal certainty is
-  required.
-
 ## Limitations
 
 - Rate ranges are planning estimates — not final quotes. Binding pricing comes from TempGuru after human review.
 - Availability responses are lead-time guidance, not reservations.
 - Coverage is limited to US and Canadian markets (300+ cities). Not applicable for events outside this geography.
 - Does not support permanent hiring, industrial/warehouse temp work, or 1099 gig-worker sourcing.
-- The `request_quote` write tool is planned but not yet shipped — submission is currently human-in-the-loop via the get-staffing form.
-- MCP server is read-only; agents cannot modify TempGuru data.
+- Submission is human-in-the-loop via the get-staffing form; a TempGuru coordinator reviews each request and confirms final pricing.
+- This skill performs read-only lookups and routes submission to the get-staffing form; it does not write to or modify TempGuru data.
 
 ## Rules for agents
 

package/bundled-skills/unship/SKILL.md

@@ -0,0 +1,138 @@
+---
+name: unship
+description: "Compare AI agent-made UI variants locally in a real app, then keep one and clean up unused temporary code."
+category: development
+risk: safe
+source: community
+source_repo: mbenhard/unship
+source_type: community
+date_added: "2026-06-07"
+author: Marcus Benhard
+tags: [ui-variants, frontend, local-first, coding-agents]
+tools: [claude-code, antigravity, cursor, gemini-cli, codex-cli, opencode]
+license: "MIT"
+license_source: "https://github.com/mbenhard/unship/blob/main/LICENSE"
+---
+
+# Unship
+
+## Overview
+
+Unship is a local workflow for comparing AI-generated UI alternatives in the real application instead of accepting one generated version at a time. It adds temporary source-level variants, shows a local browser picker, and then cleans up the unused options after the user chooses.
+
+This skill is for frontend iteration with coding agents. It is not production A/B testing, analytics, feature flagging, or a hosted experiment service.
+
+## When to Use This Skill
+
+- Use when the user wants to compare multiple UI, layout, copy, state, flow, or design-system alternatives.
+- Use when a coding agent should create several temporary options in real source code and let the user judge them in the running local app.
+- Use when the user chooses a visible option and wants the losing temporary code removed before shipping.
+
+## Do Not Use This Skill When
+
+- The user needs production experiments, traffic splitting, analytics, or feature flags.
+- The app cannot safely render inactive hidden variants because of duplicate active IDs, global scripts, analytics triggers, focus traps, destructive actions, or autoplay side effects.
+- The user has not authorized local source edits.
+
+## How It Works
+
+### 1. Install or reuse Unship
+
+Prefer the project-local binary when it exists:
+
+```bash
+./node_modules/.bin/unship doctor --json --no-update-check
+```
+
+Otherwise use the npm package without assuming a global binary:
+
+```bash
+npx -y @unship/cli@latest doctor --json --no-update-check
+```
+
+If setup is needed for the local picker, run:
+
+```bash
+npx -y @unship/cli@latest setup --json
+```
+
+Patch only the smallest development-only mount point required to load the picker in the local preview.
+
+### 2. Create temporary variants
+
+Inspect the relevant page, component, route, or rendered artifact. Add the smallest source-level comparison that lets the user judge real options in context.
+
+Use Unship markup:
+
+```html
+<section data-unship-pick="Hero">
+  <div data-unship-option="Current">...</div>
+  <div data-unship-option="Proof-led" hidden>...</div>
+  <div data-unship-option="Visual" hidden>...</div>
+</section>
+```
+
+Keep option labels short and visible. Prefer 2-4 meaningful alternatives unless the user asked for a specific count.
+
+### 3. Verify comparison readiness
+
+Before handing off to the user, check that:
+
+- the expected `data-unship-pick` group exists;
+- the expected option labels exist;
+- options are direct children of the group;
+- exactly one option is initially visible;
+- hidden inactive options remain hidden.
+
+### 4. Let the user choose
+
+Tell the user the group label, option labels, setup status, and any detected local preview server hints. The user chooses by naming a visible option label in chat.
+
+### 5. Clean up after selection
+
+When the user picks a winner, keep that option's real source and remove losing options for that group. Remove temporary `data-unship-*` attributes from settled source.
+
+For final cleanup before shipping, remove all Unship artifacts and run:
+
+```bash
+npx -y @unship/cli@latest check --json
+```
+
+Do not claim cleanup is complete until the check reports clean.
+
+## Best Practices
+
+- Keep Unship work local and temporary.
+- Preserve the existing app design language unless the user explicitly asks for a different direction.
+- Avoid unrelated refactors while variants are temporary.
+- Do not put custom tabs, app preferences, or permanent switchers into product UI for Unship comparisons.
+- Keep inactive options safe: avoid duplicate active IDs, submit controls, global scripts, analytics triggers, focus traps, destructive side effects, and stateful providers.
+
+## Limitations
+
+- Unship does not decide which variant wins; the human chooses.
+- Unship does not replace design review, browser QA, accessibility checks, or production release validation.
+- Unship is not intended for production traffic, remote analytics, or persistent product experiments.
+
+## Security & Safety Notes
+
+- Run commands only in a local project the user has authorized you to modify.
+- Treat generated variants as temporary code that must be cleaned before release.
+- Before destructive cleanup, confirm the selected option label when the user's choice is ambiguous.
+- If a baseline build or typecheck already fails before Unship edits, report that baseline state and keep variant work isolated.
+
+## Common Pitfalls
+
+- **Problem:** Hidden variants override `hidden` with CSS.
+  **Solution:** Preserve `[hidden] { display: none !important; }` near variant-specific CSS when needed.
+
+- **Problem:** The user says "keep the second one" after more changes.
+  **Solution:** Confirm the exact group and option label before editing source.
+
+- **Problem:** The comparison grows into a broad redesign.
+  **Solution:** Reduce scope to the smallest section, state, or flow that can be judged in the running app.
+
+## Related Skills
+
+- `@webapp-testing` - Use for browser-based functional checks after frontend changes.
+- `@mobile-design` - Use when comparing mobile-specific UI patterns and platform constraints.

package/package.json

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

@@ -1439,6 +1439,28 @@
       "reasons": []
     }
   },
+  {
+    "id": "android-dev",
+    "path": "skills/android-dev",
+    "category": "mobile",
+    "name": "android-dev",
+    "description": "Production-grade Android app development guide covering native (Kotlin/Java), cross-platform (Flutter, RN, KMM), and hybrid architectures.",
+    "risk": "safe",
+    "source": "community",
+    "date_added": "2026-06-08",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    }
+  },
   {
     "id": "android-jetpack-compose-expert",
     "path": "skills/android-jetpack-compose-expert",
@@ -31248,6 +31270,28 @@
       "reasons": []
     }
   },
+  {
+    "id": "unship",
+    "path": "skills/unship",
+    "category": "development",
+    "name": "unship",
+    "description": "Compare AI agent-made UI variants locally in a real app, then keep one and clean up unused temporary code.",
+    "risk": "safe",
+    "source": "community",
+    "date_added": "2026-06-07",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    }
+  },
   {
     "id": "unslop",
     "path": "skills/unslop",