@olegkoval/agent-skills 1.6.0 → 1.7.0

package/packages/software-development/ai-tools-setup/adapters/windsurf/rules/ai-tools-setup.md

@@ -0,0 +1,262 @@
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+---
+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/packages/software-development/changelog-generator/SKILL.md

@@ -1,7 +1,9 @@
 ---
 name: changelog-generator
 description: Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
-compatibility: Codex, Claude Code, Cursor, and other Agent Skills compatible tools. Requires git history access in the target repository.
+license: MIT
+allowed-tools: Bash, Read, Write
+compatibility: Codex, Claude Code, Cursor, GitHub Copilot, Windsurf, Kiro, and other Agent Skills compatible tools. Requires git history access in the target repository.
 metadata:
   author: Oleg Koval
   tags:

package/packages/software-development/changelog-generator/adapters/claude/skills/changelog-generator/SKILL.md

@@ -3,7 +3,9 @@
 ---
 name: changelog-generator
 description: Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
-compatibility: Codex, Claude Code, Cursor, and other Agent Skills compatible tools. Requires git history access in the target repository.
+license: MIT
+allowed-tools: Bash, Read, Write
+compatibility: Codex, Claude Code, Cursor, GitHub Copilot, Windsurf, Kiro, and other Agent Skills compatible tools. Requires git history access in the target repository.
 metadata:
   author: Oleg Koval
   tags:

package/packages/software-development/changelog-generator/adapters/cursor/skills/changelog-generator/SKILL.md

@@ -3,7 +3,9 @@
 ---
 name: changelog-generator
 description: Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
-compatibility: Codex, Claude Code, Cursor, and other Agent Skills compatible tools. Requires git history access in the target repository.
+license: MIT
+allowed-tools: Bash, Read, Write
+compatibility: Codex, Claude Code, Cursor, GitHub Copilot, Windsurf, Kiro, and other Agent Skills compatible tools. Requires git history access in the target repository.
 metadata:
   author: Oleg Koval
   tags:

package/packages/software-development/changelog-generator/adapters/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/packages/software-development/changelog-generator/adapters/windsurf/rules/changelog-generator.md

@@ -0,0 +1,105 @@
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+---
+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/packages/software-development/cloudflare-block-countries/SKILL.md

@@ -3,7 +3,7 @@ name: cloudflare-block-countries
 description: 'Block specific countries via Cloudflare WAF Custom Rules using the Cloudflare API. Use when user wants to geo-block traffic, block countries in Cloudflare, set up WAF country rules, or mentions blocking regions. Handles both creating new rulesets and updating existing ones.'
 license: MIT
 allowed-tools: Bash
-compatibility: Codex, Claude Code, Cursor, and other Agent Skills compatible tools. Requires curl and jq.
+compatibility: Codex, Claude Code, Cursor, GitHub Copilot, Windsurf, Kiro, and other Agent Skills compatible tools. Requires curl and jq.
 metadata:
   author: Oleg Koval
   tags:

package/packages/software-development/cloudflare-block-countries/adapters/claude/skills/cloudflare-block-countries/SKILL.md

@@ -5,7 +5,7 @@ name: cloudflare-block-countries
 description: 'Block specific countries via Cloudflare WAF Custom Rules using the Cloudflare API. Use when user wants to geo-block traffic, block countries in Cloudflare, set up WAF country rules, or mentions blocking regions. Handles both creating new rulesets and updating existing ones.'
 license: MIT
 allowed-tools: Bash
-compatibility: Codex, Claude Code, Cursor, and other Agent Skills compatible tools. Requires curl and jq.
+compatibility: Codex, Claude Code, Cursor, GitHub Copilot, Windsurf, Kiro, and other Agent Skills compatible tools. Requires curl and jq.
 metadata:
   author: Oleg Koval
   tags:

package/packages/software-development/cloudflare-block-countries/adapters/cursor/skills/cloudflare-block-countries/SKILL.md

@@ -5,7 +5,7 @@ name: cloudflare-block-countries
 description: 'Block specific countries via Cloudflare WAF Custom Rules using the Cloudflare API. Use when user wants to geo-block traffic, block countries in Cloudflare, set up WAF country rules, or mentions blocking regions. Handles both creating new rulesets and updating existing ones.'
 license: MIT
 allowed-tools: Bash
-compatibility: Codex, Claude Code, Cursor, and other Agent Skills compatible tools. Requires curl and jq.
+compatibility: Codex, Claude Code, Cursor, GitHub Copilot, Windsurf, Kiro, and other Agent Skills compatible tools. Requires curl and jq.
 metadata:
   author: Oleg Koval
   tags: