opencode-skills-collection 3.1.16 → 3.1.18

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

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "updatedAt": "2026-07-07T07:43:09.313Z",
+  "updatedAt": "2026-07-09T01:45:59.026Z",
   "entries": [
     "00-andruia-consultant",
     "007",
@@ -453,6 +453,7 @@
     "codebase-design",
     "codebase-to-wordpress-converter",
     "codex-fable5",
+    "codex-profiles",
     "codex-review",
     "codex-subagent",
     "cold-email",
@@ -880,6 +881,7 @@
     "global-chat-agent-discovery",
     "gmail-automation",
     "go-concurrency-patterns",
+    "go-in-depth",
     "go-playwright",
     "go-rod-master",
     "goal-analyzer",
@@ -1329,6 +1331,7 @@
     "php-pro",
     "pi-custom-model",
     "pi-web-search",
+    "pilot-protocol",
     "pipecat-friday-agent",
     "pipedrive-automation",
     "pitch-psychologist",
@@ -1361,6 +1364,7 @@
     "pr-merge-champion",
     "pr-writer",
     "pre-release-review",
+    "pre-ship-gate",
     "premium-3d-website",
     "price-psychology-strategist",
     "pricing",
@@ -1471,6 +1475,7 @@
     "robius-state-management",
     "robius-widget-patterns",
     "robot-framework-skill",
+    "routerbase-model-gateway",
     "ruby-pro",
     "run-deep-swe",
     "runapi-cli",
@@ -1764,6 +1769,7 @@
     "train-sentence-transformers",
     "transformers-js",
     "travel-health-analyzer",
+    "tree-ring-memory",
     "trello-automation",
     "triage",
     "trigger-dev",

package/bundled-skills/codex-profiles/SKILL.md

@@ -0,0 +1,170 @@
+---
+name: codex-profiles
+description: "Use codex-profiles to run Codex CLI or Codex Desktop with isolated CODEX_HOME profiles for separate accounts, projects, and local state."
+category: productivity
+risk: critical
+source: community
+source_repo: Ducksss/codex-profiles
+source_type: community
+date_added: "2026-07-08"
+author: Ducksss
+tags: [codex, codex-cli, profiles, code-home, account-isolation, desktop]
+tools: [codex]
+license: "MIT"
+license_source: "https://github.com/Ducksss/codex-profiles/blob/main/LICENSE"
+---
+
+# Codex Profiles
+
+## Overview
+
+Use `codex-profiles` when a user wants separate Codex CLI or Codex Desktop contexts for work, personal, school, client, or project-specific activity. The tool wraps Codex's `CODEX_HOME` support so each profile has its own Codex home directory for auth, config, sessions, connectors, plugins, caches, logs, and local state.
+
+This skill is for profile selection and operational safety around that boundary. It is not an official OpenAI project, and it does not provide full OS-level isolation.
+
+## When to Use This Skill
+
+- Use when the user wants to keep multiple Codex accounts or project contexts separate on one machine.
+- Use when a workflow needs a different `CODEX_HOME` without manually exporting environment variables.
+- Use when diagnosing which Codex profile is active or whether profiles are logged in.
+- Use when the user asks about Codex account switching without copying `auth.json`.
+- Use when launching Codex Desktop from a profile, only after confirming the user accepts app/process disruption.
+
+## How It Works
+
+### Step 1: Confirm Scope and Installation
+
+First check whether the user wants CLI-only profile switching or Codex Desktop profile launching. Desktop operations can quit, launch, clone, or rebuild app instances, so get explicit approval before running them.
+
+If the tool is already installed, inspect the live command surface:
+
+```bash
+codex-profile --help
+codex-profile doctor
+codex-profile list
+codex-profile status
+```
+
+If it is not installed, prefer package-manager installs the user can inspect and control:
+
+```bash
+npm install -g codex-profile
+brew install Ducksss/tap/codex-profile
+```
+
+Do not run remote install scripts automatically. If the user asks for a source install, clone the repository and inspect its install instructions first.
+
+### Step 2: Create or Select a Profile
+
+Create a new isolated Codex home only when the user names the intended profile:
+
+```bash
+codex-profile init work
+codex-profile path work
+```
+
+Ask the user to log in once per profile when needed:
+
+```bash
+codex-profile login work
+```
+
+Do not copy, parse, print, or migrate `auth.json` tokens between profiles.
+
+### Step 3: Run Codex CLI With a Profile
+
+Use the CLI profile wrapper for ordinary agent work:
+
+```bash
+codex-profile cli work
+codex-profile cli work exec "run tests and summarize failures"
+```
+
+For one-off shell sessions, prefer the tool's environment or shell activation commands after checking `--help`:
+
+```bash
+codex-profile env work
+codex-profile shell-init --help
+```
+
+### Step 4: Use Desktop Profile Commands Carefully
+
+Codex Desktop launch flows can affect running app state. Before running them, state which profile, app mode, and workspace will be used, then wait for approval.
+
+```bash
+codex-profile app work ~/Dev/project
+codex-profile app work --instance ~/Dev/project
+```
+
+Use `--instance` only when the user wants side-by-side Desktop profiles and accepts the additional local app clone and separate Electron user-data boundary.
+
+## Examples
+
+### Example 1: Read-Only Profile Audit
+
+```bash
+codex-profile list
+codex-profile status
+codex-profile doctor
+```
+
+Use this before changing profile state. It should not expose token contents.
+
+### Example 2: CLI Task in a Work Profile
+
+```bash
+codex-profile cli work exec "inspect this repository and run its test suite"
+```
+
+Confirm the profile name is intentional before running long tasks.
+
+### Example 3: Manual CODEX_HOME Equivalent
+
+If the wrapper is unavailable, explain the underlying boundary instead of improvising token movement:
+
+```bash
+CODEX_HOME="$HOME/.codex-work" codex
+CODEX_HOME="$HOME/.codex-work" codex exec "review this change"
+```
+
+## Best Practices
+
+- Keep profile names explicit and boring, such as `work`, `personal`, `client-a`, or `school`.
+- Use `status`, `list`, and `doctor` before destructive or Desktop actions.
+- Treat each profile as a separate local Codex home, not as a full sandbox.
+- Keep secrets inside the account/profile that owns them; do not copy auth files between profiles.
+- Prefer CLI profile commands for routine work and reserve Desktop app commands for user-approved context switches.
+- Verify behavior against the installed `codex-profile --help`, because command flags can change.
+
+## Limitations
+
+- `codex-profiles` is community-maintained and is not an official OpenAI tool.
+- It isolates Codex state through separate `CODEX_HOME` directories; it does not isolate the operating-system user, shell history, SSH keys, browser cookies, GitHub CLI auth, or unrelated application state.
+- Desktop profile launch behavior is macOS-focused and can change with Codex Desktop releases.
+- Existing Codex sessions may still contain project context from before a profile strategy was adopted.
+- The tool does not replace backups for important Codex state.
+
+## Security & Safety Notes
+
+- Never copy, print, parse, or migrate `auth.json` tokens as a shortcut.
+- Do not run Desktop launch, app clone, rebuild, remove, or profile deletion commands without explicit user approval.
+- Use `codex-profile remove` only after confirming the exact profile path and whether the user needs a backup.
+- Do not assume profile isolation protects credentials outside `CODEX_HOME`.
+- Avoid remote install scripts in automated agent runs; prefer inspectable package-manager or source-install steps.
+
+## Common Pitfalls
+
+- **Problem:** A user expects profile switching to isolate GitHub CLI, SSH, or browser state.
+  **Solution:** Explain that `codex-profiles` isolates Codex home state only; check and switch other tools separately.
+
+- **Problem:** A Desktop command disrupts an active session.
+  **Solution:** Ask before Desktop operations and prefer CLI commands when the user only needs isolated command-line work.
+
+- **Problem:** A profile exists but is logged out or missing connectors.
+  **Solution:** Run `codex-profile status` and have the user log in or configure connectors inside that profile.
+
+## Related Skills
+
+- `@environment-setup-guide` - Use when installing or documenting local development tools.
+- `@codex-maintenance` - Use when maintaining local Codex Desktop, MCP, plugin, or cache surfaces.
+- `@filesystem-context` - Use when reasoning about local files, config paths, and workspace boundaries.

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,929+ skills."
+description: "Use antigravity-awesome-skills with Jetski/Cortex without hitting context-window overflow with 1,935+ skills."
 ---
 
-# Jetski/Cortex + Gemini: safe integration with 1,929+ skills
+# Jetski/Cortex + Gemini: safe integration with 1,935+ 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 1,929+ skills, this approach fills the context window before user messages are even added, causing truncation.
+With 1,935+ 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

@@ -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,929+ skills installed.
+This pattern avoids context overflow when you have 1,935+ 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,929+ agentic skills for Claude Code, Cursor, Codex CLI, Gemini CLI, Antigravity, and other AI coding assistants.
+> Installable GitHub library of 1,935+ 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,929+ 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,935+ 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,929+ Agentic Skills`;
+- use a clean preview image that says `1,935+ 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,929+ skills from the skills directory
+- All 1,935+ 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,929+ | Total Bundles: 59_
+_Last updated: June 2026 | Total Skills: 1,935+ | 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,929+ skills instead of a narrow single-domain starter pack.
+- It includes 1,935+ 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,929+ files.
+- It helps new users get started with bundles and workflows rather than forcing a cold start from 1,935+ 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.12.0)
+# Getting Started with Antigravity Awesome Skills (V13.13.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,929+ specialized areas
+- **Domain expertise** across 1,935+ 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,929+ skill files** to your computer (default: `~/.agents/skills/`; or a custom path like `~/.agent/skills/` if you used `--path`)
+✅ **Downloaded 1,935+ 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,929+ tools (✅ done)
+- You installed a toolbox with 1,935+ 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,929+ skills at once. Here's a sensible approach:
+Don't try to use all 1,935+ 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,929+ skills installed locally, you should **not** concatenate every `SKILL.md` into a single system prompt or context block.
+No. Even though you have 1,935+ 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,929+ skills live here
+├── 📁 skills/                          ← 1,935+ skills live here
 │   │
 │   ├── 📁 brainstorming/
 │   │   └── 📄 SKILL.md                 ← Skill definition
