@olegkoval/agent-skills 1.0.0-beta.1

package/packages/marketing/viral-launch/SKILL.md

@@ -0,0 +1,101 @@
+---
+
+name: viral-launch
+description: Set up a project repository and launch plan for shareable marketing, public launch readiness, and growth loops without pretending virality is guaranteed.
+compatibility: Codex, Claude Code, Cursor, GitHub Copilot, and other Agent Skills compatible tools. Useful for product repos, open-source packages, SaaS launches, waitlists, and creator tools.
+metadata:
+  author: Oleg Koval
+  tags:
+    - marketing
+    - launch
+    - growth
+    - virality
+    - positioning
+    - github
+
+---
+
+# viral-launch
+
+Use this skill when a user wants to launch a project, make a repo marketable, improve discoverability, or build shareable launch assets.
+
+This skill is opinionated: virality is not a promise. The goal is to make the project easy to understand, easy to share, and easy to act on.
+
+## Trigger phrases
+
+- make this repo launch-ready
+- set this up to go viral
+- prepare a product launch
+- create marketing assets for this project
+- improve the README for launch
+- prepare Product Hunt / Hacker News / X / LinkedIn launch copy
+- set up an open-source repo for growth
+
+## Workflow
+
+1. Inspect the project first:
+  - product purpose
+  - target user
+  - core use case
+  - current README and docs
+  - install or demo path
+  - screenshots, videos, or visual proof
+  - analytics or waitlist capture if present
+2. Define the launch angle in one sentence:
+  - who it is for
+  - what painful job it solves
+  - why now
+  - what makes it different
+3. Make the repo launch-ready:
+  - clear README headline and first paragraph
+  - demo or quickstart within the first screen
+  - installation steps that work from a clean checkout
+  - screenshots, GIF, or demo link where possible
+  - feature list based on outcomes, not implementation trivia
+  - examples for the highest-intent use cases
+  - badges only when they add trust
+  - license, contributing notes, and issue templates when useful
+4. Create launch assets:
+  - short tagline
+  - 1-paragraph announcement
+  - 5 social post variants
+  - Product Hunt tagline and description when relevant
+  - Hacker News title candidates when relevant
+  - launch email or DM when relevant
+  - creator/influencer outreach list criteria, not spam copy
+5. Design share loops:
+  - a reason users would show the output to someone else
+  - a public artifact worth linking
+  - a before/after demo
+  - a template, benchmark, checklist, or gallery that can travel
+  - referral or waitlist loop only if it fits the product
+6. Define proof and metrics:
+  - activation event
+  - share event
+  - conversion event
+  - retention proxy
+  - launch-day dashboard or simple tracking checklist
+7. Keep claims grounded:
+  - do not invent traction, logos, benchmarks, testimonials, or user counts
+  - mark assumptions explicitly
+  - prefer specific proof over hype
+  - avoid dark patterns and spam
+
+## Output format
+
+When planning, produce:
+
+- Launch angle
+- Repo changes
+- Launch assets
+- Share loops
+- Metrics
+- Risks and assumptions
+- Next actions
+
+When editing a repository, make the smallest useful set of changes first, then validate by reading the README from a new user's perspective.
+
+## References
+
+- `references/launch-checklist.md`
+- `references/external-skills.md`

package/packages/marketing/viral-launch/adapters/claude/plugin.json

@@ -0,0 +1,10 @@
+{
+  "name": "olko:viral-launch",
+  "description": "Set up a project repository and launch plan for shareable marketing, public launch readiness, and growth loops.",
+  "skills": [
+    {
+      "name": "olko:viral-launch",
+      "source": "../../SKILL.md"
+    }
+  ]
+}

package/packages/marketing/viral-launch/adapters/codex/README.md

@@ -0,0 +1,3 @@
+# Codex adapter
+
+Use the canonical skill directly from `packages/marketing/viral-launch/SKILL.md`.

package/packages/marketing/viral-launch/adapters/cursor/plugin.json

@@ -0,0 +1,6 @@
+{
+  "name": "olko:viral-launch",
+  "version": "0.1.0",
+  "description": "Set up a project repository and launch plan for shareable marketing, public launch readiness, and growth loops.",
+  "skills": "skills/"
+}

package/packages/marketing/viral-launch/adapters/cursor/skills/viral-launch/SKILL.md

