@olegkoval/agent-skills 1.17.0 → 1.19.0

package/.claude-plugin/marketplace.json

@@ -4,13 +4,13 @@
     "name": "Oleg Koval"
   },
   "metadata": {
-    "description": "Agent-agnostic skill catalog for Codex, Claude, Cursor, and other skill-aware tools."
+    "description": "Agent-agnostic skill catalog for Codex, Claude, Cursor, Grok, Copilot, Windsurf, Kiro, and other skill-aware tools."
   },
   "plugins": [
     {
       "name": "olko-agent-skills",
       "source": "./",
-      "description": "Agent-agnostic skill catalog for Codex, Claude, Cursor, and other skill-aware tools."
+      "description": "Agent-agnostic skill catalog for Codex, Claude, Cursor, Grok, Copilot, Windsurf, Kiro, and other skill-aware tools."
     }
   ]
 }

package/.claude-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "olko-agent-skills",
-  "description": "Agent-agnostic skill catalog for Codex, Claude, Cursor, and other skill-aware tools.",
-  "version": "1.16.0",
+  "description": "Agent-agnostic skill catalog for Codex, Claude, Cursor, Grok, Copilot, Windsurf, Kiro, and other skill-aware tools.",
+  "version": "1.18.0",
   "author": {
     "name": "Oleg Koval"
   },
@@ -31,6 +31,7 @@
     "./packages/software-development/apple-store-submit",
     "./packages/software-development/macos-menubar-app",
     "./packages/software-development/skill-budget-audit",
-    "./packages/software-development/crash-course"
+    "./packages/software-development/crash-course",
+    "./packages/software-development/qodoloop"
   ]
 }

package/.cursor-plugin/index.json

@@ -105,6 +105,11 @@
       "name": "olko:crash-course",
       "source": "./packages/software-development/crash-course/adapters/cursor",
       "description": "Expert tutor for rapid, source-grounded learning of any topic: a timed 4-hour sprint plus cheat-sheet, learning-ladder, quiz-me, Feynman, and resource-curation modes."
+    },
+    {
+      "name": "olko:qodoloop",
+      "source": "./packages/software-development/qodoloop/adapters/cursor",
+      "description": "Iteratively drives a GitHub PR to zero unresolved Qodo findings — reads each finding's own Agent Prompt, applies the fix, replies to the thread, resolves it, pushes, and waits for Qodo's next pass."
     }
   ]
 }

package/.grok-plugin/index.json

