@mclawnet/agent 0.5.9 → 0.6.2

package/skills/workflow-automation/SKILL.md

@@ -0,0 +1,299 @@
+---
+name: workflow-automation
+description: Design and implement automated multi-step workflows for software development processes. Use when automating CI/CD pipelines, release processes, deployment workflows, or any repeatable multi-step task orchestration.
+disable-model-invocation: true
+---
+
+# Workflow Automation
+
+Design and implement automated workflows that orchestrate multi-step software development processes — from CI/CD pipelines to release management, deployment, and custom development workflows.
+
+## Overview
+
+This skill helps you break down complex processes into automated, repeatable workflows. Every workflow should be reliable (handles failures gracefully), observable (you can see what happened and why), and maintainable (easy to modify when requirements change).
+
+## When to Use
+
+- Setting up CI/CD pipelines for a project
+- Automating release and deployment processes
+- Creating repeatable multi-step task sequences
+- Designing build, test, and deploy workflows
+- Automating code quality gates and review processes
+- Creating custom development automation scripts
+
+## When NOT to Use
+
+- **One-off tasks** — just run the commands directly
+- **Simple single-step operations** — automation overhead isn't worth it
+- **Tasks requiring human judgment at every step** — workflows should have clear automation points
+
+## Workflow Design Process
+
+### Step 1: Map the Process
+
+Before automating, document the current manual process:
+
+1. List every step in order
+2. Identify which steps can run in parallel
+3. Mark decision points (conditions that change the flow)
+4. Identify failure modes for each step
+5. Note which steps need human approval
+
+### Step 2: Define the Workflow Structure
+
+```yaml
+name: example-workflow
+trigger: [push, pull_request, manual]
+
+steps:
+  - name: validate
+    run: lint + type-check
+    on_failure: stop
+
+  - name: test
+    run: unit tests + integration tests
+    parallel: true
+    on_failure: stop
+
+  - name: build
+    depends_on: [validate, test]
+    run: compile + bundle
+    on_failure: notify
+
+  - name: deploy
+    depends_on: [build]
+    requires_approval: true
+    run: deploy to staging
+    on_failure: rollback
+```
+
+### Step 3: Implement with Proper Error Handling
+
+Every step should:
+- Have a clear success/failure signal (exit code, output check)
+- Log what it's doing (for debugging failed runs)
+- Clean up after itself (temp files, processes)
+- Support retry for transient failures (network, rate limits)
+
+## Common Workflow Patterns
+
+### CI Pipeline
+
+```yaml
+# .github/workflows/ci.yml
+name: CI
+on: [push, pull_request]
+
+jobs:
+  lint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - run: npm ci
+      - run: npm run lint
+
+  test:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - run: npm ci
+      - run: npm test -- --coverage
+      - uses: actions/upload-artifact@v4
+        with:
+          name: coverage
+          path: coverage/
+
+  build:
+    needs: [lint, test]
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - run: npm ci
+      - run: npm run build
+```
+
+### Release Workflow
+
+```yaml
+name: Release
+on:
+  push:
+    tags: ['v*']
+
+jobs:
+  release:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v4
+      - run: npm ci
+      - run: npm test
+      - run: npm run build
+      - run: npm publish
+        env:
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
+      - uses: softprops/action-gh-release@v1
+        with:
+          generate_release_notes: true
+```
+
+### Deployment Pipeline
+
+```yaml
+name: Deploy
+on:
+  workflow_dispatch:
+    inputs:
+      environment:
+        type: choice
+        options: [staging, production]
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    environment: ${{ inputs.environment }}
+    steps:
+      - uses: actions/checkout@v4
+      - run: npm ci && npm run build
+      - run: ./scripts/deploy.sh ${{ inputs.environment }}
+      - run: ./scripts/health-check.sh ${{ inputs.environment }}
+```
+
+## Shell Script Automation
+
+For custom workflows that don't fit CI/CD platforms:
+
+### Task Runner Pattern
+
+```bash
+#!/bin/bash
+set -euo pipefail
+
+# Colors for output
+RED='\033[0;31m'
+GREEN='\033[0;32m'
+NC='\033[0m'
+
+step() { echo -e "\n${GREEN}==>${NC} $1"; }
+fail() { echo -e "${RED}FAILED:${NC} $1"; exit 1; }
+
+step "Linting..."
+npm run lint || fail "Lint errors found"
+
+step "Running tests..."
+npm test || fail "Tests failed"
+
+step "Building..."
+npm run build || fail "Build failed"
+
+step "All checks passed!"
+```
+
+### Retry Pattern
+
+```bash
+retry() {
+  local max_attempts=$1; shift
+  local delay=$1; shift
+  local attempt=1
+
+  while [ $attempt -le $max_attempts ]; do
+    if "$@"; then
+      return 0
+    fi
+    echo "Attempt $attempt/$max_attempts failed. Retrying in ${delay}s..."
+    sleep $delay
+    attempt=$((attempt + 1))
+  done
+  return 1
+}
+
+# Usage: retry 3 5 curl -f https://api.example.com/health
+```
+
+### Parallel Execution
+
+```bash
+# Run independent tasks in parallel
+lint_pid=""
+test_pid=""
+
+npm run lint &
+lint_pid=$!
+
+npm test &
+test_pid=$!
+
+# Wait and check results
+wait $lint_pid || fail "Lint failed"
+wait $test_pid || fail "Tests failed"
+```
+
+## Makefile Workflows
+
+For project-level task automation:
+
+```makefile
+.PHONY: all lint test build deploy clean
+
+all: lint test build
+
+lint:
+	npm run lint
+	npm run typecheck
+
+test:
+	npm test -- --coverage
+
+build: lint test
+	npm run build
+
+deploy: build
+	./scripts/deploy.sh $(ENV)
+
+clean:
+	rm -rf dist/ coverage/ node_modules/.cache
+```
+
+## Workflow Quality Checklist
+
+### Reliability
+- [ ] Every step has explicit error handling (set -e, || exit, try/catch)
+- [ ] Transient failures are retried with backoff
+- [ ] Rollback procedures exist for destructive steps
+- [ ] Timeouts prevent hanging steps
+
+### Observability
+- [ ] Each step logs start, progress, and completion
+- [ ] Failure messages include enough context to debug
+- [ ] Artifacts (logs, reports, screenshots) are preserved on failure
+- [ ] Notifications sent on failure (Slack, email, etc.)
+
+### Maintainability
+- [ ] Steps are independent and composable
+- [ ] Configuration is externalized (env vars, config files)
+- [ ] Secrets are managed securely (not hardcoded)
+- [ ] Workflow can be run locally for testing
+
+### Performance
+- [ ] Independent steps run in parallel
+- [ ] Caching is used for dependencies (node_modules, build artifacts)
+- [ ] Incremental builds where possible
+- [ ] Resource limits prevent runaway processes
+
+## Anti-Patterns
+
+### Monolithic Workflow
+**Problem**: One giant workflow that does everything sequentially.
+**Fix**: Break into independent jobs that run in parallel. Use `needs:` for real dependencies.
+
+### No Failure Handling
+**Problem**: Script fails silently, or failure at step 3 still runs steps 4-10.
+**Fix**: Use `set -euo pipefail` in bash. Use `needs:` and `if: failure()` in CI.
+
+### Manual Steps Disguised as Automation
+**Problem**: Workflow has "TODO: manually verify X" comments.
+**Fix**: Either automate the verification or add explicit approval gates.
+
+### Hardcoded Secrets
+**Problem**: API keys, tokens, passwords in workflow files.
+**Fix**: Use secrets management (GitHub Secrets, Vault, env vars from CI).