@@ -0,0 +1,103 @@
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+---
+
+name: viral-launch
+description: Set up a project repository and launch plan for shareable marketing, public launch readiness, and growth loops without pretending virality is guaranteed.
+compatibility: Codex, Claude Code, Cursor, GitHub Copilot, and other Agent Skills compatible tools. Useful for product repos, open-source packages, SaaS launches, waitlists, and creator tools.
+metadata:
+  author: Oleg Koval
+  tags:
+    - marketing
+    - launch
+    - growth
+    - virality
+    - positioning
+    - github
+
+---
+
+# viral-launch
+
+Use this skill when a user wants to launch a project, make a repo marketable, improve discoverability, or build shareable launch assets.
+
+This skill is opinionated: virality is not a promise. The goal is to make the project easy to understand, easy to share, and easy to act on.
+
+## Trigger phrases
+
+- make this repo launch-ready
+- set this up to go viral
+- prepare a product launch
+- create marketing assets for this project
+- improve the README for launch
+- prepare Product Hunt / Hacker News / X / LinkedIn launch copy
+- set up an open-source repo for growth
+
+## Workflow
+
+1. Inspect the project first:
+  - product purpose
+  - target user
+  - core use case
+  - current README and docs
+  - install or demo path
+  - screenshots, videos, or visual proof
+  - analytics or waitlist capture if present
+2. Define the launch angle in one sentence:
+  - who it is for
+  - what painful job it solves
+  - why now
+  - what makes it different
+3. Make the repo launch-ready:
+  - clear README headline and first paragraph
+  - demo or quickstart within the first screen
+  - installation steps that work from a clean checkout
+  - screenshots, GIF, or demo link where possible
+  - feature list based on outcomes, not implementation trivia
+  - examples for the highest-intent use cases
+  - badges only when they add trust
+  - license, contributing notes, and issue templates when useful
+4. Create launch assets:
+  - short tagline
+  - 1-paragraph announcement
+  - 5 social post variants
+  - Product Hunt tagline and description when relevant
+  - Hacker News title candidates when relevant
+  - launch email or DM when relevant
+  - creator/influencer outreach list criteria, not spam copy
+5. Design share loops:
+  - a reason users would show the output to someone else
+  - a public artifact worth linking
+  - a before/after demo
+  - a template, benchmark, checklist, or gallery that can travel
+  - referral or waitlist loop only if it fits the product
+6. Define proof and metrics:
+  - activation event
+  - share event
+  - conversion event
+  - retention proxy
+  - launch-day dashboard or simple tracking checklist
+7. Keep claims grounded:
+  - do not invent traction, logos, benchmarks, testimonials, or user counts
+  - mark assumptions explicitly
+  - prefer specific proof over hype
+  - avoid dark patterns and spam
+
+## Output format
+
+When planning, produce:
+
+- Launch angle
+- Repo changes
+- Launch assets
+- Share loops
+- Metrics
+- Risks and assumptions
+- Next actions
+
+When editing a repository, make the smallest useful set of changes first, then validate by reading the README from a new user's perspective.
+
+## References
+
+- `references/launch-checklist.md`
+- `references/external-skills.md`

package/packages/marketing/viral-launch/references/external-skills.md

@@ -0,0 +1,12 @@
+# External skills
+
+Skill search found these related launch and marketing skills:
+
+- `coreyhaines31/marketingskills@launch-strategy` - broad launch strategy skill, about 37K installs in Skills CLI search; source repo `coreyhaines31/marketingskills` has about 20K GitHub stars.
+- `refoundai/lenny-skills@launch-marketing` - product management and launch marketing skill, under 1K installs in Skills CLI search.
+
+Prefer this local `olko:viral-launch` skill when the work is specifically to make a repository launch-ready. Consider installing `coreyhaines31/marketingskills@launch-strategy` when the user wants a broader marketing strategy workflow:
+
+```bash
+npx skills add coreyhaines31/marketingskills@launch-strategy -g -y
+```

package/packages/marketing/viral-launch/references/launch-checklist.md

