daemora 1.0.3 → 1.0.5

package/skills/meeting-insights-analyzer.md

@@ -0,0 +1,327 @@
+---
+name: meeting-insights-analyzer
+description: Analyzes meeting transcripts and recordings to uncover behavioral patterns, communication insights, and actionable feedback. Identifies when you avoid conflict, use filler words, dominate conversations, or miss opportunities to listen. Perfect for professionals seeking to improve their communication and leadership skills.
+---
+
+# Meeting Insights Analyzer
+
+This skill transforms your meeting transcripts into actionable insights about your communication patterns, helping you become a more effective communicator and leader.
+
+## When to Use This Skill
+
+- Analyzing your communication patterns across multiple meetings
+- Getting feedback on your leadership and facilitation style
+- Identifying when you avoid difficult conversations
+- Understanding your speaking habits and filler words
+- Tracking improvement in communication skills over time
+- Preparing for performance reviews with concrete examples
+- Coaching team members on their communication style
+
+## What This Skill Does
+
+1. **Pattern Recognition**: Identifies recurring behaviors across meetings like:
+   - Conflict avoidance or indirect communication
+   - Speaking ratios and turn-taking
+   - Question-asking vs. statement-making patterns
+   - Active listening indicators
+   - Decision-making approaches
+
+2. **Communication Analysis**: Evaluates communication effectiveness:
+   - Clarity and directness
+   - Use of filler words and hedging language
+   - Tone and sentiment patterns
+   - Meeting control and facilitation
+
+3. **Actionable Feedback**: Provides specific, timestamped examples with:
+   - What happened
+   - Why it matters
+   - How to improve
+
+4. **Trend Tracking**: Compares patterns over time when analyzing multiple meetings
+
+## How to Use
+
+### Basic Setup
+
+1. Download your meeting transcripts to a folder (e.g., `~/meetings/`)
+2. Navigate to that folder in Claude Code
+3. Ask for the analysis you want
+
+### Quick Start Examples
+
+```
+Analyze all meetings in this folder and tell me when I avoided conflict.
+```
+
+```
+Look at my meetings from the past month and identify my communication patterns.
+```
+
+```
+Compare my facilitation style between these two meeting folders.
+```
+
+### Advanced Analysis
+
+```
+Analyze all transcripts in this folder and:
+1. Identify when I interrupted others
+2. Calculate my speaking ratio
+3. Find moments I avoided giving direct feedback
+4. Track my use of filler words
+5. Show examples of good active listening
+```
+
+## Instructions
+
+When a user requests meeting analysis:
+
+1. **Discover Available Data**
+   - Scan the folder for transcript files (.txt, .md, .vtt, .srt, .docx)
+   - Check if files contain speaker labels and timestamps
+   - Confirm the date range of meetings
+   - Identify the user's name/identifier in transcripts
+
+2. **Clarify Analysis Goals**
+   
+   If not specified, ask what they want to learn:
+   - Specific behaviors (conflict avoidance, interruptions, filler words)
+   - Communication effectiveness (clarity, directness, listening)
+   - Meeting facilitation skills
+   - Speaking patterns and ratios
+   - Growth areas for improvement
+   
+3. **Analyze Patterns**
+
+   For each requested insight:
+   
+   **Conflict Avoidance**:
+   - Look for hedging language ("maybe", "kind of", "I think")
+   - Indirect phrasing instead of direct requests
+   - Changing subject when tension arises
+   - Agreeing without commitment ("yeah, but...")
+   - Not addressing obvious problems
+   
+   **Speaking Ratios**:
+   - Calculate percentage of meeting spent speaking
+   - Count interruptions (by and of the user)
+   - Measure average speaking turn length
+   - Track question vs. statement ratios
+   
+   **Filler Words**:
+   - Count "um", "uh", "like", "you know", "actually", etc.
+   - Note frequency per minute or per speaking turn
+   - Identify situations where they increase (nervous, uncertain)
+   
+   **Active Listening**:
+   - Questions that reference others' previous points
+   - Paraphrasing or summarizing others' ideas
+   - Building on others' contributions
+   - Asking clarifying questions
+   
+   **Leadership & Facilitation**:
+   - Decision-making approach (directive vs. collaborative)
+   - How disagreements are handled
+   - Inclusion of quieter participants
+   - Time management and agenda control
+   - Follow-up and action item clarity
+
+4. **Provide Specific Examples**
+
+   For each pattern found, include:
+   
+   ```markdown
+   ### [Pattern Name]
+   
+   **Finding**: [One-sentence summary of the pattern]
+   
+   **Frequency**: [X times across Y meetings]
+   
+   **Examples**:
+   
+   1. **[Meeting Name/Date]** - [Timestamp]
+      
+      **What Happened**:
+      > [Actual quote from transcript]
+      
+      **Why This Matters**:
+      [Explanation of the impact or missed opportunity]
+      
+      **Better Approach**:
+      [Specific alternative phrasing or behavior]
+   
+   [Repeat for 2-3 strongest examples]
+   ```
+
+5. **Synthesize Insights**
+
+   After analyzing all patterns, provide:
+   
+   ```markdown
+   # Meeting Insights Summary
+   
+   **Analysis Period**: [Date range]
+   **Meetings Analyzed**: [X meetings]
+   **Total Duration**: [X hours]
+   
+   ## Key Patterns Identified
+   
+   ### 1. [Primary Pattern]
+   - **Observed**: [What you saw]
+   - **Impact**: [Why it matters]
+   - **Recommendation**: [How to improve]
+   
+   ### 2. [Second Pattern]
+   [Same structure]
+   
+   ## Communication Strengths
+   
+   1. [Strength 1 with example]
+   2. [Strength 2 with example]
+   3. [Strength 3 with example]
+   
+   ## Growth Opportunities
+   
+   1. **[Area 1]**: [Specific, actionable advice]
+   2. **[Area 2]**: [Specific, actionable advice]
+   3. **[Area 3]**: [Specific, actionable advice]
+   
+   ## Speaking Statistics
+   
+   - Average speaking time: [X% of meeting]
+   - Questions asked: [X per meeting average]
+   - Filler words: [X per minute]
+   - Interruptions: [X given / Y received per meeting]
+   
+   ## Next Steps
+   
+   [3-5 concrete actions to improve communication]
+   ```
+
+6. **Offer Follow-Up Options**
+   - Track these same metrics in future meetings
+   - Deep dive into specific meetings or patterns
+   - Compare to industry benchmarks
+   - Create a personal communication development plan
+   - Generate a summary for performance reviews
+
+## Examples
+
+### Example 1: Conflict Avoidance Analysis (Inspired by Dan Shipper)
+
+**User**: "I download all of my meeting recordings and put them in a folder. Tell me all the times I've subtly avoided conflict."
+
+**Output**: 
+```markdown
+# Conflict Avoidance Patterns
+
+Found 23 instances across 15 meetings where you used indirect 
+communication or avoided addressing tensions directly.
+
+## Pattern: Hedging on Critical Feedback
+
+**Frequency**: 8 times across 7 meetings
+
+**Example 1: 1:1 with Sarah** - 00:14:32
+
+**What Happened**:
+> "So, I was thinking... maybe we could, like, potentially 
+> consider looking at the timeline again? I mean, if you 
+> think that makes sense. But whatever you think is best!"
+
+**Why This Matters**:
+You needed to address that Sarah's project was behind schedule, 
+but the hedging language ("maybe", "potentially", "if you think") 
+and the deflection at the end ("whatever you think") made it easy 
+for her to miss the urgency.
+
+**Better Approach**:
+"Sarah, the project is two weeks behind schedule. We need to 
+discuss what's blocking progress and create a new timeline 
+today."
+
+[Additional examples...]
+
+## Recommendations
+
+1. **Name the issue directly** in the first sentence
+2. **Remove hedging words** like "maybe," "kind of," "sort of"
+3. **Ask specific questions** instead of hinting
+4. **Schedule difficult conversations** instead of raising them casually
+```
+
+### Example 2: Leadership Facilitation
+
+**User**: "Analyze my team meetings and tell me about my facilitation style."
+
+**Output**: Provides insights on:
+- How much you speak vs. team members (60% vs. 40%)
+- Whether you ask questions or make statements (3:1 ratio)
+- How you handle disagreements (tendency to resolve too quickly)
+- Who speaks least and whether you draw them in
+- Examples of good and missed facilitation moments
+
+### Example 3: Personal Development Tracking
+
+**User**: "Compare my meetings from Q1 vs. Q2 to see if I've improved my listening skills."
+
+**Output**: Creates a comparative analysis showing:
+- Decrease in interruptions (8 per meeting → 3 per meeting)
+- Increase in clarifying questions (2 → 7 per meeting)
+- Improvement in building on others' ideas
+- Specific examples showing the difference
+- Remaining areas for growth
+
+## Setup Tips
+
+### Getting Meeting Transcripts
+
+**From Granola** (free with Lenny's newsletter subscription):
+- Granola auto-transcribes your meetings
+- Export transcripts to a folder: [Instructions on how]
+- Point Claude Code to that folder
+
+**From Zoom**:
+- Enable cloud recording with transcription
+- Download VTT or SRT files after meetings
+- Store in a dedicated folder
+
+**From Google Meet**:
+- Use Google Docs auto-transcription
+- Save transcript docs to a folder
+- Download as .txt files or give Claude Code access
+
+**From Fireflies.ai, Otter.ai, etc.**:
+- Export transcripts in bulk
+- Store in a local folder
+- Run analysis on the folder
+
+### Best Practices
+
+1. **Consistent naming**: Use `YYYY-MM-DD - Meeting Name.txt` format
+2. **Regular analysis**: Review monthly or quarterly for trends
+3. **Specific queries**: Ask about one behavior at a time for depth
+4. **Privacy**: Keep sensitive meeting data local
+5. **Action-oriented**: Focus on one improvement area at a time
+
+## Common Analysis Requests
+
+- "When do I avoid difficult conversations?"
+- "How often do I interrupt others?"
+- "What's my speaking vs. listening ratio?"
+- "Do I ask good questions?"
+- "How do I handle disagreement?"
+- "Am I inclusive of all voices?"
+- "Do I use too many filler words?"
+- "How clear are my action items?"
+- "Do I stay on agenda or get sidetracked?"
+- "How has my communication changed over time?"
+
+## Related Use Cases
+
+- Creating a personal development plan from insights
+- Preparing performance review materials with examples
+- Coaching direct reports on their communication
+- Analyzing customer calls for sales or support patterns
+- Studying negotiation tactics and outcomes
+

package/skills/orchestration.md

@@ -0,0 +1,93 @@
+---
+name: orchestration
+description: Multi-agent orchestration, parallel execution, contract-based planning for complex multi-file tasks
+triggers: parallel, orchestrate, sub-agent, project, plan, multiple tasks, frontend backend, coordinate, spawn, workspace, contract, full-stack, todo app, multi-step
+---
+
+# Orchestration & Multi-Agent Planning
+
+## When to Plan vs Just Do It
+- Simple task (1-2 files, single clear action) → do it directly, no planning overhead.
+- Heavy task (3+ files, multi-agent, research-then-build, unclear scope) → plan first with projectTracker, then execute.
+
+## Planning Workflow
+1. `projectTracker("createProject")` — breaks work into tasks, creates shared workspace directory.
+2. Pass returned workspace path in `sharedContext` so all sub-agents write artifacts there.
+3. Define the **shared contract** (API schema, DOM structure, naming conventions) BEFORE spawning agents.
+4. Mark each task `in_progress` before starting, `done` with notes when finished.
+5. If interrupted → `projectTracker("listProjects")` to find and resume.
+
+## Contract-Based Pattern
+Before spawning parallel agents, define the shared contract explicitly:
+- API routes, request/response shapes, status codes
+- Data models, field names, types
+- File paths, component names, CSS class conventions
+- Paste the ACTUAL contract text into `sharedContext` — don't reference it, include it.
+
+## Always Pass Correct Working Directory
+- Include the exact workspace path and project root in `sharedContext`.
+- Never let agents guess where to create files — specify exact paths.
+
+## Parallel vs Sequential Decision
+- Does task B need output from task A? **Yes → sequential.** No → parallel.
+- Parallel agents communicate through workspace files, NOT through messages or return values.
+- Never run agents in parallel when they have data dependencies.
+
+## Profile Guide
+- **researcher**: gather info, browse web, write findings — no shell execution
+- **coder**: read/write/run full loop — building, fixing, testing
+- **writer**: produce documents and reports — no shell, no browser
+- **analyst**: data processing with shell + web + vision
+- No profile: default 27-tool set (safe general-purpose)
+- Add `extraTools` when a profile is almost right but needs one more tool
+
+## Workspace as Artifact Store
+- `projectTracker` returns workspace path (`data/workspaces/{id}/`)
+- Sub-agents write output files to workspace (code, reports, schemas)
+- Parent reads from workspace to build context for next phase
+- Artifacts survive crashes — work is never lost
+- Do NOT pass full file contents as return values — write to workspace, return summary
+
+## Structured Return Convention
+End every sub-agent response with:
+```
+DONE: One sentence describing what was accomplished
+FILES: workspace/path/file1.js, workspace/path/file2.md
+CONTRACT: Key interfaces, exports, API endpoints produced
+ERRORS: Any failures or caveats
+```
+Omit sections that don't apply.
+
+## Writing Sub-Agent Task Descriptions
+A sub-agent has NO context except what you give it. Write as if handing off to a developer with zero knowledge.
+
+Include:
+- Exact file path(s) to create or modify
+- Full spec/schema/contract (paste actual names, endpoints, fields — don't summarize)
+- Expected behavior and output
+- Constraints (no external libraries, match existing patterns, specific format)
+
+**Bad:** "Write the CSS file"
+**Good:** "Create /project/style.css. Style these DOM elements: ul#todo-list, li.todo-item, button.delete-btn, input#new-todo. Requirements: CSS Grid layout, dark mode via prefers-color-scheme, smooth opacity transition on add/remove, mobile-first responsive (600px breakpoint). No frameworks."
+
+## Sequential vs Parallel Agents
+- **Sequential**: `spawnAgent` multiple times when each step needs previous output (research → write → test).
+- **Parallel**: `parallelAgents` when steps can run simultaneously — always provide `sharedContext` with the shared contract.
+
+## Model Routing for Cost
+- Cheap tasks (research, summarization, boilerplate) → `"model":"openai:gpt-4.1-mini"` or `"model":"anthropic:claude-sonnet-4-20250514"`
+- Expensive tasks (complex code, architecture, debugging) → default model or `"model":"anthropic:claude-opus-4-6"`
+- Pass `"model"` in spawnAgent/parallelAgents options to override per-agent
+
+## Steering Running Agents
+- `manageAgents("steer")` with `{"agentId":"...", "message":"..."}` to redirect a running agent mid-task
+- Use when you realize a sub-agent is going down the wrong path — cheaper than killing and respawning
+- `manageAgents("list")` to see active agents and their status
+- `manageAgents("kill")` with `{"agentId":"..."}` to stop a stuck agent
+
+## Error Recovery
+- Sub-agent fails → read its error from the return, diagnose root cause
+- Transient failure (network, timeout) → respawn with same task description
+- Logic failure (wrong approach) → respawn with corrected instructions + add what went wrong
+- Never blindly retry — always adjust the task description based on the failure
+- If multiple agents fail on the same issue → fix the shared contract/workspace, then respawn all

package/skills/raffle-winner-picker.md

@@ -0,0 +1,159 @@
+---
+name: raffle-winner-picker
+description: Picks random winners from lists, spreadsheets, or Google Sheets for giveaways, raffles, and contests. Ensures fair, unbiased selection with transparency.
+---
+
+# Raffle Winner Picker
+
+This skill randomly selects winners from lists, spreadsheets, or Google Sheets for giveaways and contests.
+
+## When to Use This Skill
+
+- Running social media giveaways
+- Picking raffle winners at events
+- Randomly selecting participants for surveys or tests
+- Choosing winners from contest submissions
+- Fair distribution of limited spots or resources
+- Random team assignments
+
+## What This Skill Does
+
+1. **Random Selection**: Uses cryptographically random selection
+2. **Multiple Sources**: Works with CSV, Excel, Google Sheets, or plain lists
+3. **Multiple Winners**: Can pick one or multiple winners
+4. **Duplicate Prevention**: Ensures the same person can't win twice
+5. **Transparent Results**: Shows the selection process clearly
+6. **Winner Details**: Displays all relevant information about winners
+
+## How to Use
+
+### From Google Sheets
+
+```
+Pick a random row from this Google Sheet to select a winner 
+for a giveaway: [Sheet URL]
+```
+
+### From Local File
+
+```
+Pick 3 random winners from entries.csv
+```
+
+### From List
+
+```
+Pick a random winner from this list:
+- Alice (alice@email.com)
+- Bob (bob@email.com)
+- Carol (carol@email.com)
+...
+```
+
+### Multiple Winners
+
+```
+Pick 5 random winners from contest-entries.xlsx, 
+make sure no duplicates
+```
+
+## Example
+
+**User**: "Pick a random row from this Google Sheet to select a winner for a giveaway."
+
+**Output**:
+```
+Accessing Google Sheet...
+Total entries found: 247
+
+Randomly selecting winner...
+
+🎉 WINNER SELECTED! 🎉
+
+Row #142
+Name: Sarah Johnson
+Email: sarah.j@email.com
+Entry Date: March 10, 2024
+Comment: "Love your newsletter!"
+
+Selection method: Cryptographically random
+Timestamp: 2024-03-15 14:32:18 UTC
+
+Would you like to:
+- Pick another winner (excluding Sarah)?
+- Export winner details?
+- Pick runner-ups?
+```
+
+**Inspired by:** Lenny's use case - picking a Sora 2 giveaway winner from his subscriber Slack community
+
+## Features
+
+### Fair Selection
+- Uses secure random number generation
+- No bias or patterns
+- Transparent process
+- Repeatable with seed (for verification)
+
+### Exclusions
+```
+Pick a random winner excluding previous winners: 
+Alice, Bob, Carol
+```
+
+### Weighted Selection
+```
+Pick a winner with weighted probability based on 
+the "entries" column (1 entry = 1 ticket)
+```
+
+### Runner-ups
+```
+Pick 1 winner and 3 runner-ups from the list
+```
+
+## Example Workflows
+
+### Social Media Giveaway
+1. Export entries from Google Form to Sheets
+2. "Pick a random winner from [Sheet URL]"
+3. Verify winner details
+4. Announce publicly with timestamp
+
+### Event Raffle
+1. Create CSV of attendee names and emails
+2. "Pick 10 random winners from attendees.csv"
+3. Export winner list
+4. Email winners directly
+
+### Team Assignment
+1. Have list of participants
+2. "Randomly split this list into 4 equal teams"
+3. Review assignments
+4. Share team rosters
+
+## Tips
+
+- **Document the process**: Save the timestamp and method
+- **Public announcement**: Share selection details for transparency
+- **Check eligibility**: Verify winner meets contest rules
+- **Have backups**: Pick runner-ups in case winner is ineligible
+- **Export results**: Save winner list for records
+
+## Privacy & Fairness
+
+✓ Uses cryptographically secure randomness
+✓ No manipulation possible
+✓ Timestamp recorded for verification
+✓ Can provide seed for third-party verification
+✓ Respects data privacy
+
+## Common Use Cases
+
+- Newsletter subscriber giveaways
+- Product launch raffles
+- Conference ticket drawings
+- Beta tester selection
+- Focus group participant selection
+- Random prize distribution at events
+