opencode-skills-collection 3.0.27 → 3.0.28

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

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "updatedAt": "2026-05-26T01:59:07.090Z",
+  "updatedAt": "2026-05-27T02:07:52.841Z",
   "entries": [
     "00-andruia-consultant",
     "007",
@@ -572,6 +572,7 @@
     "fixing-accessibility",
     "fixing-metadata",
     "fixing-motion-performance",
+    "flowhunt-skill",
     "flutter-expert",
     "food-database-query",
     "form-cro",
@@ -623,6 +624,7 @@
     "gdpr-data-handling",
     "gemini-api-dev",
     "gemini-api-integration",
+    "geminiignore-finops",
     "geo-fundamentals",
     "geoffrey-hinton",
     "gh-review-requests",
@@ -716,6 +718,7 @@
     "idea-os",
     "identity-mirror",
     "idor-testing",
+    "ii-commons",
     "ilya-sutskever",
     "image-studio",
     "imagen",
@@ -863,6 +866,7 @@
     "mental-health-analyzer",
     "mercury-mcp",
     "mermaid-expert",
+    "mesh-memory",
     "metasploit-framework",
     "micro-saas-launcher",
     "microservices-patterns",
@@ -1238,6 +1242,7 @@
     "social-orchestrator",
     "social-post-writer-seo",
     "social-proof-architect",
+    "socialclaw",
     "software-architecture",
     "solidity-security",
     "spark-optimization",

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

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

@@ -0,0 +1,141 @@
+---
+name: flowhunt-skill
+description: "Automation discovery audit skill. Walks through a 5-question workflow intake, then audits Gmail/Calendar/Slack/task trackers to identify automation opportunities. Use when a user wants to discover what processes in their business can be automated."
+category: automation
+risk: safe
+source: community
+source_repo: heyneuron/flowhunt-skill
+source_type: community
+date_added: "2026-05-23"
+author: heyneuron
+tags: [automation, discovery, audit, gmail, calendar, slack, productivity, workflow]
+tools: [claude, codex, gemini, cursor]
+license: "MIT"
+license_source: "https://github.com/heyneuron/flowhunt-skill/blob/main/LICENSE"
+---
+
+# FlowHunt Skill — Automation Discovery Audit
+
+## Overview
+
+FlowHunt is an automation discovery audit skill. It guides agents through a structured 5-question intake to understand the user's business context, then systematically audits connected tools (Gmail, Google Calendar, Slack, task trackers, and more) to surface concrete automation opportunities ranked by impact and effort.
+
+The skill is cross-agent: it works with Claude Code, Codex CLI, Gemini CLI, OpenCode, and any agent that accepts markdown skill files.
+
+Install: `npx skills add heyneuron/flowhunt-skill`
+
+## When to Use This Skill
+
+- Use when the user asks "what can I automate in my business?"
+- Use when the user wants a workflow audit across Gmail, Calendar, Slack, or task tools
+- Use when starting an automation engagement and need structured discovery before recommending solutions
+- Use when the user says "show me automation opportunities" or "FlowHunt"
+
+## How It Works
+
+### Step 1: Intake — 5-Question Workflow Questionnaire
+
+Ask the user exactly these five questions, one at a time:
+
+1. **Role & team size** — What is your role, and how many people are on your team?
+2. **Top 3 repetitive tasks** — What are the three most repetitive tasks you or your team do every week?
+3. **Connected tools** — Which tools do you actively use? (Gmail, Google Calendar, Slack, Notion, Jira, Asana, HubSpot, etc.)
+4. **Pain point** — Which of those repetitive tasks costs you the most time or causes the most errors?
+5. **Automation goal** — Are you looking to save time, reduce errors, or hand off tasks entirely?
+
+Wait for answers before moving to the audit.
+
+### Step 2: Audit — Scan Connected Tools
+
+For each tool the user mentioned, surface automation patterns:
+
+**Gmail**
+- Auto-labeling and routing rules
+- Draft generation for recurring email types
+- Invoice / attachment extraction to Drive or Notion
+- Follow-up reminders when no reply received
+
+**Google Calendar**
+- Meeting prep summaries (agenda + attendee context) sent automatically
+- Booking link workflows with intake forms
+- Post-meeting action item extraction
+
+**Slack**
+- Daily standup collection → summary to channel or doc
+- Keyword alerts routed to the right person
+- Approval workflows with emoji reactions
+
+**Task trackers (Asana, Jira, Notion, Linear)**
+- Auto-create tasks from emails or Slack messages
+- Status update reminders
+- Weekly digest of overdue or blocked items
+
+**CRMs (HubSpot, Salesforce, Pipedrive)**
+- Lead scoring and routing rules
+- Follow-up sequences triggered by deal stage change
+- Contact enrichment on new lead creation
+
+### Step 3: Prioritization Matrix
+
+Rank each identified opportunity on a 2x2:
+
+| | Low effort | High effort |
+|---|---|---|
+| **High impact** | Do first (quick wins) | Plan carefully |
+| **Low impact** | Nice to have | Skip for now |
+
+Present the top 3 quick-win automations with:
+- What it does
+- Which tools it connects
+- Estimated time saved per week
+- Suggested implementation path (Zapier / Make / n8n / custom code)
+
+### Step 4: Output
+
+Deliver a structured Automation Opportunity Report in markdown:
+
+```
+# Automation Opportunity Report
+
+## Business Context
+[Summary from intake]
+
+## Top 3 Quick Wins
+1. [Name] — [What it does] — [Tools] — [~X hrs/week saved]
+2. ...
+3. ...
+
+## Full Opportunity List
+[All identified automations, ranked]
+
+## Recommended Next Step
+[Single clearest action the user can take today]
+```
+
+## Common Rationalizations to Reject
+
+| Excuse | Why it's wrong |
+|--------|----------------|
+| "I'll skip the intake and guess their stack" | Intake prevents wasted recommendations on tools they don't use |
+| "I'll list every possible automation" | Overwhelming output kills adoption — prioritize ruthlessly |
+| "I'll recommend complex custom code first" | Start with no-code/low-code quick wins; earn the right to build |
+
+## Red Flags
+
+- User has no clear repetitive task → dig deeper, they always exist
+- Recommending automations for tools the user didn't mention → stay scoped
+- Skipping the prioritization matrix → every opportunity looks equal without it
+
+## Limitations
+
+- This skill identifies and prioritizes automation opportunities; it does not implement the automations for the user.
+- Tool audits depend on the user's stated stack and any explicitly connected data sources; do not assume access to Gmail, Calendar, Slack, CRMs, or task trackers.
+- Time-saved estimates are directional planning aids, not guaranteed outcomes.
+
+## Verification
+
+The skill is complete when the user has:
+- [ ] Answered all 5 intake questions
+- [ ] Received a ranked list of automation opportunities
+- [ ] Identified at least one quick-win automation they can start this week
+- [ ] A clear recommended next step

package/bundled-skills/geminiignore-finops/SKILL.md

@@ -0,0 +1,173 @@
+---
+name: geminiignore-finops
+description: "Configure and optimize .geminiignore files for AI context window efficiency and token cost reduction (FinOps)."
+category: context-optimization
+risk: safe
+source: community
+source_repo: iradoweck/antigravity-awesome-skills
+source_type: community
+date_added: "2026-05-25"
+author: iradoweck
+tags: [finops, context-management, token-optimization, geminiignore]
+tools: [gemini, claude, cursor]
+license: "MIT"
+license_source: "https://github.com/iradoweck/antigravity-awesome-skills/blob/main/LICENSE"
+---
+
+# GeminiIgnore FinOps Setup & Optimization
+
+## Overview
+
+A skill to construct, refine, and maintain high-performance `.geminiignore` files across diverse tech stacks. By filtering out machine-generated code, heavy logs, package locks, and binary assets, this skill optimizes the AI agent's context window, accelerates processing speed, and reduces token consumption costs (FinOps).
+
+## When to Use This Skill
+
+- Use when initializing a new repository or workspace for pair-programming with AI agents.
+- Use when the AI context window is reaching its limits or when billing optimization (FinOps) is a priority.
+- Use when the AI agent is accidentally reading build outputs, lock files, databases, or binary media.
+
+## How It Works
+
+### Step 1: Analyze the Workspace Tech Stack
+Detect the languages, frameworks, and dependency managers present in the project (e.g., Node.js, Python, PHP, Dart/Flutter, Rust).
+
+### Step 2: Initialize or Update the `.geminiignore` File
+Create a `.geminiignore` file at the root of the active workspace. If one already exists, review it to add missing categories.
+
+### Step 3: Implement the 7 Core Rules
+Add rules divided into the following categories to filter out unnecessary machine noise while keeping human-written code visible:
+
+1. **System & Editor Noise**: Block OS temp files (`.DS_Store`, `Thumbs.db`) and user-specific IDE caches (`.idea/`, `.vscode/*`, Xcode user data).
+2. **Dependency Folders & Lock Files**: Ignore third-party package directories (`node_modules/`, `vendor/`) and giant machine-generated lock files (`package-lock.json`, `yarn.lock`, `Cargo.lock`, `composer.lock`).
+3. **Build & Target Output**: Block compiled folders (`dist/`, `build/`, `.next/`, `.nuxt/`).
+4. **Caches & Tool Metadata**: Block compiler caches (`.tsbuildinfo`, `.vite/`, `.pytest_cache/`, `.eslintcache`).
+5. **Binary & Rich Assets**: Block media types (`*.png`, `*.pdf`, `*.mp4`, `*.woff2`) to prevent triggering expensive vision/multimodal tokens.
+6. **Local Databases & Logs**: Block log files (`*.log`) and SQL dumps or local SQLite DBs (`*.sqlite`, `*.db`).
+7. **Compiled Binaries & Mobile Builds**: Block mobile package files (`*.apk`, `*.ipa`) and compiled binaries (`*.class`, `*.pyc`, `*.dll`).
+
+### Step 4: Validate Exclusions
+Verify that the AI can still see critical configuration blueprints (like `.env.example`, `package.json`, `composer.json`, `pyproject.toml`) but ignores the actual `.env` files and compilation artifacts.
+
+## Examples
+
+### Example 1: Standard Universal `.geminiignore` Template
+
+Here is a recommended baseline configuration for a multi-language project:
+
+```ini
+# ==============================================================================
+# .geminiignore - BASELINE DE FINOPS E ARQUITETURA
+# ==============================================================================
+
+# 1. SISTEMA OPERACIONAL E IDEs
+.DS_Store
+Thumbs.db
+Desktop.ini
+$RECYCLE.BIN/
+.vscode/*
+!.vscode/settings.json
+!.vscode/tasks.json
+!.vscode/launch.json
+.idea/
+*.iml
+.gradle/
+local.properties
+.history/
+
+# 2. DEPENDÊNCIAS (ECONOMIA DE TOKENS EM LOCK FILES)
+node_modules/
+package-lock.json
+yarn.lock
+pnpm-lock.yaml
+vendor/
+composer.lock
+venv/
+.venv/
+env/
+.env
+.env.*
+!.env.example
+poetry.lock
+Cargo.lock
+pubspec.lock
+
+# 3. BUILDS E EXPORTAÇÕES
+dist/
+build/
+out/
+target/
+.next/
+.nuxt/
+.output/
+bin/
+obj/
+
+# 4. CACHES DE FRAMEWORKS
+.vite/
+.parcel-cache/
+.eslintcache
+.babel-cache/
+.tsbuildinfo
+.turbo/
+.pytest_cache/
+.ruff_cache/
+storage/framework/
+storage/logs/
+
+# 5. ASSETS BINÁRIOS E MULTIMÍDIA EXTREMOS
+*.png
+*.jpg
+*.jpeg
+*.gif
+*.webp
+*.svg
+*.ico
+*.psd
+*.fig
+*.pdf
+*.zip
+*.tar.gz
+*.woff
+*.woff2
+*.ttf
+
+# 6. BANCOS DE DADOS E LOGS
+*.log
+*.db
+*.sqlite
+*.sqlite3
+*.sql
+*.sql.gz
+
+# 7. ARQUIVOS COMPILADOS
+*.apk
+*.aab
+*.ipa
+*.jar
+*.class
+*.pyc
+__pycache__/
+*.so
+*.dylib
+*.dll
+*.exe
+*.js.map
+*.css.map
+```
+
+## Best Practices
+
+- ✅ **Ignore dependency lock files**: Standard lock files (e.g., `package-lock.json`, `yarn.lock`) contain thousands of lines of redundant package resolution trees. Ignoring them is the single largest FinOps win.
+- ✅ **Keep configurations visible**: Ensure manifests like `package.json`, `composer.json`, `Cargo.toml`, and `pyproject.toml` are NEVER ignored, as the AI needs them to understand dependencies.
+- ✅ **Whitelist config examples**: Use rules like `!.env.example` alongside `.env` ignores so the AI understands configuration structure without exposing credentials.
+- ❌ **Do not ignore source code**: Avoid overly broad folder patterns like `lib/` or `app/` if they contain primary source code. Be specific (e.g., block `vendor/bundle/` but not your actual code).
+
+## Limitations
+
+- A `.geminiignore` file only affects AI tools parsing the workspace; it does not replace `.gitignore` for Git repository hosting.
+- Patterns must be formatted correctly according to gitignore-style globbing to avoid accidentally ignoring source files.
+
+## Related Skills
+
+- `@context-optimization` - Broad tactics for context window management.
+- `@clean-code` - Architectural practices for clean, human-readable codebases.

package/bundled-skills/ii-commons/SKILL.md

@@ -0,0 +1,110 @@
+---
+name: ii-commons
+description: "Deterministic search across arXiv, PubMed/PMC, and US policy corpora with daily freshness cutoffs."
+category: research
+risk: safe
+source: community
+source_repo: Intelligent-Internet/II-Commons-Skills
+source_type: community
+date_added: "2026-05-26"
+author: Intelligent Internet
+tags: [research, arxiv, pubmed, pmc, policy, retrieval, cli, codex]
+tools: [claude, cursor, gemini, codex, antigravity]
+license: "Apache-2.0"
+license_source: "https://github.com/Intelligent-Internet/II-Commons-Skills/blob/main/LICENSE"
+---
+
+# II-Commons
+
+## Overview
+
+II-Commons provides deterministic retrieval for research agents across arXiv, PubMed/PMC, and supported US policy corpora. Use it when a task needs reproducible search, metadata lookup, full-document Markdown retrieval, or a freshness check before answering with recent evidence.
+
+The upstream project publishes a Node.js CLI as `@intelligentinternet/ii-commons` and a full agent skill at `skills/ii-commons/`.
+
+## When to Use This Skill
+
+- Use when searching arXiv, PubMed/PMC, or supported US policy corpora for evidence.
+- Use when the user asks for latest or recent research and corpus freshness matters.
+- Use when you need stable identifiers, metadata, or full-document Markdown for downstream analysis.
+- Use when comparing evidence across scientific literature and policy documents.
+
+## How It Works
+
+### Step 1: Check Corpus Freshness
+
+Run `cutoff` before freshness-sensitive searches:
+
+```bash
+npx @intelligentinternet/ii-commons cutoff
+```
+
+Report the relevant cutoff date before interpreting recent results.
+
+### Step 2: Search the Right Corpus
+
+Use exactly this command shape:
+
+```bash
+npx @intelligentinternet/ii-commons search arxiv "large language model inference" --max-results 10
+npx @intelligentinternet/ii-commons search pubmed "type 2 diabetes review" --start 20240000 --max-results 10
+npx @intelligentinternet/ii-commons search policy "state overtime rule for agricultural workers" --jurisdictions US-CA --max-results 10
+```
+
+Choose `arxiv` for preprints and technical research, `pubmed` for biomedical and clinical literature, and `policy` for supported US policy corpora.
+
+### Step 3: Retrieve Metadata or Markdown
+
+Use stable identifiers from search results:
+
+```bash
+npx @intelligentinternet/ii-commons meta "arXiv:2402.03578"
+npx @intelligentinternet/ii-commons markdown "PMCID:PMC11152602"
+```
+
+Build summaries from search results first, then request Markdown when detailed inspection or full-document grounding is needed.
+
+## Installation
+
+Run the CLI with `npx`:
+
+```bash
+npx @intelligentinternet/ii-commons --help
+```
+
+Or install globally:
+
+```bash
+npm install -g @intelligentinternet/ii-commons
+ii-commons cutoff
+```
+
+To install the full upstream agent skill, install the `skills/ii-commons/` folder from:
+
+```text
+https://github.com/Intelligent-Internet/II-Commons-Skills
+```
+
+## Best Practices
+
+- Prefer server-side date filters such as `--start` and `--end` for time-bounded arXiv and PubMed searches.
+- Preserve canonical identifiers such as `arXiv:<id>`, `PMID:<id>`, `PMCID:PMC<id>`, and `policy:<jurisdiction>:<id>`.
+- Use `cutoff` as the authoritative freshness boundary for each corpus.
+- Keep non-time filters conservative until initial search results show the right scope.
+
+## Limitations
+
+- Requires Node.js 18 or newer and outbound network access to `commons.ii.inc`.
+- Basic usage works without authentication; higher usage limits may require an API token from `https://commons.ii.inc/`.
+- Supported policy coverage is limited to the policy corpora exposed by II-Commons.
+
+## Security & Safety Notes
+
+- Do not print or expose `II_COMMONS_API_KEY` values.
+- Treat outputs as retrieval evidence, not expert review. For medical, legal, or policy-sensitive work, cite sources and preserve uncertainty.
+- Commands call an external API service; confirm network access is allowed in the user's environment before running them.
+
+## Related Skills
+
+- Use broader web-search or deep-research skills when evidence is outside arXiv, PubMed/PMC, or supported policy corpora.
+- Use citation-management skills after II-Commons has identified stable source records.

package/bundled-skills/mesh-memory/SKILL.md

@@ -0,0 +1,161 @@
+---
+name: mesh-memory
+description: "Self-hosted semantic memory for AI agents via MCP. Save worklogs, decisions, and notes, then recall them across sessions by meaning, not keyword. Postgres + pgvector with auto-tagging."
+risk: safe
+source: dklymentiev/mesh-memory (MIT)
+date_added: "2026-05-23"
+---
+
+# Mesh Memory
+
+Mesh Memory is a self-hosted semantic memory service with a built-in MCP server. It stores documents (worklogs, decisions, notes, research) in PostgreSQL with pgvector and retrieves them by meaning, so a query like "what database did we pick?" surfaces a saved note that says "chose Redis for caching" even with zero keyword overlap. Embeddings are generated locally with `multilingual-e5-base` (768 dimensions); the core flow requires no external API keys.
+
+Use this skill when an agent needs persistent memory across sessions: saving its own work, recalling prior decisions, or building a project knowledge base shared between multiple agents.
+
+## When to Use This Skill
+
+- Saving a session worklog, decision, or research note so a later session can find it.
+- Recalling past work by topic when you do not remember the exact words you used.
+- Sharing a long-lived knowledge base across multiple agents, terminals, or teammates.
+- Organizing context by role or project through workspaces (one workspace per role/project).
+- Looking up structured tags (e.g. all `type:decision` entries from one project).
+
+## Prerequisites
+
+- A running Mesh Memory instance reachable from the MCP server. Local Docker is the common path -- `docker compose up -d` in the upstream repo brings it up; see https://github.com/dklymentiev/mesh-memory for the full Quick Start.
+- The MCP server (`mcp_server.py`) registered with your client (Claude Code, Cursor, Claude Desktop, or any other MCP-aware agent).
+- `MESH_API_URL` pointing at the running instance (default: `http://localhost:8000`).
+
+## Setup
+
+Register the MCP server in your client configuration:
+
+```json
+{
+  "mcpServers": {
+    "mesh": {
+      "command": "python3",
+      "args": ["/path/to/mesh-memory/mcp_server.py"],
+      "env": {
+        "MESH_API_URL": "http://localhost:8000"
+      }
+    }
+  }
+}
+```
+
+When the server is reachable, the 13 tools listed below become available.
+
+## MCP Tools
+
+| Tool | Purpose |
+|------|---------|
+| `mesh_focus` | Switch the active workspace (optionally prefetch recent docs). |
+| `mesh_add` | Save a document with optional tags. Auto-adds `date:YYYY-MM-DD` and `source:`. |
+| `mesh_update` | Update content, tags, or pinned status of an existing document. |
+| `mesh_delete` | Delete a document by GUID. |
+| `mesh_get` | Fetch a single document by GUID. |
+| `mesh_search` | Semantic search by query, optionally across multiple workspaces with weights. |
+| `mesh_bytag` | List documents that match one or more tags (AND logic). |
+| `mesh_recent` | List most recently created documents, optionally filtered by `type:` tag. |
+| `mesh_projects` | List per-project document counts (uses `guid:` tag as project marker). |
+| `mesh_tags` | List existing tags with counts; optional prefix filter. |
+| `mesh_versions` | Show the version chain of a document (similarity-linked revisions). |
+| `mesh_stats` | Memory statistics for the active workspace. |
+| `mesh_schema` | Show the tag schema (recognized prefixes and types). |
+
+## Workflows
+
+### Save a session worklog
+
+After completing work, persist it for future sessions:
+
+```
+mesh_add(
+  content="Investigated 502s on the checkout flow. Root cause: missing CORS header on the cart API. Fix shipped in commit abc123.",
+  tags="type:worklog,topic:checkout,date:2026-05-23",
+  workspace="developer"
+)
+```
+
+`date:` and `source:` are added automatically when omitted. Type and topic tags are inferred from nearest neighbors after the embedding completes (5-10 seed documents required before inference kicks in).
+
+### Recall past work by meaning
+
+Search across sessions for related context, even with different vocabulary:
+
+```
+mesh_search(query="checkout was failing for some users", limit=5, workspace="developer")
+```
+
+The query shares no keywords with the original note ("502s", "CORS"), but the embedding-based search surfaces it.
+
+### Switch role / context
+
+For a multi-role agent, switch the active workspace at the start of a session:
+
+```
+mesh_focus(workspace="sysadmin", prefetch=true, limit=5)
+```
+
+Subsequent calls default to that workspace. Pin a role-prompt document at the top of each workspace so the agent re-orients on every prefetch.
+
+### Cross-workspace search with weights
+
+To pull context from related domains without diluting the primary signal:
+
+```
+mesh_search(
+  query="nginx rate limit recipe",
+  workspaces={"sysadmin": 0.7, "security": 0.2, "developer": 0.1},
+  limit=10
+)
+```
+
+Results are merged across workspaces and re-scored by workspace weight.
+
+### Structured lookups by tag
+
+When you need an exact filter rather than semantic similarity:
+
+```
+mesh_bytag(tags="type:decision,status:active,guid:my-project", limit=20)
+```
+
+## Tag Conventions
+
+Mesh accepts arbitrary tags. The recommended prefixes (used by auto-inference and surfaced by `mesh_schema`):
+
+| Prefix | Meaning |
+|--------|---------|
+| `type:worklog` | Completed work; the most common type. |
+| `type:note` | Quick notes, observations. |
+| `type:decision` | Architecture or product decisions. |
+| `type:research` | Investigation results, findings. |
+| `type:task` | Action items. |
+| `type:rfc` | Proposals for review. |
+| `status:active` / `status:completed` / `status:archived` | Lifecycle. |
+| `date:YYYY-MM-DD` | When the document was created (auto-added). |
+| `source:` | How the document arrived (auto-added: `mcp`, `api`, etc.). |
+| `guid:<project-id>` | Project marker -- use a consistent slug across all docs of a project. |
+
+With fewer than ~5-10 documents in a workspace, neighbor inference is skipped; manually tag seed documents until the corpus self-organizes.
+
+## Troubleshooting
+
+**Tool calls fail with connection errors.** The MCP server cannot reach `MESH_API_URL`. Verify the instance is up (`curl $MESH_API_URL/health` returns `{"status":"healthy"}`) and the env var is set in the MCP config.
+
+**A saved document does not appear in semantic search yet.** Embedding generation runs in the background. After a save, expect a 1-2 second delay before semantic search hits the new document. `mesh_get(guid=...)` confirms the document exists immediately.
+
+**Search returns results from the wrong domain.** The active workspace is not what you expected. Call `mesh_focus(workspace="<name>")` explicitly, or pass `workspace=` on every call. With no focus and no explicit param, calls land in the `default` workspace.
+
+**Auto-tagging never adds anything.** The workspace has too few documents for neighbor inference (~5-10 minimum). Manually tag a handful of seed documents, then auto-inference takes over.
+
+**A deleted document still appears in a search result.** Embedding indices are eventually consistent; rerun the search after a few seconds, or use `mesh_get(guid=...)` to confirm deletion.
+
+## Limitations
+
+- Mesh is a knowledge store, not a chat memory. Long conversation transcripts should be summarized before being saved.
+- Vector similarity is robust but not perfect; for high-precision structured lookups, prefer `mesh_bytag` over `mesh_search`.
+- Embeddings run on CPU by default; very large corpora (hundreds of thousands of documents) benefit from a dedicated instance and pgvector tuning, not covered here.
+- The optional AI categorizer requires an OpenAI-compatible LLM endpoint and is disabled by default.

package/bundled-skills/socialclaw/SKILL.md

@@ -0,0 +1,107 @@
+---
+name: socialclaw
+description: "Agent-first social media publishing skill — schedule and publish posts across 13 platforms (X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, Pinterest) via a single workspace API key."
+category: marketing
+risk: safe
+source: community
+source_repo: ndesv21/socialclaw
+source_type: community
+date_added: "2026-05-25"
+author: ndesv21
+tags: [social-media, publishing, scheduling, marketing, twitter, linkedin, instagram, tiktok, discord, telegram, reddit, wordpress, pinterest]
+tools: [claude]
+license: "MIT"
+license_source: "https://github.com/ndesv21/socialclaw/blob/main/LICENSE"
+---
+
+# SocialClaw — Social Media Publisher
+
+## Overview
+
+SocialClaw is an agent-first social media publishing skill that lets you schedule and publish posts across 13 platforms using a single workspace API key. No per-platform OAuth setup required — one key covers everything.
+
+## When to Use
+
+- Use when the user wants to plan, schedule, or publish a social media campaign across multiple platforms.
+- Use when the user has a SocialClaw workspace API key and wants one workflow for X, LinkedIn, Instagram, Facebook, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, or Pinterest.
+- Use when the user asks for social publishing automation that can validate schedules, attach media, and retrieve post performance metrics.
+
+## Supported Platforms
+
+- X (Twitter)
+- LinkedIn (Profile + Page)
+- Instagram (Business + Standalone)
+- Facebook Pages
+- TikTok
+- Discord
+- Telegram
+- YouTube
+- Reddit
+- WordPress
+- Pinterest
+
+## Installation
+
+```bash
+npx skills add ndesv21/socialclaw
+```
+
+Or install the npm package directly:
+
+```bash
+npm install socialclaw@0.1.12
+```
+
+## Configuration
+
+Set your workspace API key:
+
+```bash
+export SOCIALCLAW_API_KEY=your_workspace_api_key
+```
+
+Get your API key at [getsocialclaw.com](https://getsocialclaw.com).
+
+## Workflow
+
+### Step 1: Create a Campaign
+
+Define your campaign with target platforms, content, and schedule.
+
+### Step 2: Upload Media (Optional)
+
+Upload images or videos to attach to posts.
+
+### Step 3: Validate Schedule
+
+Confirm platform-specific timing rules are met (e.g., rate limits, posting windows).
+
+### Step 4: Publish or Schedule
+
+Publish immediately or schedule for a future time across all selected platforms simultaneously.
+
+### Step 5: Analytics
+
+Retrieve post performance metrics after publishing.
+
+## Example Usage
+
+```
+/social-publishing
+
+Create a campaign for our product launch:
+- Platforms: X, LinkedIn, Instagram
+- Message: "Excited to announce our new feature! Check it out at example.com #launch #product"
+- Schedule: Tomorrow at 9am PST
+```
+
+## Source
+
+GitHub: [ndesv21/socialclaw](https://github.com/ndesv21/socialclaw)
+Website: [getsocialclaw.com](https://getsocialclaw.com)
+
+## Limitations
+
+- Requires a valid SocialClaw workspace API key; do not attempt publishing without explicit user-provided credentials.
+- Platform availability, rate limits, analytics fields, and scheduling behavior depend on the upstream SocialClaw service.
+- This skill describes the publishing workflow; it does not replace platform-specific compliance, brand review, or legal approval before posting.

package/package.json

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

@@ -12725,6 +12725,28 @@
       "reasons": []
     }
   },
+  {
+    "id": "flowhunt-skill",
+    "path": "skills/flowhunt-skill",
+    "category": "automation",
+    "name": "flowhunt-skill",
+    "description": "Automation discovery audit skill. Walks through a 5-question workflow intake, then audits Gmail/Calendar/Slack/task trackers to identify automation opportunities. Use when a user wants to discover what processes in their business can be automated.",
+    "risk": "safe",
+    "source": "community",
+    "date_added": "2026-05-23",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    }
+  },
   {
     "id": "flutter-expert",
     "path": "skills/flutter-expert",
@@ -13693,6 +13715,28 @@
       "reasons": []
     }
   },