@@ -0,0 +1,42 @@
+# Launch checklist
+
+Use this checklist before calling a project launch-ready.
+
+## Repo
+
+- README headline says what the project does and for whom.
+- First screen contains a demo, screenshot, or quickstart.
+- Install steps work from a clean checkout.
+- Examples cover the highest-intent use cases.
+- License and contribution expectations are clear.
+- Known limitations are stated without weakening the launch angle.
+
+## Message
+
+- One-sentence positioning is specific.
+- The hook names a real problem or desire.
+- Differentiation is concrete.
+- Claims are backed by repo content, screenshots, demos, benchmarks, or examples.
+- Copy avoids fake urgency, fake social proof, and generic hype.
+
+## Distribution
+
+- Launch channels are chosen for the actual audience.
+- Each channel gets native copy, not pasted generic copy.
+- Assets include at least one short post, one longer post, and one direct outreach note.
+- Launch timing includes a response window for comments, issues, and feedback.
+
+## Shareability
+
+- There is a public artifact people can link to.
+- The demo shows a before/after or clear transformation.
+- Users have a reason to share the output, not only the product.
+- Any referral or waitlist mechanism is tied to user value.
+
+## Metrics
+
+- Activation event is defined.
+- Share event is defined.
+- Conversion event is defined.
+- Feedback collection path is defined.
+- Launch review date is defined before launch.

package/packages/music/fill-music-player/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Oleg Koval
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/packages/music/fill-music-player/SKILL.md

@@ -0,0 +1,108 @@
+---
+name: fill-music-player
+description: Use when a user wants to fill a portable music player (Walkman, iPod, USB drive) with a curated random selection from a music library on a NAS or local directory. Handles format filtering, artist/album diversity balancing, and size targeting.
+license: MIT
+compatibility: Codex, Claude Code, Cursor, and other Agent Skills compatible tools. Requires shell access and the fill-music-player CLI or underlying script in the target environment.
+metadata:
+  author: Oleg Koval
+  tags:
+    - music
+    - media
+    - curation
+    - copy
+    - cli
+---
+
+# fill-music-player
+
+Curates a DJ-balanced selection of tracks from a source music library and copies them to a portable player, respecting device capacity and supported formats.
+
+## Quick Reference
+
+```bash
+# Dry run first (always recommend this)
+fill-music-player --source /Volumes/music --dest /Volumes/WALKMAN/MUSIC --dry-run
+
+# Copy for real
+fill-music-player --source /Volumes/music --dest /Volumes/WALKMAN/MUSIC
+
+# Or run the script directly with uv
+uv run fill_music_player.py --source ~/Music --dest /Volumes/USB --dry-run
+```
+
+Run `fill-music-player --help` for all options.
+
+## Key Parameters
+
+| Flag | Default | Purpose |
+|------|---------|---------|
+| `--source` / `-s` | required | Source music root (NAS mount, ~/Music, etc.) |
+| `--dest` / `-d` | required | Player destination directory |
+| `--target-gb` | 95% of free space | How many GB to fill |
+| `--formats` | mp3,m4a,wma,aac | Allowed extensions |
+| `--max-per-artist` | 4 | Artist diversity cap |
+| `--max-per-album` | 3 | Album diversity cap |
+| `--skip-dirs` | (none) | Top-level dirs to skip |
+| `--dry-run` | false | Preview without copying |
+
+## Workflow
+
+1. Always do `--dry-run` first
+2. Review the per-genre breakdown
+3. Adjust `--skip-dirs`, `--max-file-mb`, or `--max-per-artist` if needed
+4. Run without `--dry-run` to copy
+
+## Device Formats
+
+| Device | Recommended `--formats` |
+|--------|------------------------|
+| Sony Walkman NWZ series | `mp3,m4a,wma` |
+| iPod (classic/nano) | `mp3,m4a,aac` |
+| Generic USB player | `mp3` |
+| Any modern player | `mp3,m4a,wma,aac,ogg,flac` |
+
+## Edge Cases and Troubleshooting
+
+| Situation | What happens | Fix |
+|-----------|-------------|-----|
+| NAS disconnects mid-copy | Copy fails for that file, logged as error, continues with next track | Re-run; already-copied files are skipped (`if not dst.exists()`) |
+| Source has only FLAC/lossless | 0 files selected (FLAC not in default formats) | Use `--formats flac` or `--formats mp3,flac` |
+| FAT32 filename too long or illegal chars | Filenames are sanitized: `<>:"/\|?*` replaced with `_`, truncated to 80 chars | Automatic — no action needed |
+| Mixed/broken ID3 tags | Falls back to folder name parsing (`Genre/Artist - Album/track.mp3`) | Works transparently; folder structure is the reliable fallback |
+| Very large files (DJ mixes, radio shows) | Skipped by default (>20 MB) | Adjust with `--max-file-mb 50` to include mixes |
+| Tiny files (jingles, corrupt) | Skipped by default (<300 KB) | Adjust with `--min-file-kb 100` to be more permissive |
+| One artist dominates the library | Capped at 4 tracks per artist, 3 per album | Lower with `--max-per-artist 2` for more variety |
+| Empty genre directories | Silently skipped, no error | Normal behavior |
+| Destination already has files | Existing files are not overwritten or deleted; new tracks added alongside | Clear destination first if you want a fresh set |
+| SMB/NFS mount is slow | Scanning with mutagen tag reading can take 5-10 min for large libraries | Expected; the dry-run output appears once scanning completes |
+
+## Real-World Example
+
+Filling a **Sony Walkman NWZ-B183F (4 GB)** from a **Synology DS918+ NAS** with ~9,000 tracks across blues, funk, hip-hop, soul, IDM, dubstep, dub, indie, and post-rock:
+
+```bash
+# Step 1: Preview
+fill-music-player \
+  --source /Volumes/music \
+  --dest /Volumes/WALKMAN/MUSIC \
+  --skip-dirs "jingles,!recordings,!restored,dubrecords" \
+  --formats mp3,m4a,wma \
+  --dry-run
+
+# Output:
+#   Found 8914 candidate tracks across 14 genres
+#   Funk     →  86 tracks  (440.8 MB)
+#   blues    →  38 tracks  (316.7 MB)
+#   hiphop   →  33 tracks  (234.7 MB)
+#   ...
+#   Selected 348 tracks  (2473.0 MB)
+
+# Step 2: Copy
+fill-music-player \
+  --source /Volumes/music \
+  --dest /Volumes/WALKMAN/MUSIC \
+  --skip-dirs "jingles,!recordings,!restored,dubrecords" \
+  --formats mp3,m4a,wma
+```
+
+Result: 348 tracks, 2.4 GB, balanced across 14 genres with max 4 tracks per artist. Artists included Fela Kuti, ZZ Top, Mobb Deep, Gregory Porter, Tinariwen, Chick Corea, Hudson Mohawke, and Funkadelic. Total copy time over SMB: ~12 minutes.