package/skills/xlsx/SKILL.md

@@ -0,0 +1,305 @@
+---
+name: xlsx
+description: Create, edit, and analyze Excel spreadsheets (.xlsx) with support for formulas, formatting, data analysis, and visualization. Use when building spreadsheets, working with tabular data, creating financial models, or recalculating formula-based workbooks.
+disable-model-invocation: true
+---
+
+# Requirements for Outputs
+
+## When to Use
+
+- Creating new Excel spreadsheets with formulas and formatting
+- Reading, analyzing, or transforming data in .xlsx/.csv/.tsv files
+- Editing existing spreadsheets while preserving formulas and styles
+- Building financial models with proper formula structure
+- Data visualization within spreadsheets
+
+## When NOT to Use
+
+- **Word documents** — use the `docx` skill
+- **Presentations** — use the `pptx` skill
+- **PDF documents** — use the `pdf` skill
+- **One-off data analysis without Excel output** — use `data-analysis` skill
+- **Chart generation for reports** — use `chart-visualization` skill
+
+## All Excel files
+
+### Zero Formula Errors
+- Every Excel model MUST be delivered with ZERO formula errors (#REF!, #DIV/0!, #VALUE!, #N/A, #NAME?)
+
+### Preserve Existing Templates (when updating templates)
+- Study and EXACTLY match existing format, style, and conventions when modifying files
+- Never impose standardized formatting on files with established patterns
+- Existing template conventions ALWAYS override these guidelines
+
+## Financial models
+
+### Color Coding Standards
+Unless otherwise stated by the user or existing template
+
+#### Industry-Standard Color Conventions
+- **Blue text (RGB: 0,0,255)**: Hardcoded inputs, and numbers users will change for scenarios
+- **Black text (RGB: 0,0,0)**: ALL formulas and calculations
+- **Green text (RGB: 0,128,0)**: Links pulling from other worksheets within same workbook
+- **Red text (RGB: 255,0,0)**: External links to other files
+- **Yellow background (RGB: 255,255,0)**: Key assumptions needing attention or cells that need to be updated
+
+### Number Formatting Standards
+
+#### Required Format Rules
+- **Years**: Format as text strings (e.g., "2024" not "2,024")
+- **Currency**: Use $#,##0 format; ALWAYS specify units in headers ("Revenue ($mm)")
+- **Zeros**: Use number formatting to make all zeros "-", including percentages (e.g., "$#,##0;($#,##0);-")
+- **Percentages**: Default to 0.0% format (one decimal)
+- **Multiples**: Format as 0.0x for valuation multiples (EV/EBITDA, P/E)
+- **Negative numbers**: Use parentheses (123) not minus -123
+
+### Formula Construction Rules
+
+#### Assumptions Placement
+- Place ALL assumptions (growth rates, margins, multiples, etc.) in separate assumption cells
+- Use cell references instead of hardcoded values in formulas
+- Example: Use =B5*(1+$B$6) instead of =B5*1.05
+
+#### Formula Error Prevention
+- Verify all cell references are correct
+- Check for off-by-one errors in ranges
+- Ensure consistent formulas across all projection periods
+- Test with edge cases (zero values, negative numbers)
+- Verify no unintended circular references
+
+#### Documentation Requirements for Hardcodes
+- Comment or in cells beside (if end of table). Format: "Source: [System/Document], [Date], [Specific Reference], [URL if applicable]"
+- Examples:
+  - "Source: Company 10-K, FY2024, Page 45, Revenue Note, [SEC EDGAR URL]"
+  - "Source: Company 10-Q, Q2 2025, Exhibit 99.1, [SEC EDGAR URL]"
+  - "Source: Bloomberg Terminal, 8/15/2025, AAPL US Equity"
+  - "Source: FactSet, 8/20/2025, Consensus Estimates Screen"
+
+# XLSX creation, editing, and analysis
+
+## Overview
+
+A user may ask you to create, edit, or analyze the contents of an .xlsx file. You have different tools and workflows available for different tasks.
+
+## Important Requirements
+
+**LibreOffice Required for Formula Recalculation**: You can assume LibreOffice is installed for recalculating formula values using the `recalc.py` script. The script automatically configures LibreOffice on first run
+
+## Reading and analyzing data
+
+### Data analysis with pandas
+For data analysis, visualization, and basic operations, use **pandas** which provides powerful data manipulation capabilities:
+
+```python
+import pandas as pd
+
+# Read Excel
+df = pd.read_excel('file.xlsx')  # Default: first sheet
+all_sheets = pd.read_excel('file.xlsx', sheet_name=None)  # All sheets as dict
+
+# Analyze
+df.head()      # Preview data
+df.info()      # Column info
+df.describe()  # Statistics
+
+# Write Excel
+df.to_excel('output.xlsx', index=False)
+```
+
+## Excel File Workflows
+
+## CRITICAL: Use Formulas, Not Hardcoded Values
+
+**Always use Excel formulas instead of calculating values in Python and hardcoding them.** This ensures the spreadsheet remains dynamic and updateable.
+
+### ❌ WRONG - Hardcoding Calculated Values
+```python
+# Bad: Calculating in Python and hardcoding result
+total = df['Sales'].sum()
+sheet['B10'] = total  # Hardcodes 5000
+
+# Bad: Computing growth rate in Python
+growth = (df.iloc[-1]['Revenue'] - df.iloc[0]['Revenue']) / df.iloc[0]['Revenue']
+sheet['C5'] = growth  # Hardcodes 0.15
+
+# Bad: Python calculation for average
+avg = sum(values) / len(values)
+sheet['D20'] = avg  # Hardcodes 42.5
+```
+
+### ✅ CORRECT - Using Excel Formulas
+```python
+# Good: Let Excel calculate the sum
+sheet['B10'] = '=SUM(B2:B9)'
+
+# Good: Growth rate as Excel formula
+sheet['C5'] = '=(C4-C2)/C2'
+
+# Good: Average using Excel function
+sheet['D20'] = '=AVERAGE(D2:D19)'
+```
+
+This applies to ALL calculations - totals, percentages, ratios, differences, etc. The spreadsheet should be able to recalculate when source data changes.
+
+## Common Workflow
+1. **Choose tool**: pandas for data, openpyxl for formulas/formatting
+2. **Create/Load**: Create new workbook or load existing file
+3. **Modify**: Add/edit data, formulas, and formatting
+4. **Save**: Write to file
+5. **Recalculate formulas (MANDATORY IF USING FORMULAS)**: Use the recalc.py script
+   ```bash
+   python recalc.py output.xlsx
+   ```
+6. **Verify and fix any errors**: 
+   - The script returns JSON with error details
+   - If `status` is `errors_found`, check `error_summary` for specific error types and locations
+   - Fix the identified errors and recalculate again
+   - Common errors to fix:
+     - `#REF!`: Invalid cell references
+     - `#DIV/0!`: Division by zero
+     - `#VALUE!`: Wrong data type in formula
+     - `#NAME?`: Unrecognized formula name
+
+### Creating new Excel files
+
+```python
+# Using openpyxl for formulas and formatting
+from openpyxl import Workbook
+from openpyxl.styles import Font, PatternFill, Alignment
+
+wb = Workbook()
+sheet = wb.active
+
+# Add data
+sheet['A1'] = 'Hello'
+sheet['B1'] = 'World'
+sheet.append(['Row', 'of', 'data'])
+
+# Add formula
+sheet['B2'] = '=SUM(A1:A10)'
+
+# Formatting
+sheet['A1'].font = Font(bold=True, color='FF0000')
+sheet['A1'].fill = PatternFill('solid', start_color='FFFF00')
+sheet['A1'].alignment = Alignment(horizontal='center')
+
+# Column width
+sheet.column_dimensions['A'].width = 20
+
+wb.save('output.xlsx')
+```
+
+### Editing existing Excel files
+
+```python
+# Using openpyxl to preserve formulas and formatting
+from openpyxl import load_workbook
+
+# Load existing file
+wb = load_workbook('existing.xlsx')
+sheet = wb.active  # or wb['SheetName'] for specific sheet
+
+# Working with multiple sheets
+for sheet_name in wb.sheetnames:
+    sheet = wb[sheet_name]
+    print(f"Sheet: {sheet_name}")
+
+# Modify cells
+sheet['A1'] = 'New Value'
+sheet.insert_rows(2)  # Insert row at position 2
+sheet.delete_cols(3)  # Delete column 3
+
+# Add new sheet
+new_sheet = wb.create_sheet('NewSheet')
+new_sheet['A1'] = 'Data'
+
+wb.save('modified.xlsx')
+```
+
+## Recalculating formulas
+
+Excel files created or modified by openpyxl contain formulas as strings but not calculated values. Use the provided `recalc.py` script to recalculate formulas:
+
+```bash
+python recalc.py <excel_file> [timeout_seconds]
+```
+
+Example:
+```bash
+python recalc.py output.xlsx 30
+```
+
+The script:
+- Automatically sets up LibreOffice macro on first run
+- Recalculates all formulas in all sheets
+- Scans ALL cells for Excel errors (#REF!, #DIV/0!, etc.)
+- Returns JSON with detailed error locations and counts
+- Works on both Linux and macOS
+
+## Formula Verification Checklist
+
+Quick checks to ensure formulas work correctly:
+
+### Essential Verification
+- [ ] **Test 2-3 sample references**: Verify they pull correct values before building full model
+- [ ] **Column mapping**: Confirm Excel columns match (e.g., column 64 = BL, not BK)
+- [ ] **Row offset**: Remember Excel rows are 1-indexed (DataFrame row 5 = Excel row 6)
+
+### Common Pitfalls
+- [ ] **NaN handling**: Check for null values with `pd.notna()`
+- [ ] **Far-right columns**: FY data often in columns 50+ 
+- [ ] **Multiple matches**: Search all occurrences, not just first
+- [ ] **Division by zero**: Check denominators before using `/` in formulas (#DIV/0!)
+- [ ] **Wrong references**: Verify all cell references point to intended cells (#REF!)
+- [ ] **Cross-sheet references**: Use correct format (Sheet1!A1) for linking sheets
+
+### Formula Testing Strategy
+- [ ] **Start small**: Test formulas on 2-3 cells before applying broadly
+- [ ] **Verify dependencies**: Check all cells referenced in formulas exist
+- [ ] **Test edge cases**: Include zero, negative, and very large values
+
+### Interpreting recalc.py Output
+The script returns JSON with error details:
+```json
+{
+  "status": "success",           // or "errors_found"
+  "total_errors": 0,              // Total error count
+  "total_formulas": 42,           // Number of formulas in file
+  "error_summary": {              // Only present if errors found
+    "#REF!": {
+      "count": 2,
+      "locations": ["Sheet1!B5", "Sheet1!C10"]
+    }
+  }
+}
+```
+
+## Best Practices
+
+### Library Selection
+- **pandas**: Best for data analysis, bulk operations, and simple data export
+- **openpyxl**: Best for complex formatting, formulas, and Excel-specific features
+
+### Working with openpyxl
+- Cell indices are 1-based (row=1, column=1 refers to cell A1)
+- Use `data_only=True` to read calculated values: `load_workbook('file.xlsx', data_only=True)`
+- **Warning**: If opened with `data_only=True` and saved, formulas are replaced with values and permanently lost
+- For large files: Use `read_only=True` for reading or `write_only=True` for writing
+- Formulas are preserved but not evaluated - use recalc.py to update values
+
+### Working with pandas
+- Specify data types to avoid inference issues: `pd.read_excel('file.xlsx', dtype={'id': str})`
+- For large files, read specific columns: `pd.read_excel('file.xlsx', usecols=['A', 'C', 'E'])`
+- Handle dates properly: `pd.read_excel('file.xlsx', parse_dates=['date_column'])`
+
+## Code Style Guidelines
+**IMPORTANT**: When generating Python code for Excel operations:
+- Write minimal, concise Python code without unnecessary comments
+- Avoid verbose variable names and redundant operations
+- Avoid unnecessary print statements
+
+**For Excel files themselves**:
+- Add comments to cells with complex formulas or important assumptions
+- Document data sources for hardcoded values
+- Include notes for key calculations and model sections