@olegkoval/agent-skills 1.5.1 → 1.7.0

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.5.0",
+  "version": "1.6.0",
   "author": {
     "name": "Oleg Koval"
   },
@@ -23,6 +23,7 @@
     "./packages/software-development/starter-rules",
     "./packages/software-development/open-source-publisher",
     "./packages/marketing/viral-launch",
-    "./packages/marketing/search-console-indexing-audit"
+    "./packages/marketing/search-console-indexing-audit",
+    "./packages/software-development/cloudflare-block-countries"
   ]
 }

package/.cursor-plugin/index.json

@@ -75,6 +75,11 @@
       "name": "olko:search-console-indexing-audit",
       "source": "./packages/marketing/search-console-indexing-audit/adapters/cursor",
       "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/cursor",
+      "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."
     }
   ]
 }

package/.kiro/steering/add-to-my-skills.md

@@ -0,0 +1,78 @@
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+---
+inclusion: manual
+description: "Copy a newly created skill into this catalog, refresh manifests, and publish the change."
+---
+
+
+# Add to My Skills
+
+Use this skill when a skill was created in another repository and needs to be copied into this catalog as a first-class package.
+
+## Outcome
+
+Bring the source skill into `packages/software-development/`, register it in the catalog, refresh generated docs and adapters, and publish the change with a git commit and push.
+
+## When to Use
+
+- The user created a new `SKILL.md` in another repo and wants it added here
+- The user wants this catalog to become the canonical home for that skill
+- The user wants the README, generated manifests, commit, and push handled in one pass
+
+## Clarify Before Acting
+
+If any of these are unclear, ask up to 3 questions in one batch before editing:
+
+- Source repo or source skill path
+- Final skill name if it should differ from the source
+- Destination branch or remote if the push target is unclear
+
+Default assumptions when not specified:
+
+- Copy the source skill as a new canonical package in `packages/software-development/<skill-name>/`
+- Keep the source skill name unless the user asks to rename it
+- Use this repository as the destination
+- Commit with a conventional commit message and push to the current branch's upstream
+
+## Workflow
+
+1. Inspect the source skill:
+   - locate the source `SKILL.md`
+   - copy any supporting `references/`, `scripts/`, or `assets/` files that the skill needs
+   - note any repo-specific assumptions that need to be rewritten for this catalog
+2. Choose the package location:
+   - default to `packages/software-development/<skill-name>/`
+   - ensure the package directory name matches the `name` frontmatter value
+3. Create or update the canonical package:
+   - write `SKILL.md` first
+   - keep the frontmatter accurate and concise
+   - make the workflow explicit, actionable, and self-contained
+4. Register the package in the repository inventory:
+   - add the package to `catalog/skills.json`
+   - add it to the appropriate collection file if it belongs in a bundle
+   - update `README.md` so the package list, counts, and usage examples stay current
+5. Refresh generated outputs:
+   - run `./scripts/build-adapters.sh`
+   - run `./scripts/validate-catalog.sh`
+6. Verify the new package actually exists:
+   - confirm `packages/software-development/<skill-name>/SKILL.md`
+   - confirm generated adapter files and prompt files were created
+7. Commit and push:
+   - inspect `git status`
+   - commit the change with a conventional message
+   - push to the current upstream branch
+
+## Git Safety
+
+- Never overwrite unrelated changes
+- Never force push unless the user explicitly asks
+- Never commit secrets copied from the source repo
+- If the source skill is incomplete or ambiguous, stop and ask for clarification instead of guessing
+
+## Verification
+
+- `./scripts/build-adapters.sh` completes successfully
+- `./scripts/validate-catalog.sh` passes
+- `git status` shows only the intended package, catalog, README, and generated files
+- `git push` succeeds to the expected remote

package/.kiro/steering/ai-tools-setup.md