@@ -0,0 +1,125 @@
+{
+  "name": "agent-skills",
+  "plugins": [
+    {
+      "name": "olko:self-critique",
+      "source": "./packages/software-development/self-critique/adapters/grok",
+      "description": "Adversarially critique your own last answer: spawn a critic agent that verifies claims against live sources, finds the related issue or pattern you missed, then loop until satisfied and report where you were wrong, iterations-to-satisfy, the numeric improvement, and a final score."
+    },
+    {
+      "name": "olko:docs-index-keeper",
+      "source": "./packages/software-development/docs-index-keeper/adapters/grok",
+      "description": "Keep a Markdown docs index in sync through pre-commit, CI, or one-off maintenance flows."
+    },
+    {
+      "name": "olko:semantic-release-beta",
+      "source": "./packages/software-development/semantic-release-beta/adapters/grok",
+      "description": "Set up semantic-release-npm-github-publish with stable main releases and prerelease beta releases on a beta branch."
+    },
+    {
+      "name": "olko:gh-cli",
+      "source": "./packages/software-development/gh-cli/adapters/grok",
+      "description": "Use the GitHub CLI effectively for repositories, PRs, Actions, releases, and more."
+    },
+    {
+      "name": "olko:git-commit",
+      "source": "./packages/software-development/git-commit/adapters/grok",
+      "description": "Create conventional commits with diff-aware staging and message generation."
+    },
+    {
+      "name": "olko:gallery",
+      "source": "./packages/photography/gallery/adapters/grok",
+      "description": "Create photo galleries with AI-assisted layout curation and sequencing."
+    },
+    {
+      "name": "olko:promptctl",
+      "source": "./packages/software-development/promptctl/adapters/grok",
+      "description": "Use promptctl for template-based prompt engineering, scoring, and workflow automation."
+    },
+    {
+      "name": "olko:fill-music-player",
+      "source": "./packages/music/fill-music-player/adapters/grok",
+      "description": "Fill a portable music player with a curated random selection from a source music library while balancing formats, artists, albums, and capacity."
+    },
+    {
+      "name": "olko:product-builder",
+      "source": "./packages/software-development/product-builder/adapters/grok",
+      "description": "Build a full-stack web application or SaaS product from a user description using production-oriented defaults."
+    },
+    {
+      "name": "olko:mvp-oneshot",
+      "source": "./packages/software-development/mvp-oneshot/adapters/grok",
+      "description": "Turn a rough product idea into a shippable one-week MVP in one pass via a four-role prompt chain: scope a build prompt, ruthlessly trim it, plan the build, and self-review the vertical slice."
+    },
+    {
+      "name": "olko:starter-rules",
+      "source": "./packages/software-development/starter-rules/adapters/grok",
+      "description": "Load and enforce hard rules for every oleg-koval/* starter: 300-line files, E2E tests, pre-commit hooks, Vertical Slice architecture, no comments, KISS/DRY/SOLID."
+    },
+    {
+      "name": "olko:review-past-performance",
+      "source": "./packages/software-development/review-past-performance/adapters/grok",
+      "description": "Self-improvement loop that pulls the last 24h of ICM memories, git history, and skill analytics to detect repeated mistakes, slow workflows, and missing coverage, then proposes 1-3 concrete improvements."
+    },
+    {
+      "name": "olko:relay",
+      "source": "./packages/software-development/relay/adapters/grok",
+      "description": "Use claude-relay to run long or rate-limit-prone tasks autonomously across subscription accounts."
+    },
+    {
+      "name": "olko:open-source-publisher",
+      "source": "./packages/software-development/open-source-publisher/adapters/grok",
+      "description": "Prepare an open-source repository for public publishing with a minimal icon, social preview image, GitHub Pages site, README standardization, CI/CD checks, release hygiene, optional donation setup, and optional motion previews for generated static images."
+    },
+    {
+      "name": "olko:viral-launch",
+      "source": "./packages/marketing/viral-launch/adapters/grok",
+      "description": "Set up a project repository and launch plan for shareable marketing, public launch readiness, and growth loops."
+    },
+    {
+      "name": "olko:search-console-indexing-audit",
+      "source": "./packages/marketing/search-console-indexing-audit/adapters/grok",
+      "description": "Analyze Google Search Console Coverage CSV exports and correlate them with sitemap, robots, canonical, redirect, and noindex signals."
+    },
+    {
+      "name": "olko:cloudflare-block-countries",
+      "source": "./packages/software-development/cloudflare-block-countries/adapters/grok",
+      "description": "Block specific countries via Cloudflare WAF Custom Rules using the Cloudflare API. Handles creating new rulesets and updating existing ones across single or multiple zones."
+    },
+    {
+      "name": "olko:obsidian-pr-sync",
+      "source": "./packages/software-development/obsidian-pr-sync/adapters/grok",
+      "description": "Fetch open GitHub PRs assigned to you or requesting your review, and write a grouped, age-sorted '## PRs to review' section into today's Obsidian daily note. Idempotent — re-running replaces the section."
+    },
+    {
+      "name": "olko:obsidian-task-rollover",
+      "source": "./packages/software-development/obsidian-task-rollover/adapters/grok",
+      "description": "Bullet-journal end-of-day task migration: copy unchecked tasks from today's Obsidian daily note to the next workday's note under '## Carried over', and mark them [>] in the source. Skips weekends, idempotent."
+    },
+    {
+      "name": "olko:apple-store-submit",
+      "source": "./packages/software-development/apple-store-submit/adapters/grok",
+      "description": "Handle Apple App Store rejection emails end-to-end: parse rejection reasons, plan fixes, implement code changes, navigate App Store Connect, and resubmit."
+    },
+    {
+      "name": "olko:macos-menubar-app",
+      "source": "./packages/software-development/macos-menubar-app/adapters/grok",
+      "description": "Build a production-quality macOS menubar or notch app in SwiftUI — MenuBarExtra, sandbox entitlements, keyboard shortcuts, sound effects, accessibility permissions, and App Store preparation."
+    },
+    {
+      "name": "olko:skill-budget-audit",
+      "source": "./packages/software-development/skill-budget-audit/adapters/grok",
+      "description": "Diagnose and fix Claude Code skill context budget overflow — identify heavy plugin bundles, remove domain-specific ones, and restore skill discoverability."
+    },
+    {
+      "name": "olko:crash-course",
+      "source": "./packages/software-development/crash-course/adapters/grok",
+      "description": "Expert tutor for rapid, source-grounded learning of any topic: a timed 4-hour sprint plus cheat-sheet, learning-ladder, quiz-me, Feynman, and resource-curation modes."
+    },
+    {
+      "name": "olko:qodoloop",
+      "source": "./packages/software-development/qodoloop/adapters/grok",
+      "description": "Iteratively drives a GitHub PR to zero unresolved Qodo findings — reads each finding's own Agent Prompt, applies the fix, replies to the thread, resolves it, pushes, and waits for Qodo's next pass."
+    }
+  ]
+}

