shmakk 1.1.0 → 1.2.0

package/skills/logs.md

@@ -0,0 +1,156 @@
+---
+name: logs
+version: 1
+category: system
+---
+
+# Log Analysis
+
+Parse, search, and analyze log files to find errors, diagnose issues, and understand activity.
+
+## When to use this skill
+
+- User wants to find errors or exceptions in logs
+- User wants to understand what happened at a specific time
+- User wants to see activity patterns or anomalies
+- User asks about "logs", "errors", "what happened", "why did it crash", "exceptions"
+
+## Procedure
+
+### Step 1: Locate the logs
+
+Common log locations:
+```
+/var/log/syslog          # system log (Debian/Ubuntu)
+/var/log/messages        # system log (RHEL/CentOS)
+journalctl               # systemd journal (modern Linux)
+/var/log/nginx/          # nginx access and error logs
+/var/log/apache2/        # apache logs
+~/.local/share/          # user application logs
+./logs/                  # application-local logs
+```
+
+Check recent files:
+```
+ls -lt /var/log/ | head -20
+find . -name "*.log" -newer /tmp -type f 2>/dev/null
+```
+
+### Step 2: Quick error scan
+
+```
+grep -i "error\|exception\|fatal\|critical\|panic\|fail" logfile.log | tail -50
+```
+
+For systemd:
+```
+journalctl -p err --since "1 hour ago"
+journalctl -p err --since "2024-01-15 12:00" --until "2024-01-15 13:00"
+```
+
+### Step 3: Find errors around a specific time
+
+```
+grep "2024-01-15 14:3" logfile.log         # all events in that minute range
+awk '/14:30/,/14:35/' logfile.log           # events between two times
+```
+
+### Step 4: Count error frequency
+
+```
+grep -i "error" logfile.log | awk '{print $5}' | sort | uniq -c | sort -rn | head -20
+```
+
+Find repeated error patterns:
+```
+grep -i "error" logfile.log | sed 's/[0-9]\{1,\}/N/g' | sort | uniq -c | sort -rn | head -20
+```
+
+(Replacing numbers with N normalizes "error on line 42" and "error on line 87" into the same pattern)
+
+### Step 5: Analyze access logs (nginx/apache)
+
+```
+# Top requested URLs
+awk '{print $7}' /var/log/nginx/access.log | sort | uniq -c | sort -rn | head -20
+
+# Top IPs
+awk '{print $1}' /var/log/nginx/access.log | sort | uniq -c | sort -rn | head -20
+
+# HTTP errors (4xx, 5xx)
+awk '$9 ~ /^[45]/' /var/log/nginx/access.log | tail -50
+
+# Requests per minute (traffic pattern)
+awk '{print $4}' /var/log/nginx/access.log | cut -d: -f1,2 | sort | uniq -c
+```
+
+### Step 6: Follow live logs
+
+```
+tail -f logfile.log                         # follow
+tail -f logfile.log | grep -i error         # follow with filter
+journalctl -f -u service-name              # follow systemd service
+```
+
+### Step 7: Application stack traces
+
+For multi-line stack traces (Java, Python, Node.js):
+```
+# Python tracebacks
+grep -A 20 "Traceback" logfile.log | head -100
+
+# Node.js errors  
+grep -A 10 "Error:" logfile.log | head -100
+
+# Java exceptions
+grep -A 15 "Exception" logfile.log | head -100
+```
+
+### Step 8: Large log files
+
+For files too large to read entirely:
+```
+wc -l logfile.log                  # count lines
+head -100 logfile.log              # first 100 lines
+tail -500 logfile.log              # last 500 lines
+grep -n "keyword" logfile.log | head -20  # find line numbers, then read_file with offset
+```
+
+## Output format
+
+```
+LOG ANALYSIS: /var/log/nginx/error.log (last 24h)
+
+SUMMARY
+Total log lines: 84,312
+Error lines: 1,247 (1.5%)
+Time range: 2024-01-14 14:00 → 2024-01-15 14:00
+
+TOP ERRORS (by frequency)
+  847×  "connect() failed (111: Connection refused) while connecting to upstream"
+        → App server on :3000 was unreachable. Spikes at 02:15 and 09:45.
+  312×  "open() failed (13: Permission denied) while reading upstream response header"
+        → File permission issue. All from same endpoint: /api/export
+   88×  "upstream timed out (110: Connection timed out)"
+        → Occasional timeouts. Check if correlated with high load periods.
+
+TIMELINE
+  02:15-02:22  — 847 connection refused errors. App server crash/restart?
+  09:45-09:47  — Another spike of 120 connection errors. Investigate restart cycle.
+
+RECOMMENDED INVESTIGATION
+1. Check what happened at 02:15 — look at app logs: journalctl -u myapp --since "02:10" --until "02:30"
+2. Fix file permissions for /api/export endpoint
+3. Set up process supervisor (systemd) to auto-restart app on crash
+```
+
+## Pitfalls
+
+- Log timestamps may be in UTC — convert to local time before presenting to user
+- Large log files: don't try to read them entirely — sample and search
+- Some errors are expected/benign — distinguish new errors from known background noise
+- Rotating logs: `logfile.log.1`, `.gz` files may contain relevant history; check if needed
+
+## Verification
+
+After identifying an error: confirm the error is real by reading the surrounding context (not just the error line in isolation).