@@ -0,0 +1,263 @@
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+---
+inclusion: manual
+description: "Install, repair, and measure the RTK+ICM+Vox AI development toolkit. Fixes missing hooks and MCP config, and shows a weekly effectiveness digest of token savings and memory health."
+---
+
+
+# AI Tools Setup — RTK + ICM + Vox
+
+Install, repair, and measure the RTK+ICM+Vox toolkit for Claude Code.
+
+## What This Skill Does
+
+| Mode | When to use |
+|------|-------------|
+| **Setup** | First install on a new machine |
+| **Repair** | Something broke — hooks missing, MCP not loading |
+| **Digest** | Weekly check: token savings, memory health, voice stats |
+
+## Tools in the Bundle
+
+| Tool | Version | Purpose |
+|------|---------|---------|
+| **RTK** | latest | Compresses CLI output by ~89% before it reaches the model |
+| **ICM** | latest | Persistent SQLite memory across sessions (knowledge graph + hybrid search) |
+| **Vox** | latest | Spoken task notifications via local TTS — zero API calls |
+
+---
+
+## Step 1: Detect Current State
+
+Run this to see what is installed and what is missing:
+
+```bash
+echo "=== Binary check ===" && \
+  (rtk --version 2>/dev/null && echo "RTK: ok") || echo "RTK: MISSING" && \
+  (icm --version 2>/dev/null && echo "ICM: ok") || echo "ICM: MISSING" && \
+  (vox --version 2>/dev/null && echo "Vox: ok") || echo "Vox: MISSING"
+
+echo "=== RTK hook ===" && \
+  grep -c '"rtk hook claude"' ~/.claude/settings.json 2>/dev/null \
+    && echo "RTK hook: ok" || echo "RTK hook: MISSING"
+
+echo "=== ICM hooks ===" && \
+  grep -c '"icm hook' ~/.claude/settings.json 2>/dev/null \
+    && echo "ICM hooks: ok" || echo "ICM hooks: MISSING"
+
+echo "=== ICM MCP ===" && \
+  python3 -c "import json; d=json.load(open(open('$HOME/.claude.json').name)); print('ICM MCP: ok' if 'icm' in d.get('mcpServers',{}) else 'ICM MCP: MISSING')" 2>/dev/null || echo "ICM MCP: MISSING"
+
+echo "=== Vox MCP ===" && \
+  python3 -c "import json; d=json.load(open(open('$HOME/.claude.json').name)); print('Vox MCP: ok' if 'vox' in d.get('mcpServers',{}) else 'Vox MCP: MISSING')" 2>/dev/null || echo "Vox MCP: MISSING"
+
+echo "=== ICM CLAUDE.md ===" && \
+  grep -c 'icm:start' ~/.claude/CLAUDE.md 2>/dev/null \
+    && echo "ICM CLAUDE.md: ok" || echo "ICM CLAUDE.md: MISSING"
+```
+
+Read the output and determine which of the following repair steps are needed.
+
+---
+
+## Step 2: Install Missing Binaries
+
+Only run for tools that showed MISSING above.
+
+**RTK:**
+```bash
+brew install rtk
+rtk --version
+```
+
+**ICM:**
+```bash
+brew install rtk-ai/tap/icm
+icm --version
+```
+
+**Vox:**
+```bash
+brew install rtk-ai/tap/vox
+vox --version
+```
+
+---
+
+## Step 3: Repair Hooks
+
+### RTK hook missing
+
+Add the `PreToolUse` RTK hook to `~/.claude/settings.json`. Read the file first, then add inside the existing `"hooks"` block (or create one):
+
+```json
+"PreToolUse": [
+  {
+    "matcher": "Bash",
+    "hooks": [{ "type": "command", "command": "rtk hook claude" }]
+  }
+]
+```
+
+Then verify: `grep -c '"rtk hook claude"' ~/.claude/settings.json`
+
+### ICM hooks missing
+
+Run:
+```bash
+icm init --mode hook
+```
+
+This adds `PreToolUse`, `PostToolUse`, `PreCompact`, `UserPromptSubmit`, `SessionStart`, `SessionEnd` hooks automatically.
+
+### Vox Stop hook missing
+
+Run:
+```bash
+vox init --mode cli
+```
+
+---
+
+## Step 4: Repair MCP Servers
+
+### ICM MCP missing
+
+```bash
+icm init --mode mcp
+```
+
+### Vox MCP missing
+
+```bash
+vox init --mode mcp
+```
+
+Verify both by checking `~/.claude.json`:
+```bash
+python3 -c "import json; d=json.load(open('$HOME/.claude.json')); print(list(d.get('mcpServers',{}).keys()))"
+```
+
+---
+
+## Step 5: Repair CLAUDE.md Instructions
+
+If ICM instructions are missing from `~/.claude/CLAUDE.md`:
+
+```bash
+icm init --mode cli
+```
+
+Then move the block from wherever `icm init` placed it into `~/.claude/CLAUDE.md` (the global file), and remove it from any project-local files.
+
+---
+
+## Step 6: Effectiveness Digest
+
+Run this report to see how the toolkit is performing. Good to run weekly.
+
+```bash
+echo "=============================="
+echo "  AI TOOLS EFFECTIVENESS"
+echo "=============================="
+echo ""
+echo "--- RTK: Token Savings ---"
+rtk gain 2>/dev/null || echo "No data yet (run some commands first)"
+echo ""
+echo "--- ICM: Memory Health ---"
+icm health 2>/dev/null || echo "No memories yet"
+echo ""
+echo "--- ICM: Topics ---"
+icm topics 2>/dev/null || echo "No topics yet"
+echo ""
+echo "--- Vox: Usage ---"
+vox stats 2>/dev/null || echo "No stats yet"
+echo ""
+echo "=============================="
+```
+
+### What healthy output looks like
+
+- **RTK**: `Tokens saved: 5M+ (85%+)` across `500+ commands` — if savings are low, run `rtk discover` to find uncovered commands
+- **ICM**: Topics like `decisions-*`, `errors-resolved`, `preferences` with recent timestamps — if empty, start storing manually with `icm store`
+- **Vox**: Non-zero speak count means the Stop hook fired
+
+---
+
+## Step 7 (Optional): Schedule a Weekly Digest
+
+To get a weekly automated report without having to remember to run this skill:
+
+```bash
+# Create a weekly digest script
+cat > ~/ai-tools-digest.sh << 'EOF'
+#!/bin/bash
+echo "=== Weekly AI Tools Digest — $(date) ===" | tee -a ~/ai-tools-digest.log
+echo "" | tee -a ~/ai-tools-digest.log
+rtk gain 2>/dev/null | tee -a ~/ai-tools-digest.log
+echo "" | tee -a ~/ai-tools-digest.log
+icm health 2>/dev/null | tee -a ~/ai-tools-digest.log
+echo "" | tee -a ~/ai-tools-digest.log
+icm topics 2>/dev/null | tee -a ~/ai-tools-digest.log
+# Speak the summary if Vox is available
+vox "Weekly digest complete. Check your log." 2>/dev/null || true
+EOF
+chmod +x ~/ai-tools-digest.sh
+```
+
+Then set up a weekly launchd job (macOS):
+
+```bash
+cat > ~/Library/LaunchAgents/com.oleg.ai-tools-digest.plist << 'EOF'
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
+<plist version="1.0">
+<dict>
+  <key>Label</key>
+  <string>com.oleg.ai-tools-digest</string>
+  <key>ProgramArguments</key>
+  <array>
+    <string>/bin/bash</string>
+    <string>/Users/oleg.koval/ai-tools-digest.sh</string>
+  </array>
+  <key>StartCalendarInterval</key>
+  <dict>
+    <key>Weekday</key>
+    <integer>1</integer>
+    <key>Hour</key>
+    <integer>9</integer>
+    <key>Minute</key>
+    <integer>0</integer>
+  </dict>
+  <key>StandardOutPath</key>
+  <string>/tmp/ai-tools-digest.log</string>
+  <key>StandardErrorPath</key>
+  <string>/tmp/ai-tools-digest.err</string>
+</dict>
+</plist>
+EOF
+
+launchctl load ~/Library/LaunchAgents/com.oleg.ai-tools-digest.plist
+echo "Weekly digest scheduled for Mondays at 9am"
+```
+
+To view the digest log anytime: `cat ~/ai-tools-digest.log`
+
+To unload: `launchctl unload ~/Library/LaunchAgents/com.oleg.ai-tools-digest.plist`
+
+---
+
+## Quick Reference
+
+| Command | What it does |
+|---------|-------------|
+| `rtk gain` | Total tokens saved to date |
+| `rtk discover` | Find commands not yet covered by RTK |
+| `icm topics` | List all memory topic buckets |
+| `icm health` | Memory hygiene — stale, redundant, decay stats |
+| `icm recall "query"` | Search memories semantically |
+| `icm store -t topic -c "content" -i high` | Store a memory manually |
+| `vox "text"` | Speak text immediately |
+| `vox stats` | Usage stats for the Vox backend |
+| `cat ~/ai-tools-digest.log` | View scheduled digest history |