+  {
+    "id": "geminiignore-finops",
+    "path": "skills/geminiignore-finops",
+    "category": "context-optimization",
+    "name": "geminiignore-finops",
+    "description": "Configure and optimize .geminiignore files for AI context window efficiency and token cost reduction (FinOps).",
+    "risk": "safe",
+    "source": "community",
+    "date_added": "2026-05-25",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    }
+  },
   {
     "id": "geo-fundamentals",
     "path": "skills/geo-fundamentals",
@@ -15741,6 +15785,28 @@
       "reasons": []
     }
   },
+  {
+    "id": "ii-commons",
+    "path": "skills/ii-commons",
+    "category": "research",
+    "name": "ii-commons",
+    "description": "Deterministic search across arXiv, PubMed/PMC, and US policy corpora with daily freshness cutoffs.",
+    "risk": "safe",
+    "source": "community",
+    "date_added": "2026-05-26",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    }
+  },
   {
     "id": "ilya-sutskever",
     "path": "skills/ilya-sutskever",
@@ -18897,6 +18963,28 @@
       "reasons": []
     }
   },
+  {
+    "id": "mesh-memory",
+    "path": "skills/mesh-memory",
+    "category": "ai-ml",
+    "name": "mesh-memory",
+    "description": "Self-hosted semantic memory for AI agents via MCP. Save worklogs, decisions, and notes, then recall them across sessions by meaning, not keyword. Postgres + pgvector with auto-tagging.",
+    "risk": "safe",
+    "source": "dklymentiev/mesh-memory (MIT)",
+    "date_added": "2026-05-23",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    }
+  },
   {
     "id": "metasploit-framework",
     "path": "skills/metasploit-framework",
@@ -27148,6 +27236,28 @@
       "reasons": []
     }
   },
+  {
+    "id": "socialclaw",
+    "path": "skills/socialclaw",
+    "category": "marketing",
+    "name": "socialclaw",
+    "description": "Agent-first social media publishing skill \u2014 schedule and publish posts across 13 platforms (X, LinkedIn, Instagram, Facebook Pages, TikTok, Discord, Telegram, YouTube, Reddit, WordPress, Pinterest) via a single workspace API key.",
+    "risk": "safe",
+    "source": "community",
+    "date_added": "2026-05-25",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    }
+  },
   {
     "id": "software-architecture",
     "path": "skills/software-architecture",