package/skills/marketing.md

@@ -0,0 +1,139 @@
+---
+name: marketing
+version: 1
+category: business
+---
+
+# Marketing & Growth
+
+Content strategy, copywriting, SEO analysis, campaign planning, and audience development.
+
+## When to use this skill
+
+- User wants to write marketing copy, ads, or promotional content
+- User wants to develop a content strategy or editorial calendar
+- User wants to analyze or improve SEO for a page or site
+- User wants to plan a launch, campaign, or growth initiative
+- User asks about audience, positioning, messaging, or brand voice
+- User mentions "marketing", "copy", "SEO", "campaign", "launch", "audience", "growth"
+
+## Core Marketing Frameworks
+
+### Positioning statement
+
+Before writing any copy, establish positioning:
+```
+For [target audience], [product] is the [category] that [key benefit]
+because [reason to believe].
+```
+
+Ask the user for this if they haven't articulated it. All copy flows from clear positioning.
+
+### Message hierarchy
+
+1. **Primary message** — the single most important thing to communicate
+2. **Supporting messages** — 3-5 proof points or benefits
+3. **Call to action** — what you want the reader to do next
+
+Keep this hierarchy in mind for every piece of content.
+
+## Procedure
+
+### Writing marketing copy
+
+**Before writing, gather:**
+- Target audience (who specifically is this for?)
+- Key benefit (what's the most compelling reason to care?)
+- Tone (professional, casual, bold, warm?)
+- Constraints (character limits, format requirements)
+- Existing examples (what does the user like?)
+
+**Copy formula — AIDA:**
+- **Attention**: Hook that stops the scroll
+- **Interest**: Why this matters to them
+- **Desire**: Paint the picture of a better outcome
+- **Action**: Clear, specific CTA
+
+**Headline writing:**
+- Lead with the benefit, not the feature
+- Use numbers when possible ("5 ways to...", "3x faster")
+- Create curiosity gaps or specificity
+- Write 5-10 options and evaluate
+
+### SEO analysis
+
+Analyze a page's SEO health:
+```
+fetch_url("https://example.com/page")
+```
+
+Check for:
+- Title tag: 50-60 chars, includes primary keyword
+- Meta description: 150-160 chars, compelling with keyword
+- H1: present, includes keyword, matches search intent
+- URL structure: clean, descriptive, keyword-included
+- Content: keyword used naturally, comprehensive topic coverage
+- Internal links: to related content
+- Image alt text: descriptive with keyword where natural
+- Page speed: check for large images or blocking scripts
+
+For keyword research, search:
+```
+web_search("keyword research tool free")
+web_search("[topic] keyword volume search intent")
+```
+
+### Content strategy
+
+**For a content calendar, identify:**
+1. Content pillars (3-5 main topics you'll own)
+2. Content types (blog, video, social, email, etc.)
+3. Publishing cadence (realistic for the team)
+4. Distribution channels (where the audience lives)
+
+**Content ideas by intent:**
+- Awareness: "What is X", "Why X matters", trend pieces
+- Consideration: "How to choose", comparisons, case studies
+- Decision: testimonials, demos, free trials, pricing
+
+### Campaign planning
+
+**Campaign structure:**
+1. **Objective** — what measurable outcome (signups, revenue, awareness)?
+2. **Target segment** — exactly who?
+3. **Core offer** — what are we giving them?
+4. **Channels** — where will we reach them?
+5. **Messaging** — primary message per channel
+6. **Timeline** — pre-launch, launch, follow-up phases
+7. **Success metrics** — how will we know it worked?
+
+### Social media copy
+
+Platform-specific guidance:
+- **LinkedIn**: Professional tone, insights over promotion, longer posts work well, add relevant hashtags (3-5)
+- **Twitter/X**: Punchy, opinionated, conversational; threads for depth; 1-2 hashtags max
+- **Instagram**: Story-first, visual-led, caption reinforces image; use all 30 hashtags in first comment
+- **Email newsletter**: Clear subject line, personal tone, single clear CTA per email
+
+## Output format
+
+**Copy deliverables:** provide multiple variations (at least 3) so the user can choose and refine.
+
+**Strategy documents:** use clear headers, bullet points, and concrete examples. Avoid vague advice.
+
+**Campaign plans:** structured table or numbered list with owner, deadline, and metric per item.
+
+## Pitfalls
+
+- Don't write copy before understanding the audience — generic copy doesn't convert
+- Avoid jargon and superlatives ("best", "revolutionary", "world-class") — be specific instead
+- More features ≠ better copy. Focus on the one benefit that matters most to this audience
+- SEO: don't keyword-stuff. Write for humans first, optimize for search second
+- Marketing claims should be accurate — don't overstate capabilities or outcomes
+- Always check if there are brand guidelines or existing voice/tone docs before writing
+
+## Verification
+
+**Copy:** read it aloud — if it sounds stiff or unnatural, revise it.
+**SEO recommendations:** verify with `fetch_url` after changes to confirm implementation.
+**Campaign plan:** confirm every item has an owner and a measurable success metric.

package/skills/media-image-manipulation-image-magick.md

@@ -0,0 +1,253 @@
+---
+name: image-manipulation-image-magick
+description: Process and manipulate images using ImageMagick. Supports resizing, format conversion, batch processing, and retrieving image metadata. Use when working with images, creating thumbnails, resizing wallpapers, or performing batch image operations.
+compatibility: Requires ImageMagick installed and available as `magick` on PATH. Cross-platform examples provided for PowerShell (Windows) and Bash (Linux/macOS).
+category: media
+---
+
+# Image Manipulation with ImageMagick
+
+This skill enables image processing and manipulation tasks using ImageMagick
+across Windows, Linux, and macOS systems.
+
+## When to Use This Skill
+
+Use this skill when you need to:
+
+- Resize images (single or batch)
+- Get image dimensions and metadata
+- Convert between image formats
+- Create thumbnails
+- Process wallpapers for different screen sizes
+- Batch process multiple images with specific criteria
+
+## Prerequisites
+
+- ImageMagick installed on the system
+- **Windows**: PowerShell with ImageMagick available as `magick` (or at `C:\Program Files\ImageMagick-*\magick.exe`)
+- **Linux/macOS**: Bash with ImageMagick installed via package manager (`apt`, `brew`, etc.)
+
+## Core Capabilities
+
+### 1. Image Information
+
+- Get image dimensions (width x height)
+- Retrieve detailed metadata (format, color space, etc.)
+- Identify image format
+
+### 2. Image Resizing
+
+- Resize single images
+- Batch resize multiple images
+- Create thumbnails with specific dimensions
+- Maintain aspect ratios
+
+### 3. Batch Processing
+
+- Process images based on dimensions
+- Filter and process specific file types
+- Apply transformations to multiple files
+
+## Usage Examples
+
+### Example 0: Resolve `magick` executable
+
+**PowerShell (Windows):**
+```powershell
+# Prefer ImageMagick on PATH
+$magick = (Get-Command magick -ErrorAction SilentlyContinue)?.Source
+
+# Fallback: common install pattern under Program Files
+if (-not $magick) {
+    $magick = Get-ChildItem "C:\\Program Files\\ImageMagick-*\\magick.exe" -ErrorAction SilentlyContinue |
+        Select-Object -First 1 -ExpandProperty FullName
+}
+
+if (-not $magick) {
+    throw "ImageMagick not found. Install it and/or add 'magick' to PATH."
+}
+```
+
+**Bash (Linux/macOS):**
+```bash
+# Check if magick is available on PATH
+if ! command -v magick &> /dev/null; then
+    echo "ImageMagick not found. Install it using your package manager:"
+    echo "  Ubuntu/Debian: sudo apt install imagemagick"
+    echo "  macOS: brew install imagemagick"
+    exit 1
+fi
+```
+
+### Example 1: Get Image Dimensions
+
+**PowerShell (Windows):**
+```powershell
+# For a single image
+& $magick identify -format "%wx%h" path/to/image.jpg
+
+# For multiple images
+Get-ChildItem "path/to/images/*" | ForEach-Object { 
+    $dimensions = & $magick identify -format "%f: %wx%h`n" $_.FullName
+    Write-Host $dimensions 
+}
+```
+
+**Bash (Linux/macOS):**
+```bash
+# For a single image
+magick identify -format "%wx%h" path/to/image.jpg
+
+# For multiple images
+for img in path/to/images/*; do
+    magick identify -format "%f: %wx%h\n" "$img"
+done
+```
+
+### Example 2: Resize Images
+
+**PowerShell (Windows):**
+```powershell
+# Resize a single image
+& $magick input.jpg -resize 427x240 output.jpg
+
+# Batch resize images
+Get-ChildItem "path/to/images/*" | ForEach-Object { 
+    & $magick $_.FullName -resize 427x240 "path/to/output/thumb_$($_.Name)"
+}
+```
+
+**Bash (Linux/macOS):**
+```bash
+# Resize a single image
+magick input.jpg -resize 427x240 output.jpg
+
+# Batch resize images
+for img in path/to/images/*; do
+    filename=$(basename "$img")
+    magick "$img" -resize 427x240 "path/to/output/thumb_$filename"
+done
+```
+
+### Example 3: Get Detailed Image Information
+
+**PowerShell (Windows):**
+```powershell
+# Get verbose information about an image
+& $magick identify -verbose path/to/image.jpg
+```
+
+**Bash (Linux/macOS):**
+```bash
+# Get verbose information about an image
+magick identify -verbose path/to/image.jpg
+```
+
+### Example 4: Process Images Based on Dimensions
+
+**PowerShell (Windows):**
+```powershell
+Get-ChildItem "path/to/images/*" | ForEach-Object { 
+    $dimensions = & $magick identify -format "%w,%h" $_.FullName
+    if ($dimensions) {
+        $width,$height = $dimensions -split ','
+        if ([int]$width -eq 2560 -or [int]$height -eq 1440) {
+            Write-Host "Processing $($_.Name)"
+            & $magick $_.FullName -resize 427x240 "path/to/output/thumb_$($_.Name)"
+        }
+    }
+}
+```
+
+**Bash (Linux/macOS):**
+```bash
+for img in path/to/images/*; do
+    dimensions=$(magick identify -format "%w,%h" "$img")
+    if [[ -n "$dimensions" ]]; then
+        width=$(echo "$dimensions" | cut -d',' -f1)
+        height=$(echo "$dimensions" | cut -d',' -f2)
+        if [[ "$width" -eq 2560 || "$height" -eq 1440 ]]; then
+            filename=$(basename "$img")
+            echo "Processing $filename"
+            magick "$img" -resize 427x240 "path/to/output/thumb_$filename"
+        fi
+    fi
+done
+```
+
+## Guidelines
+
+1. **Always quote file paths** - Use quotes around file paths that might contain spaces
+2. **Use the `&` operator (PowerShell)** - Invoke the magick executable using `&` in PowerShell
+3. **Store the path in a variable (PowerShell)** - Assign the ImageMagick path to `$magick` for cleaner code
+4. **Wrap in loops** - When processing multiple files, use `ForEach-Object` (PowerShell) or `for` loops (Bash)
+5. **Verify dimensions first** - Check image dimensions before processing to avoid unnecessary operations
+6. **Use appropriate resize flags** - Consider using `!` to force exact dimensions or `^` for minimum dimensions
+
+## Common Patterns
+
+### PowerShell Patterns
+
+#### Pattern: Store ImageMagick Path
+
+```powershell
+$magick = (Get-Command magick).Source
+```
+
+#### Pattern: Get Dimensions as Variables
+
+```powershell
+$dimensions = & $magick identify -format "%w,%h" $_.FullName
+$width,$height = $dimensions -split ','
+```
+
+#### Pattern: Conditional Processing
+
+```powershell
+if ([int]$width -gt 1920) {
+    & $magick $_.FullName -resize 1920x1080 $outputPath
+}
+```
+
+#### Pattern: Create Thumbnails
+
+```powershell
+& $magick $_.FullName -resize 427x240 "thumbnails/thumb_$($_.Name)"
+```
+
+### Bash Patterns
+
+#### Pattern: Check ImageMagick Installation
+
+```bash
+command -v magick &> /dev/null || { echo "ImageMagick required"; exit 1; }
+```
+
+#### Pattern: Get Dimensions as Variables
+
+```bash
+dimensions=$(magick identify -format "%w,%h" "$img")
+width=$(echo "$dimensions" | cut -d',' -f1)
+height=$(echo "$dimensions" | cut -d',' -f2)
+```
+
+#### Pattern: Conditional Processing
+
+```bash
+if [[ "$width" -gt 1920 ]]; then
+    magick "$img" -resize 1920x1080 "$outputPath"
+fi
+```
+
+#### Pattern: Create Thumbnails
+
+```bash
+filename=$(basename "$img")
+magick "$img" -resize 427x240 "thumbnails/thumb_$filename"
+```
+
+## Limitations
+
+- Large batch operations may be memory-intensive
+- Some complex operations may require additional ImageMagick delegates
+- On older Linux systems, use `convert` instead of `magick` (ImageMagick 6.x vs 7.x)