package/.kiro/steering/changelog-generator.md

@@ -0,0 +1,106 @@
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+---
+inclusion: manual
+description: "Generate user-facing changelogs and release notes from git history."
+---
+
+
+# Changelog Generator
+
+This skill transforms technical git commits into polished, user-friendly changelogs that your customers and users will actually understand and appreciate.
+
+## When to Use This Skill
+
+- Preparing release notes for a new version
+- Creating weekly or monthly product update summaries
+- Documenting changes for customers
+- Writing changelog entries for app store submissions
+- Generating update notifications
+- Creating internal release documentation
+- Maintaining a public changelog/product updates page
+
+## What This Skill Does
+
+1. **Scans Git History**: Analyzes commits from a specific time period or between versions
+2. **Categorizes Changes**: Groups commits into logical categories (features, improvements, bug fixes, breaking changes, security)
+3. **Translates Technical → User-Friendly**: Converts developer commits into customer language
+4. **Formats Professionally**: Creates clean, structured changelog entries
+5. **Filters Noise**: Excludes internal commits (refactoring, tests, etc.)
+6. **Follows Best Practices**: Applies changelog guidelines and your brand voice
+
+## How to Use
+
+### Basic Usage
+
+From your project repository:
+
+```
+Create a changelog from commits since last release
+```
+
+```
+Generate changelog for all commits from the past week
+```
+
+```
+Create release notes for version 2.5.0
+```
+
+### With Specific Date Range
+
+```
+Create a changelog for all commits between March 1 and March 15
+```
+
+### With Custom Guidelines
+
+```
+Create a changelog for commits since v2.4.0, using my changelog
+guidelines from CHANGELOG_STYLE.md
+```
+
+## Example
+
+**User**: "Create a changelog for commits from the past 7 days"
+
+**Output**:
+```markdown
+# Updates - Week of March 10, 2024
+
+## ✨ New Features
+
+- **Team Workspaces**: Create separate workspaces for different
+  projects. Invite team members and keep everything organized.
+
+- **Keyboard Shortcuts**: Press ? to see all available shortcuts.
+  Navigate faster without touching your mouse.
+
+## 🔧 Improvements
+
+- **Faster Sync**: Files now sync 2x faster across devices
+- **Better Search**: Search now includes file contents, not just titles
+
+## 🐛 Fixes
+
+- Fixed issue where large images wouldn't upload
+- Resolved timezone confusion in scheduled posts
+- Corrected notification badge count
+```
+
+**Inspired by:** Manik Aggarwal's use case from Lenny's Newsletter
+
+## Tips
+
+- Run from your git repository root
+- Specify date ranges for focused changelogs
+- Use your CHANGELOG_STYLE.md for consistent formatting
+- Review and adjust the generated changelog before publishing
+- Save output directly to CHANGELOG.md
+
+## Related Use Cases
+
+- Creating GitHub release notes
+- Writing app store update descriptions
+- Generating email updates for users
+- Creating social media announcement posts