package/packages/music/fill-music-player/adapters/claude/plugin.json

@@ -0,0 +1,10 @@
+{
+  "name": "olko:fill-music-player",
+  "description": "Fill a portable music player with a curated random selection from a source music library.",
+  "skills": [
+    {
+      "name": "olko:fill-music-player",
+      "source": "../../SKILL.md"
+    }
+  ]
+}

package/packages/music/fill-music-player/adapters/codex/README.md

@@ -0,0 +1,3 @@
+# Codex adapter
+
+Use the canonical skill directly from `packages/music/fill-music-player/SKILL.md`.

package/packages/music/fill-music-player/adapters/cursor/plugin.json

@@ -0,0 +1,6 @@
+{
+  "name": "olko:fill-music-player",
+  "version": "0.1.0",
+  "description": "Fill a portable music player with a curated random selection from a source music library.",
+  "skills": "skills/"
+}

package/packages/music/fill-music-player/adapters/cursor/skills/fill-music-player/SKILL.md

@@ -0,0 +1,110 @@
+<!-- Generated by scripts/build-adapters.sh. Do not edit directly. -->
+
+---
+name: fill-music-player
+description: Use when a user wants to fill a portable music player (Walkman, iPod, USB drive) with a curated random selection from a music library on a NAS or local directory. Handles format filtering, artist/album diversity balancing, and size targeting.
+license: MIT
+compatibility: Codex, Claude Code, Cursor, and other Agent Skills compatible tools. Requires shell access and the fill-music-player CLI or underlying script in the target environment.
+metadata:
+  author: Oleg Koval
+  tags:
+    - music
+    - media
+    - curation
+    - copy
+    - cli
+---
+
+# fill-music-player
+
+Curates a DJ-balanced selection of tracks from a source music library and copies them to a portable player, respecting device capacity and supported formats.
+
+## Quick Reference
+
+```bash
+# Dry run first (always recommend this)
+fill-music-player --source /Volumes/music --dest /Volumes/WALKMAN/MUSIC --dry-run
+
+# Copy for real
+fill-music-player --source /Volumes/music --dest /Volumes/WALKMAN/MUSIC
+
+# Or run the script directly with uv
+uv run fill_music_player.py --source ~/Music --dest /Volumes/USB --dry-run
+```
+
+Run `fill-music-player --help` for all options.
+
+## Key Parameters
+
+| Flag | Default | Purpose |
+|------|---------|---------|
+| `--source` / `-s` | required | Source music root (NAS mount, ~/Music, etc.) |
+| `--dest` / `-d` | required | Player destination directory |
+| `--target-gb` | 95% of free space | How many GB to fill |
+| `--formats` | mp3,m4a,wma,aac | Allowed extensions |
+| `--max-per-artist` | 4 | Artist diversity cap |
+| `--max-per-album` | 3 | Album diversity cap |
+| `--skip-dirs` | (none) | Top-level dirs to skip |
+| `--dry-run` | false | Preview without copying |
+
+## Workflow
+
+1. Always do `--dry-run` first
+2. Review the per-genre breakdown
+3. Adjust `--skip-dirs`, `--max-file-mb`, or `--max-per-artist` if needed
+4. Run without `--dry-run` to copy
+
+## Device Formats
+
+| Device | Recommended `--formats` |
+|--------|------------------------|
+| Sony Walkman NWZ series | `mp3,m4a,wma` |
+| iPod (classic/nano) | `mp3,m4a,aac` |
+| Generic USB player | `mp3` |
+| Any modern player | `mp3,m4a,wma,aac,ogg,flac` |
+
+## Edge Cases and Troubleshooting
+
+| Situation | What happens | Fix |
+|-----------|-------------|-----|
+| NAS disconnects mid-copy | Copy fails for that file, logged as error, continues with next track | Re-run; already-copied files are skipped (`if not dst.exists()`) |
+| Source has only FLAC/lossless | 0 files selected (FLAC not in default formats) | Use `--formats flac` or `--formats mp3,flac` |
+| FAT32 filename too long or illegal chars | Filenames are sanitized: `<>:"/\|?*` replaced with `_`, truncated to 80 chars | Automatic — no action needed |
+| Mixed/broken ID3 tags | Falls back to folder name parsing (`Genre/Artist - Album/track.mp3`) | Works transparently; folder structure is the reliable fallback |
+| Very large files (DJ mixes, radio shows) | Skipped by default (>20 MB) | Adjust with `--max-file-mb 50` to include mixes |
+| Tiny files (jingles, corrupt) | Skipped by default (<300 KB) | Adjust with `--min-file-kb 100` to be more permissive |
+| One artist dominates the library | Capped at 4 tracks per artist, 3 per album | Lower with `--max-per-artist 2` for more variety |
+| Empty genre directories | Silently skipped, no error | Normal behavior |
+| Destination already has files | Existing files are not overwritten or deleted; new tracks added alongside | Clear destination first if you want a fresh set |
+| SMB/NFS mount is slow | Scanning with mutagen tag reading can take 5-10 min for large libraries | Expected; the dry-run output appears once scanning completes |
+
+## Real-World Example
+
+Filling a **Sony Walkman NWZ-B183F (4 GB)** from a **Synology DS918+ NAS** with ~9,000 tracks across blues, funk, hip-hop, soul, IDM, dubstep, dub, indie, and post-rock:
+
+```bash
+# Step 1: Preview
+fill-music-player \
+  --source /Volumes/music \
+  --dest /Volumes/WALKMAN/MUSIC \
+  --skip-dirs "jingles,!recordings,!restored,dubrecords" \
+  --formats mp3,m4a,wma \
+  --dry-run
+
+# Output:
+#   Found 8914 candidate tracks across 14 genres
+#   Funk     →  86 tracks  (440.8 MB)
+#   blues    →  38 tracks  (316.7 MB)
+#   hiphop   →  33 tracks  (234.7 MB)
+#   ...
+#   Selected 348 tracks  (2473.0 MB)
+
+# Step 2: Copy
+fill-music-player \
+  --source /Volumes/music \
+  --dest /Volumes/WALKMAN/MUSIC \
+  --skip-dirs "jingles,!recordings,!restored,dubrecords" \
+  --formats mp3,m4a,wma
+```
+
+Result: 348 tracks, 2.4 GB, balanced across 14 genres with max 4 tracks per artist. Artists included Fela Kuti, ZZ Top, Mobb Deep, Gregory Porter, Tinariwen, Chick Corea, Hudson Mohawke, and Funkadelic. Total copy time over SMB: ~12 minutes.

package/packages/photography/gallery/.skillfish.json

@@ -0,0 +1,10 @@
+{
+  "version": 2,
+  "name": "gallery",
+  "owner": "chufucious",
+  "repo": "chu-gallery-plugin",
+  "path": "skills/gallery",
+  "branch": "main",
+  "sha": "24083efe2eb3c38bcf8960276d37fd98fb94ba16",
+  "source": "manual"
+}