package/.kiro/steering/qodoloop.md

@@ -0,0 +1,127 @@
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+---
+inclusion: manual
+description: "Iteratively drives a GitHub PR to zero unresolved Qodo findings — reads each finding's own Agent Prompt, applies the fix, replies to the thread, resolves it, pushes, and waits for Qodo's next pass."
+---
+
+# Qodoloop
+
+Fix every actionable Qodo finding on a PR, answer each thread, resolve it, and keep going until Qodo has nothing left to say (or a finding needs a human call).
+
+## Inputs
+
+- **PR number** (optional): detect from the current branch if not given.
+- **Include optional findings** (optional, default off): Qodo tags each finding "Review recommended" (actionable) or "Optional" (informational/lower-confidence). By default only "Review recommended" findings count toward done; pass `--include-optional` to also fix and resolve the optional ones.
+
+## How Qodo actually posts (verified against a live install — don't assume otherwise)
+
+Qodo runs as `qodo-code-review[bot]` and posts **two independent things** per review pass, not one:
+
+1. A rollup **issue comment** titled `<h3>Code Review by Qodo</h3>` — human-readable, all findings in one place. A separate `<h3>PR Summary by Qodo</h3>` comment is a plain description, not a review — ignore it. While running, Qodo posts `<h3>Qodo is busy working</h3>` as its own comment (not an edit of a prior one).
+2. A **formal PR review** (`state: COMMENTED`) carrying one **inline review comment per finding**, each a real, resolvable GitHub review thread at the finding's file/line — same machinery as any human inline comment.
+
+**Use the inline threads as the source of truth.** They carry `isResolved` state natively (fetch via GraphQL, see `references/graphql-queries.md`), so "done" is answerable directly instead of re-parsing the rollup's HTML on every iteration. Each thread's body contains a `<details><summary>Agent Prompt</summary>` (or `**Agent Prompt**`) section with a ready-made fix spec, and a severity badge image whose `alt` text is `Remediation recommended` or `Informational` (recommended ↔ "Review recommended", informational ↔ "Optional").
+
+Qodo has **no check run to poll** — there is nothing in `gh pr checks` to wait on. Completion means a new `qodo-code-review[bot]` comment/review appears after your push; poll comments, not checks.
+
+**Rate limit is a real terminal state, not a bug.** A completed-looking comment reading "Qodo reviews are paused" / "you've reached your PR review limit" means Qodo will not review again this cycle — stop and report it, don't loop waiting for something that isn't coming.
+
+## Instructions
+
+### 1. Identify the PR
+
+```bash
+gh pr view --json number,headRefName,headRefOid -q '{number, branch: .headRefName, sha: .headRefOid}'
+```
+
+Check out the branch if not already on it.
+
+### 2. Loop (max 5 iterations)
+
+#### A. Wait for a review of the current head
+
+On **iteration 1**, if there is nothing to push yet (you haven't fixed anything in this loop), don't wait for a brand-new review — use whatever Qodo has already posted as your starting point and go straight to step B. Otherwise:
+
+```bash
+SINCE=$(date -u +%Y-%m-%dT%H:%M:%SZ)
+git push
+```
+
+Poll (every ~10s, timeout ~5min), fetching **every page** of comments, not just the first:
+
+```bash
+gh api --paginate "repos/{owner}/{repo}/issues/<PR_NUMBER>/comments?per_page=100" | jq -s '
+  add | map(select(.user.login == "qodo-code-review[bot]")) | sort_by(.created_at)'
+```
+
+From the comments created **after `$SINCE`** (ignore anything older — that's leftover from a prior push, not this one):
+- Any of them contains "review limit" or "paused" → **stop the loop now**, go to Report with `blocked: rate-limited`.
+- The latest one starts with `<h3>Code Review by Qodo</h3>` → proceed to step B.
+- Otherwise (nothing yet, or only "Qodo is busy working") → sleep 10s and poll again, up to the 5-minute timeout.
+
+#### B. Fetch unresolved findings
+
+Run the paginated GraphQL query in `references/graphql-queries.md` (`unresolvedQodoThreads`) — **follow `pageInfo.hasNextPage`/`endCursor` until it's exhausted**; a PR with more than 100 Qodo threads silently loses every finding past the first page otherwise. For each unresolved thread from `qodo-code-review[bot]`: parse the finding title, severity (recommended/optional), file/line, and the **Agent Prompt** block.
+
+Build the working set: all `recommended` threads, plus `optional` ones too if `--include-optional`.
+
+#### C. Check exit conditions
+
+Stop if the working set is empty, or max iterations reached.
+
+#### D. Fix each finding
+
+For each thread in the working set, in order: read the Agent Prompt in full — it already names the issue, the context, the fix focus files/lines, and often the suggested fix. Apply it. Do not go beyond its stated scope. Track two lists as you go: **fixed** (thread id + the exact files you touched for it) and **blocked** (thread id + why — the prompt's suggestion was wrong, unsafe, or needs a product decision). Do not force a fix into the blocked list; do not resolve anything yet.
+
+#### E. Commit and push
+
+If **fixed** is empty, skip straight to F (nothing to commit). Otherwise, stage **only the files you touched in D** — never `git add -A`, which can sweep in unrelated local changes or secrets that have nothing to do with this loop:
+
+```bash
+git add <files touched by this iteration's fixes>
+git commit -m "address Qodo review feedback (qodoloop iteration N)"
+git push
+```
+
+Confirm the push actually succeeded before moving on — a resolved thread whose fix never made it to the branch is worse than an unresolved one.
+
+#### F. Answer each finding
+
+This is the "answer to the comments" half of the job, not optional cleanup — and it only runs **after** E's push is confirmed durable, so a thread is never marked resolved while its fix still only exists locally:
+
+- **Fixed** findings: reply with one or two sentences (what you changed and why), **then** resolve:
+  ```bash
+  gh api graphql -f query='
+    mutation($threadId: ID!, $body: String!) {
+      addPullRequestReviewThreadReply(input: {pullRequestReviewThreadId: $threadId, body: $body}) {
+        comment { id }
+      }
+    }' -f threadId="$THREAD_ID" -f body="$REPLY_TEXT"
+  ```
+  Pass the thread id and reply text as GraphQL **variables** (`-f threadId=... -f body=...`), never interpolated into the query string itself — a reply containing a quote, backtick, or newline breaks (or worse, injects into) a hand-built query. Then resolve with `resolveReviewThread` (see references file).
+- **Blocked** findings: reply explaining exactly why (false positive / needs a human call), but **do not resolve** — leave the thread open. A blocked finding that gets silently resolved is a false "done".
+
+Go back to step A.
+
+### 3. Report
+
+| Field              | Value |
+|--------------------|-------|
+| Iterations         | N     |
+| Findings resolved  | N     |
+| Findings blocked   | N (with reasons, left unresolved) |
+| Remaining          | N (if any) |
+| Blocked            | rate-limited / human-intervention / max-iterations / none |
+
+```text
+Qodoloop complete.
+  Iterations:  2
+  Resolved:    4 (fixed, replied + resolved)
+  Blocked:     1 (needs a human call, replied, left unresolved)
+  Remaining:   0
+```
+
+## References
+
+- `references/graphql-queries.md` — the exact `unresolvedQodoThreads` query and the `resolveReviewThread` / `addPullRequestReviewThreadReply` mutations, with field notes.

package/.windsurf/rules/qodoloop.md

@@ -0,0 +1,126 @@
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+---
+description: "Iteratively drives a GitHub PR to zero unresolved Qodo findings — reads each finding's own Agent Prompt, applies the fix, replies to the thread, resolves it, pushes, and waits for Qodo's next pass."
+---
+
+# Qodoloop
+
+Fix every actionable Qodo finding on a PR, answer each thread, resolve it, and keep going until Qodo has nothing left to say (or a finding needs a human call).
+
+## Inputs
+
+- **PR number** (optional): detect from the current branch if not given.
+- **Include optional findings** (optional, default off): Qodo tags each finding "Review recommended" (actionable) or "Optional" (informational/lower-confidence). By default only "Review recommended" findings count toward done; pass `--include-optional` to also fix and resolve the optional ones.
+
+## How Qodo actually posts (verified against a live install — don't assume otherwise)
+
+Qodo runs as `qodo-code-review[bot]` and posts **two independent things** per review pass, not one:
+
+1. A rollup **issue comment** titled `<h3>Code Review by Qodo</h3>` — human-readable, all findings in one place. A separate `<h3>PR Summary by Qodo</h3>` comment is a plain description, not a review — ignore it. While running, Qodo posts `<h3>Qodo is busy working</h3>` as its own comment (not an edit of a prior one).
+2. A **formal PR review** (`state: COMMENTED`) carrying one **inline review comment per finding**, each a real, resolvable GitHub review thread at the finding's file/line — same machinery as any human inline comment.
+
+**Use the inline threads as the source of truth.** They carry `isResolved` state natively (fetch via GraphQL, see `references/graphql-queries.md`), so "done" is answerable directly instead of re-parsing the rollup's HTML on every iteration. Each thread's body contains a `<details><summary>Agent Prompt</summary>` (or `**Agent Prompt**`) section with a ready-made fix spec, and a severity badge image whose `alt` text is `Remediation recommended` or `Informational` (recommended ↔ "Review recommended", informational ↔ "Optional").
+
+Qodo has **no check run to poll** — there is nothing in `gh pr checks` to wait on. Completion means a new `qodo-code-review[bot]` comment/review appears after your push; poll comments, not checks.
+
+**Rate limit is a real terminal state, not a bug.** A completed-looking comment reading "Qodo reviews are paused" / "you've reached your PR review limit" means Qodo will not review again this cycle — stop and report it, don't loop waiting for something that isn't coming.
+
+## Instructions
+
+### 1. Identify the PR
+
+```bash
+gh pr view --json number,headRefName,headRefOid -q '{number, branch: .headRefName, sha: .headRefOid}'
+```
+
+Check out the branch if not already on it.
+
+### 2. Loop (max 5 iterations)
+
+#### A. Wait for a review of the current head
+
+On **iteration 1**, if there is nothing to push yet (you haven't fixed anything in this loop), don't wait for a brand-new review — use whatever Qodo has already posted as your starting point and go straight to step B. Otherwise:
+
+```bash
+SINCE=$(date -u +%Y-%m-%dT%H:%M:%SZ)
+git push
+```
+
+Poll (every ~10s, timeout ~5min), fetching **every page** of comments, not just the first:
+
+```bash
+gh api --paginate "repos/{owner}/{repo}/issues/<PR_NUMBER>/comments?per_page=100" | jq -s '
+  add | map(select(.user.login == "qodo-code-review[bot]")) | sort_by(.created_at)'
+```
+
+From the comments created **after `$SINCE`** (ignore anything older — that's leftover from a prior push, not this one):
+- Any of them contains "review limit" or "paused" → **stop the loop now**, go to Report with `blocked: rate-limited`.
+- The latest one starts with `<h3>Code Review by Qodo</h3>` → proceed to step B.
+- Otherwise (nothing yet, or only "Qodo is busy working") → sleep 10s and poll again, up to the 5-minute timeout.
+
+#### B. Fetch unresolved findings
+
+Run the paginated GraphQL query in `references/graphql-queries.md` (`unresolvedQodoThreads`) — **follow `pageInfo.hasNextPage`/`endCursor` until it's exhausted**; a PR with more than 100 Qodo threads silently loses every finding past the first page otherwise. For each unresolved thread from `qodo-code-review[bot]`: parse the finding title, severity (recommended/optional), file/line, and the **Agent Prompt** block.
+
+Build the working set: all `recommended` threads, plus `optional` ones too if `--include-optional`.
+
+#### C. Check exit conditions
+
+Stop if the working set is empty, or max iterations reached.
+
+#### D. Fix each finding
+
+For each thread in the working set, in order: read the Agent Prompt in full — it already names the issue, the context, the fix focus files/lines, and often the suggested fix. Apply it. Do not go beyond its stated scope. Track two lists as you go: **fixed** (thread id + the exact files you touched for it) and **blocked** (thread id + why — the prompt's suggestion was wrong, unsafe, or needs a product decision). Do not force a fix into the blocked list; do not resolve anything yet.
+
+#### E. Commit and push
+
+If **fixed** is empty, skip straight to F (nothing to commit). Otherwise, stage **only the files you touched in D** — never `git add -A`, which can sweep in unrelated local changes or secrets that have nothing to do with this loop:
+
+```bash
+git add <files touched by this iteration's fixes>
+git commit -m "address Qodo review feedback (qodoloop iteration N)"
+git push
+```
+
+Confirm the push actually succeeded before moving on — a resolved thread whose fix never made it to the branch is worse than an unresolved one.
+
+#### F. Answer each finding
+
+This is the "answer to the comments" half of the job, not optional cleanup — and it only runs **after** E's push is confirmed durable, so a thread is never marked resolved while its fix still only exists locally:
+
+- **Fixed** findings: reply with one or two sentences (what you changed and why), **then** resolve:
+  ```bash
+  gh api graphql -f query='
+    mutation($threadId: ID!, $body: String!) {
+      addPullRequestReviewThreadReply(input: {pullRequestReviewThreadId: $threadId, body: $body}) {
+        comment { id }
+      }
+    }' -f threadId="$THREAD_ID" -f body="$REPLY_TEXT"
+  ```
+  Pass the thread id and reply text as GraphQL **variables** (`-f threadId=... -f body=...`), never interpolated into the query string itself — a reply containing a quote, backtick, or newline breaks (or worse, injects into) a hand-built query. Then resolve with `resolveReviewThread` (see references file).
+- **Blocked** findings: reply explaining exactly why (false positive / needs a human call), but **do not resolve** — leave the thread open. A blocked finding that gets silently resolved is a false "done".
+
+Go back to step A.
+
+### 3. Report
+
+| Field              | Value |
+|--------------------|-------|
+| Iterations         | N     |
+| Findings resolved  | N     |
+| Findings blocked   | N (with reasons, left unresolved) |
+| Remaining          | N (if any) |
+| Blocked            | rate-limited / human-intervention / max-iterations / none |
+
+```text
+Qodoloop complete.
+  Iterations:  2
+  Resolved:    4 (fixed, replied + resolved)
+  Blocked:     1 (needs a human call, replied, left unresolved)
+  Remaining:   0
+```
+
+## References
+
+- `references/graphql-queries.md` — the exact `unresolvedQodoThreads` query and the `resolveReviewThread` / `addPullRequestReviewThreadReply` mutations, with field notes.

package/README.md

@@ -1,15 +1,15 @@
 <div align="center">
   <h1>agent skills</h1>
-  <p><strong>Agent-agnostic skill catalog for Codex, Claude, Cursor, Copilot, Windsurf, Kiro, and other skill-aware tools.</strong></p>
+  <p><strong>Agent-agnostic skill catalog for Codex, Claude, Cursor, Grok, Copilot, Windsurf, Kiro, and other skill-aware tools.</strong></p>
   <p>
     <img src="https://img.shields.io/badge/license-MIT-16a34a" alt="MIT license">
-    <img src="https://img.shields.io/badge/skills-23-2563eb" alt="23 skills">
-    <img src="https://img.shields.io/badge/platforms-Codex%20%7C%20Claude%20%7C%20Cursor%20%7C%20Copilot%20%7C%20Windsurf%20%7C%20Kiro-111827" alt="Codex Claude Cursor Copilot Windsurf Kiro">
+    <img src="https://img.shields.io/badge/skills-24-2563eb" alt="24 skills">
+    <img src="https://img.shields.io/badge/platforms-Codex%20%7C%20Claude%20%7C%20Cursor%20%7C%20Grok%20%7C%20Copilot%20%7C%20Windsurf%20%7C%20Kiro-111827" alt="Codex Claude Cursor Grok Copilot Windsurf Kiro">
     <img src="https://img.shields.io/badge/status-public%20catalog-16a34a" alt="Public catalog">
   </p>
 </div>
 
-Agent-agnostic skill collection for Codex, Claude, Cursor, and other skill-aware tools.
+Agent-agnostic skill collection for Codex, Claude, Cursor, Grok, and other skill-aware tools.
 
 These skills are opinionated by design. They encode working defaults, preferred tools, and repeatable workflows instead of trying to be neutral snippets. Treat them as starting points with taste: useful out of the box, easy to inspect, and specific enough for an agent to execute consistently.
 
@@ -76,6 +76,27 @@ claude --plugin-dir /path/to/agent-skills
 
 </details>
 
+<details>
+<summary><b>Grok</b></summary>
+
+Grok (xAI) supports plugins via marketplace or direct path. Add this catalog as a marketplace source:
+
+```bash
+grok plugin marketplace add oleg-koval/agent-skills
+```
+
+Or for local development / direct use:
+
+```bash
+grok agent --plugin-dir /path/to/agent-skills
+```
+
+Skills are available via their `olko:*` names or through the installed plugin. Grok discovers `plugin.json` + `skills/` (and falls back to `.claude-plugin/` manifests for compatibility).
+
+The repo generates `.grok-plugin/index.json` for structured plugin discovery.
+
+</details>
+
 <details>
 <summary><b>Cursor</b></summary>
 
@@ -115,11 +136,11 @@ packages/{category}/{skill}/SKILL.md
 
 </details>
 
-## All 23 Skills
+## All 24 Skills
 
 Each entry links to its `SKILL.md`. Reference any skill by its `olko:*` lookup name in a new agent session.
 
-### Software development (19)
+### Software development (21)
 
 | Skill | What it does | Use when |
 |-------|-------------|----------|
@@ -139,6 +160,7 @@ Each entry links to its `SKILL.md`. Reference any skill by its `olko:*` lookup n
 | [open-source-publisher](packages/software-development/open-source-publisher/SKILL.md) | Prepares an open-source repository for public publishing with branding, CI/CD, and release hygiene | Releasing a private project publicly with proper GitHub Pages, README, and social preview |
 | [product-builder](packages/software-development/product-builder/SKILL.md) | Builds a full-stack web app or SaaS product from a user description using production-oriented defaults | Building a complete app, SaaS, dashboard, or product rather than a prototype |
 | [promptctl](packages/software-development/promptctl/SKILL.md) | Uses `promptctl` for reusable prompt templates, scoring, and workflow automation | A project needs prompt conventions, review, scoring, or reusable prompt workflows |
+| [qodoloop](packages/software-development/qodoloop/SKILL.md) | Iteratively drives a GitHub PR to zero unresolved Qodo findings, reading each finding's own Agent Prompt, replying to the thread, and resolving it | Fully addressing a PR against Qodo's code review before merging |
 | [review-past-performance](packages/software-development/review-past-performance/SKILL.md) | Pulls 24h of ICM memories, git history, and skill analytics; detects repeated mistakes and slow workflows; proposes 1-3 concrete fixes | Daily self-improvement loop or codifying a repeated workflow |
 | [semantic-release-beta](packages/software-development/semantic-release-beta/SKILL.md) | Sets up `semantic-release` with stable `main` releases and beta prereleases on a `beta` branch | A Node package needs stable npm publishing plus beta prereleases |
 | [skill-budget-audit](packages/software-development/skill-budget-audit/SKILL.md) | Diagnoses and fixes Claude Code's skill context budget overflow — identifies heavy plugin bundles that exceed the 2% budget | Skills failing to load or Claude hitting context limits from plugin bundles |
@@ -204,6 +226,7 @@ When adding or changing a skill:
 | Claude Code | `.claude-plugin/marketplace.json` | Marketplace plugin registry |
 | Claude Code | `.claude-plugin/plugin.json` | Plugin manifest |
 | Cursor | `.cursor-plugin/index.json` | Plugin index |
+| Grok | `.grok-plugin/index.json` | Plugin index (plus `.claude-plugin/` compatibility) |
 | GitHub Copilot | `.github/copilot-instructions.md` | Repository instructions |
 | GitHub Copilot | `.github/prompts/*.prompt.md` | Per-skill prompt files |
 | Windsurf | `.windsurf/rules/*.md` | Cascade rules |
@@ -223,6 +246,7 @@ packages/{category}/{skill}/
     ├── codex/
     ├── claude/
     ├── cursor/
+    ├── grok/
     ├── windsurf/
     └── kiro/
 ```