feat: add initial skills
This commit is contained in:
Prathit-tech
185
CONTRIBUTING.md
Normal file
185
CONTRIBUTING.md
Normal file
@@ -0,0 +1,185 @@
|
|||||||
|
# Contributing to Awesome Claude Skills
|
||||||
|
|
||||||
|
Thank you for your interest in contributing to the premier collection of Claude Skills! This guide will help you add new skills that benefit the entire Claude community.
|
||||||
|
|
||||||
|
## Before You Start
|
||||||
|
|
||||||
|
- Ensure your skill is based on a **real use case**, not a hypothetical scenario.
|
||||||
|
- Search existing skills to avoid duplicates.
|
||||||
|
- If possible, attribute the use case to the original person or source.
|
||||||
|
|
||||||
|
## Skill Requirements
|
||||||
|
|
||||||
|
All skills must:
|
||||||
|
|
||||||
|
1. **Solve a real problem** - Based on actual usage, not theoretical applications.
|
||||||
|
2. **Be well-documented** - Include clear instructions, examples, and use cases.
|
||||||
|
3. **Be accessible** - Written for non-technical users when possible.
|
||||||
|
4. **Include examples** - Show practical, real-world usage.
|
||||||
|
5. **Be tested** - Verify the skill works across Claude.ai, Claude Code, and/or API.
|
||||||
|
6. **Be safe** - Confirm before destructive operations.
|
||||||
|
7. **Be portable** - Work across Claude platforms when applicable.
|
||||||
|
|
||||||
|
## Skill Structure
|
||||||
|
|
||||||
|
Create a new folder with your skill name (use lowercase and hyphens):
|
||||||
|
|
||||||
|
```
|
||||||
|
skill-name/
|
||||||
|
└── SKILL.md
|
||||||
|
```
|
||||||
|
|
||||||
|
## SKILL.md Template
|
||||||
|
|
||||||
|
Use this template for your skill:
|
||||||
|
|
||||||
|
```markdown
|
||||||
|
---
|
||||||
|
name: skill-name
|
||||||
|
description: One-sentence description of what this skill does and when to use it.
|
||||||
|
---
|
||||||
|
|
||||||
|
# Skill Name
|
||||||
|
|
||||||
|
Detailed description of the skill and what it helps users accomplish.
|
||||||
|
|
||||||
|
## When to Use This Skill
|
||||||
|
|
||||||
|
- Bullet point use case 1
|
||||||
|
- Bullet point use case 2
|
||||||
|
- Bullet point use case 3
|
||||||
|
|
||||||
|
## What This Skill Does
|
||||||
|
|
||||||
|
1. **Capability 1**: Description
|
||||||
|
2. **Capability 2**: Description
|
||||||
|
3. **Capability 3**: Description
|
||||||
|
|
||||||
|
## How to Use
|
||||||
|
|
||||||
|
### Basic Usage
|
||||||
|
|
||||||
|
```
|
||||||
|
Simple example prompt
|
||||||
|
```
|
||||||
|
|
||||||
|
### Advanced Usage
|
||||||
|
|
||||||
|
```
|
||||||
|
More complex example prompt with options
|
||||||
|
```
|
||||||
|
|
||||||
|
## Example
|
||||||
|
|
||||||
|
**User**: "Example prompt"
|
||||||
|
|
||||||
|
**Output**:
|
||||||
|
```
|
||||||
|
Show what the skill produces
|
||||||
|
```
|
||||||
|
|
||||||
|
**Inspired by:** [Attribution to original source, if applicable]
|
||||||
|
|
||||||
|
## Tips
|
||||||
|
|
||||||
|
- Tip 1
|
||||||
|
- Tip 2
|
||||||
|
- Tip 3
|
||||||
|
|
||||||
|
## Common Use Cases
|
||||||
|
|
||||||
|
- Use case 1
|
||||||
|
- Use case 2
|
||||||
|
- Use case 3
|
||||||
|
```
|
||||||
|
|
||||||
|
## Adding Your Skill to README
|
||||||
|
|
||||||
|
1. Choose the appropriate category:
|
||||||
|
- Business & Marketing
|
||||||
|
- Communication & Writing
|
||||||
|
- Creative & Media
|
||||||
|
- Development
|
||||||
|
- Productivity & Organization
|
||||||
|
|
||||||
|
2. Add your skill in alphabetical order within the category:
|
||||||
|
|
||||||
|
```markdown
|
||||||
|
- [Skill Name](./skill-name/) - One-sentence description. Inspired by [Person/Source].
|
||||||
|
```
|
||||||
|
|
||||||
|
3. Follow the existing format exactly - no emojis, consistent punctuation.
|
||||||
|
|
||||||
|
## Pull Request Process
|
||||||
|
|
||||||
|
1. Fork the repository
|
||||||
|
2. Create a branch: `git checkout -b add-skill-name`
|
||||||
|
3. Add your skill folder with SKILL.md
|
||||||
|
4. Update README.md with your skill in the appropriate category
|
||||||
|
5. Commit your changes: `git commit -m "Add [Skill Name] skill"`
|
||||||
|
6. Push to your fork: `git push origin add-skill-name`
|
||||||
|
7. Open a Pull Request
|
||||||
|
|
||||||
|
## Pull Request Guidelines
|
||||||
|
|
||||||
|
Your PR should:
|
||||||
|
|
||||||
|
- **Title**: "Add [Skill Name] skill"
|
||||||
|
- **Description**: Explain the real-world use case and include:
|
||||||
|
- What problem it solves
|
||||||
|
- Who uses this workflow
|
||||||
|
- Attribution/inspiration source
|
||||||
|
- Example of how it's used
|
||||||
|
|
||||||
|
## Code of Conduct
|
||||||
|
|
||||||
|
- Be respectful and constructive
|
||||||
|
- Credit original sources and inspirations
|
||||||
|
- Focus on practical, helpful skills
|
||||||
|
- Write clear, accessible documentation
|
||||||
|
- Test your skills before submitting
|
||||||
|
|
||||||
|
## Questions?
|
||||||
|
|
||||||
|
Open an issue if you have questions about contributing or need help structuring your skill.
|
||||||
|
|
||||||
|
## Attribution
|
||||||
|
|
||||||
|
When adding a skill based on someone's workflow or use case, include proper attribution:
|
||||||
|
|
||||||
|
```markdown
|
||||||
|
**Inspired by:** [Person Name]'s workflow
|
||||||
|
```
|
||||||
|
|
||||||
|
or
|
||||||
|
|
||||||
|
```markdown
|
||||||
|
**Credit:** Based on [Company/Team]'s process
|
||||||
|
```
|
||||||
|
|
||||||
|
Examples:
|
||||||
|
- **Inspired by:** Dan Shipper's meeting analysis workflow
|
||||||
|
- **Inspired by:** Teresa Torres's content research process
|
||||||
|
- **Credit:** Based on Notion's documentation workflow
|
||||||
|
|
||||||
|
## Skill Categories
|
||||||
|
|
||||||
|
### Business & Marketing
|
||||||
|
Skills for lead generation, competitive research, branding, and business development.
|
||||||
|
|
||||||
|
### Communication & Writing
|
||||||
|
Skills for improving communication, analyzing conversations, and creating content.
|
||||||
|
|
||||||
|
### Creative & Media
|
||||||
|
Skills for working with images, videos, audio, and creative content.
|
||||||
|
|
||||||
|
### Development
|
||||||
|
Skills for software development, documentation, and technical workflows.
|
||||||
|
|
||||||
|
### Productivity & Organization
|
||||||
|
Skills for organizing files, managing tasks, and personal productivity.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
Thank you for contributing to Awesome Claude Skills!
|
||||||
|
|
||||||
207
README.md
Normal file
207
README.md
Normal file
@@ -0,0 +1,207 @@
|
|||||||
|
# Awesome Claude Skills
|
||||||
|
|
||||||
|
A curated list of practical Claude Skills for enhancing productivity across Claude.ai, Claude Code, and the Claude API.
|
||||||
|
|
||||||
|
## Contents
|
||||||
|
|
||||||
|
- [What Are Claude Skills?](#what-are-claude-skills)
|
||||||
|
- [Skills](#skills)
|
||||||
|
- [Business & Marketing](#business--marketing)
|
||||||
|
- [Communication & Writing](#communication--writing)
|
||||||
|
- [Creative & Media](#creative--media)
|
||||||
|
- [Development](#development)
|
||||||
|
- [Productivity & Organization](#productivity--organization)
|
||||||
|
- [Getting Started](#getting-started)
|
||||||
|
- [Creating Skills](#creating-skills)
|
||||||
|
- [Contributing](#contributing)
|
||||||
|
- [Resources](#resources)
|
||||||
|
- [License](#license)
|
||||||
|
|
||||||
|
## What Are Claude Skills?
|
||||||
|
|
||||||
|
Claude Skills are customizable workflows that teach Claude how to perform specific tasks according to your unique requirements. Skills enable Claude to execute tasks in a repeatable, standardized manner across all Claude platforms.
|
||||||
|
|
||||||
|
### Key Features
|
||||||
|
|
||||||
|
- **Composable** - Combine multiple skills for complex workflows.
|
||||||
|
- **Portable** - Use the same skill across Claude.ai, Claude Code, and the API.
|
||||||
|
- **Efficient** - Claude loads only what's needed for optimal performance.
|
||||||
|
- **Powerful** - Include executable code for technical reliability.
|
||||||
|
|
||||||
|
Skills can codify your organization's processes, brand guidelines, workflows, and expertise into reusable components that Claude applies automatically when needed.
|
||||||
|
|
||||||
|
## Skills
|
||||||
|
|
||||||
|
### Business & Marketing
|
||||||
|
|
||||||
|
- [Competitive Ads Extractor](./competitive-ads-extractor/) - Extracts and analyzes competitors' ads from ad libraries to understand messaging and creative approaches that resonate.
|
||||||
|
- [Domain Name Brainstormer](./domain-name-brainstormer/) - Generates creative domain name ideas and checks availability across multiple TLDs including .com, .io, .dev, and .ai extensions.
|
||||||
|
- [Lead Research Assistant](./lead-research-assistant/) - Identifies and qualifies high-quality leads by analyzing your product, searching for target companies, and providing actionable outreach strategies.
|
||||||
|
|
||||||
|
### Communication & Writing
|
||||||
|
|
||||||
|
- [Content Research Writer](./content-research-writer/) - Assists in writing high-quality content by conducting research, adding citations, improving hooks, and providing section-by-section feedback.
|
||||||
|
- [Meeting Insights Analyzer](./meeting-insights-analyzer/) - Analyzes meeting transcripts to uncover behavioral patterns including conflict avoidance, speaking ratios, filler words, and leadership style.
|
||||||
|
|
||||||
|
### Creative & Media
|
||||||
|
|
||||||
|
- [Image Enhancer](./image-enhancer/) - Improves image and screenshot quality by enhancing resolution, sharpness, and clarity for professional presentations and documentation.
|
||||||
|
- [Video Downloader](./video-downloader/) - Downloads videos from YouTube and other platforms for offline viewing, editing, or archival with support for various formats and quality options.
|
||||||
|
|
||||||
|
### Development
|
||||||
|
|
||||||
|
- [Changelog Generator](./changelog-generator/) - Automatically creates user-facing changelogs from git commits by analyzing history and transforming technical commits into customer-friendly release notes.
|
||||||
|
|
||||||
|
### Productivity & Organization
|
||||||
|
|
||||||
|
- [File Organizer](./file-organizer/) - Intelligently organizes files and folders by understanding context, finding duplicates, and suggesting better organizational structures.
|
||||||
|
- [Invoice Organizer](./invoice-organizer/) - Automatically organizes invoices and receipts for tax preparation by reading files, extracting information, and renaming consistently.
|
||||||
|
- [Raffle Winner Picker](./raffle-winner-picker/) - Randomly selects winners from lists, spreadsheets, or Google Sheets for giveaways and contests with cryptographically secure randomness.
|
||||||
|
|
||||||
|
## Getting Started
|
||||||
|
|
||||||
|
### Using Skills in Claude.ai
|
||||||
|
|
||||||
|
1. Navigate to your Claude.ai account
|
||||||
|
2. Go to Settings → Skills
|
||||||
|
3. Upload or create a new skill
|
||||||
|
4. The skill will be available automatically when relevant to your conversations
|
||||||
|
|
||||||
|
### Using Skills in Claude Code
|
||||||
|
|
||||||
|
1. Install Claude Code:
|
||||||
|
```bash
|
||||||
|
# Mac
|
||||||
|
curl -fsSL https://claude.ai/install.sh | bash
|
||||||
|
|
||||||
|
# Windows
|
||||||
|
irm https://claude.ai/install.ps1 | iex
|
||||||
|
```
|
||||||
|
|
||||||
|
2. Navigate to the skill folder:
|
||||||
|
```bash
|
||||||
|
cd awesome-claude-skills/lead-research-assistant
|
||||||
|
```
|
||||||
|
|
||||||
|
3. Start Claude Code:
|
||||||
|
```bash
|
||||||
|
claude
|
||||||
|
```
|
||||||
|
|
||||||
|
4. The skill loads automatically and activates when relevant.
|
||||||
|
|
||||||
|
### Using Skills via API
|
||||||
|
|
||||||
|
Use the Claude Skills API to programmatically load and manage skills:
|
||||||
|
|
||||||
|
```python
|
||||||
|
import anthropic
|
||||||
|
|
||||||
|
client = anthropic.Anthropic(api_key="your-api-key")
|
||||||
|
|
||||||
|
response = client.messages.create(
|
||||||
|
model="claude-3-5-sonnet-20241022",
|
||||||
|
skills=["skill-id-here"],
|
||||||
|
messages=[{"role": "user", "content": "Your prompt"}]
|
||||||
|
)
|
||||||
|
```
|
||||||
|
|
||||||
|
See the [Skills API documentation](https://docs.claude.com/en/api/skills-guide) for details.
|
||||||
|
|
||||||
|
## Creating Skills
|
||||||
|
|
||||||
|
### Skill Structure
|
||||||
|
|
||||||
|
Each skill is a folder containing a `SKILL.md` file with YAML frontmatter:
|
||||||
|
|
||||||
|
```
|
||||||
|
skill-name/
|
||||||
|
├── SKILL.md # Required: Skill instructions and metadata
|
||||||
|
├── scripts/ # Optional: Helper scripts
|
||||||
|
├── templates/ # Optional: Document templates
|
||||||
|
└── resources/ # Optional: Reference files
|
||||||
|
```
|
||||||
|
|
||||||
|
### Basic Skill Template
|
||||||
|
|
||||||
|
```markdown
|
||||||
|
---
|
||||||
|
name: my-skill-name
|
||||||
|
description: A clear description of what this skill does and when to use it.
|
||||||
|
---
|
||||||
|
|
||||||
|
# My Skill Name
|
||||||
|
|
||||||
|
Detailed description of the skill's purpose and capabilities.
|
||||||
|
|
||||||
|
## When to Use This Skill
|
||||||
|
|
||||||
|
- Use case 1
|
||||||
|
- Use case 2
|
||||||
|
- Use case 3
|
||||||
|
|
||||||
|
## Instructions
|
||||||
|
|
||||||
|
[Detailed instructions for Claude on how to execute this skill]
|
||||||
|
|
||||||
|
## Examples
|
||||||
|
|
||||||
|
[Real-world examples showing the skill in action]
|
||||||
|
```
|
||||||
|
|
||||||
|
### Skill Best Practices
|
||||||
|
|
||||||
|
- Focus on specific, repeatable tasks
|
||||||
|
- Include clear examples and edge cases
|
||||||
|
- Write instructions for Claude, not end users
|
||||||
|
- Test across Claude.ai, Claude Code, and API
|
||||||
|
- Document prerequisites and dependencies
|
||||||
|
- Include error handling guidance
|
||||||
|
|
||||||
|
## Contributing
|
||||||
|
|
||||||
|
We welcome contributions! Please read our [Contributing Guidelines](CONTRIBUTING.md) for details on:
|
||||||
|
|
||||||
|
- How to submit new skills
|
||||||
|
- Skill quality standards
|
||||||
|
- Pull request process
|
||||||
|
- Code of conduct
|
||||||
|
|
||||||
|
### Quick Contribution Steps
|
||||||
|
|
||||||
|
1. Ensure your skill is based on a real use case
|
||||||
|
2. Check for duplicates in existing skills
|
||||||
|
3. Follow the skill structure template
|
||||||
|
4. Test your skill across platforms
|
||||||
|
5. Submit a pull request with clear documentation
|
||||||
|
|
||||||
|
## Resources
|
||||||
|
|
||||||
|
### Official Documentation
|
||||||
|
|
||||||
|
- [Claude Skills Overview](https://www.anthropic.com/news/skills) - Official announcement and features
|
||||||
|
- [Skills User Guide](https://support.claude.com/en/articles/12512180-using-skills-in-claude) - How to use skills in Claude
|
||||||
|
- [Creating Custom Skills](https://support.claude.com/en/articles/12512198-creating-custom-skills) - Skill development guide
|
||||||
|
- [Skills API Documentation](https://docs.claude.com/en/api/skills-guide) - API integration guide
|
||||||
|
- [Agent Skills Blog Post](https://anthropic.com/engineering/equipping-agents-for-the-real-world-with-agent-skills) - Engineering deep dive
|
||||||
|
|
||||||
|
### Community Resources
|
||||||
|
|
||||||
|
- [Anthropic Skills Repository](https://github.com/anthropics/skills) - Official example skills
|
||||||
|
- [Claude Community](https://community.anthropic.com) - Discuss skills with other users
|
||||||
|
- [Skills Marketplace](https://claude.ai/marketplace) - Discover and share skills
|
||||||
|
|
||||||
|
### Inspiration & Use Cases
|
||||||
|
|
||||||
|
- [Lenny's Newsletter](https://www.lennysnewsletter.com/p/everyone-should-be-using-claude-code) - 50 ways people use Claude Code
|
||||||
|
- [Notion Skills](https://www.notion.so/notiondevs/Notion-Skills-for-Claude-28da4445d27180c7af1df7d8615723d0) - Notion integration skills
|
||||||
|
|
||||||
|
## License
|
||||||
|
|
||||||
|
This repository is licensed under the Apache License 2.0.
|
||||||
|
|
||||||
|
Individual skills may have different licenses - please check each skill's folder for specific licensing information.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
**Note**: Claude Skills work across Claude.ai, Claude Code, and the Claude API. Once you create a skill, it's portable across all platforms, making your workflows consistent everywhere you use Claude.
|
||||||
104
changelog-generator/SKILL.md
Normal file
104
changelog-generator/SKILL.md
Normal file
@@ -0,0 +1,104 @@
|
|||||||
|
---
|
||||||
|
name: changelog-generator
|
||||||
|
description: Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.
|
||||||
|
---
|
||||||
|
|
||||||
|
# Changelog Generator
|
||||||
|
|
||||||
|
This skill transforms technical git commits into polished, user-friendly changelogs that your customers and users will actually understand and appreciate.
|
||||||
|
|
||||||
|
## When to Use This Skill
|
||||||
|
|
||||||
|
- Preparing release notes for a new version
|
||||||
|
- Creating weekly or monthly product update summaries
|
||||||
|
- Documenting changes for customers
|
||||||
|
- Writing changelog entries for app store submissions
|
||||||
|
- Generating update notifications
|
||||||
|
- Creating internal release documentation
|
||||||
|
- Maintaining a public changelog/product updates page
|
||||||
|
|
||||||
|
## What This Skill Does
|
||||||
|
|
||||||
|
1. **Scans Git History**: Analyzes commits from a specific time period or between versions
|
||||||
|
2. **Categorizes Changes**: Groups commits into logical categories (features, improvements, bug fixes, breaking changes, security)
|
||||||
|
3. **Translates Technical → User-Friendly**: Converts developer commits into customer language
|
||||||
|
4. **Formats Professionally**: Creates clean, structured changelog entries
|
||||||
|
5. **Filters Noise**: Excludes internal commits (refactoring, tests, etc.)
|
||||||
|
6. **Follows Best Practices**: Applies changelog guidelines and your brand voice
|
||||||
|
|
||||||
|
## How to Use
|
||||||
|
|
||||||
|
### Basic Usage
|
||||||
|
|
||||||
|
From your project repository:
|
||||||
|
|
||||||
|
```
|
||||||
|
Create a changelog from commits since last release
|
||||||
|
```
|
||||||
|
|
||||||
|
```
|
||||||
|
Generate changelog for all commits from the past week
|
||||||
|
```
|
||||||
|
|
||||||
|
```
|
||||||
|
Create release notes for version 2.5.0
|
||||||
|
```
|
||||||
|
|
||||||
|
### With Specific Date Range
|
||||||
|
|
||||||
|
```
|
||||||
|
Create a changelog for all commits between March 1 and March 15
|
||||||
|
```
|
||||||
|
|
||||||
|
### With Custom Guidelines
|
||||||
|
|
||||||
|
```
|
||||||
|
Create a changelog for commits since v2.4.0, using my changelog
|
||||||
|
guidelines from CHANGELOG_STYLE.md
|
||||||
|
```
|
||||||
|
|
||||||
|
## Example
|
||||||
|
|
||||||
|
**User**: "Create a changelog for commits from the past 7 days"
|
||||||
|
|
||||||
|
**Output**:
|
||||||
|
```markdown
|
||||||
|
# Updates - Week of March 10, 2024
|
||||||
|
|
||||||
|
## ✨ New Features
|
||||||
|
|
||||||
|
- **Team Workspaces**: Create separate workspaces for different
|
||||||
|
projects. Invite team members and keep everything organized.
|
||||||
|
|
||||||
|
- **Keyboard Shortcuts**: Press ? to see all available shortcuts.
|
||||||
|
Navigate faster without touching your mouse.
|
||||||
|
|
||||||
|
## 🔧 Improvements
|
||||||
|
|
||||||
|
- **Faster Sync**: Files now sync 2x faster across devices
|
||||||
|
- **Better Search**: Search now includes file contents, not just titles
|
||||||
|
|
||||||
|
## 🐛 Fixes
|
||||||
|
|
||||||
|
- Fixed issue where large images wouldn't upload
|
||||||
|
- Resolved timezone confusion in scheduled posts
|
||||||
|
- Corrected notification badge count
|
||||||
|
```
|
||||||
|
|
||||||
|
**Inspired by:** Manik Aggarwal's use case from Lenny's Newsletter
|
||||||
|
|
||||||
|
## Tips
|
||||||
|
|
||||||
|
- Run from your git repository root
|
||||||
|
- Specify date ranges for focused changelogs
|
||||||
|
- Use your CHANGELOG_STYLE.md for consistent formatting
|
||||||
|
- Review and adjust the generated changelog before publishing
|
||||||
|
- Save output directly to CHANGELOG.md
|
||||||
|
|
||||||
|
## Related Use Cases
|
||||||
|
|
||||||
|
- Creating GitHub release notes
|
||||||
|
- Writing app store update descriptions
|
||||||
|
- Generating email updates for users
|
||||||
|
- Creating social media announcement posts
|
||||||
|
|
||||||
293
competitive-ads-extractor/SKILL.md
Normal file
293
competitive-ads-extractor/SKILL.md
Normal file
@@ -0,0 +1,293 @@
|
|||||||
|
---
|
||||||
|
name: competitive-ads-extractor
|
||||||
|
description: Extracts and analyzes competitors' ads from ad libraries (Facebook, LinkedIn, etc.) to understand what messaging, problems, and creative approaches are working. Helps inspire and improve your own ad campaigns.
|
||||||
|
---
|
||||||
|
|
||||||
|
# Competitive Ads Extractor
|
||||||
|
|
||||||
|
This skill extracts your competitors' ads from ad libraries and analyzes what's working—the problems they're highlighting, use cases they're targeting, and copy/creative that's resonating.
|
||||||
|
|
||||||
|
## When to Use This Skill
|
||||||
|
|
||||||
|
- Researching competitor ad strategies
|
||||||
|
- Finding inspiration for your own ads
|
||||||
|
- Understanding market positioning
|
||||||
|
- Identifying successful ad patterns
|
||||||
|
- Analyzing messaging that works
|
||||||
|
- Discovering new use cases or pain points
|
||||||
|
- Planning ad campaigns with proven concepts
|
||||||
|
|
||||||
|
## What This Skill Does
|
||||||
|
|
||||||
|
1. **Extracts Ads**: Scrapes ads from Facebook Ad Library, LinkedIn, etc.
|
||||||
|
2. **Captures Screenshots**: Saves visual copies of all ads
|
||||||
|
3. **Analyzes Messaging**: Identifies problems, use cases, and value props
|
||||||
|
4. **Categorizes Ads**: Groups by theme, audience, or format
|
||||||
|
5. **Identifies Patterns**: Finds common successful approaches
|
||||||
|
6. **Provides Insights**: Explains why certain ads likely perform well
|
||||||
|
|
||||||
|
## How to Use
|
||||||
|
|
||||||
|
### Basic Extraction
|
||||||
|
|
||||||
|
```
|
||||||
|
Extract all current ads from [Competitor Name] on Facebook Ad Library
|
||||||
|
```
|
||||||
|
|
||||||
|
```
|
||||||
|
Scrape ads from [Company] and analyze their messaging
|
||||||
|
```
|
||||||
|
|
||||||
|
### Specific Analysis
|
||||||
|
|
||||||
|
```
|
||||||
|
Get all ads from [Competitor] focusing on their messaging
|
||||||
|
about [specific problem]. What pain points are they highlighting?
|
||||||
|
```
|
||||||
|
|
||||||
|
### Competitive Set
|
||||||
|
|
||||||
|
```
|
||||||
|
Extract ads from these 5 competitors: [list].
|
||||||
|
Compare their approaches and tell me what's working.
|
||||||
|
```
|
||||||
|
|
||||||
|
### Specific Platform
|
||||||
|
|
||||||
|
```
|
||||||
|
Get LinkedIn ads from [Competitor] and analyze their
|
||||||
|
B2B positioning strategy
|
||||||
|
```
|
||||||
|
|
||||||
|
## Example
|
||||||
|
|
||||||
|
**User**: "Extract ads from Notion on Facebook Ad Library and tell me what messaging is working for them."
|
||||||
|
|
||||||
|
**Process**:
|
||||||
|
```
|
||||||
|
Accessing Facebook Ad Library...
|
||||||
|
Searching for: Notion
|
||||||
|
Found: 23 active ads
|
||||||
|
|
||||||
|
Extracting screenshots...
|
||||||
|
[████████████████████] 100%
|
||||||
|
|
||||||
|
Saved to: competitor-ads/notion/
|
||||||
|
- ad-001-collaboration.png
|
||||||
|
- ad-002-productivity.png
|
||||||
|
- ad-003-templates.png
|
||||||
|
...
|
||||||
|
|
||||||
|
Analyzing messaging...
|
||||||
|
```
|
||||||
|
|
||||||
|
**Output**:
|
||||||
|
```
|
||||||
|
# Notion Ad Analysis
|
||||||
|
|
||||||
|
## Overview
|
||||||
|
- Total Ads: 23 active
|
||||||
|
- Primary Themes: Productivity (35%), Collaboration (30%),
|
||||||
|
Templates (20%), AI Features (15%)
|
||||||
|
- Ad Formats: Static images (60%), Video (40%)
|
||||||
|
- CTA Patterns: "Try for free", "Get started"
|
||||||
|
|
||||||
|
## Key Problems They're Highlighting
|
||||||
|
|
||||||
|
1. **Scattered Information** (8 ads)
|
||||||
|
Copy: "Stop switching between 10 different tools"
|
||||||
|
Why it works: Direct pain point many teams face
|
||||||
|
|
||||||
|
2. **Meeting Overload** (5 ads)
|
||||||
|
Copy: "Replace unnecessary meetings with async updates"
|
||||||
|
Why it works: Post-COVID remote work pain point
|
||||||
|
|
||||||
|
3. **Lost Documentation** (4 ads)
|
||||||
|
Copy: "Never ask 'where is that doc?' again"
|
||||||
|
Why it works: Universal workplace frustration
|
||||||
|
|
||||||
|
## Successful Creative Patterns
|
||||||
|
|
||||||
|
### Pattern 1: Before/After Split
|
||||||
|
- Shows chaotic tool landscape → Clean Notion workspace
|
||||||
|
- Used in 6 high-performing ads
|
||||||
|
- Visual metaphor is immediately clear
|
||||||
|
|
||||||
|
### Pattern 2: Feature Showcase
|
||||||
|
- GIF of actual product usage
|
||||||
|
- Shows specific feature in 5 seconds
|
||||||
|
- Used for new features (AI, templates)
|
||||||
|
|
||||||
|
### Pattern 3: Social Proof
|
||||||
|
- "Join 20M users" messaging
|
||||||
|
- Customer logos
|
||||||
|
- Used in 4 ads targeting enterprise
|
||||||
|
|
||||||
|
## Copy That's Working
|
||||||
|
|
||||||
|
Best Headlines:
|
||||||
|
1. "Your team's knowledge, finally in one place"
|
||||||
|
→ Benefit-focused, addresses pain directly
|
||||||
|
|
||||||
|
2. "The all-in-one workspace"
|
||||||
|
→ Clear positioning, broad appeal
|
||||||
|
|
||||||
|
3. "AI that actually helps you work"
|
||||||
|
→ Addresses AI skepticism, practical angle
|
||||||
|
|
||||||
|
Best Body Copy Patterns:
|
||||||
|
- Short sentences (under 10 words)
|
||||||
|
- Focus on outcomes not features
|
||||||
|
- Include specific numbers ("Cut meetings by 50%")
|
||||||
|
|
||||||
|
## Audience Targeting Insights
|
||||||
|
|
||||||
|
Based on ad variations:
|
||||||
|
- Startup founders: Solo productivity angle
|
||||||
|
- Team leads: Collaboration and alignment
|
||||||
|
- Enterprise: Security and compliance mentions
|
||||||
|
- Students: Free plan, templates, organization
|
||||||
|
|
||||||
|
## Recommendations for Your Ads
|
||||||
|
|
||||||
|
1. **Test the "tool sprawl" pain point**
|
||||||
|
→ Strong resonance based on their ad frequency
|
||||||
|
|
||||||
|
2. **Use product screenshots over abstract visuals**
|
||||||
|
→ All their top ads show actual UI
|
||||||
|
|
||||||
|
3. **Lead with the problem, not the solution**
|
||||||
|
→ "Tired of X?" performs better than "Introducing Y"
|
||||||
|
|
||||||
|
4. **Keep copy under 100 characters**
|
||||||
|
→ Their shortest ads seem most frequent
|
||||||
|
|
||||||
|
5. **Test before/after visual formats**
|
||||||
|
→ Proven pattern in their creative
|
||||||
|
|
||||||
|
## Files Saved
|
||||||
|
- All ads: ~/competitor-ads/notion/
|
||||||
|
- Analysis: ~/competitor-ads/notion/analysis.md
|
||||||
|
- Best performers: ~/competitor-ads/notion/top-10/
|
||||||
|
```
|
||||||
|
|
||||||
|
**Inspired by:** Sumant Subrahmanya's use case from Lenny's Newsletter
|
||||||
|
|
||||||
|
## What You Can Learn
|
||||||
|
|
||||||
|
### Messaging Analysis
|
||||||
|
- What problems they emphasize
|
||||||
|
- How they position against competition
|
||||||
|
- Value propositions that resonate
|
||||||
|
- Target audience segments
|
||||||
|
|
||||||
|
### Creative Patterns
|
||||||
|
- Visual styles that work
|
||||||
|
- Video vs. static image performance
|
||||||
|
- Color schemes and branding
|
||||||
|
- Layout patterns
|
||||||
|
|
||||||
|
### Copy Formulas
|
||||||
|
- Headline structures
|
||||||
|
- Call-to-action patterns
|
||||||
|
- Length and tone
|
||||||
|
- Emotional triggers
|
||||||
|
|
||||||
|
### Campaign Strategy
|
||||||
|
- Seasonal campaigns
|
||||||
|
- Product launch approaches
|
||||||
|
- Feature announcement tactics
|
||||||
|
- Retargeting patterns
|
||||||
|
|
||||||
|
## Best Practices
|
||||||
|
|
||||||
|
### Legal & Ethical
|
||||||
|
✓ Only use for research and inspiration
|
||||||
|
✓ Don't copy ads directly
|
||||||
|
✓ Respect intellectual property
|
||||||
|
✓ Use insights to inform original creative
|
||||||
|
✗ Don't plagiarize copy or steal designs
|
||||||
|
|
||||||
|
### Analysis Tips
|
||||||
|
1. **Look for patterns**: What themes repeat?
|
||||||
|
2. **Track over time**: Save ads monthly to see evolution
|
||||||
|
3. **Test hypotheses**: Adapt successful patterns for your brand
|
||||||
|
4. **Segment by audience**: Different messages for different targets
|
||||||
|
5. **Compare platforms**: LinkedIn vs Facebook messaging differs
|
||||||
|
|
||||||
|
## Advanced Features
|
||||||
|
|
||||||
|
### Trend Tracking
|
||||||
|
```
|
||||||
|
Compare [Competitor]'s ads from Q1 vs Q2.
|
||||||
|
What messaging has changed?
|
||||||
|
```
|
||||||
|
|
||||||
|
### Multi-Competitor Analysis
|
||||||
|
```
|
||||||
|
Extract ads from [Company A], [Company B], [Company C].
|
||||||
|
What are the common patterns? Where do they differ?
|
||||||
|
```
|
||||||
|
|
||||||
|
### Industry Benchmarks
|
||||||
|
```
|
||||||
|
Show me ad patterns across the top 10 project management
|
||||||
|
tools. What problems do they all focus on?
|
||||||
|
```
|
||||||
|
|
||||||
|
### Format Analysis
|
||||||
|
```
|
||||||
|
Analyze video ads vs static image ads from [Competitor].
|
||||||
|
Which gets more engagement? (if data available)
|
||||||
|
```
|
||||||
|
|
||||||
|
## Common Workflows
|
||||||
|
|
||||||
|
### Ad Campaign Planning
|
||||||
|
1. Extract competitor ads
|
||||||
|
2. Identify successful patterns
|
||||||
|
3. Note gaps in their messaging
|
||||||
|
4. Brainstorm unique angles
|
||||||
|
5. Draft test ad variations
|
||||||
|
|
||||||
|
### Positioning Research
|
||||||
|
1. Get ads from 5 competitors
|
||||||
|
2. Map their positioning
|
||||||
|
3. Find underserved angles
|
||||||
|
4. Develop differentiated messaging
|
||||||
|
5. Test against their approaches
|
||||||
|
|
||||||
|
### Creative Inspiration
|
||||||
|
1. Extract ads by theme
|
||||||
|
2. Analyze visual patterns
|
||||||
|
3. Note color and layout trends
|
||||||
|
4. Adapt successful patterns
|
||||||
|
5. Create original variations
|
||||||
|
|
||||||
|
## Tips for Success
|
||||||
|
|
||||||
|
1. **Regular Monitoring**: Check monthly for changes
|
||||||
|
2. **Broad Research**: Look at adjacent competitors too
|
||||||
|
3. **Save Everything**: Build a reference library
|
||||||
|
4. **Test Insights**: Run your own experiments
|
||||||
|
5. **Track Performance**: A/B test inspired concepts
|
||||||
|
6. **Stay Original**: Use for inspiration, not copying
|
||||||
|
7. **Multiple Platforms**: Compare Facebook, LinkedIn, TikTok, etc.
|
||||||
|
|
||||||
|
## Output Formats
|
||||||
|
|
||||||
|
- **Screenshots**: All ads saved as images
|
||||||
|
- **Analysis Report**: Markdown summary of insights
|
||||||
|
- **Spreadsheet**: CSV with ad copy, CTAs, themes
|
||||||
|
- **Presentation**: Visual deck of top performers
|
||||||
|
- **Pattern Library**: Categorized by approach
|
||||||
|
|
||||||
|
## Related Use Cases
|
||||||
|
|
||||||
|
- Writing better ad copy for your campaigns
|
||||||
|
- Understanding market positioning
|
||||||
|
- Finding content gaps in your messaging
|
||||||
|
- Discovering new use cases for your product
|
||||||
|
- Planning product marketing strategy
|
||||||
|
- Inspiring social media content
|
||||||
|
|
||||||
538
content-research-writer/SKILL.md
Normal file
538
content-research-writer/SKILL.md
Normal file
@@ -0,0 +1,538 @@
|
|||||||
|
---
|
||||||
|
name: content-research-writer
|
||||||
|
description: Assists in writing high-quality content by conducting research, adding citations, improving hooks, iterating on outlines, and providing real-time feedback on each section. Transforms your writing process from solo effort to collaborative partnership.
|
||||||
|
---
|
||||||
|
|
||||||
|
# Content Research Writer
|
||||||
|
|
||||||
|
This skill acts as your writing partner, helping you research, outline, draft, and refine content while maintaining your unique voice and style.
|
||||||
|
|
||||||
|
## When to Use This Skill
|
||||||
|
|
||||||
|
- Writing blog posts, articles, or newsletters
|
||||||
|
- Creating educational content or tutorials
|
||||||
|
- Drafting thought leadership pieces
|
||||||
|
- Researching and writing case studies
|
||||||
|
- Producing technical documentation with sources
|
||||||
|
- Writing with proper citations and references
|
||||||
|
- Improving hooks and introductions
|
||||||
|
- Getting section-by-section feedback while writing
|
||||||
|
|
||||||
|
## What This Skill Does
|
||||||
|
|
||||||
|
1. **Collaborative Outlining**: Helps you structure ideas into coherent outlines
|
||||||
|
2. **Research Assistance**: Finds relevant information and adds citations
|
||||||
|
3. **Hook Improvement**: Strengthens your opening to capture attention
|
||||||
|
4. **Section Feedback**: Reviews each section as you write
|
||||||
|
5. **Voice Preservation**: Maintains your writing style and tone
|
||||||
|
6. **Citation Management**: Adds and formats references properly
|
||||||
|
7. **Iterative Refinement**: Helps you improve through multiple drafts
|
||||||
|
|
||||||
|
## How to Use
|
||||||
|
|
||||||
|
### Setup Your Writing Environment
|
||||||
|
|
||||||
|
Create a dedicated folder for your article:
|
||||||
|
```
|
||||||
|
mkdir ~/writing/my-article-title
|
||||||
|
cd ~/writing/my-article-title
|
||||||
|
```
|
||||||
|
|
||||||
|
Create your draft file:
|
||||||
|
```
|
||||||
|
touch article-draft.md
|
||||||
|
```
|
||||||
|
|
||||||
|
Open Claude Code from this directory and start writing.
|
||||||
|
|
||||||
|
### Basic Workflow
|
||||||
|
|
||||||
|
1. **Start with an outline**:
|
||||||
|
```
|
||||||
|
Help me create an outline for an article about [topic]
|
||||||
|
```
|
||||||
|
|
||||||
|
2. **Research and add citations**:
|
||||||
|
```
|
||||||
|
Research [specific topic] and add citations to my outline
|
||||||
|
```
|
||||||
|
|
||||||
|
3. **Improve the hook**:
|
||||||
|
```
|
||||||
|
Here's my introduction. Help me make the hook more compelling.
|
||||||
|
```
|
||||||
|
|
||||||
|
4. **Get section feedback**:
|
||||||
|
```
|
||||||
|
I just finished the "Why This Matters" section. Review it and give feedback.
|
||||||
|
```
|
||||||
|
|
||||||
|
5. **Refine and polish**:
|
||||||
|
```
|
||||||
|
Review the full draft for flow, clarity, and consistency.
|
||||||
|
```
|
||||||
|
|
||||||
|
## Instructions
|
||||||
|
|
||||||
|
When a user requests writing assistance:
|
||||||
|
|
||||||
|
1. **Understand the Writing Project**
|
||||||
|
|
||||||
|
Ask clarifying questions:
|
||||||
|
- What's the topic and main argument?
|
||||||
|
- Who's the target audience?
|
||||||
|
- What's the desired length/format?
|
||||||
|
- What's your goal? (educate, persuade, entertain, explain)
|
||||||
|
- Any existing research or sources to include?
|
||||||
|
- What's your writing style? (formal, conversational, technical)
|
||||||
|
|
||||||
|
2. **Collaborative Outlining**
|
||||||
|
|
||||||
|
Help structure the content:
|
||||||
|
|
||||||
|
```markdown
|
||||||
|
# Article Outline: [Title]
|
||||||
|
|
||||||
|
## Hook
|
||||||
|
- [Opening line/story/statistic]
|
||||||
|
- [Why reader should care]
|
||||||
|
|
||||||
|
## Introduction
|
||||||
|
- Context and background
|
||||||
|
- Problem statement
|
||||||
|
- What this article covers
|
||||||
|
|
||||||
|
## Main Sections
|
||||||
|
|
||||||
|
### Section 1: [Title]
|
||||||
|
- Key point A
|
||||||
|
- Key point B
|
||||||
|
- Example/evidence
|
||||||
|
- [Research needed: specific topic]
|
||||||
|
|
||||||
|
### Section 2: [Title]
|
||||||
|
- Key point C
|
||||||
|
- Key point D
|
||||||
|
- Data/citation needed
|
||||||
|
|
||||||
|
### Section 3: [Title]
|
||||||
|
- Key point E
|
||||||
|
- Counter-arguments
|
||||||
|
- Resolution
|
||||||
|
|
||||||
|
## Conclusion
|
||||||
|
- Summary of main points
|
||||||
|
- Call to action
|
||||||
|
- Final thought
|
||||||
|
|
||||||
|
## Research To-Do
|
||||||
|
- [ ] Find data on [topic]
|
||||||
|
- [ ] Get examples of [concept]
|
||||||
|
- [ ] Source citation for [claim]
|
||||||
|
```
|
||||||
|
|
||||||
|
**Iterate on outline**:
|
||||||
|
- Adjust based on feedback
|
||||||
|
- Ensure logical flow
|
||||||
|
- Identify research gaps
|
||||||
|
- Mark sections for deep dives
|
||||||
|
|
||||||
|
3. **Conduct Research**
|
||||||
|
|
||||||
|
When user requests research on a topic:
|
||||||
|
|
||||||
|
- Search for relevant information
|
||||||
|
- Find credible sources
|
||||||
|
- Extract key facts, quotes, and data
|
||||||
|
- Add citations in requested format
|
||||||
|
|
||||||
|
Example output:
|
||||||
|
```markdown
|
||||||
|
## Research: AI Impact on Productivity
|
||||||
|
|
||||||
|
Key Findings:
|
||||||
|
|
||||||
|
1. **Productivity Gains**: Studies show 40% time savings for
|
||||||
|
content creation tasks [1]
|
||||||
|
|
||||||
|
2. **Adoption Rates**: 67% of knowledge workers use AI tools
|
||||||
|
weekly [2]
|
||||||
|
|
||||||
|
3. **Expert Quote**: "AI augments rather than replaces human
|
||||||
|
creativity" - Dr. Jane Smith, MIT [3]
|
||||||
|
|
||||||
|
Citations:
|
||||||
|
[1] McKinsey Global Institute. (2024). "The Economic Potential
|
||||||
|
of Generative AI"
|
||||||
|
[2] Stack Overflow Developer Survey (2024)
|
||||||
|
[3] Smith, J. (2024). MIT Technology Review interview
|
||||||
|
|
||||||
|
Added to outline under Section 2.
|
||||||
|
```
|
||||||
|
|
||||||
|
4. **Improve Hooks**
|
||||||
|
|
||||||
|
When user shares an introduction, analyze and strengthen:
|
||||||
|
|
||||||
|
**Current Hook Analysis**:
|
||||||
|
- What works: [positive elements]
|
||||||
|
- What could be stronger: [areas for improvement]
|
||||||
|
- Emotional impact: [current vs. potential]
|
||||||
|
|
||||||
|
**Suggested Alternatives**:
|
||||||
|
|
||||||
|
Option 1: [Bold statement]
|
||||||
|
> [Example]
|
||||||
|
*Why it works: [explanation]*
|
||||||
|
|
||||||
|
Option 2: [Personal story]
|
||||||
|
> [Example]
|
||||||
|
*Why it works: [explanation]*
|
||||||
|
|
||||||
|
Option 3: [Surprising data]
|
||||||
|
> [Example]
|
||||||
|
*Why it works: [explanation]*
|
||||||
|
|
||||||
|
**Questions to hook**:
|
||||||
|
- Does it create curiosity?
|
||||||
|
- Does it promise value?
|
||||||
|
- Is it specific enough?
|
||||||
|
- Does it match the audience?
|
||||||
|
|
||||||
|
5. **Provide Section-by-Section Feedback**
|
||||||
|
|
||||||
|
As user writes each section, review for:
|
||||||
|
|
||||||
|
```markdown
|
||||||
|
# Feedback: [Section Name]
|
||||||
|
|
||||||
|
## What Works Well ✓
|
||||||
|
- [Strength 1]
|
||||||
|
- [Strength 2]
|
||||||
|
- [Strength 3]
|
||||||
|
|
||||||
|
## Suggestions for Improvement
|
||||||
|
|
||||||
|
### Clarity
|
||||||
|
- [Specific issue] → [Suggested fix]
|
||||||
|
- [Complex sentence] → [Simpler alternative]
|
||||||
|
|
||||||
|
### Flow
|
||||||
|
- [Transition issue] → [Better connection]
|
||||||
|
- [Paragraph order] → [Suggested reordering]
|
||||||
|
|
||||||
|
### Evidence
|
||||||
|
- [Claim needing support] → [Add citation or example]
|
||||||
|
- [Generic statement] → [Make more specific]
|
||||||
|
|
||||||
|
### Style
|
||||||
|
- [Tone inconsistency] → [Match your voice better]
|
||||||
|
- [Word choice] → [Stronger alternative]
|
||||||
|
|
||||||
|
## Specific Line Edits
|
||||||
|
|
||||||
|
Original:
|
||||||
|
> [Exact quote from draft]
|
||||||
|
|
||||||
|
Suggested:
|
||||||
|
> [Improved version]
|
||||||
|
|
||||||
|
Why: [Explanation]
|
||||||
|
|
||||||
|
## Questions to Consider
|
||||||
|
- [Thought-provoking question 1]
|
||||||
|
- [Thought-provoking question 2]
|
||||||
|
|
||||||
|
Ready to move to next section!
|
||||||
|
```
|
||||||
|
|
||||||
|
6. **Preserve Writer's Voice**
|
||||||
|
|
||||||
|
Important principles:
|
||||||
|
|
||||||
|
- **Learn their style**: Read existing writing samples
|
||||||
|
- **Suggest, don't replace**: Offer options, not directives
|
||||||
|
- **Match tone**: Formal, casual, technical, friendly
|
||||||
|
- **Respect choices**: If they prefer their version, support it
|
||||||
|
- **Enhance, don't override**: Make their writing better, not different
|
||||||
|
|
||||||
|
Ask periodically:
|
||||||
|
- "Does this sound like you?"
|
||||||
|
- "Is this the right tone?"
|
||||||
|
- "Should I be more/less [formal/casual/technical]?"
|
||||||
|
|
||||||
|
7. **Citation Management**
|
||||||
|
|
||||||
|
Handle references based on user preference:
|
||||||
|
|
||||||
|
**Inline Citations**:
|
||||||
|
```markdown
|
||||||
|
Studies show 40% productivity improvement (McKinsey, 2024).
|
||||||
|
```
|
||||||
|
|
||||||
|
**Numbered References**:
|
||||||
|
```markdown
|
||||||
|
Studies show 40% productivity improvement [1].
|
||||||
|
|
||||||
|
[1] McKinsey Global Institute. (2024)...
|
||||||
|
```
|
||||||
|
|
||||||
|
**Footnote Style**:
|
||||||
|
```markdown
|
||||||
|
Studies show 40% productivity improvement^1
|
||||||
|
|
||||||
|
^1: McKinsey Global Institute. (2024)...
|
||||||
|
```
|
||||||
|
|
||||||
|
Maintain a running citations list:
|
||||||
|
```markdown
|
||||||
|
## References
|
||||||
|
|
||||||
|
1. Author. (Year). "Title". Publication.
|
||||||
|
2. Author. (Year). "Title". Publication.
|
||||||
|
...
|
||||||
|
```
|
||||||
|
|
||||||
|
8. **Final Review and Polish**
|
||||||
|
|
||||||
|
When draft is complete, provide comprehensive feedback:
|
||||||
|
|
||||||
|
```markdown
|
||||||
|
# Full Draft Review
|
||||||
|
|
||||||
|
## Overall Assessment
|
||||||
|
|
||||||
|
**Strengths**:
|
||||||
|
- [Major strength 1]
|
||||||
|
- [Major strength 2]
|
||||||
|
- [Major strength 3]
|
||||||
|
|
||||||
|
**Impact**: [Overall effectiveness assessment]
|
||||||
|
|
||||||
|
## Structure & Flow
|
||||||
|
- [Comments on organization]
|
||||||
|
- [Transition quality]
|
||||||
|
- [Pacing assessment]
|
||||||
|
|
||||||
|
## Content Quality
|
||||||
|
- [Argument strength]
|
||||||
|
- [Evidence sufficiency]
|
||||||
|
- [Example effectiveness]
|
||||||
|
|
||||||
|
## Technical Quality
|
||||||
|
- Grammar and mechanics: [assessment]
|
||||||
|
- Consistency: [assessment]
|
||||||
|
- Citations: [completeness check]
|
||||||
|
|
||||||
|
## Readability
|
||||||
|
- Clarity score: [evaluation]
|
||||||
|
- Sentence variety: [evaluation]
|
||||||
|
- Paragraph length: [evaluation]
|
||||||
|
|
||||||
|
## Final Polish Suggestions
|
||||||
|
|
||||||
|
1. **Introduction**: [Specific improvements]
|
||||||
|
2. **Body**: [Specific improvements]
|
||||||
|
3. **Conclusion**: [Specific improvements]
|
||||||
|
4. **Title**: [Options if needed]
|
||||||
|
|
||||||
|
## Pre-Publish Checklist
|
||||||
|
- [ ] All claims sourced
|
||||||
|
- [ ] Citations formatted
|
||||||
|
- [ ] Examples clear
|
||||||
|
- [ ] Transitions smooth
|
||||||
|
- [ ] Call to action present
|
||||||
|
- [ ] Proofread for typos
|
||||||
|
|
||||||
|
Ready to publish! 🚀
|
||||||
|
```
|
||||||
|
|
||||||
|
## Examples
|
||||||
|
|
||||||
|
### Example 1: Teresa Torres's Workflow
|
||||||
|
|
||||||
|
**User**: "I'm writing an article about continuous discovery. Help me create an outline."
|
||||||
|
|
||||||
|
**Process**:
|
||||||
|
1. Collaborates on outline structure
|
||||||
|
2. Identifies research needs
|
||||||
|
3. User starts writing introduction
|
||||||
|
4. Reviews and improves the hook
|
||||||
|
5. User writes each section
|
||||||
|
6. Provides feedback after each section
|
||||||
|
7. Conducts research and adds citations
|
||||||
|
8. Final review of complete draft
|
||||||
|
9. Polish and prep for publishing
|
||||||
|
|
||||||
|
**Result**: Well-researched, properly cited article written in Teresa's voice with strong structure and flow.
|
||||||
|
|
||||||
|
### Example 2: Research-Heavy Article
|
||||||
|
|
||||||
|
**User**: "I'm writing about AI's impact on product management. Help me find current data and examples."
|
||||||
|
|
||||||
|
**Output**:
|
||||||
|
```markdown
|
||||||
|
## Research Compiled
|
||||||
|
|
||||||
|
### Recent Data
|
||||||
|
- Gartner: 80% of PMs will use AI tools by 2025 [1]
|
||||||
|
- Survey: 45% report faster feature shipping [2]
|
||||||
|
- Case study: Airbnb's AI-assisted prioritization [3]
|
||||||
|
|
||||||
|
### Expert Quotes
|
||||||
|
- "AI amplifies PM judgment, not replaces it" - Marty Cagan
|
||||||
|
- [Additional quotes with citations]
|
||||||
|
|
||||||
|
### Real Examples
|
||||||
|
1. **Company A**: Used AI for user research synthesis
|
||||||
|
- Result: 60% time savings
|
||||||
|
- Source: [citation]
|
||||||
|
|
||||||
|
2. **Company B**: AI-powered roadmap analysis
|
||||||
|
- Result: Better stakeholder alignment
|
||||||
|
- Source: [citation]
|
||||||
|
|
||||||
|
All added to your outline with proper citations.
|
||||||
|
```
|
||||||
|
|
||||||
|
### Example 3: Hook Improvement
|
||||||
|
|
||||||
|
**User's Original Hook**:
|
||||||
|
> "Product management is changing because of AI. In this article, I'll discuss some ways AI affects product managers."
|
||||||
|
|
||||||
|
**Improved Options**:
|
||||||
|
|
||||||
|
**Option 1 (Data-driven)**:
|
||||||
|
> "Last month, I asked AI to analyze 500 customer interviews. It took 30 minutes instead of 3 weeks. Product management will never be the same."
|
||||||
|
|
||||||
|
**Option 2 (Question)**:
|
||||||
|
> "What if you could talk to every customer, read every review, and analyze every support ticket—all before your morning coffee?"
|
||||||
|
|
||||||
|
**Option 3 (Story)**:
|
||||||
|
> "Sarah spent two weeks building the wrong feature. Not because she didn't understand her users, but because she couldn't process the hundreds of interviews fast enough to spot the pattern."
|
||||||
|
|
||||||
|
### Example 4: Section Feedback
|
||||||
|
|
||||||
|
**User**: "Just finished my 'Common Mistakes' section. Thoughts?"
|
||||||
|
|
||||||
|
**Response**:
|
||||||
|
```markdown
|
||||||
|
# Feedback: Common Mistakes Section
|
||||||
|
|
||||||
|
## What Works Well ✓
|
||||||
|
- Strong examples (the Slack notification story)
|
||||||
|
- Clear structure (3 mistakes, clean layout)
|
||||||
|
- Practical advice for each mistake
|
||||||
|
|
||||||
|
## Suggestions
|
||||||
|
|
||||||
|
### Make It More Specific
|
||||||
|
Your second point says "Bad prioritization" but could be stronger:
|
||||||
|
|
||||||
|
Current:
|
||||||
|
> "Many teams prioritize badly by focusing on features instead of outcomes."
|
||||||
|
|
||||||
|
Suggested:
|
||||||
|
> "I've watched teams ship 14 features in a quarter yet move none of their key metrics. They prioritized activity over progress."
|
||||||
|
|
||||||
|
### Add Data
|
||||||
|
The third mistake would benefit from evidence:
|
||||||
|
> "[Add citation]: Studies show teams without regular user contact are 3x more likely to build unused features [needs source]"
|
||||||
|
|
||||||
|
### Flow Improvement
|
||||||
|
Consider reordering: Mistake 3 → Mistake 2 → Mistake 1
|
||||||
|
This builds from small to big impact.
|
||||||
|
|
||||||
|
Ready for the next section!
|
||||||
|
```
|
||||||
|
|
||||||
|
## Writing Workflows
|
||||||
|
|
||||||
|
### Blog Post Workflow
|
||||||
|
1. Outline together
|
||||||
|
2. Research key points
|
||||||
|
3. Write introduction → get feedback
|
||||||
|
4. Write body sections → feedback each
|
||||||
|
5. Write conclusion → final review
|
||||||
|
6. Polish and edit
|
||||||
|
|
||||||
|
### Newsletter Workflow
|
||||||
|
1. Discuss hook ideas
|
||||||
|
2. Quick outline (shorter format)
|
||||||
|
3. Draft in one session
|
||||||
|
4. Review for clarity and links
|
||||||
|
5. Quick polish
|
||||||
|
|
||||||
|
### Technical Tutorial Workflow
|
||||||
|
1. Outline steps
|
||||||
|
2. Write code examples
|
||||||
|
3. Add explanations
|
||||||
|
4. Test instructions
|
||||||
|
5. Add troubleshooting section
|
||||||
|
6. Final review for accuracy
|
||||||
|
|
||||||
|
### Thought Leadership Workflow
|
||||||
|
1. Brainstorm unique angle
|
||||||
|
2. Research existing perspectives
|
||||||
|
3. Develop your thesis
|
||||||
|
4. Write with strong POV
|
||||||
|
5. Add supporting evidence
|
||||||
|
6. Craft compelling conclusion
|
||||||
|
|
||||||
|
## Pro Tips
|
||||||
|
|
||||||
|
1. **Work in VS Code**: Better than web Claude for long-form writing
|
||||||
|
2. **One section at a time**: Get feedback incrementally
|
||||||
|
3. **Save research separately**: Keep a research.md file
|
||||||
|
4. **Version your drafts**: article-v1.md, article-v2.md, etc.
|
||||||
|
5. **Read aloud**: Use feedback to identify clunky sentences
|
||||||
|
6. **Set deadlines**: "I want to finish the draft today"
|
||||||
|
7. **Take breaks**: Write, get feedback, pause, revise
|
||||||
|
|
||||||
|
## File Organization
|
||||||
|
|
||||||
|
Recommended structure for writing projects:
|
||||||
|
|
||||||
|
```
|
||||||
|
~/writing/article-name/
|
||||||
|
├── outline.md # Your outline
|
||||||
|
├── research.md # All research and citations
|
||||||
|
├── draft-v1.md # First draft
|
||||||
|
├── draft-v2.md # Revised draft
|
||||||
|
├── final.md # Publication-ready
|
||||||
|
├── feedback.md # Collected feedback
|
||||||
|
└── sources/ # Reference materials
|
||||||
|
├── study1.pdf
|
||||||
|
└── article2.md
|
||||||
|
```
|
||||||
|
|
||||||
|
## Best Practices
|
||||||
|
|
||||||
|
### For Research
|
||||||
|
- Verify sources before citing
|
||||||
|
- Use recent data when possible
|
||||||
|
- Balance different perspectives
|
||||||
|
- Link to original sources
|
||||||
|
|
||||||
|
### For Feedback
|
||||||
|
- Be specific about what you want: "Is this too technical?"
|
||||||
|
- Share your concerns: "I'm worried this section drags"
|
||||||
|
- Ask questions: "Does this flow logically?"
|
||||||
|
- Request alternatives: "What's another way to explain this?"
|
||||||
|
|
||||||
|
### For Voice
|
||||||
|
- Share examples of your writing
|
||||||
|
- Specify tone preferences
|
||||||
|
- Point out good matches: "That sounds like me!"
|
||||||
|
- Flag mismatches: "Too formal for my style"
|
||||||
|
|
||||||
|
## Related Use Cases
|
||||||
|
|
||||||
|
- Creating social media posts from articles
|
||||||
|
- Adapting content for different audiences
|
||||||
|
- Writing email newsletters
|
||||||
|
- Drafting technical documentation
|
||||||
|
- Creating presentation content
|
||||||
|
- Writing case studies
|
||||||
|
- Developing course outlines
|
||||||
|
|
||||||
212
domain-name-brainstormer/SKILL.md
Normal file
212
domain-name-brainstormer/SKILL.md
Normal file
@@ -0,0 +1,212 @@
|
|||||||
|
---
|
||||||
|
name: domain-name-brainstormer
|
||||||
|
description: Generates creative domain name ideas for your project and checks availability across multiple TLDs (.com, .io, .dev, .ai, etc.). Saves hours of brainstorming and manual checking.
|
||||||
|
---
|
||||||
|
|
||||||
|
# Domain Name Brainstormer
|
||||||
|
|
||||||
|
This skill helps you find the perfect domain name for your project by generating creative options and checking what's actually available to register.
|
||||||
|
|
||||||
|
## When to Use This Skill
|
||||||
|
|
||||||
|
- Starting a new project or company
|
||||||
|
- Launching a product or service
|
||||||
|
- Creating a personal brand or portfolio site
|
||||||
|
- Rebranding an existing project
|
||||||
|
- Registering a domain for a side project
|
||||||
|
- Finding available alternatives when your first choice is taken
|
||||||
|
|
||||||
|
## What This Skill Does
|
||||||
|
|
||||||
|
1. **Understands Your Project**: Analyzes what you're building and who it's for
|
||||||
|
2. **Generates Creative Names**: Creates relevant, memorable domain options
|
||||||
|
3. **Checks Availability**: Verifies which domains are actually available across multiple TLDs
|
||||||
|
4. **Multiple Extensions**: Suggests .com, .io, .dev, .ai, .app, and more
|
||||||
|
5. **Provides Alternatives**: Offers variations if top choices are taken
|
||||||
|
6. **Branding Insights**: Explains why certain names work well
|
||||||
|
|
||||||
|
## How to Use
|
||||||
|
|
||||||
|
### Basic Brainstorming
|
||||||
|
|
||||||
|
```
|
||||||
|
I'm building a project management tool for remote teams.
|
||||||
|
Suggest domain names.
|
||||||
|
```
|
||||||
|
|
||||||
|
```
|
||||||
|
Help me brainstorm domain names for a personal finance app
|
||||||
|
```
|
||||||
|
|
||||||
|
### Specific Preferences
|
||||||
|
|
||||||
|
```
|
||||||
|
I need a domain name for my AI writing assistant.
|
||||||
|
Prefer short names with .ai or .io extension.
|
||||||
|
```
|
||||||
|
|
||||||
|
### With Keywords
|
||||||
|
|
||||||
|
```
|
||||||
|
Suggest domain names using the words "pixel" or "studio"
|
||||||
|
for my design agency
|
||||||
|
```
|
||||||
|
|
||||||
|
## Example
|
||||||
|
|
||||||
|
**User**: "I'm building a tool for developers to share code snippets. Suggest creative domain names."
|
||||||
|
|
||||||
|
**Output**:
|
||||||
|
```
|
||||||
|
Analyzing your project...
|
||||||
|
Target audience: Developers
|
||||||
|
Key features: Code sharing, snippets, collaboration
|
||||||
|
|
||||||
|
🎯 Domain Name Suggestions
|
||||||
|
|
||||||
|
## Available (.com)
|
||||||
|
1. ✓ snippetbox.com - Clear, memorable, available!
|
||||||
|
Why: Directly describes the product, easy to remember
|
||||||
|
|
||||||
|
2. ✓ codeclip.com - Short and snappy
|
||||||
|
Why: Implies quick code sharing, only 8 characters
|
||||||
|
|
||||||
|
3. ✓ devpaste.com - Developer-focused
|
||||||
|
Why: Familiar to devs (like pastebin), clear purpose
|
||||||
|
|
||||||
|
## Available (Alternative TLDs)
|
||||||
|
4. ✓ snippet.dev - Perfect extension for developers
|
||||||
|
Why: .dev extension signals developer tool
|
||||||
|
|
||||||
|
5. ✓ codebox.io - Tech-forward
|
||||||
|
Why: .io popular with tech startups, clean name
|
||||||
|
|
||||||
|
6. ✓ sharecode.app - Descriptive
|
||||||
|
Why: .app extension, clearly states the action
|
||||||
|
|
||||||
|
## Premium/Taken (.com)
|
||||||
|
- codeshare.com (Taken, est. $2,500)
|
||||||
|
- snippets.com (Taken, premium domain)
|
||||||
|
|
||||||
|
## Recommendations
|
||||||
|
|
||||||
|
🏆 Top Pick: snippet.dev
|
||||||
|
- Perfect for developer audience
|
||||||
|
- Short and memorable
|
||||||
|
- .dev extension adds credibility
|
||||||
|
- Available now!
|
||||||
|
|
||||||
|
🥈 Runner-up: snippetbox.com
|
||||||
|
- .com is universally recognized
|
||||||
|
- Slightly longer but descriptive
|
||||||
|
- Great brandability
|
||||||
|
|
||||||
|
Next steps:
|
||||||
|
1. Register your favorite before someone else does!
|
||||||
|
2. Want me to check more variations?
|
||||||
|
3. Need help with logo ideas for these names?
|
||||||
|
```
|
||||||
|
|
||||||
|
**Inspired by:** Ben Aiad's use case from Lenny's Newsletter
|
||||||
|
|
||||||
|
## Domain Naming Tips
|
||||||
|
|
||||||
|
### What Makes a Good Domain
|
||||||
|
|
||||||
|
✓ **Short**: Under 15 characters ideal
|
||||||
|
✓ **Memorable**: Easy to recall and spell
|
||||||
|
✓ **Pronounceable**: Can be said in conversation
|
||||||
|
✓ **Descriptive**: Hints at what you do
|
||||||
|
✓ **Brandable**: Unique enough to stand out
|
||||||
|
✓ **No hyphens**: Easier to share verbally
|
||||||
|
|
||||||
|
### TLD Guide
|
||||||
|
|
||||||
|
- **.com**: Universal, trusted, great for businesses
|
||||||
|
- **.io**: Tech startups, developer tools
|
||||||
|
- **.dev**: Developer-focused products
|
||||||
|
- **.ai**: AI/ML products
|
||||||
|
- **.app**: Mobile or web applications
|
||||||
|
- **.co**: Alternative to .com
|
||||||
|
- **.xyz**: Modern, creative projects
|
||||||
|
- **.design**: Creative/design agencies
|
||||||
|
- **.tech**: Technology companies
|
||||||
|
|
||||||
|
## Advanced Features
|
||||||
|
|
||||||
|
### Check Similar Variations
|
||||||
|
|
||||||
|
```
|
||||||
|
Check availability for "codebase" and similar variations
|
||||||
|
across .com, .io, .dev
|
||||||
|
```
|
||||||
|
|
||||||
|
### Industry-Specific
|
||||||
|
|
||||||
|
```
|
||||||
|
Suggest domain names for a sustainable fashion brand,
|
||||||
|
checking .eco and .fashion TLDs
|
||||||
|
```
|
||||||
|
|
||||||
|
### Multilingual Options
|
||||||
|
|
||||||
|
```
|
||||||
|
Brainstorm domain names in English and Spanish for
|
||||||
|
a language learning app
|
||||||
|
```
|
||||||
|
|
||||||
|
### Competitor Analysis
|
||||||
|
|
||||||
|
```
|
||||||
|
Show me domain patterns used by successful project
|
||||||
|
management tools, then suggest similar available ones
|
||||||
|
```
|
||||||
|
|
||||||
|
## Example Workflows
|
||||||
|
|
||||||
|
### Startup Launch
|
||||||
|
1. Describe your startup idea
|
||||||
|
2. Get 10-15 domain suggestions across TLDs
|
||||||
|
3. Review availability and pricing
|
||||||
|
4. Pick top 3 favorites
|
||||||
|
5. Register immediately
|
||||||
|
|
||||||
|
### Personal Brand
|
||||||
|
1. Share your name and profession
|
||||||
|
2. Get variations (firstname.com, firstnamelastname.dev, etc.)
|
||||||
|
3. Check social media handle availability too
|
||||||
|
4. Register consistent brand across platforms
|
||||||
|
|
||||||
|
### Product Naming
|
||||||
|
1. Describe product and target market
|
||||||
|
2. Get creative, brandable names
|
||||||
|
3. Check trademark conflicts
|
||||||
|
4. Verify domain and social availability
|
||||||
|
5. Test names with target audience
|
||||||
|
|
||||||
|
## Tips for Success
|
||||||
|
|
||||||
|
1. **Act Fast**: Good domains get taken quickly
|
||||||
|
2. **Register Variations**: Get .com and .io to protect brand
|
||||||
|
3. **Avoid Numbers**: Hard to communicate verbally
|
||||||
|
4. **Check Social Media**: Make sure @username is available too
|
||||||
|
5. **Say It Out Loud**: Test if it's easy to pronounce
|
||||||
|
6. **Check Trademarks**: Ensure no legal conflicts
|
||||||
|
7. **Think Long-term**: Will it still make sense in 5 years?
|
||||||
|
|
||||||
|
## Pricing Context
|
||||||
|
|
||||||
|
When suggesting domains, I'll note:
|
||||||
|
- Standard domains: ~$10-15/year
|
||||||
|
- Premium TLDs (.io, .ai): ~$30-50/year
|
||||||
|
- Taken domains: Market price if listed
|
||||||
|
- Premium domains: $hundreds to $thousands
|
||||||
|
|
||||||
|
## Related Tools
|
||||||
|
|
||||||
|
After picking a domain:
|
||||||
|
- Check logo design options
|
||||||
|
- Verify social media handles
|
||||||
|
- Research trademark availability
|
||||||
|
- Plan brand identity colors/fonts
|
||||||
|
|
||||||
433
file-organizer/SKILL.md
Normal file
433
file-organizer/SKILL.md
Normal file
@@ -0,0 +1,433 @@
|
|||||||
|
---
|
||||||
|
name: file-organizer
|
||||||
|
description: Intelligently organizes your files and folders across your computer by understanding context, finding duplicates, suggesting better structures, and automating cleanup tasks. Reduces cognitive load and keeps your digital workspace tidy without manual effort.
|
||||||
|
---
|
||||||
|
|
||||||
|
# File Organizer
|
||||||
|
|
||||||
|
This skill acts as your personal organization assistant, helping you maintain a clean, logical file structure across your computer without the mental overhead of constant manual organization.
|
||||||
|
|
||||||
|
## When to Use This Skill
|
||||||
|
|
||||||
|
- Your Downloads folder is a chaotic mess
|
||||||
|
- You can't find files because they're scattered everywhere
|
||||||
|
- You have duplicate files taking up space
|
||||||
|
- Your folder structure doesn't make sense anymore
|
||||||
|
- You want to establish better organization habits
|
||||||
|
- You're starting a new project and need a good structure
|
||||||
|
- You're cleaning up before archiving old projects
|
||||||
|
|
||||||
|
## What This Skill Does
|
||||||
|
|
||||||
|
1. **Analyzes Current Structure**: Reviews your folders and files to understand what you have
|
||||||
|
2. **Finds Duplicates**: Identifies duplicate files across your system
|
||||||
|
3. **Suggests Organization**: Proposes logical folder structures based on your content
|
||||||
|
4. **Automates Cleanup**: Moves, renames, and organizes files with your approval
|
||||||
|
5. **Maintains Context**: Makes smart decisions based on file types, dates, and content
|
||||||
|
6. **Reduces Clutter**: Identifies old files you probably don't need anymore
|
||||||
|
|
||||||
|
## How to Use
|
||||||
|
|
||||||
|
### From Your Home Directory
|
||||||
|
|
||||||
|
```
|
||||||
|
cd ~
|
||||||
|
```
|
||||||
|
|
||||||
|
Then run Claude Code and ask for help:
|
||||||
|
|
||||||
|
```
|
||||||
|
Help me organize my Downloads folder
|
||||||
|
```
|
||||||
|
|
||||||
|
```
|
||||||
|
Find duplicate files in my Documents folder
|
||||||
|
```
|
||||||
|
|
||||||
|
```
|
||||||
|
Review my project directories and suggest improvements
|
||||||
|
```
|
||||||
|
|
||||||
|
### Specific Organization Tasks
|
||||||
|
|
||||||
|
```
|
||||||
|
Organize these downloads into proper folders based on what they are
|
||||||
|
```
|
||||||
|
|
||||||
|
```
|
||||||
|
Find duplicate files and help me decide which to keep
|
||||||
|
```
|
||||||
|
|
||||||
|
```
|
||||||
|
Clean up old files I haven't touched in 6+ months
|
||||||
|
```
|
||||||
|
|
||||||
|
```
|
||||||
|
Create a better folder structure for my [work/projects/photos/etc]
|
||||||
|
```
|
||||||
|
|
||||||
|
## Instructions
|
||||||
|
|
||||||
|
When a user requests file organization help:
|
||||||
|
|
||||||
|
1. **Understand the Scope**
|
||||||
|
|
||||||
|
Ask clarifying questions:
|
||||||
|
- Which directory needs organization? (Downloads, Documents, entire home folder?)
|
||||||
|
- What's the main problem? (Can't find things, duplicates, too messy, no structure?)
|
||||||
|
- Any files or folders to avoid? (Current projects, sensitive data?)
|
||||||
|
- How aggressively to organize? (Conservative vs. comprehensive cleanup)
|
||||||
|
|
||||||
|
2. **Analyze Current State**
|
||||||
|
|
||||||
|
Review the target directory:
|
||||||
|
```bash
|
||||||
|
# Get overview of current structure
|
||||||
|
ls -la [target_directory]
|
||||||
|
|
||||||
|
# Check file types and sizes
|
||||||
|
find [target_directory] -type f -exec file {} \; | head -20
|
||||||
|
|
||||||
|
# Identify largest files
|
||||||
|
du -sh [target_directory]/* | sort -rh | head -20
|
||||||
|
|
||||||
|
# Count file types
|
||||||
|
find [target_directory] -type f | sed 's/.*\.//' | sort | uniq -c | sort -rn
|
||||||
|
```
|
||||||
|
|
||||||
|
Summarize findings:
|
||||||
|
- Total files and folders
|
||||||
|
- File type breakdown
|
||||||
|
- Size distribution
|
||||||
|
- Date ranges
|
||||||
|
- Obvious organization issues
|
||||||
|
|
||||||
|
3. **Identify Organization Patterns**
|
||||||
|
|
||||||
|
Based on the files, determine logical groupings:
|
||||||
|
|
||||||
|
**By Type**:
|
||||||
|
- Documents (PDFs, DOCX, TXT)
|
||||||
|
- Images (JPG, PNG, SVG)
|
||||||
|
- Videos (MP4, MOV)
|
||||||
|
- Archives (ZIP, TAR, DMG)
|
||||||
|
- Code/Projects (directories with code)
|
||||||
|
- Spreadsheets (XLSX, CSV)
|
||||||
|
- Presentations (PPTX, KEY)
|
||||||
|
|
||||||
|
**By Purpose**:
|
||||||
|
- Work vs. Personal
|
||||||
|
- Active vs. Archive
|
||||||
|
- Project-specific
|
||||||
|
- Reference materials
|
||||||
|
- Temporary/scratch files
|
||||||
|
|
||||||
|
**By Date**:
|
||||||
|
- Current year/month
|
||||||
|
- Previous years
|
||||||
|
- Very old (archive candidates)
|
||||||
|
|
||||||
|
4. **Find Duplicates**
|
||||||
|
|
||||||
|
When requested, search for duplicates:
|
||||||
|
```bash
|
||||||
|
# Find exact duplicates by hash
|
||||||
|
find [directory] -type f -exec md5 {} \; | sort | uniq -d
|
||||||
|
|
||||||
|
# Find files with same name
|
||||||
|
find [directory] -type f -printf '%f\n' | sort | uniq -d
|
||||||
|
|
||||||
|
# Find similar-sized files
|
||||||
|
find [directory] -type f -printf '%s %p\n' | sort -n
|
||||||
|
```
|
||||||
|
|
||||||
|
For each set of duplicates:
|
||||||
|
- Show all file paths
|
||||||
|
- Display sizes and modification dates
|
||||||
|
- Recommend which to keep (usually newest or best-named)
|
||||||
|
- **Important**: Always ask for confirmation before deleting
|
||||||
|
|
||||||
|
5. **Propose Organization Plan**
|
||||||
|
|
||||||
|
Present a clear plan before making changes:
|
||||||
|
|
||||||
|
```markdown
|
||||||
|
# Organization Plan for [Directory]
|
||||||
|
|
||||||
|
## Current State
|
||||||
|
- X files across Y folders
|
||||||
|
- [Size] total
|
||||||
|
- File types: [breakdown]
|
||||||
|
- Issues: [list problems]
|
||||||
|
|
||||||
|
## Proposed Structure
|
||||||
|
|
||||||
|
```
|
||||||
|
[Directory]/
|
||||||
|
├── Work/
|
||||||
|
│ ├── Projects/
|
||||||
|
│ ├── Documents/
|
||||||
|
│ └── Archive/
|
||||||
|
├── Personal/
|
||||||
|
│ ├── Photos/
|
||||||
|
│ ├── Documents/
|
||||||
|
│ └── Media/
|
||||||
|
└── Downloads/
|
||||||
|
├── To-Sort/
|
||||||
|
└── Archive/
|
||||||
|
```
|
||||||
|
|
||||||
|
## Changes I'll Make
|
||||||
|
|
||||||
|
1. **Create new folders**: [list]
|
||||||
|
2. **Move files**:
|
||||||
|
- X PDFs → Work/Documents/
|
||||||
|
- Y images → Personal/Photos/
|
||||||
|
- Z old files → Archive/
|
||||||
|
3. **Rename files**: [any renaming patterns]
|
||||||
|
4. **Delete**: [duplicates or trash files]
|
||||||
|
|
||||||
|
## Files Needing Your Decision
|
||||||
|
|
||||||
|
- [List any files you're unsure about]
|
||||||
|
|
||||||
|
Ready to proceed? (yes/no/modify)
|
||||||
|
```
|
||||||
|
|
||||||
|
6. **Execute Organization**
|
||||||
|
|
||||||
|
After approval, organize systematically:
|
||||||
|
|
||||||
|
```bash
|
||||||
|
# Create folder structure
|
||||||
|
mkdir -p "path/to/new/folders"
|
||||||
|
|
||||||
|
# Move files with clear logging
|
||||||
|
mv "old/path/file.pdf" "new/path/file.pdf"
|
||||||
|
|
||||||
|
# Rename files with consistent patterns
|
||||||
|
# Example: "YYYY-MM-DD - Description.ext"
|
||||||
|
```
|
||||||
|
|
||||||
|
**Important Rules**:
|
||||||
|
- Always confirm before deleting anything
|
||||||
|
- Log all moves for potential undo
|
||||||
|
- Preserve original modification dates
|
||||||
|
- Handle filename conflicts gracefully
|
||||||
|
- Stop and ask if you encounter unexpected situations
|
||||||
|
|
||||||
|
7. **Provide Summary and Maintenance Tips**
|
||||||
|
|
||||||
|
After organizing:
|
||||||
|
|
||||||
|
```markdown
|
||||||
|
# Organization Complete! ✨
|
||||||
|
|
||||||
|
## What Changed
|
||||||
|
|
||||||
|
- Created [X] new folders
|
||||||
|
- Organized [Y] files
|
||||||
|
- Freed [Z] GB by removing duplicates
|
||||||
|
- Archived [W] old files
|
||||||
|
|
||||||
|
## New Structure
|
||||||
|
|
||||||
|
[Show the new folder tree]
|
||||||
|
|
||||||
|
## Maintenance Tips
|
||||||
|
|
||||||
|
To keep this organized:
|
||||||
|
|
||||||
|
1. **Weekly**: Sort new downloads
|
||||||
|
2. **Monthly**: Review and archive completed projects
|
||||||
|
3. **Quarterly**: Check for new duplicates
|
||||||
|
4. **Yearly**: Archive old files
|
||||||
|
|
||||||
|
## Quick Commands for You
|
||||||
|
|
||||||
|
```bash
|
||||||
|
# Find files modified this week
|
||||||
|
find . -type f -mtime -7
|
||||||
|
|
||||||
|
# Sort downloads by type
|
||||||
|
[custom command for their setup]
|
||||||
|
|
||||||
|
# Find duplicates
|
||||||
|
[custom command]
|
||||||
|
```
|
||||||
|
|
||||||
|
Want to organize another folder?
|
||||||
|
```
|
||||||
|
|
||||||
|
## Examples
|
||||||
|
|
||||||
|
### Example 1: Organizing Downloads (From Justin Dielmann)
|
||||||
|
|
||||||
|
**User**: "My Downloads folder is a mess with 500+ files. Help me organize it."
|
||||||
|
|
||||||
|
**Process**:
|
||||||
|
1. Analyzes Downloads folder
|
||||||
|
2. Finds patterns: work docs, personal photos, installers, random PDFs
|
||||||
|
3. Proposes structure:
|
||||||
|
- Downloads/
|
||||||
|
- Work/
|
||||||
|
- Personal/
|
||||||
|
- Installers/ (DMG, PKG files)
|
||||||
|
- Archive/
|
||||||
|
- ToSort/ (things needing decisions)
|
||||||
|
4. Asks for confirmation
|
||||||
|
5. Moves files intelligently based on content and names
|
||||||
|
6. Results: 500 files → 5 organized folders
|
||||||
|
|
||||||
|
### Example 2: Finding and Removing Duplicates
|
||||||
|
|
||||||
|
**User**: "Find duplicate files in my Documents and help me decide which to keep."
|
||||||
|
|
||||||
|
**Output**:
|
||||||
|
```markdown
|
||||||
|
# Found 23 Sets of Duplicates (156 MB total)
|
||||||
|
|
||||||
|
## Duplicate Set 1: "proposal.pdf"
|
||||||
|
- `/Documents/proposal.pdf` (2.3 MB, modified: 2024-03-15)
|
||||||
|
- `/Documents/old/proposal.pdf` (2.3 MB, modified: 2024-03-15)
|
||||||
|
- `/Desktop/proposal.pdf` (2.3 MB, modified: 2024-03-10)
|
||||||
|
|
||||||
|
**Recommendation**: Keep `/Documents/proposal.pdf` (most recent in correct location)
|
||||||
|
Delete the other 2 copies?
|
||||||
|
|
||||||
|
[Continue for all duplicates...]
|
||||||
|
```
|
||||||
|
|
||||||
|
### Example 3: Restructuring Projects Folder
|
||||||
|
|
||||||
|
**User**: "Review my ~/Projects directory and suggest improvements."
|
||||||
|
|
||||||
|
**Output**:
|
||||||
|
```markdown
|
||||||
|
# Analysis of ~/Projects
|
||||||
|
|
||||||
|
## Current Structure Issues
|
||||||
|
- Mix of active and archived projects (3+ years old)
|
||||||
|
- No consistent naming convention
|
||||||
|
- Some projects at root, others in random subfolders
|
||||||
|
- Duplicate folders (project-name, project-name-old, project-name-v2)
|
||||||
|
|
||||||
|
## Proposed Structure
|
||||||
|
|
||||||
|
```
|
||||||
|
Projects/
|
||||||
|
├── Active/
|
||||||
|
│ ├── client-work/
|
||||||
|
│ ├── side-projects/
|
||||||
|
│ └── learning/
|
||||||
|
├── Archive/
|
||||||
|
│ ├── 2022/
|
||||||
|
│ ├── 2023/
|
||||||
|
│ └── 2024/
|
||||||
|
└── Templates/
|
||||||
|
```
|
||||||
|
|
||||||
|
## Specific Changes
|
||||||
|
1. Move 12 projects not touched since 2022 → Archive/
|
||||||
|
2. Consolidate 4 duplicate project folders
|
||||||
|
3. Rename projects to consistent format: "client-name-project-name"
|
||||||
|
4. Create Archive for old work
|
||||||
|
|
||||||
|
Want me to implement this?
|
||||||
|
```
|
||||||
|
|
||||||
|
### Example 4: Organizing Photos by Date
|
||||||
|
|
||||||
|
**User**: "Organize my photo folders by year and month."
|
||||||
|
|
||||||
|
**Output**: Creates structure like:
|
||||||
|
```
|
||||||
|
Photos/
|
||||||
|
├── 2023/
|
||||||
|
│ ├── 01-January/
|
||||||
|
│ ├── 02-February/
|
||||||
|
│ └── ...
|
||||||
|
├── 2024/
|
||||||
|
│ ├── 01-January/
|
||||||
|
│ └── ...
|
||||||
|
└── Unsorted/
|
||||||
|
```
|
||||||
|
|
||||||
|
Then moves photos based on EXIF data or file modification dates.
|
||||||
|
|
||||||
|
## Common Organization Tasks
|
||||||
|
|
||||||
|
### Downloads Cleanup
|
||||||
|
```
|
||||||
|
Organize my Downloads folder - move documents to Documents,
|
||||||
|
images to Pictures, keep installers separate, and archive files
|
||||||
|
older than 3 months.
|
||||||
|
```
|
||||||
|
|
||||||
|
### Project Organization
|
||||||
|
```
|
||||||
|
Review my Projects folder structure and help me separate active
|
||||||
|
projects from old ones I should archive.
|
||||||
|
```
|
||||||
|
|
||||||
|
### Duplicate Removal
|
||||||
|
```
|
||||||
|
Find all duplicate files in my Documents folder and help me
|
||||||
|
decide which ones to keep.
|
||||||
|
```
|
||||||
|
|
||||||
|
### Desktop Cleanup
|
||||||
|
```
|
||||||
|
My Desktop is covered in files. Help me organize everything into
|
||||||
|
my Documents folder properly.
|
||||||
|
```
|
||||||
|
|
||||||
|
### Photo Organization
|
||||||
|
```
|
||||||
|
Organize all photos in this folder by date (year/month) based
|
||||||
|
on when they were taken.
|
||||||
|
```
|
||||||
|
|
||||||
|
### Work/Personal Separation
|
||||||
|
```
|
||||||
|
Help me separate my work files from personal files across my
|
||||||
|
Documents folder.
|
||||||
|
```
|
||||||
|
|
||||||
|
## Pro Tips
|
||||||
|
|
||||||
|
1. **Start Small**: Begin with one messy folder (like Downloads) to build trust
|
||||||
|
2. **Regular Maintenance**: Run weekly cleanup on Downloads
|
||||||
|
3. **Consistent Naming**: Use "YYYY-MM-DD - Description" format for important files
|
||||||
|
4. **Archive Aggressively**: Move old projects to Archive instead of deleting
|
||||||
|
5. **Keep Active Separate**: Maintain clear boundaries between active and archived work
|
||||||
|
6. **Trust the Process**: Let Claude handle the cognitive load of where things go
|
||||||
|
|
||||||
|
## Best Practices
|
||||||
|
|
||||||
|
### Folder Naming
|
||||||
|
- Use clear, descriptive names
|
||||||
|
- Avoid spaces (use hyphens or underscores)
|
||||||
|
- Be specific: "client-proposals" not "docs"
|
||||||
|
- Use prefixes for ordering: "01-current", "02-archive"
|
||||||
|
|
||||||
|
### File Naming
|
||||||
|
- Include dates: "2024-10-17-meeting-notes.md"
|
||||||
|
- Be descriptive: "q3-financial-report.xlsx"
|
||||||
|
- Avoid version numbers in names (use version control instead)
|
||||||
|
- Remove download artifacts: "document-final-v2 (1).pdf" → "document.pdf"
|
||||||
|
|
||||||
|
### When to Archive
|
||||||
|
- Projects not touched in 6+ months
|
||||||
|
- Completed work that might be referenced later
|
||||||
|
- Old versions after migration to new systems
|
||||||
|
- Files you're hesitant to delete (archive first)
|
||||||
|
|
||||||
|
## Related Use Cases
|
||||||
|
|
||||||
|
- Setting up organization for a new computer
|
||||||
|
- Preparing files for backup/archiving
|
||||||
|
- Cleaning up before storage cleanup
|
||||||
|
- Organizing shared team folders
|
||||||
|
- Structuring new project directories
|
||||||
|
|
||||||
99
image-enhancer/SKILL.md
Normal file
99
image-enhancer/SKILL.md
Normal file
@@ -0,0 +1,99 @@
|
|||||||
|
---
|
||||||
|
name: image-enhancer
|
||||||
|
description: Improves the quality of images, especially screenshots, by enhancing resolution, sharpness, and clarity. Perfect for preparing images for presentations, documentation, or social media posts.
|
||||||
|
---
|
||||||
|
|
||||||
|
# Image Enhancer
|
||||||
|
|
||||||
|
This skill takes your images and screenshots and makes them look better—sharper, clearer, and more professional.
|
||||||
|
|
||||||
|
## When to Use This Skill
|
||||||
|
|
||||||
|
- Improving screenshot quality for blog posts or documentation
|
||||||
|
- Enhancing images before sharing on social media
|
||||||
|
- Preparing images for presentations or reports
|
||||||
|
- Upscaling low-resolution images
|
||||||
|
- Sharpening blurry photos
|
||||||
|
- Cleaning up compressed images
|
||||||
|
|
||||||
|
## What This Skill Does
|
||||||
|
|
||||||
|
1. **Analyzes Image Quality**: Checks resolution, sharpness, and compression artifacts
|
||||||
|
2. **Enhances Resolution**: Upscales images intelligently
|
||||||
|
3. **Improves Sharpness**: Enhances edges and details
|
||||||
|
4. **Reduces Artifacts**: Cleans up compression artifacts and noise
|
||||||
|
5. **Optimizes for Use Case**: Adjusts based on intended use (web, print, social media)
|
||||||
|
|
||||||
|
## How to Use
|
||||||
|
|
||||||
|
### Basic Enhancement
|
||||||
|
|
||||||
|
```
|
||||||
|
Improve the image quality of screenshot.png
|
||||||
|
```
|
||||||
|
|
||||||
|
```
|
||||||
|
Enhance all images in this folder
|
||||||
|
```
|
||||||
|
|
||||||
|
### Specific Improvements
|
||||||
|
|
||||||
|
```
|
||||||
|
Upscale this image to 4K resolution
|
||||||
|
```
|
||||||
|
|
||||||
|
```
|
||||||
|
Sharpen this blurry screenshot
|
||||||
|
```
|
||||||
|
|
||||||
|
```
|
||||||
|
Reduce compression artifacts in this image
|
||||||
|
```
|
||||||
|
|
||||||
|
### Batch Processing
|
||||||
|
|
||||||
|
```
|
||||||
|
Improve the quality of all PNG files in this directory
|
||||||
|
```
|
||||||
|
|
||||||
|
## Example
|
||||||
|
|
||||||
|
**User**: "Improve the image quality of screenshot-2024.png"
|
||||||
|
|
||||||
|
**Output**:
|
||||||
|
```
|
||||||
|
Analyzing screenshot-2024.png...
|
||||||
|
|
||||||
|
Current specs:
|
||||||
|
- Resolution: 1920x1080
|
||||||
|
- Format: PNG
|
||||||
|
- Quality: Good, but slight blur
|
||||||
|
|
||||||
|
Enhancements applied:
|
||||||
|
✓ Upscaled to 2560x1440 (retina)
|
||||||
|
✓ Sharpened edges
|
||||||
|
✓ Enhanced text clarity
|
||||||
|
✓ Optimized file size
|
||||||
|
|
||||||
|
Saved as: screenshot-2024-enhanced.png
|
||||||
|
Original preserved as: screenshot-2024-original.png
|
||||||
|
```
|
||||||
|
|
||||||
|
**Inspired by:** Lenny Rachitsky's workflow from his newsletter - used for screenshots in his articles
|
||||||
|
|
||||||
|
## Tips
|
||||||
|
|
||||||
|
- Always keeps original files as backup
|
||||||
|
- Works best with screenshots and digital images
|
||||||
|
- Can batch process entire folders
|
||||||
|
- Specify output format if needed (PNG for quality, JPG for smaller size)
|
||||||
|
- For social media, mention the platform for optimal sizing
|
||||||
|
|
||||||
|
## Common Use Cases
|
||||||
|
|
||||||
|
- **Blog Posts**: Enhance screenshots before publishing
|
||||||
|
- **Documentation**: Make UI screenshots crystal clear
|
||||||
|
- **Social Media**: Optimize images for Twitter, LinkedIn, Instagram
|
||||||
|
- **Presentations**: Upscale images for large screens
|
||||||
|
- **Print Materials**: Increase resolution for physical media
|
||||||
|
|
||||||
446
invoice-organizer/SKILL.md
Normal file
446
invoice-organizer/SKILL.md
Normal file
@@ -0,0 +1,446 @@
|
|||||||
|
---
|
||||||
|
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.
|
||||||
|
|
||||||
|
## 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 Claude Code:
|
||||||
|
```
|
||||||
|
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
|
||||||
|
|
||||||
199
lead-research-assistant/SKILL.md
Normal file
199
lead-research-assistant/SKILL.md
Normal file
@@ -0,0 +1,199 @@
|
|||||||
|
---
|
||||||
|
name: lead-research-assistant
|
||||||
|
description: Identifies high-quality leads for your product or service by analyzing your business, searching for target companies, and providing actionable contact strategies. Perfect for sales, business development, and marketing professionals.
|
||||||
|
---
|
||||||
|
|
||||||
|
# Lead Research Assistant
|
||||||
|
|
||||||
|
This skill helps you identify and qualify potential leads for your business by analyzing your product/service, understanding your ideal customer profile, and providing actionable outreach strategies.
|
||||||
|
|
||||||
|
## When to Use This Skill
|
||||||
|
|
||||||
|
- Finding potential customers or clients for your product/service
|
||||||
|
- Building a list of companies to reach out to for partnerships
|
||||||
|
- Identifying target accounts for sales outreach
|
||||||
|
- Researching companies that match your ideal customer profile
|
||||||
|
- Preparing for business development activities
|
||||||
|
|
||||||
|
## What This Skill Does
|
||||||
|
|
||||||
|
1. **Understands Your Business**: Analyzes your product/service, value proposition, and target market
|
||||||
|
2. **Identifies Target Companies**: Finds companies that match your ideal customer profile based on:
|
||||||
|
- Industry and sector
|
||||||
|
- Company size and location
|
||||||
|
- Technology stack and tools they use
|
||||||
|
- Growth stage and funding
|
||||||
|
- Pain points your product solves
|
||||||
|
3. **Prioritizes Leads**: Ranks companies based on fit score and relevance
|
||||||
|
4. **Provides Contact Strategies**: Suggests how to approach each lead with personalized messaging
|
||||||
|
5. **Enriches Data**: Gathers relevant information about decision-makers and company context
|
||||||
|
|
||||||
|
## How to Use
|
||||||
|
|
||||||
|
### Basic Usage
|
||||||
|
|
||||||
|
Simply describe your product/service and what you're looking for:
|
||||||
|
|
||||||
|
```
|
||||||
|
I'm building [product description]. Find me 10 companies in [location/industry]
|
||||||
|
that would be good leads for this.
|
||||||
|
```
|
||||||
|
|
||||||
|
### With Your Codebase
|
||||||
|
|
||||||
|
For even better results, run this from your product's source code directory:
|
||||||
|
|
||||||
|
```
|
||||||
|
Look at what I'm building in this repository and identify the top 10 companies
|
||||||
|
in [location/industry] that would benefit from this product.
|
||||||
|
```
|
||||||
|
|
||||||
|
### Advanced Usage
|
||||||
|
|
||||||
|
For more targeted research:
|
||||||
|
|
||||||
|
```
|
||||||
|
My product: [description]
|
||||||
|
Ideal customer profile:
|
||||||
|
- Industry: [industry]
|
||||||
|
- Company size: [size range]
|
||||||
|
- Location: [location]
|
||||||
|
- Current pain points: [pain points]
|
||||||
|
- Technologies they use: [tech stack]
|
||||||
|
|
||||||
|
Find me 20 qualified leads with contact strategies for each.
|
||||||
|
```
|
||||||
|
|
||||||
|
## Instructions
|
||||||
|
|
||||||
|
When a user requests lead research:
|
||||||
|
|
||||||
|
1. **Understand the Product/Service**
|
||||||
|
- If in a code directory, analyze the codebase to understand the product
|
||||||
|
- Ask clarifying questions about the value proposition
|
||||||
|
- Identify key features and benefits
|
||||||
|
- Understand what problems it solves
|
||||||
|
|
||||||
|
2. **Define Ideal Customer Profile**
|
||||||
|
- Determine target industries and sectors
|
||||||
|
- Identify company size ranges
|
||||||
|
- Consider geographic preferences
|
||||||
|
- Understand relevant pain points
|
||||||
|
- Note any technology requirements
|
||||||
|
|
||||||
|
3. **Research and Identify Leads**
|
||||||
|
- Search for companies matching the criteria
|
||||||
|
- Look for signals of need (job postings, tech stack, recent news)
|
||||||
|
- Consider growth indicators (funding, expansion, hiring)
|
||||||
|
- Identify companies with complementary products/services
|
||||||
|
- Check for budget indicators
|
||||||
|
|
||||||
|
4. **Prioritize and Score**
|
||||||
|
- Create a fit score (1-10) for each lead
|
||||||
|
- Consider factors like:
|
||||||
|
- Alignment with ICP
|
||||||
|
- Signals of immediate need
|
||||||
|
- Budget availability
|
||||||
|
- Competitive landscape
|
||||||
|
- Timing indicators
|
||||||
|
|
||||||
|
5. **Provide Actionable Output**
|
||||||
|
|
||||||
|
For each lead, provide:
|
||||||
|
- **Company Name** and website
|
||||||
|
- **Why They're a Good Fit**: Specific reasons based on their business
|
||||||
|
- **Priority Score**: 1-10 with explanation
|
||||||
|
- **Decision Maker**: Role/title to target (e.g., "VP of Engineering")
|
||||||
|
- **Contact Strategy**: Personalized approach suggestions
|
||||||
|
- **Value Proposition**: How your product solves their specific problem
|
||||||
|
- **Conversation Starters**: Specific points to mention in outreach
|
||||||
|
- **LinkedIn URL**: If available, for easy connection
|
||||||
|
|
||||||
|
6. **Format the Output**
|
||||||
|
|
||||||
|
Present results in a clear, scannable format:
|
||||||
|
|
||||||
|
```markdown
|
||||||
|
# Lead Research Results
|
||||||
|
|
||||||
|
## Summary
|
||||||
|
- Total leads found: [X]
|
||||||
|
- High priority (8-10): [X]
|
||||||
|
- Medium priority (5-7): [X]
|
||||||
|
- Average fit score: [X]
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Lead 1: [Company Name]
|
||||||
|
|
||||||
|
**Website**: [URL]
|
||||||
|
**Priority Score**: [X/10]
|
||||||
|
**Industry**: [Industry]
|
||||||
|
**Size**: [Employee count/revenue range]
|
||||||
|
|
||||||
|
**Why They're a Good Fit**:
|
||||||
|
[2-3 specific reasons based on their business]
|
||||||
|
|
||||||
|
**Target Decision Maker**: [Role/Title]
|
||||||
|
**LinkedIn**: [URL if available]
|
||||||
|
|
||||||
|
**Value Proposition for Them**:
|
||||||
|
[Specific benefit for this company]
|
||||||
|
|
||||||
|
**Outreach Strategy**:
|
||||||
|
[Personalized approach - mention specific pain points, recent company news, or relevant context]
|
||||||
|
|
||||||
|
**Conversation Starters**:
|
||||||
|
- [Specific point 1]
|
||||||
|
- [Specific point 2]
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
[Repeat for each lead]
|
||||||
|
```
|
||||||
|
|
||||||
|
7. **Offer Next Steps**
|
||||||
|
- Suggest saving results to a CSV for CRM import
|
||||||
|
- Offer to draft personalized outreach messages
|
||||||
|
- Recommend prioritization based on timing
|
||||||
|
- Suggest follow-up research for top leads
|
||||||
|
|
||||||
|
## Examples
|
||||||
|
|
||||||
|
### Example 1: From Lenny's Newsletter
|
||||||
|
|
||||||
|
**User**: "I'm building a tool that masks sensitive data in AI coding assistant queries. Find potential leads."
|
||||||
|
|
||||||
|
**Output**: Creates a prioritized list of companies that:
|
||||||
|
- Use AI coding assistants (Copilot, Cursor, etc.)
|
||||||
|
- Handle sensitive data (fintech, healthcare, legal)
|
||||||
|
- Have evidence in their GitHub repos of using coding agents
|
||||||
|
- May have accidentally exposed sensitive data in code
|
||||||
|
- Includes LinkedIn URLs of relevant decision-makers
|
||||||
|
|
||||||
|
### Example 2: Local Business
|
||||||
|
|
||||||
|
**User**: "I run a consulting practice for remote team productivity. Find me 10 companies in the Bay Area that recently went remote."
|
||||||
|
|
||||||
|
**Output**: Identifies companies that:
|
||||||
|
- Recently posted remote job listings
|
||||||
|
- Announced remote-first policies
|
||||||
|
- Are hiring distributed teams
|
||||||
|
- Show signs of remote work challenges
|
||||||
|
- Provides personalized outreach strategies for each
|
||||||
|
|
||||||
|
## Tips for Best Results
|
||||||
|
|
||||||
|
- **Be specific** about your product and its unique value
|
||||||
|
- **Run from your codebase** if applicable for automatic context
|
||||||
|
- **Provide context** about your ideal customer profile
|
||||||
|
- **Specify constraints** like industry, location, or company size
|
||||||
|
- **Request follow-up** research on promising leads for deeper insights
|
||||||
|
|
||||||
|
## Related Use Cases
|
||||||
|
|
||||||
|
- Drafting personalized outreach emails after identifying leads
|
||||||
|
- Building a CRM-ready CSV of qualified prospects
|
||||||
|
- Researching specific companies in detail
|
||||||
|
- Analyzing competitor customer bases
|
||||||
|
- Identifying partnership opportunities
|
||||||
327
meeting-insights-analyzer/SKILL.md
Normal file
327
meeting-insights-analyzer/SKILL.md
Normal file
@@ -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
|
||||||
|
|
||||||
159
raffle-winner-picker/SKILL.md
Normal file
159
raffle-winner-picker/SKILL.md
Normal file
@@ -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
|
||||||
|
|
||||||
106
video-downloader/SKILL.md
Normal file
106
video-downloader/SKILL.md
Normal file
@@ -0,0 +1,106 @@
|
|||||||
|
---
|
||||||
|
name: video-downloader
|
||||||
|
description: Downloads videos from YouTube and other platforms for offline viewing, editing, or archival. Handles various formats and quality options.
|
||||||
|
---
|
||||||
|
|
||||||
|
# Video Downloader
|
||||||
|
|
||||||
|
This skill downloads videos from YouTube and other platforms directly to your computer.
|
||||||
|
|
||||||
|
## When to Use This Skill
|
||||||
|
|
||||||
|
- Downloading YouTube videos for offline viewing
|
||||||
|
- Saving educational content for reference
|
||||||
|
- Archiving important videos
|
||||||
|
- Getting video files for editing or repurposing
|
||||||
|
- Downloading your own content from platforms
|
||||||
|
- Saving conference talks or webinars
|
||||||
|
|
||||||
|
## What This Skill Does
|
||||||
|
|
||||||
|
1. **Downloads Videos**: Fetches videos from YouTube and other platforms
|
||||||
|
2. **Quality Selection**: Lets you choose resolution (480p, 720p, 1080p, 4K)
|
||||||
|
3. **Format Options**: Downloads in various formats (MP4, WebM, audio-only)
|
||||||
|
4. **Batch Downloads**: Can download multiple videos or playlists
|
||||||
|
5. **Metadata Preservation**: Saves title, description, and thumbnail
|
||||||
|
|
||||||
|
## How to Use
|
||||||
|
|
||||||
|
### Basic Download
|
||||||
|
|
||||||
|
```
|
||||||
|
Download this YouTube video: https://youtube.com/watch?v=...
|
||||||
|
```
|
||||||
|
|
||||||
|
```
|
||||||
|
Download this video in 1080p quality
|
||||||
|
```
|
||||||
|
|
||||||
|
### Audio Only
|
||||||
|
|
||||||
|
```
|
||||||
|
Download the audio from this YouTube video as MP3
|
||||||
|
```
|
||||||
|
|
||||||
|
### Playlist Download
|
||||||
|
|
||||||
|
```
|
||||||
|
Download all videos from this YouTube playlist: [URL]
|
||||||
|
```
|
||||||
|
|
||||||
|
### Batch Download
|
||||||
|
|
||||||
|
```
|
||||||
|
Download these 5 YouTube videos:
|
||||||
|
1. [URL]
|
||||||
|
2. [URL]
|
||||||
|
...
|
||||||
|
```
|
||||||
|
|
||||||
|
## Example
|
||||||
|
|
||||||
|
**User**: "Download this YouTube video: https://youtube.com/watch?v=abc123"
|
||||||
|
|
||||||
|
**Output**:
|
||||||
|
```
|
||||||
|
Downloading from YouTube...
|
||||||
|
|
||||||
|
Video: "How to Build Products Users Love"
|
||||||
|
Channel: Lenny's Podcast
|
||||||
|
Duration: 45:32
|
||||||
|
Quality: 1080p
|
||||||
|
|
||||||
|
Progress: ████████████████████ 100%
|
||||||
|
|
||||||
|
✓ Downloaded: how-to-build-products-users-love.mp4
|
||||||
|
✓ Saved thumbnail: how-to-build-products-users-love.jpg
|
||||||
|
✓ Size: 342 MB
|
||||||
|
|
||||||
|
Saved to: ~/Downloads/
|
||||||
|
```
|
||||||
|
|
||||||
|
**Inspired by:** Lenny's workflow from his newsletter
|
||||||
|
|
||||||
|
## Important Notes
|
||||||
|
|
||||||
|
⚠️ **Copyright & Fair Use**
|
||||||
|
- Only download videos you have permission to download
|
||||||
|
- Respect copyright laws and platform terms of service
|
||||||
|
- Use for personal, educational, or fair use purposes
|
||||||
|
- Don't redistribute copyrighted content
|
||||||
|
|
||||||
|
## Tips
|
||||||
|
|
||||||
|
- Specify quality if you need lower file size (720p vs 1080p)
|
||||||
|
- Use audio-only for podcasts or music to save space
|
||||||
|
- Download to a dedicated folder to stay organized
|
||||||
|
- Check file size before downloading on slow connections
|
||||||
|
|
||||||
|
## Common Use Cases
|
||||||
|
|
||||||
|
- **Education**: Save tutorials and courses for offline learning
|
||||||
|
- **Research**: Archive videos for reference
|
||||||
|
- **Content Creation**: Download your own content from platforms
|
||||||
|
- **Backup**: Save important videos before they're removed
|
||||||
|
- **Offline Viewing**: Watch videos without internet access
|
||||||
|
|
||||||
Reference in New Issue
Block a user