package/.kiro/steering/cloudflare-block-countries.md

@@ -0,0 +1,167 @@
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+---
+inclusion: manual
+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."
+---
+
+
+# Cloudflare Country Block via WAF Custom Rules
+
+Block traffic from specific countries using Cloudflare WAF Custom Rules and the Cloudflare API.
+
+## Prerequisites
+
+- Cloudflare API Token with `Zone:Rulesets:Edit` permission
+- Zone ID for the target domain
+- `curl` and `jq` installed
+
+## Workflow
+
+### 1. Get Zone IDs
+
+```bash
+curl -s -X GET \
+  "https://api.cloudflare.com/client/v4/zones?account.id=YOUR_ACCOUNT_ID&status=active" \
+  -H "Authorization: Bearer YOUR_API_TOKEN" \
+  -H "Content-Type: application/json" | jq '.result[] | {name: .name, id: .id}'
+```
+
+### 2. Check Existing Custom Firewall Rulesets
+
+```bash
+curl -s -X GET \
+  "https://api.cloudflare.com/client/v4/zones/YOUR_ZONE_ID/rulesets" \
+  -H "Authorization: Bearer YOUR_API_TOKEN" \
+  -H "Content-Type: application/json" | \
+  jq '.result[] | select(.phase == "http_request_firewall_custom")'
+```
+
+If the output is empty — no existing ruleset. Go to **3a**. If a ruleset exists, note its `id` and go to **3b**.
+
+### 3a. Create NEW Ruleset with Block Rule
+
+```bash
+curl -s -X POST \
+  "https://api.cloudflare.com/client/v4/zones/YOUR_ZONE_ID/rulesets" \
+  -H "Authorization: Bearer YOUR_API_TOKEN" \
+  -H "Content-Type: application/json" \
+  --data '{
+    "name": "default",
+    "description": "WAF Custom Rules",
+    "kind": "zone",
+    "phase": "http_request_firewall_custom",
+    "rules": [
+      {
+        "action": "block",
+        "description": "Block traffic from sanctioned countries",
+        "enabled": true,
+        "expression": "(ip.src.country in {\"RU\" \"BY\" \"IR\" \"KP\"})"
+      }
+    ]
+  }' | jq '.success'
+```
+
+### 3b. Update EXISTING Ruleset
+
+```bash
+curl -s -X PUT \
+  "https://api.cloudflare.com/client/v4/zones/YOUR_ZONE_ID/rulesets/RULESET_ID" \
+  -H "Authorization: Bearer YOUR_API_TOKEN" \
+  -H "Content-Type: application/json" \
+  --data '{
+    "description": "WAF Custom Rules",
+    "rules": [
+      {
+        "action": "block",
+        "description": "Block traffic from sanctioned countries",
+        "enabled": true,
+        "expression": "(ip.src.country in {\"RU\" \"BY\" \"IR\" \"KP\"})"
+      }
+    ]
+  }' | jq '.success'
+```
+
+### 4. Verify the Rule is Active
+
+```bash
+curl -s -X GET \
+  "https://api.cloudflare.com/client/v4/zones/YOUR_ZONE_ID/rulesets/RULESET_ID" \
+  -H "Authorization: Bearer YOUR_API_TOKEN" \
+  -H "Content-Type: application/json" | jq '.result.rules'
+```
+
+## Country Codes Reference
+
+| Code | Country |
+|------|---------|
+| `RU` | Russia |
+| `BY` | Belarus |
+| `IR` | Iran |
+| `KP` | North Korea |
+| `CN` | China |
+| `CU` | Cuba |
+| `SY` | Syria |
+| `VE` | Venezuela |
+
+## WAF Expression Examples
+
+```
+# Block multiple countries
+(ip.src.country in {"RU" "BY" "IR" "KP"})
+
+# Block country + specific ASN
+(ip.src.country eq "RU") or (ip.geoip.asnum eq 12345)
+
+# Block all except allowlisted IPs
+(ip.src.country in {"RU" "BY"}) and not (ip.src in {1.2.3.4/32})
+```
+
+## Multi-Zone Script
+
+To apply the same block rule across multiple zones:
+
+```bash
+#!/usr/bin/env bash
+API_TOKEN="YOUR_API_TOKEN"
+ZONES=("ZONE_ID_1" "ZONE_ID_2" "ZONE_ID_3")
+EXPRESSION='(ip.src.country in {"RU" "BY" "IR" "KP"})'
+
+for ZONE_ID in "${ZONES[@]}"; do
+  EXISTING=$(curl -s -X GET \
+    "https://api.cloudflare.com/client/v4/zones/$ZONE_ID/rulesets" \
+    -H "Authorization: Bearer $API_TOKEN" \
+    -H "Content-Type: application/json" | \
+    jq -r '.result[] | select(.phase == "http_request_firewall_custom") | .id')
+
+  if [ -z "$EXISTING" ]; then
+    METHOD="POST"
+    URL="https://api.cloudflare.com/client/v4/zones/$ZONE_ID/rulesets"
+    DATA=$(jq -n --arg expr "$EXPRESSION" '{
+      name: "default", description: "WAF Custom Rules",
+      kind: "zone", phase: "http_request_firewall_custom",
+      rules: [{action: "block", description: "Block sanctioned countries", enabled: true, expression: $expr}]
+    }')
+  else
+    METHOD="PUT"
+    URL="https://api.cloudflare.com/client/v4/zones/$ZONE_ID/rulesets/$EXISTING"
+    DATA=$(jq -n --arg expr "$EXPRESSION" '{
+      description: "WAF Custom Rules",
+      rules: [{action: "block", description: "Block sanctioned countries", enabled: true, expression: $expr}]
+    }')
+  fi
+
+  RESULT=$(curl -s -X "$METHOD" "$URL" \
+    -H "Authorization: Bearer $API_TOKEN" \
+    -H "Content-Type: application/json" \
+    --data "$DATA" | jq '.success')
+
+  echo "Zone $ZONE_ID: $RESULT"
+done
+```
+
+## Notes
+
+- `PUT` on an existing ruleset **replaces all rules** in it. Include all rules in the payload if the ruleset already has other rules.
+- WAF Custom Rules require a Cloudflare plan that supports rulesets (Free includes basic WAF; Pro/Business/Enterprise for full custom rules).
+- Changes are applied globally within seconds; no cache purge needed.

