anymous 1.3.0 → 1.3.2

package/skills/internal-comms/examples/company-newsletter.md

@@ -1,65 +0,0 @@
-## Instructions
-You are being asked to write a company-wide newsletter update. You are meant to summarize the past week/month of a company in the form of a newsletter that the entire company will read. It should be maybe ~20-25 bullet points long. It will be sent via Slack and email, so make it consumable for that.
-
-Ideally it includes the following attributes:
-- Lots of links: pulling documents from Google Drive that are very relevant, linking to prominent Slack messages in announce channels and from executives, perhgaps referencing emails that went company-wide, highlighting significant things that have happened in the company.
-- Short and to-the-point: each bullet should probably be no longer than ~1-2 sentences
-- Use the "we" tense, as you are part of the company. Many of the bullets should say "we did this" or "we did that"
-
-## Tools to use
-If you have access to the following tools, please try to use them. If not, you can also let the user know directly that their responses would be better if they gave them access.
-
-- Slack: look for messages in channels with lots of people, with lots of reactions or lots of responses within the thread
-- Email: look for things from executives that discuss company-wide announcements
-- Calendar: if there were meetings with large attendee lists, particularly things like All-Hands meetings, big company announcements, etc. If there were documents attached to those meetings, those are great links to include.
-- Documents: if there were new docs published in the last week or two that got a lot of attention, you can link them. These should be things like company-wide vision docs, plans for the upcoming quarter or half, things authored by critical executives, etc.
-- External press: if you see references to articles or press we've received over the past week, that could be really cool too.
-
-If you don't have access to any of these things, you can ask the user for things they want to cover. In this case, you'll mostly just be polishing up and fitting to this format more directly.
-
-## Sections
-The company is pretty big: 1000+ people. There are a variety of different teams and initiatives going on across the company. To make sure the update works well, try breaking it into sections of similar things. You might break into clusters like {product development, go to market, finance} or {recruiting, execution, vision}, or {external news, internal news} etc. Try to make sure the different areas of the company are highlighted well.
-
-## Prioritization
-Focus on:
-- Company-wide impact (not team-specific details)
-- Announcements from leadership
-- Major milestones and achievements
-- Information that affects most employees
-- External recognition or press
-
-Avoid:
-- Overly granular team updates (save those for 3Ps)
-- Information only relevant to small groups
-- Duplicate information already communicated
-
-## Example Formats
-
-:megaphone: Company Announcements
-- Announcement 1
-- Announcement 2
-- Announcement 3
-
-:dart: Progress on Priorities
-- Area 1
-    - Sub-area 1
-    - Sub-area 2
-    - Sub-area 3
-- Area 2
-    - Sub-area 1
-    - Sub-area 2
-    - Sub-area 3
-- Area 3
-    - Sub-area 1
-    - Sub-area 2
-    - Sub-area 3
-
-:pillar: Leadership Updates
-- Post 1
-- Post 2
-- Post 3
-
-:thread: Social Updates
-- Update 1
-- Update 2
-- Update 3

package/skills/internal-comms/examples/faq-answers.md

