opencode-skills-collection 2.0.254 → 2.0.256

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

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "updatedAt": "2026-04-26T11:40:27.710Z",
+  "updatedAt": "2026-04-26T14:45:21.449Z",
   "entries": [
     "00-andruia-consultant",
     "007",
@@ -1345,6 +1345,7 @@
     "unity-developer",
     "unity-ecs-patterns",
     "unreal-engine-cpp-pro",
+    "unslop",
     "unsplash-integration",
     "upgrading-expo",
     "upstash-qstash",

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

package/bundled-skills/loki-mode/examples/todo-app-generated/frontend/package-lock.json

@@ -1540,9 +1540,9 @@
       }
     },
     "node_modules/postcss": {
-      "version": "8.5.6",
-      "resolved": "https://registry.npmjs.org/postcss/-/postcss-8.5.6.tgz",
-      "integrity": "sha512-3Ybi1tAuwAP9s0r1UQ2J4n5Y0G05bJkpUIO0/bI9MhwmD70S5aTWbXGBwxHrelT+XM1k6dM0pk+SwNkpTRN7Pg==",
+      "version": "8.5.12",
+      "resolved": "https://registry.npmjs.org/postcss/-/postcss-8.5.12.tgz",
+      "integrity": "sha512-W62t/Se6rA0Az3DfCL0AqJwXuKwBeYg6nOaIgzP+xZ7N5BFCI7DYi1qs6ygUYT6rvfi6t9k65UMLJC+PHZpDAA==",
       "dev": true,
       "funding": [
         {

package/bundled-skills/social-post-writer-seo/SKILL.md

@@ -4,19 +4,37 @@ description: "Social Media Strategist and Content Writer. Creates clear, engagin
 category: growth
 risk: safe
 source: self
+source_type: self
 date_added: "2026-04-17"
 author: WHOISABHISHEKADHIKARI
+tags: [social-media, marketing, content-writing, seo, growth]
+tools: [claude, cursor, gemini]
+version: 1.0.1
 ---
 
 # Social Media Strategist and Content Writer
 
+## Overview
+This skill is designed to help users create high-quality, engaging, and platform-optimized social media content. It focuses on clarity, readability, and platform-specific nuances for Instagram, LinkedIn, and Facebook.
+
 ## When to Use This Skill
 - Use this skill when you need a clear, engaging, and accurate social media post for Instagram, LinkedIn, or Facebook.
 - Use it to transform topics and keywords into audience-focused content with platform-native structure.
 
-Your task is to create a clear, engaging, and accurate social media post that works for a global audience on platforms like Instagram, LinkedIn, and Facebook.
+## How It Works
 
----
+### Step 1: Input Gathering
+The skill starts by collecting essential details like the topic, primary keyword, target audience, and the specific social media platform.
+
+### Step 2: Content Generation
+Based on the inputs, it follows strict writing rules to ensure simplicity, factual accuracy, and engagement. It structures the post with a hook, context, value, and a call to action.
+
+### Step 3: Platform Optimization
+The output is tailored for the selected platform, adjusting emoji density and tone (e.g., more professional for LinkedIn, more visual/casual for Instagram).
+
+## Prompt Template
+
+Your task is to create a clear, engaging, and accurate social media post that works for a global audience on platforms like Instagram, LinkedIn, and Facebook.
 
 ### INPUT:
 - **Topic**: {Insert Topic}
@@ -51,8 +69,6 @@ Create a post that is easy to understand, useful, and encourages engagement.
 4. **Call to Action**: Check the comment section or follow.
 5. **Hashtags**: 5-8 relevant tags.
 
----
-
 ## Examples
 
 ### Example: New Product Launch
@@ -64,15 +80,35 @@ Create a post that is easy to understand, useful, and encourages engagement.
 
 **Output**:
 ☕️ Your morning coffee just got a clean energy upgrade! 
-Did you know commuters throw away billions of cups annually? 
-The SolMug keeps your brew hot using only sunlight. 
-A small change for your bag, a big win for the planet. 
+Meet SolMug, a solar powered coffee mug concept for busy commutes.
+It is designed to keep your drink warm without adding another charger to your bag.
+A small change for your morning routine, with sustainability in mind.
 Check the link in bio to pre-order! 
 #ecofriendly #coffee #sustainability #tech #morningroutine
 
----
+## Best Practices
+- ✅ Always include a "Hook" in the first line to capture attention.
+- ✅ Use line breaks frequently to make the post scannable on mobile.
+- ✅ Tailor the tone: LinkedIn should be more professional, Instagram more visual/energetic.
+- ❌ Avoid using more than 10 hashtags; it can look like spam.
+- ❌ Never guess facts; if info isn't provided, stick to general industry knowledge.
 
 ## Limitations
 - This skill does not generate image or video assets.
 - It requires manual copy-pasting to the respective social media platforms.
 - It cannot schedule or post content directly to social media accounts.
+
+## Security & Safety Notes
+- This skill only generates text content and does not interact with system APIs or run shell commands.
+- Ensure any links included in the generated content are verified by the user before posting.
+
+## Common Pitfalls
+- **Problem:** Post feels too "salesy".
+  **Solution:** Focus more on the "Value/Insight" section to provide helpful info before the CTA.
+- **Problem:** Low engagement on LinkedIn.
+  **Solution:** Reduce emoji count and ensure the "Hook" addresses a professional pain point.
+
+## Related Skills
+- `@copywriting` - For longer form sales copy and landing pages.
+- `@seo-content` - For blog-style SEO content optimization.
+- `@ad-creative` - Specifically for paid social media advertisements.

package/bundled-skills/unslop/SKILL.md

@@ -0,0 +1,138 @@
+---
+name: unslop
+description: "Post-process AI-generated text through the unslop CLI to strip AI writing patterns before publishing"
+category: writing
+risk: safe
+source: community
+source_repo: MohamedAbdallah-14/unslop
+source_type: community
+date_added: "2026-04-25"
+author: MohamedAbdallah-14
+tags: [writing, content-quality, ai-writing, text-processing, cli, publishing]
+tools: [claude-code, cursor, gemini-cli, codex-cli, antigravity]
+license: "MIT"
+license_source: "https://github.com/MohamedAbdallah-14/unslop/blob/main/LICENSE"
+---
+
+# unslop — Strip AI Writing Patterns via CLI
+
+## Overview
+
+unslop is a CLI tool that post-processes text to remove AI writing patterns programmatically. Unlike skills that ask the agent to avoid AI-isms, unslop runs as a deterministic pipeline step: pipe text in, get clean text out. Use it as a final pass before committing docs, publishing posts, or sending any AI-generated content to production.
+
+The `--deterministic` flag makes output reproducible — same input always produces same output. The `--stdin` flag reads from stdin, enabling shell pipeline composition.
+
+## When to Use This Skill
+
+- When you have AI-generated text ready to publish and want a final cleanup pass
+- When working in a shell pipeline where text quality needs to be enforced automatically
+- When writing commit hooks or CI steps that validate content before it ships
+- When you need reproducible text normalization across multiple runs
+
+## Setup
+
+Install once:
+
+```bash
+pipx install unslop
+# or
+uv tool install unslop
+```
+
+Verify:
+
+```bash
+unslop --version
+```
+
+## How It Works
+
+### Step 1: Pipe Text Through unslop
+
+Standard cleanup (may vary slightly between runs):
+
+```bash
+echo "This leverages cutting-edge AI to deliver robust solutions." | unslop --stdin
+```
+
+Deterministic cleanup (same input → same output every run):
+
+```bash
+echo "This leverages cutting-edge AI to deliver robust solutions." | unslop --stdin --deterministic
+```
+
+### Step 2: Use in Shell Pipelines
+
+Pipe the output of any command through unslop:
+
+```bash
+cat draft.md | unslop --stdin --deterministic > clean.md
+```
+
+Or chain with other tools:
+
+```bash
+cat draft.md | unslop --stdin --deterministic | pbcopy   # macOS: copy clean text to clipboard
+```
+
+### Step 3: Integrate into Commit Hooks or CI
+
+Add to a pre-commit hook or CI step to enforce quality gates on any generated content before it ships:
+
+```bash
+# In .git/hooks/pre-commit or a CI script
+CONTENT=$(cat docs/changelog.md)
+CLEANED=$(echo "$CONTENT" | unslop --stdin --deterministic)
+if [ "$CONTENT" != "$CLEANED" ]; then
+  echo "Changelog contains AI writing patterns. Run: cat docs/changelog.md | unslop --stdin --deterministic > docs/changelog.md"
+  exit 1
+fi
+```
+
+## Examples
+
+### Example 1: Clean a Draft Document
+
+```bash
+cat blog-post-draft.md | unslop --stdin --deterministic > blog-post-final.md
+```
+
+### Example 2: Inline Cleanup During Writing
+
+```bash
+# Write content, pipe through unslop, write result back
+cat README.md | unslop --stdin > README.clean.md && mv README.clean.md README.md
+```
+
+### Example 3: Validate Before Submitting a PR
+
+```bash
+# Check if any generated docs need cleanup
+for f in docs/*.md; do
+  ORIGINAL=$(cat "$f")
+  CLEANED=$(echo "$ORIGINAL" | unslop --stdin --deterministic)
+  [ "$ORIGINAL" != "$CLEANED" ] && echo "Needs cleanup: $f"
+done
+```
+
+## Best Practices
+
+- ✅ Use `--deterministic` in CI and automation to ensure reproducible output
+- ✅ Run on the final draft, not intermediate iterations
+- ✅ Combine with the `avoid-ai-writing` skill for both generation-time guidance and post-processing
+- ❌ Don't run on code files — unslop targets prose, not source code
+- ❌ Don't skip review after unslop: automated cleanup can occasionally change meaning; read the output
+
+## Limitations
+
+- Processes prose only — not code, JSON, or structured data
+- Does not catch factual errors or substantive writing issues
+- Some replacements may not fit every context; review the output before publishing
+- Requires Python tooling such as `pipx` or `uv` for standalone CLI installation
+
+## Security & Safety Notes
+
+- unslop reads from stdin and writes to stdout — no file system side effects by default
+- `--deterministic` mode is local and does not make LLM API calls
+- Default LLM mode may use `ANTHROPIC_API_KEY` or the Claude CLI; use `--deterministic` for sensitive local files and CI gates
+- Safe to run in CI pipelines and commit hooks when pinned to deterministic mode

package/bundled-skills/wordpress-centric-high-seo-optimized-blogwriting-skill/SKILL.md

@@ -1,14 +1,42 @@
 ---
 name: wordpress-centric-high-seo-optimized-blogwriting-skill
-description: "Use this skill when the user asks to write a blog post, article, or SEO content. This applies a professional structure, truth boxes, click-bait-free accurate information, and outputs direct WordPress-ready content."
-version: 1.0.0
-author: Whoisabhishekadhikari
-created: 2026-04-12
+description: "Create long-form, high-quality, SEO-optimized blog posts ready for WordPress with truth boxes and FAQ schema."
 category: content
+risk: safe
+source: self
+source_type: self
+date_added: "2026-04-12"
+author: Whoisabhishekadhikari
 tags: [writing, blog, seo, content, wordpress]
+tools: [claude, cursor, gemini]
+version: 1.0.3
 ---
 
-# wordpress-centric-high-seo-optimized-blogwriting-skill
+# WordPress Centric High SEO Optimized Blog Writing Skill
+
+## Overview
+
+This skill is designed for Senior Content Strategists and Expert Copywriters to create high-quality, long-form blog posts that are ready for direct publication in WordPress. It emphasizes professional structure, factual accuracy (Truth Boxes), and comprehensive SEO optimization (Yoast elements and Schema markup).
+
+## When to Use This Skill
+
+- Use when you need to write a professional blog post or article.
+- Use when creating SEO-optimized content for a WordPress site.
+- Use when you need structured elements like Truth Boxes, Comparison Tables, and FAQ sections.
+- Use when the user requires Yoast SEO metadata and JSON-LD schema.
+
+## How It Works
+
+### Step 1: Gather Inputs
+The skill requires a Title, Primary Keyword, Intent, and Niche/Industry. It also prompts for Yoast SEO preference and image count if not provided.
+
+### Step 2: Content Generation
+The agent follows a structured prompt to generate a clickable contents section, a truth box, well-structured sections with tables, common misconceptions, and a short FAQ.
+
+### Step 3: SEO & Schema (Optional)
+If requested, the agent provides Yoast SEO metadata (Social titles, meta descriptions) and JSON-LD Schema (BlogPosting, FAQPage).
+
+## Prompt Template
 
 FINAL MASTER PROMPT (Refined & Generalized Version)
 
@@ -23,6 +51,10 @@ Primary Keyword: {Insert Primary Keyword}
 Intent: {Informational / Commercial / Transactional}
 Niche/Industry: {Insert Industry or Subject Area}
 
+USER PREFERENCES (ASK IF MISSING)
+Yoast SEO: {Are Yoast SEO elements like meta descriptions and focus keyphrases needed?}
+Image Count: {How many images should be included in the SEO plan?}
+
 Optional Context
 Brand: {Insert Brand Name}
 Target Audience: {Insert Target Audience}
@@ -52,6 +84,7 @@ Maintain clean and consistent formatting
 Make content easy to scan and copy
 
 FACT AND ACCURACY RULES
+
 Do not guess or fabricate data.
 - Requirement: Provide citation-backed estimates with a verifiable source or an explicit "no reliable estimate available" response.
 - Prohibited: Do not use vague "industry estimates suggest a range" fallbacks if no verifiable evidence was found.
@@ -59,29 +92,6 @@ Do not guess or fabricate data.
 Avoid fake or unreliable sources
 Keep all information practical, realistic, and up-to-date
 
-SEO SECTION (PLACE AT THE TOP)
-
-Provide the following:
-
-Focus Keyphrase
-SEO Title
-Slug
-Meta Description
-Social Title
-Social Description
-
-Include this exact line:
-Data accurate as of [Current Month & Year] based on market research
-
-SCHEMA MARKUP
-
-Add clean JSON-LD for:
-
-BlogPosting
-FAQPage
-
-Use placeholder URLs if needed
-
 CONTENTS SECTION
 
 Create a clickable contents section with:
@@ -104,9 +114,10 @@ MAIN BLOG STRUCTURE
 
 Main Title
 
+Introduction
+
 Truth Box
 
-Introduction
 
 [Core Topic Section 1]
 
@@ -159,7 +170,7 @@ Keep answers short and clear
 
 IMAGE SEO SECTION
 
-Include 3 to 5 images
+Include {User Requested Count} images
 
 For each image, provide:
 
@@ -184,7 +195,12 @@ Ensure clean and consistent structure
 
 OUTPUT REQUIREMENT
 
-The final output must be:
+The final output must be generated in this order:
+1. The full blog post (from Main Title to Conclusion)
+2. SEO Section (if requested)
+3. Schema Markup (if requested)
+
+The content must be:
 
 Clean and well-structured
 SEO optimized
@@ -192,7 +208,67 @@ Human-sounding
 Professional quality
 Ready to copy and paste into WordPress
 
+SEO SECTION (YOAST)
+*Only provide this section if the user requested Yoast SEO elements.*
+
+Provide the following:
+
+Focus Keyphrase
+SEO Title
+Slug
+Meta Description
+Social Title
+Social Description
+
+If the user provided or approved reliable market sources, include this line with the actual month and year:
+Data accurate as of [Month Year] based on cited market research.
+
+If no reliable market sources were provided or reviewed, omit the line instead of implying research was performed.
+
+SCHEMA MARKUP
+*Only provide this section if the user requested Yoast/SEO schema.*
+
+Add clean JSON-LD for:
+
+BlogPosting
+FAQPage
+
+Use placeholder URLs if needed
+
+## Examples
+
+### Example 1: Informational Blog Post
+**User:** Write a blog post about "Sustainable Gardening for Beginners".
+**Agent:** (Generates Title, Truth Box, clickable contents, well-structured sections with tables, Misconceptions, and FAQ.)
+
+## Best Practices
+
+- ✅ Use short, punchy sentences.
+- ✅ Ensure tables are clean and use `|` markdown syntax.
+- ✅ Maintain the Truth Box at the very beginning of the post for high engagement.
+- ❌ Avoid using numbered headings; stick to standard markdown `#`, `##`, `###`.
+- ❌ Do not use hyphen bullets in the contents section.
+
 ## Limitations
+
+- This skill does not replace environment-specific validation, testing, or expert review.
+- Stop and ask for clarification if required inputs, permissions, or safety boundaries are missing.
 - Use this skill only when the task clearly matches the scope described above.
-- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.
-- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.
+
+## Security & Safety Notes
+
+- This skill focuses on content generation and does not involve shell commands or direct system mutation.
+- Ensure any generated JSON-LD is properly escaped if used in a programmatic context.
+
+## Common Pitfalls
+
+- **Problem:** Missing Primary Keyword in Alt Text.
+  **Solution:** Ensure the `IMAGE SEO SECTION` explicitly includes the primary keyword in at least one Alt Text field.
+- **Problem:** AI-sounding or repetitive tone.
+  **Solution:** Use the "Human-sounding" requirement in the `WRITING RULES` to re-check the draft.
+
+## Related Skills
+
+- `@seo-plan` - Use for high-level SEO strategy before writing.
+- `@seo-content` - For broader SEO content optimization across different platforms.
+- `@copywriting` - General professional writing and marketing copy.

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

@@ -1,83 +1,98 @@
 ---
 id: zipai-optimizer
 name: zipai-optimizer
-version: "11.0"
-description: "Adaptive token optimizer: intelligent filtering, surgical output, ambiguity-first, context-window-aware, VCS-aware."
+version: "12.0"
+description: "Adaptive token optimizer: intelligent filtering, surgical output, ambiguity-first, context-window-aware, VCS-aware, MCP-aware."
 category: agent-behavior
 risk: safe
 ---
 
 # ZipAI: Context & Token Optimizer
 
-<rules>
-  <rule id="1" name="Adaptive Verbosity">
-    <instruction>
-      - **Ops/Fixes:** technical content only. No filler, no echo, no meta.
-      - **Architecture/Analysis:** full reasoning authorized and encouraged.
-      - **Direct questions:** one paragraph max unless exhaustive enumeration explicitly required.
-      - **Long sessions:** never re-summarize prior context. Assume developer retains full thread memory.
-    </instruction>
-  </rule>
-
-  <rule id="2" name="Ambiguity-First Execution">
-    <instruction>
-      Before producing output on any request with 2+ divergent interpretations: ask exactly ONE targeted question.
-      Never ask about obvious intent. Never stack multiple questions.
-      When uncertain between a minor variant and a full rewrite: default to minimal intervention and state the assumption made.
-    </instruction>
-  </rule>
-
-  <rule id="3" name="Intelligent Input Filtering">
-    <instruction>
-      Classify before ingesting — never read raw:
-
-      - **Builds/Installs (pip, npm, make, docker):** `grep -A 10 -B 10 -iE "(error|fail|warn|fatal)"`
-      - **Errors/Stacktraces (pytest, crashes, stderr):** `grep -A 10 -B 5 -iE "(error|exception|traceback|failed|assert)"`
-      - **Large source files (>300 lines):** locate with `grep -n "def \|class "`, read with `view_range`.
-      - **JSON/YAML payloads:** `jq 'keys'` or `head -n 40` before committing to full read.
-      - **Files already read this session:** use cached in-context version. Do not re-read unless explicitly modified.
-      - **VCS Operations (git, gh):**
-        - `git log` → `| head -n 20` unless a specific range is requested.
-        - `git diff` >50 lines → `| grep -E "^(\+\+\+|---|@@|\+|-)"` to extract hunks only without artificial truncation.
-        - `git status` → read as-is.
-        - `git pull/push` with conflicts/errors → `grep -A 5 -B 2 "CONFLICT\|error\|rejected\|denied"`.
-        - `git log --graph` → `| head -n 40`.
-      - **Context window pressure (session >80% capacity):** summarize resolved sub-problems into a single anchor block, drop their raw detail from active reasoning.
-    </instruction>
-  </rule>
-
-  <rule id="4" name="Surgical Output">
-    <instruction>
-      - Single-line fix → str_replace only, no reprint.
-      - Multi-location changes in one file → batch str_replace calls in dependency order within single response.
-      - Cross-file refactor → one file per response turn, labeled, in dependency order (leaf dependencies first).
-      - Complex structural diffs → unified diff format (`--- a/file / +++ b/file`) when str_replace would be ambiguous.
-      - Never silently bundle unrelated changes.
-    </instruction>
-  </rule>
-
-  <rule id="5" name="Context Pruning & Response Structure">
-    <instruction>
-      - Never restate the user's input.
-      - Lead with conclusion, follow with reasoning (inverted pyramid).
-      - Distinguish when relevant: `[FACT]` (verified) vs `[ASSUMPTION]` (inferred) vs `[RISK]` (potential side effect).
-      - If a response requires more than 3 sections, provide a structured summary at the top.
-    </instruction>
-  </rule>
-</rules>
-
-<negative_constraints>
-  - No filler: "Here is", "I understand", "Let me", "Great question", "Certainly", "Of course", "Happy to help".
-  - No blind truncation of stacktraces or error logs.
-  - No full-file reads when targeted grep/view_range suffices.
-  - No re-reading files already in context.
-  - No multi-question clarification dumps.
-  - No silent bundling of unrelated changes.
-  - No full git diff ingestion on large changesets — extract hunks only.
-  - No git log beyond 20 entries unless a specific range is requested.
-</negative_constraints>
+## Rules
+
+### Rule 1 — Adaptive Verbosity
+
+- **Ops/Fixes:** technical content only. No filler, no echo, no meta.
+- **Architecture/Analysis:** full reasoning authorized and encouraged.
+- **Direct questions:** one paragraph max unless exhaustive enumeration explicitly required.
+- **Long sessions:** never re-summarize prior context. Assume developer retains full thread memory.
+- **Review mode (code review, PR analysis):** structured output with labeled sections (`[ISSUE]`, `[SUGGESTION]`, `[NITPICK]`) is authorized and preferred.
+
+### Rule 2 — Ambiguity-First Execution
+
+Before producing output on any request with 2+ divergent interpretations: ask exactly ONE targeted question.
+Never ask about obvious intent. Never stack multiple questions.
+When uncertain between a minor variant and a full rewrite: default to minimal intervention and state the assumption made.
+When the scope is ambiguous (file vs. project vs. repo): ask once, scoped to the narrowest useful boundary.
+
+### Rule 3 — Intelligent Input Filtering
+
+Classify before ingesting — never read raw:
+
+- **Builds/Installs (pip, npm, make, docker):** `grep -A 10 -B 10 -iE "(error|fail|warn|fatal)"`
+- **Errors/Stacktraces (pytest, crashes, stderr):** `grep -A 10 -B 5 -iE "(error|exception|traceback|failed|assert)"`
+- **Large source files (>300 lines):** locate with `grep -n "def \|class "`, read with `view_range`.
+- **Medium source files (100–300 lines):** `head -n 60` + targeted `grep` before full read.
+- **JSON/YAML payloads:** `jq 'keys'` or `head -n 40` before committing to full read.
+- **Files already read this session:** use cached in-context version. Do not re-read unless explicitly modified.
+- **VCS Operations (git, gh):**
+  - `git log` → `| head -n 20` unless a specific range is requested.
+  - `git diff` >50 lines → `| grep -E "^(\+\+\+|---|@@|\+|-)"` to extract hunks only without artificial truncation.
+  - `git status` → read as-is.
+  - `git pull/push` with conflicts/errors → `grep -A 5 -B 2 "CONFLICT\|error\|rejected\|denied"`.
+  - `git log --graph` → `| head -n 40`.
+  - `git blame` on targeted lines only — never full file.
+- **MCP tool responses:** treat as structured data. Use field-level access (`result.items`, `result.pageInfo`) rather than full-object inspection. Paginate only when the target entity is not found on the first page.
+- **Context window pressure (session >80% capacity):** summarize resolved sub-problems into a single anchor block, drop their raw detail from active reasoning.
+
+### Rule 4 — Surgical Output
+
+- Single-line fix → `str_replace` only, no reprint.
+- Multi-location changes in one file → batch `str_replace` calls in dependency order within single response.
+- Cross-file refactor → one file per response turn, labeled, in dependency order (leaf dependencies first).
+- Complex structural diffs → unified diff format (`--- a/file / +++ b/file`) when `str_replace` would be ambiguous.
+- Never silently bundle unrelated changes.
+- **Regression guard:** when modifying a function or module, explicitly check and mention if existing tests cover the changed path. If none exist, flag as `[RISK: untested path]`.
+
+### Rule 5 — Context Pruning & Response Structure
+
+- Never restate the user's input.
+- Lead with conclusion, follow with reasoning (inverted pyramid).
+- Distinguish when relevant: `[FACT]` (verified) vs `[ASSUMPTION]` (inferred) vs `[RISK]` (potential side effect) vs `[DEPRECATED]` (known obsolete pattern).
+- If a response requires more than 3 sections, provide a structured summary at the top.
+- In multi-step tasks, emit a minimal progress anchor after each completed step: `✓ Step N done — <one-line result>`.
+
+### Rule 6 — MCP-Aware Tool Usage
+
+- **Resolve IDs before acting:** never assume resource IDs (user, repo, issue, PR). Always resolve via lookup first.
+- **Prefer read-before-write:** fetch current state of a resource before any mutating call.
+- **Paginate lazily:** stop pagination as soon as the target entity is found; do not exhaust all pages by default.
+- **Batch when possible:** prefer single multi-file push over sequential single-file commits.
+- **Treat MCP errors as blocking:** surface error detail immediately, do not silently retry more than once.
+- **SHA discipline:** always retrieve current file SHA before `create_or_update_file`. Never hardcode or cache SHAs across sessions.
+
+---
+
+## Negative Constraints
+
+- No filler: "Here is", "I understand", "Let me", "Great question", "Certainly", "Of course", "Happy to help".
+- No blind truncation of stacktraces or error logs.
+- No full-file reads when targeted `grep`/`view_range` suffices.
+- No re-reading files already in context.
+- No multi-question clarification dumps.
+- No silent bundling of unrelated changes.
+- No full git diff ingestion on large changesets — extract hunks only.
+- No git log beyond 20 entries unless a specific range is requested.
+- No full MCP object inspection when field-level access suffices.
+- No MCP mutations without prior read of current resource state.
+- No SHA reuse across sessions for file updates.
+
+---
 
 ## Limitations
+
 - **Ideation Constrained:** Do not use this protocol during pure creative brainstorming or open-ended design phases where exhaustive exploration and maximum token verbosity are required.
 - **Log Blindness Risk:** Intelligent truncation via `grep` and `tail` may occasionally hide underlying root causes located outside the captured error boundaries.
 - **Context Overshadowing:** In extremely long sessions, aggressive anchor summarization might cause the agent to lose track of microscopic variable states dropped during context pruning.
+- **MCP Pagination Truncation:** Lazy pagination stops early on first match — may miss duplicate entity names in large datasets. Override by specifying `paginate:full` explicitly in the request.

package/package.json

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

@@ -29498,6 +29498,28 @@
       "reasons": []
     }
   },
+  {
+    "id": "unslop",
+    "path": "skills/unslop",
+    "category": "writing",
+    "name": "unslop",
+    "description": "Post-process AI-generated text through the unslop CLI to strip AI writing patterns before publishing",
+    "risk": "safe",
+    "source": "community",
+    "date_added": "2026-04-25",
+    "plugin": {
+      "targets": {
+        "codex": "supported",
+        "claude": "supported"
+      },
+      "setup": {
+        "type": "none",
+        "summary": "",
+        "docs": null
+      },
+      "reasons": []
+    }
+  },
   {
     "id": "unsplash-integration",
     "path": "skills/unsplash-integration",
@@ -30915,10 +30937,10 @@
     "path": "skills/wordpress-centric-high-seo-optimized-blogwriting-skill",
     "category": "content",
     "name": "wordpress-centric-high-seo-optimized-blogwriting-skill",
-    "description": "Use this skill when the user asks to write a blog post, article, or SEO content. This applies a professional structure, truth boxes, click-bait-free accurate information, and outputs direct WordPress-ready content.",
-    "risk": "unknown",
-    "source": "unknown",
-    "date_added": null,
+    "description": "Create long-form, high-quality, SEO-optimized blog posts ready for WordPress with truth boxes and FAQ schema.",
+    "risk": "safe",
+    "source": "self",
+    "date_added": "2026-04-12",
     "plugin": {
       "targets": {
         "codex": "supported",
@@ -31531,7 +31553,7 @@
     "path": "skills/zipai-optimizer",
     "category": "agent-behavior",
     "name": "zipai-optimizer",
-    "description": "Adaptive token optimizer: intelligent filtering, surgical output, ambiguity-first, context-window-aware, VCS-aware.",
+    "description": "Adaptive token optimizer: intelligent filtering, surgical output, ambiguity-first, context-window-aware, VCS-aware, MCP-aware.",
     "risk": "safe",
     "source": "unknown",
     "date_added": null,