package/.kiro/steering/docs-index-keeper.md

@@ -0,0 +1,53 @@
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+---
+inclusion: manual
+description: "Keep a Markdown docs index in sync through pre-commit, CI, or one-off maintenance flows."
+---
+
+
+# docs-index-keeper
+
+Use this skill when a repository keeps docs under `docs/` and needs a Markdown index table updated automatically as docs are added or changed.
+
+## Trigger phrases
+
+- keep a docs index up to date
+- auto-update `docs/README.md`
+- add a pre-commit hook for docs indexing
+- enforce docs index freshness in CI
+- add a specific `docs/*.md` file into a Markdown index table
+
+## Workflow
+
+1. Confirm the repo has a docs directory and an index table such as `| Doc | Purpose |`.
+2. Install the package if it is not already present:
+
+```bash
+npm install -D docs-index-keeper
+```
+
+3. Initialize the hook:
+
+```bash
+npx docs-index-keeper init
+```
+
+4. For CI enforcement, run:
+
+```bash
+npx docs-index-keeper check
+```
+
+5. For one-off staged maintenance, run:
+
+```bash
+npx docs-index-keeper update
+```
+
+## Notes
+
+- `update` operates on staged Markdown files.
+- `check` exits non-zero when the index is missing entries for staged docs.
+- Purpose text comes from the first Markdown heading when available.
+- New rows are inserted before an archive sentinel row when present.