@@ -1,30 +0,0 @@
-## Instructions
-You are an assistant for answering questions that are being asked across the company. Every week, there are lots of questions that get asked across the company, and your goal is to try to summarize what those questions are. We want our company to be well-informed and on the same page, so your job is to produce a set of frequently asked questions that our employees are asking and attempt to answer them. Your singular job is to do two things:
-
-- Find questions that are big sources of confusion for lots of employees at the company, generally about things that affect a large portion of the employee base
-- Attempt to give a nice summarized answer to that question in order to minimize confusion.
-
-Some examples of areas that may be interesting to folks: recent corporate events (fundraising, new executives, etc.), upcoming launches, hiring progress, changes to vision or focus, etc.
-
-
-## Tools Available
-You should use the company's available tools, where communication and work happens. For most companies, it looks something like this:
-- Slack: questions being asked across the company - it could be questions in response to posts with lots of responses, questions being asked with lots of reactions or thumbs up to show support, or anything else to show that a large number of employees want to ask the same things
-- Email: emails with FAQs written directly in them can be a good source as well
-- Documents: docs in places like Google Drive, linked on calendar events, etc. can also be a good source of FAQs, either directly added or inferred based on the contents of the doc
-
-## Formatting
-The formatting should be pretty basic:
-
-- *Question*: [insert question - 1 sentence]
-- *Answer*: [insert answer - 1-2 sentence]
-
-## Guidance
-Make sure you're being holistic in your questions. Don't focus too much on just the user in question or the team they are a part of, but try to capture the entire company. Try to be as holistic as you can in reading all the tools available, producing responses that are relevant to all at the company.
-
-## Answer Guidelines
-- Base answers on official company communications when possible
-- If information is uncertain, indicate that clearly
-- Link to authoritative sources (docs, announcements, emails)
-- Keep tone professional but approachable
-- Flag if a question requires executive input or official response

package/skills/internal-comms/examples/general-comms.md

@@ -1,16 +0,0 @@
-  ## Instructions
-  You are being asked to write internal company communication that doesn't fit into the standard formats (3P
-  updates, newsletters, or FAQs).
-
-  Before proceeding:
-  1. Ask the user about their target audience
-  2. Understand the communication's purpose
-  3. Clarify the desired tone (formal, casual, urgent, informational)
-  4. Confirm any specific formatting requirements
-
-  Use these general principles:
-  - Be clear and concise
-  - Use active voice
-  - Put the most important information first
-  - Include relevant links and references
-  - Match the company's communication style

package/skills/invoice-organizer/SKILL.md