@@ -47,7 +47,7 @@ antigravity-awesome-skills/
 │   │   └── 📁 2d-games/
 │   │       └── 📄 SKILL.md             ← Nested skills also supported
 │   │
-│   └── ... (1,929+ total)
+│   └── ... (1,935+ total)
 │
 ├── 📁 apps/
 │   └── 📁 web-app/                     ← Interactive browser
@@ -100,7 +100,7 @@ antigravity-awesome-skills/
 
 ```
                     ┌─────────────────────────┐
-                    │  1,929+ SKILLS          │
+                    │  1,935+ 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,929+ total)                │
+│   └── ... (1,935+ total)                │
 └─────────────────────────────────────────┘
 ```
 

package/bundled-skills/go-in-depth/SKILL.md

@@ -0,0 +1,59 @@
+---
+name: go-in-depth
+description: Go in depth harness — fan-out web searches, fetch sources, adversarially verify claims, synthesize a cited report.
+risk: safe
+source: self
+source_type: self
+date_added: "2026-07-07"
+---
+
+# Go In Depth
+
+## Overview
+
+Go in depth harness — fan-out web searches, fetch sources, adversarially verify claims, synthesize a cited report. Run the "go-in-depth" workflow.
+
+## When to Use
+
+When the user wants a deep, multi-source, fact-checked research report on any topic. BEFORE invoking, check if the question is specific enough to research directly — if underspecified (e.g., "what car to buy" without budget/use-case/region), ask 2-3 clarifying questions to narrow scope. Then pass the refined question as args, weaving the answers in.
+
+## How It Works
+
+Phases:
+- Scope: Decompose question (from args) into 5 search angles
+- Search: 5 parallel WebSearch agents, one per angle
+- Fetch: URL-dedup, fetch top 15 sources, extract falsifiable claims
+- Verify: 3-vote adversarial verification per claim (need 2/3 refutes to kill)
+- Synthesize: Merge semantic dupes, rank by confidence, cite sources
+
+## Examples
+
+### Example 1: Run go-in-depth workflow
+```
+Workflow({ name: "go-in-depth" })
+```
+
+### Example 2: Research with refined question
+```
+Workflow({ name: "go-in-depth", args: { query: "best hybrid cars under $30k in the US for families" } })
+```
+
+### Example 3: Deep dive into a technical concept
+```
+Workflow({ name: "go-in-depth", args: { query: "how does the transformer architecture handle positional encoding?" } })
+```
+
+### Example 4: Fact-checking a medical claim
+```
+Workflow({ name: "go-in-depth", args: { query: "efficacy of intermittent fasting for long-term weight loss in adults" } })
+```
+
+## Workflow Script
+
+[scripts/workflow-script.js](scripts/workflow-script.js)
+
+## Limitations
+
+- **Slow execution**: Multi-agent searches, fetching, and 3-vote verification take significant time. Not for quick facts.
+- **Context intensive**: Analyzing 15 full sources uses large context limits.
+- **Synthesis risks**: May struggle if source material is weak or equally conflicting.