@@ -1,452 +0,0 @@
----
-name: invoice-organizer
-description: Automatically organizes invoices and receipts for tax preparation by reading messy files, extracting key information, renaming them consistently, and sorting them into logical folders. Turns hours of manual bookkeeping into minutes of automated organization.
----
-
-# Invoice Organizer
-
-This skill transforms chaotic folders of invoices, receipts, and financial documents into a clean, tax-ready filing system without manual effort.
-
-## Prerequisites
-
-- **PDF processing**: pdftotext (poppler-utils) or pdfplumber for reading invoice content
-- **OCR for receipts**: tesseract-ocr for scanned receipt images
-- **Optional**: Pandoc for converting documents to text format
-
-## When to Use This Skill
-
-- Preparing for tax season and need organized records
-- Managing business expenses across multiple vendors
-- Organizing receipts from a messy folder or email downloads
-- Setting up automated invoice filing for ongoing bookkeeping
-- Archiving financial records by year or category
-- Reconciling expenses for reimbursement
-- Preparing documentation for accountants
-
-## What This Skill Does
-
-1. **Reads Invoice Content**: Extracts information from PDFs, images, and documents:
-   - Vendor/company name
-   - Invoice number
-   - Date
-   - Amount
-   - Product or service description
-   - Payment method
-
-2. **Renames Files Consistently**: Creates standardized filenames:
-   - Format: `YYYY-MM-DD Vendor - Invoice - ProductOrService.pdf`
-   - Examples: `2024-03-15 Adobe - Invoice - Creative Cloud.pdf`
-
-3. **Organizes by Category**: Sorts into logical folders:
-   - By vendor
-   - By expense category (software, office, travel, etc.)
-   - By time period (year, quarter, month)
-   - By tax category (deductible, personal, etc.)
-
-4. **Handles Multiple Formats**: Works with:
-   - PDF invoices
-   - Scanned receipts (JPG, PNG)
-   - Email attachments
-   - Screenshots
-   - Bank statements
-
-5. **Maintains Originals**: Preserves original files while organizing copies
-
-## How to Use
-
-### Basic Usage
-
-Navigate to your messy invoice folder:
-```
-cd ~/Desktop/receipts-to-sort
-```
-
-Then ask OpenCode:
-```
-Organize these invoices for taxes
-```
-
-Or more specifically:
-```
-Read all invoices in this folder, rename them to 
-"YYYY-MM-DD Vendor - Invoice - Product.pdf" format, 
-and organize them by vendor
-```
-
-### Advanced Organization
-
-```
-Organize these invoices:
-1. Extract date, vendor, and description from each file
-2. Rename to standard format
-3. Sort into folders by expense category (Software, Office, Travel, etc.)
-4. Create a CSV spreadsheet with all invoice details for my accountant
-```
-
-## Instructions
-
-When a user requests invoice organization:
-
-1. **Scan the Folder**
-   
-   Identify all invoice files:
-   ```bash
-   # Find all invoice-related files
-   find . -type f \( -name "*.pdf" -o -name "*.jpg" -o -name "*.png" \) -print
-   ```
-   
-   Report findings:
-   - Total number of files
-   - File types
-   - Date range (if discernible from names)
-   - Current organization (or lack thereof)
-
-2. **Extract Information from Each File**
-   
-   For each invoice, extract:
-   
-   **From PDF invoices**:
-   - Use text extraction to read invoice content
-   - Look for common patterns:
-     - "Invoice Date:", "Date:", "Issued:"
-     - "Invoice #:", "Invoice Number:"
-     - Company name (usually at top)
-     - "Amount Due:", "Total:", "Amount:"
-     - "Description:", "Service:", "Product:"
-   
-   **From image receipts**:
-   - Read visible text from images
-   - Identify vendor name (often at top)
-   - Look for date (common formats)
-   - Find total amount
-   
-   **Fallback for unclear files**:
-   - Use filename clues
-   - Check file creation/modification date
-   - Flag for manual review if critical info missing
-
-3. **Determine Organization Strategy**
-   
-   Ask user preference if not specified:
-   
-   ```markdown
-   I found [X] invoices from [date range].
-   
-   How would you like them organized?
-   
-   1. **By Vendor** (Adobe/, Amazon/, Stripe/, etc.)
-   2. **By Category** (Software/, Office Supplies/, Travel/, etc.)
-   3. **By Date** (2024/Q1/, 2024/Q2/, etc.)
-   4. **By Tax Category** (Deductible/, Personal/, etc.)
-   5. **Custom** (describe your structure)
-   
-   Or I can use a default structure: Year/Category/Vendor
-   ```
-
-4. **Create Standardized Filename**
-   
-   For each invoice, create a filename following this pattern:
-   
-   ```
-   YYYY-MM-DD Vendor - Invoice - Description.ext
-   ```
-   
-   Examples:
-   - `2024-03-15 Adobe - Invoice - Creative Cloud.pdf`
-   - `2024-01-10 Amazon - Receipt - Office Supplies.pdf`
-   - `2023-12-01 Stripe - Invoice - Monthly Payment Processing.pdf`
-   
-   **Filename Best Practices**:
-   - Remove special characters except hyphens
-   - Capitalize vendor names properly
-   - Keep descriptions concise but meaningful
-   - Use consistent date format (YYYY-MM-DD) for sorting
-   - Preserve original file extension
-
-5. **Execute Organization**
-   
-   Before moving files, show the plan:
-   
-   ```markdown
-   # Organization Plan
-   
-   ## Proposed Structure
-   ```
-   Invoices/
-   ├── 2023/
-   │   ├── Software/
-   │   │   ├── Adobe/
-   │   │   └── Microsoft/
-   │   ├── Services/
-   │   └── Office/
-   └── 2024/
-       ├── Software/
-       ├── Services/
-       └── Office/
-   ```
-   
-   ## Sample Changes
-   
-   Before: `invoice_adobe_march.pdf`
-   After: `2024-03-15 Adobe - Invoice - Creative Cloud.pdf`
-   Location: `Invoices/2024/Software/Adobe/`
-   
-   Before: `IMG_2847.jpg`
-   After: `2024-02-10 Staples - Receipt - Office Supplies.jpg`
-   Location: `Invoices/2024/Office/Staples/`
-   
-   Process [X] files? (yes/no)
-   ```
-   
-   After approval:
-   ```bash
-   # Create folder structure
-   mkdir -p "Invoices/2024/Software/Adobe"
-   
-   # Copy (don't move) to preserve originals
-   cp "original.pdf" "Invoices/2024/Software/Adobe/2024-03-15 Adobe - Invoice - Creative Cloud.pdf"
-   
-   # Or move if user prefers
-   mv "original.pdf" "new/path/standardized-name.pdf"
-   ```
-
-6. **Generate Summary Report**
-   
-   Create a CSV file with all invoice details:
-   
-   ```csv
-   Date,Vendor,Invoice Number,Description,Amount,Category,File Path
-   2024-03-15,Adobe,INV-12345,Creative Cloud,52.99,Software,Invoices/2024/Software/Adobe/2024-03-15 Adobe - Invoice - Creative Cloud.pdf
-   2024-03-10,Amazon,123-4567890-1234567,Office Supplies,127.45,Office,Invoices/2024/Office/Amazon/2024-03-10 Amazon - Receipt - Office Supplies.pdf
-   ...
-   ```
-   
-   This CSV is useful for:
-   - Importing into accounting software
-   - Sharing with accountants
-   - Expense tracking and reporting
-   - Tax preparation
-
-7. **Provide Completion Summary**
-   
-   ```markdown
-   # Organization Complete! 📊
-   
-   ## Summary
-   - **Processed**: [X] invoices
-   - **Date range**: [earliest] to [latest]
-   - **Total amount**: $[sum] (if amounts extracted)
-   - **Vendors**: [Y] unique vendors
-   
-   ## New Structure
-   ```
-   Invoices/
-   ├── 2024/ (45 files)
-   │   ├── Software/ (23 files)
-   │   ├── Services/ (12 files)
-   │   └── Office/ (10 files)
-   └── 2023/ (12 files)
-   ```
-   
-   ## Files Created
-   - `/Invoices/` - Organized invoices
-   - `/Invoices/invoice-summary.csv` - Spreadsheet for accounting
-   - `/Invoices/originals/` - Original files (if copied)
-   
-   ## Files Needing Review
-   [List any files where information couldn't be extracted completely]
-   
-   ## Next Steps
-   1. Review the `invoice-summary.csv` file
-   2. Check files in "Needs Review" folder
-   3. Import CSV into your accounting software
-   4. Set up auto-organization for future invoices
-   
-   Ready for tax season! 🎉
-   ```
-
-## Examples
-
-### Example 1: Tax Preparation (From Martin Merschroth)
-
-**User**: "I have a messy folder of invoices for taxes. Sort them and rename properly."
-
-**Process**:
-1. Scans folder: finds 147 PDFs and images
-2. Reads each invoice to extract:
-   - Date
-   - Vendor name
-   - Invoice number
-   - Product/service description
-3. Renames all files: `YYYY-MM-DD Vendor - Invoice - Product.pdf`
-4. Organizes into: `2024/Software/`, `2024/Travel/`, etc.
-5. Creates `invoice-summary.csv` for accountant
-6. Result: Tax-ready organized invoices in minutes
-
-### Example 2: Monthly Expense Reconciliation
-
-**User**: "Organize my business receipts from last month by category."
-
-**Output**:
-```markdown
-# March 2024 Receipts Organized
-
-## By Category
-- Software & Tools: $847.32 (12 invoices)
-- Office Supplies: $234.18 (8 receipts)
-- Travel & Meals: $1,456.90 (15 receipts)
-- Professional Services: $2,500.00 (3 invoices)
-
-Total: $5,038.40
-
-All receipts renamed and filed in:
-`Business-Receipts/2024/03-March/[Category]/`
-
-CSV export: `march-2024-expenses.csv`
-```
-
-### Example 3: Multi-Year Archive
-
-**User**: "I have 3 years of random invoices. Organize them by year, then by vendor."
-
-**Output**: Creates structure:
-```
-Invoices/
-├── 2022/
-│   ├── Adobe/
-│   ├── Amazon/
-│   └── ...
-├── 2023/
-│   ├── Adobe/
-│   ├── Amazon/
-│   └── ...
-└── 2024/
-    ├── Adobe/
-    ├── Amazon/
-    └── ...
-```
-
-Each file properly renamed with date and description.
-
-### Example 4: Email Downloads Cleanup
-
-**User**: "I download invoices from Gmail. They're all named 'invoice.pdf', 'invoice(1).pdf', etc. Fix this mess."
-
-**Output**:
-```markdown
-Found 89 files all named "invoice*.pdf"
-
-Reading each file to extract real information...
-
-Renamed examples:
-- invoice.pdf → 2024-03-15 Shopify - Invoice - Monthly Subscription.pdf
-- invoice(1).pdf → 2024-03-14 Google - Invoice - Workspace.pdf
-- invoice(2).pdf → 2024-03-10 Netlify - Invoice - Pro Plan.pdf
-
-All files renamed and organized by vendor.
-```
-
-## Common Organization Patterns
-
-### By Vendor (Simple)
-```
-Invoices/
-├── Adobe/
-├── Amazon/
-├── Google/
-└── Microsoft/
-```
-
-### By Year and Category (Tax-Friendly)
-```
-Invoices/
-├── 2023/
-│   ├── Software/
-│   ├── Hardware/
-│   ├── Services/
-│   └── Travel/
-└── 2024/
-    └── ...
-```
-
-### By Quarter (Detailed Tracking)
-```
-Invoices/
-├── 2024/
-│   ├── Q1/
-│   │   ├── Software/
-│   │   ├── Office/
-│   │   └── Travel/
-│   └── Q2/
-│       └── ...
-```
-
-### By Tax Category (Accountant-Ready)
-```
-Invoices/
-├── Deductible/
-│   ├── Software/
-│   ├── Office/
-│   └── Professional-Services/
-├── Partially-Deductible/
-│   └── Meals-Travel/
-└── Personal/
-```
-
-## Automation Setup
-
-For ongoing organization:
-
-```
-Create a script that watches my ~/Downloads/invoices folder 
-and auto-organizes any new invoice files using our standard 
-naming and folder structure.
-```
-
-This creates a persistent solution that organizes invoices as they arrive.
-
-## Pro Tips
-
-1. **Scan emails to PDF**: Use Preview or similar to save email invoices as PDFs first
-2. **Consistent downloads**: Save all invoices to one folder for batch processing
-3. **Monthly routine**: Organize invoices monthly, not annually
-4. **Backup originals**: Keep original files before reorganizing
-5. **Include amounts in CSV**: Useful for budget tracking
-6. **Tag by deductibility**: Note which expenses are tax-deductible
-7. **Keep receipts 7 years**: Standard audit period
-
-## Handling Special Cases
-
-### Missing Information
-If date/vendor can't be extracted:
-- Flag file for manual review
-- Use file modification date as fallback
-- Create "Needs-Review/" folder
-
-### Duplicate Invoices
-If same invoice appears multiple times:
-- Compare file hashes
-- Keep highest quality version
-- Note duplicates in summary
-
-### Multi-Page Invoices
-For invoices split across files:
-- Merge PDFs if needed
-- Use consistent naming for parts
-- Note in CSV if invoice is split
-
-### Non-Standard Formats
-For unusual receipt formats:
-- Extract what's possible
-- Standardize what you can
-- Flag for review if critical info missing
-
-## Related Use Cases
-
-- Creating expense reports for reimbursement
-- Organizing bank statements
-- Managing vendor contracts
-- Archiving old financial records
-- Preparing for audits
-- Tracking subscription costs over time
-