{"items":[{"id":"cmugucv6d00mwqu06fw9jpelb","slug":"travisvn-awesome-claude-skills-awesome-claude-skills","name":"Awesome Claude Skills","description":"A curated list of awesome Claude Skills, resources, and tools for customizing Claude AI workflows โ€” particularly Claude Code","authorId":"gh:travisvn","authorName":"travisvn","version":"0.1.0","category":"MCP","securityLevel":"Community","downloadsCount":0,"githubStars":15170,"pricePerCall":0,"manifest":{"name":"Awesome Claude Skills","tools":[],"category":"MCP","entrypoint":{"args":["-y","github:travisvn/awesome-claude-skills"],"type":"mcp-stdio","command":"npx"},"description":"A curated list of awesome Claude Skills, resources, and tools for customizing Claude AI workflows โ€” particularly Claude Code","permissions":["shell","network"],"schemaVersion":1},"repoUrl":"https://github.com/travisvn/awesome-claude-skills","tags":["agentic-coding","anthropic","awesome","awesome-list","awesome-lists","claude","claude-ai","claude-code","claude-desktop","claude-skills","claudeskills","mcp"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"awesome-claude-skills","audit":{"files":[],"binaries":[],"findings":[],"packages":0,"auditedAt":"2026-09-25T10:52:07.717Z","lockfiles":[]},"forks":1990,"owner":"travisvn","stars":15170,"topics":["agentic-coding","anthropic","awesome","awesome-list","awesome-lists","claude","claude-ai","claude-code","claude-desktop","claude-skills","claudeskills"],"license":null,"fullName":"travisvn/awesome-claude-skills","homepage":null,"language":null,"pushedAt":"2026-04-28T19:30:24Z","avatarUrl":"https://avatars.githubusercontent.com/u/2686415?v=4","crawledAt":"2026-09-25T10:52:07.481Z","openIssues":839,"manifestFile":"README.md","manifestPath":"README.md","defaultBranch":"main"},"readme":"

\n \n \"Awesome\n \n

\n\n# Awesome Claude Skills\n\n[![Awesome](https://awesome.re/badge.svg)](https://awesome.re)\n[![Last Updated](https://img.shields.io/badge/updated-Feb%202026-green.svg)]()\n[![PRs Welcome](https://img.shields.io/badge/PRs-welcome-brightgreen.svg)](CONTRIBUTING.md)\n\n> A curated list of awesome Claude Skills, resources, and tools for customizing Claude AI workflows\n\n**Claude Skills** teach Claude how to **perform tasks in a repeatable way**\n\nThey are specialized folders containing instructions, scripts, and resources that Claude dynamically discovers and loads when relevant to tasks.\n\n### How Skills Work\n\nSkills employ a **progressive disclosure architecture** for efficiency:\n\n1. **Metadata loading** (~100 tokens): Claude scans available Skills to identify relevant matches\n2. **Full instructions** (<5k tokens): Load when Claude determines the Skill applies\n3. **Bundled resources**: Files and executable code load only as needed\n\nThis design allows multiple Skills to remain available without overwhelming Claude's context window.\n\n## ๐Ÿš€ Getting Started\n\n### Claude.ai Web Interface\n\n1. Go to [Settings > Capabilities](https://claude.ai/settings/capabilities)\n2. Enable Skills toggle\n3. Browse available skills or upload custom skills\n4. **For Team/Enterprise**: Admin must enable Skills organization-wide first\n\n### Claude Code CLI\n\n```bash\n# Install skills from marketplace\n/plugin marketplace add anthropics/skills\n\n# Or install from local directory\n/plugin add /path/to/skill-directory\n```\n\n### Claude API\n\nSkills are accessible via the `/v1/skills` API endpoint. See the [Skills API documentation](https://platform.claude.com/docs/en/api/beta/skills) for detailed integration examples.\n\n```python\nimport anthropic\n\nclient = anthropic.Client(api_key=\"your-api-key\")\n# See API docs for full implementation details\n```\n\n## ๐ŸŽฏ Official Skills\n\n### Document Skills\n\nSkills for working with complex file formats:\n\n- **[docx](https://github.com/anthropics/skills/tree/main/skills/docx)** - Create, edit, and analyze Word documents with support for tracked changes, comments, formatting preservation, and text extraction\n- **[pdf](https://github.com/anthropics/skills/tree/main/skills/pdf)** - Comprehensive PDF manipulation toolkit for extracting text and tables, creating new PDFs, merging/splitting documents, and handling forms\n- **[pptx](https://github.com/anthropics/skills/tree/main/skills/pptx)** - Create, edit, and analyze PowerPoint presentations with support for layouts, templates, charts, and automated slide generation\n- **[xlsx](https://github.com/anthropics/skills/tree/main/skills/xlsx)** - Create, edit, and analyze Excel spreadsheets with support for formulas, formatting, data analysis, and visualization\n\n### Design & Creative\n\n- **[algorithmic-art](https://github.com/anthropics/skills/tree/main/skills/algorithmic-art)** - Create generative art using p5.js with seeded randomness, flow fields, and particle systems\n- **[canvas-design](https://github.com/anthropics/skills/tree/main/skills/canvas-design)** - Design beautiful visual art in .png and .pdf formats using design philosophies\n- **[slack-gif-creator](https://github.com/anthropics/skills/tree/main/skills/slack-gif-creator)** - Create animated GIFs optimized for Slack's size constraints\n\n### Development\n\n- **[frontend-design](https://github.com/anthropics/skills/blob/main/skills/frontend-design)** - Instructs Claude to avoid \"AI slop\" or generic aesthetics and to make bold design decisions. Works very well for React & Tailwind.\n- **[web-artifacts-builder](https://github.com/anthropics/skills/tree/main/skills/web-artifacts-builder)** - Build complex claude.ai HTML artifacts using React, Tailwind CSS, and shadcn/ui components\n- **[mcp-builder](https://github.com/anthropics/skills/tree/main","createdAt":"2026-09-25T10:52:07.766Z","updatedAt":"2026-09-25T10:52:07.766Z"},{"id":"cmugud4s300wbqu06ircpvef9","slug":"ikaijua-awesome-aitools","name":"Awesome-AITools","description":"Collection of AI-related utilities. Welcome to submit pull requests /ๆ”ถ่—AI็›ธๅ…ณ็š„ๅฎž็”จๅทฅๅ…ท๏ผŒๆฌข่ฟŽๆไบคpull requests","authorId":"gh:ikaijua","authorName":"ikaijua","version":"0.1.0","category":"MCP","securityLevel":"Community","downloadsCount":0,"githubStars":6194,"pricePerCall":0,"manifest":{"name":"Awesome-AITools","tools":[],"category":"MCP","entrypoint":{"args":["-y","github:ikaijua/Awesome-AITools"],"type":"mcp-stdio","command":"npx"},"description":"Collection of AI-related utilities. Welcome to submit pull requests /ๆ”ถ่—AI็›ธๅ…ณ็š„ๅฎž็”จๅทฅๅ…ท๏ผŒๆฌข่ฟŽๆไบคpull requests","permissions":["shell","network"],"schemaVersion":1},"repoUrl":"https://github.com/ikaijua/Awesome-AITools","tags":["agent-skills","ai","artificial-intelligence","awesome","awesome-list","awesome-lists","chatgpt","claude","claude-skills","claudecode","deepseek","gemini"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"Awesome-AITools","audit":{"files":[],"binaries":[],"findings":[],"packages":0,"auditedAt":"2026-09-25T10:52:20.205Z","lockfiles":[]},"forks":796,"owner":"ikaijua","stars":6194,"topics":["agent-skills","ai","artificial-intelligence","awesome","awesome-list","awesome-lists","chatgpt","claude","claude-skills","claudecode","deepseek","gemini","gpt","gpt-image-2","llm","machinelearning","nanobanana","seedance","tools"],"license":null,"fullName":"ikaijua/Awesome-AITools","homepage":null,"language":"Python","pushedAt":"2026-09-25T08:15:06Z","avatarUrl":"https://avatars.githubusercontent.com/u/126046795?v=4","crawledAt":"2026-09-25T10:52:19.985Z","openIssues":37,"manifestFile":"README.md","manifestPath":"README.md","defaultBranch":"main"},"readme":"
\n

Awesome AI Tools

\n \n
\n \"Stars\"\n \"Forks\"\n \"Last\n
\n\nEnglish | [ไธญๆ–‡](README-CN.md)\n\nThis repo collects awesome AI tools. Welcome everyone to recommend more awesome AI tools together! Please use the following template as a reference for your recommendations. [issue](https://github.com/ikaijua/Awesome-AITools/issues/233)\n\n\n\"Buy\n\n- [AI News](https://github.com/ikaijua/Awesome-AITools/discussions?discussions_q=is%3Aopen+label%3A%22ai%E2%80%91news%E2%80%91en%22)\n- [Become Sponsors](#become-sponsors)\n\n## ๐Ÿ’Ž Sponsor\n\n

\n A huge thank you to our sponsors for their generous support!\n

\n\n
\nClick to collapse\n\n \n \n \n
\n \n \n \"Xuanshu\n \n
\n ใ€Xuanshu API is a next-generation AI model routing gateway for enterprises, technical teams, and individual developers. It provides one-stop API access to world-class top models (Claude, GPT, Grok, etc.) with enterprise-grade stability. Recharge and enjoy 20% off, models starting from 20% of the original price, $5 free upon registration, invoice support for enterprises. Click this link to register and get an extra $5 credit.ใ€‘\n
\n \n \"Visit\n \n \n
\n
\n\n## All Categories\n- [All Categories](#all-categories)\n - [AI Assistants & Proprietary Models](#ai-assistants--proprietary-models)\n - [Open Source LLMs](#open-source-llms)\n - [LLM Leaderboard](#llm-leaderboard)\n - [AI Agent](#ai-agent)\n - [Agent Skills](#agent-skills)\n - [AI News & Information](#ai-news--information)\n - [AI Coding](#ai-coding)\n - [General LLM Applications](#general-llm-applications)\n - [Office Collaboration CLI/MCP](#office-collaboration-climcp)\n - [AI Finance & Quant Investment](#ai-finance--quant-investment)\n - [AI Image Creation and UI Design](#ai-image-creation-and-ui-design)\n - [Video Creation](#video-creation)\n - [AI Infrastructure Platform](#ai-infrastructure-platform)\n - [GPU Programming](#gpu-programming)\n - [LLM Prompts](#llm-prompts)\n - [LLM training platform](#llm-training-platform)\n - [LLM Inference & Deployment](#llm-inference--deployment)\n - [Writing](#writing)\n - [Translation](#translation)\n - [Speech Recognition](#speech-recognition)\n - [Text To Speech](#text-to-speech)\n - [Music Recognition](#music-recognition)\n - [Voice Processing](#voice-processing)\n - [AI generated music or sound effects](#ai-generated-music-or-sound-effects)\n - [Speech translation](#speech-translation)\n - [Video Content Summary](#video-content-summary)\n - [Academic research](#academic-research)\n - [OCR](#ocr)\n - [AI Detection](#ai-detection)\n - ","createdAt":"2026-09-25T10:52:20.212Z","updatedAt":"2026-09-25T10:52:20.212Z"},{"id":"cmugwii9t025qqu066ciqnzcp","slug":"prat011-awesome-llm-skills-domain-name-brainstormer","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.","authorId":"gh:prat011","authorName":"Prat011","version":"0.1.0","category":"Prompt","securityLevel":"Community","downloadsCount":0,"githubStars":1761,"pricePerCall":0,"manifest":{"name":"domain-name-brainstormer","tools":[],"category":"Prompt","entrypoint":{"type":"prompt"},"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.","permissions":[],"systemPrompt":"# Domain Name Brainstormer\n\nThis skill helps you find the perfect domain name for your project by generating creative options and checking what's actually available to register.\n\n## When to Use This Skill\n\n- Starting a new project or company\n- Launching a product or service\n- Creating a personal brand or portfolio site\n- Rebranding an existing project\n- Registering a domain for a side project\n- Finding available alternatives when your first choice is taken\n\n## What This Skill Does\n\n1. **Understands Your Project**: Analyzes what you're building and who it's for\n2. **Generates Creative Names**: Creates relevant, memorable domain options\n3. **Checks Availability**: Verifies which domains are actually available across multiple TLDs\n4. **Multiple Extensions**: Suggests .com, .io, .dev, .ai, .app, and more\n5. **Provides Alternatives**: Offers variations if top choices are taken\n6. **Branding Insights**: Explains why certain names work well\n\n## How to Use\n\n### Basic Brainstorming\n\n```\nI'm building a project management tool for remote teams. \nSuggest domain names.\n```\n\n```\nHelp me brainstorm domain names for a personal finance app\n```\n\n### Specific Preferences\n\n```\nI need a domain name for my AI writing assistant. \nPrefer short names with .ai or .io extension.\n```\n\n### With Keywords\n\n```\nSuggest domain names using the words \"pixel\" or \"studio\" \nfor my design agency\n```\n\n## Example\n\n**User**: \"I'm building a tool for developers to share code snippets. Suggest creative domain names.\"\n\n**Output**:\n```\nAnalyzing your project...\nTarget audience: Developers\nKey features: Code sharing, snippets, collaboration\n\n๐ŸŽฏ Domain Name Suggestions\n\n## Available (.com)\n1. โœ“ snippetbox.com - Clear, memorable, available!\n Why: Directly describes the product, easy to remember\n\n2. โœ“ codeclip.com - Short and snappy\n Why: Implies quick code sharing, only 8 characters\n\n3. โœ“ devpaste.com - Developer-focused\n Why: Familiar to devs (like pastebin), clear purpose\n\n## Available (Alternative TLDs)\n4. โœ“ snippet.dev - Perfect extension for developers\n Why: .dev extension signals developer tool\n\n5. โœ“ codebox.io - Tech-forward\n Why: .io popular with tech startups, clean name\n\n6. โœ“ sharecode.app - Descriptive\n Why: .app extension, clearly states the action\n\n## Premium/Taken (.com)\n- codeshare.com (Taken, est. $2,500)\n- snippets.com (Taken, premium domain)\n\n## Recommendations\n\n๐Ÿ† Top Pick: snippet.dev\n- Perfect for developer audience\n- Short and memorable \n- .dev extension adds credibility\n- Available now!\n\n๐Ÿฅˆ Runner-up: snippetbox.com\n- .com is universally recognized\n- Slightly longer but descriptive\n- Great brandability\n\nNext steps:\n1. Register your favorite before someone else does!\n2. Want me to check more variations?\n3. Need help with logo ideas for these names?\n```\n\n**Inspired by:** Ben Aiad's use case from Lenny's Newsletter\n\n## Domain Naming Tips\n\n### What Makes a Good Domain\n\nโœ“ **Short**: Under 15 characters ideal\nโœ“ **Memorable**: Easy to recall and spell\nโœ“ **Pronounceable**: Can be said in conversation\nโœ“ **Descriptive**: Hints at what you do\nโœ“ **Brandable**: Unique enough to stand out\nโœ“ **No hyphens**: Easier to share verbally\n\n### TLD Guide\n\n- **.com**: Universal, trusted, great for businesses\n- **.io**: Tech startups, developer tools\n- **.dev**: Developer-focused products\n- **.ai**: AI/ML products\n- **.app**: Mobile or web applications\n- **.co**: Alternative to .com\n- **.xyz**: Modern, creative projects\n- **.design**: Creative/design agencies\n- **.tech**: Technology companies\n\n## Advanced Features\n\n### Check Similar Variations\n\n```\nCheck availability for \"codebase\" and similar variations \nacross .com, .io, .dev\n```\n\n### Industry-Specific\n\n```\nSuggest domain names for a sustainable fashion brand, \nchecking .eco and .fashion TLDs\n```\n\n### Multilingual Options\n\n```\nBrainstorm domain names in English and Spanish for \na language learning app\n```\n\n### Competitor Analysis\n\n```\nShow me domain patterns used by successful project \nmanagement tools, then suggest similar available ones\n```\n\n## Example Workflows\n\n### Startup Launch\n1. Describe your startup idea\n2. Get 10-15 domain suggestions across TLDs\n3. Review availability and pricing\n4. Pick top 3 favorites\n5. Register immediately\n\n### Personal Brand\n1. Share your name and profession\n2. Get variations (firstname.com, firstnamelastname.dev, etc.)\n3. Check social media handle availability too\n4. Register consistent brand across platforms\n\n### Product Naming\n1. Describe product and target market\n2. Get creative, brandable names\n3. Check trademark conflicts\n4. Verify domain and social availability\n5. Test names with target audience\n\n## Tips for Success\n\n1. **Act Fast**: Good domains get taken quickly\n2. **Register Variations**: Get .com and .io to protect brand\n3. **Avoid Numbers**: Hard to communicate verbally\n4. **Check Social Media**: Make sure @username is available too\n5. **Say It Out Loud**: Test if it's easy to pronounce\n6. **Check Trademarks**: Ensure no legal conflicts\n7. **Think Long-term**: Will it still make sense in 5 years?\n\n## Pricing Context\n\nWhen suggesting domains, I'll note:\n- Standard domains: ~$10-15/year\n- Premium TLDs (.io, .ai): ~$30-50/year\n- Taken domains: Market price if listed\n- Premium domains: $hundreds to $thousands\n\n## Related Tools\n\nAfter picking a domain:\n- Check logo design options\n- Verify social media handles\n- Research trademark availability\n- Plan brand identity colors/fonts","schemaVersion":1},"repoUrl":"https://github.com/Prat011/awesome-llm-skills/tree/master/domain-name-brainstormer","tags":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"awesome-llm-skills","audit":{"files":["slack-gif-creator/requirements.txt"],"binaries":[],"findings":[{"kind":"dependency","rule":"DP-04","message":"Python dependencies are not pinned and there is no lock file.","surface":"slack-gif-creator/requirements.txt","evidence":"pillow>=10.0.0, imageio>=2.31.0, imageio-ffmpeg>=0.4.9, numpy>=1.24.0","severity":"medium"}],"packages":4,"auditedAt":"2026-09-25T11:52:30.068Z","lockfiles":[]},"forks":313,"owner":"Prat011","stars":1761,"topics":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms","openai","opencode","qwen","qwen-coder","skills"],"license":null,"fullName":"Prat011/awesome-llm-skills","homepage":null,"language":"Python","pushedAt":"2026-07-14T09:53:56Z","avatarUrl":"https://avatars.githubusercontent.com/u/67639393?v=4","crawledAt":"2026-09-25T11:52:22.319Z","openIssues":170,"manifestFile":"SKILL.md","manifestPath":"domain-name-brainstormer/SKILL.md","defaultBranch":"master"},"readme":"# Domain Name Brainstormer\n\nThis skill helps you find the perfect domain name for your project by generating creative options and checking what's actually available to register.\n\n## When to Use This Skill\n\n- Starting a new project or company\n- Launching a product or service\n- Creating a personal brand or portfolio site\n- Rebranding an existing project\n- Registering a domain for a side project\n- Finding available alternatives when your first choice is taken\n\n## What This Skill Does\n\n1. **Understands Your Project**: Analyzes what you're building and who it's for\n2. **Generates Creative Names**: Creates relevant, memorable domain options\n3. **Checks Availability**: Verifies which domains are actually available across multiple TLDs\n4. **Multiple Extensions**: Suggests .com, .io, .dev, .ai, .app, and more\n5. **Provides Alternatives**: Offers variations if top choices are taken\n6. **Branding Insights**: Explains why certain names work well\n\n## How to Use\n\n### Basic Brainstorming\n\n```\nI'm building a project management tool for remote teams. \nSuggest domain names.\n```\n\n```\nHelp me brainstorm domain names for a personal finance app\n```\n\n### Specific Preferences\n\n```\nI need a domain name for my AI writing assistant. \nPrefer short names with .ai or .io extension.\n```\n\n### With Keywords\n\n```\nSuggest domain names using the words \"pixel\" or \"studio\" \nfor my design agency\n```\n\n## Example\n\n**User**: \"I'm building a tool for developers to share code snippets. Suggest creative domain names.\"\n\n**Output**:\n```\nAnalyzing your project...\nTarget audience: Developers\nKey features: Code sharing, snippets, collaboration\n\n๐ŸŽฏ Domain Name Suggestions\n\n## Available (.com)\n1. โœ“ snippetbox.com - Clear, memorable, available!\n Why: Directly describes the product, easy to remember\n\n2. โœ“ codeclip.com - Short and snappy\n Why: Implies quick code sharing, only 8 characters\n\n3. โœ“ devpaste.com - Developer-focused\n Why: Familiar to devs (like pastebin), clear purpose\n\n## Available (Alternative TLDs)\n4. โœ“ snippet.dev - Perfect extension for developers\n Why: .dev extension signals developer tool\n\n5. โœ“ codebox.io - Tech-forward\n Why: .io popular with tech startups, clean name\n\n6. โœ“ sharecode.app - Descriptive\n Why: .app extension, clearly states the action\n\n## Premium/Taken (.com)\n- codeshare.com (Taken, est. $2,500)\n- snippets.com (Taken, premium domain)\n\n## Recommendations\n\n๐Ÿ† Top Pick: snippet.dev\n- Perfect for developer audience\n- Short and memorable \n- .dev extension adds credibility\n- Available now!\n\n๐Ÿฅˆ Runner-up: snippetbox.com\n- .com is universally recognized\n- Slightly longer but descriptive\n- Great brandability\n\nNext steps:\n1. Register your favorite before someone else does!\n2. Want me to check more variations?\n3. Need help with logo ideas for these names?\n```\n\n**Inspired by:** Ben Aiad's use case from Lenny's Newsletter\n\n## Domain Naming Tips\n\n### What Makes a Good Domain\n\nโœ“ **Short**: Under 15 characters ideal\nโœ“ **Memorable**: Easy to recall and spell\nโœ“ **Pronounceable**: Can be said in conversation\nโœ“ **Descriptive**: Hints at what you do\nโœ“ **Brandable**: Unique enough to stand out\nโœ“ **No hyphens**: Easier to share verbally\n\n### TLD Guide\n\n- **.com**: Universal, trusted, great for businesses\n- **.io**: Tech startups, developer tools\n- **.dev**: Developer-focused products\n- **.ai**: AI/ML products\n- **.app**: Mobile or web applications\n- **.co**: Alternative to .com\n- **.xyz**: Modern, creative projects\n- **.design**: Creative/design agencies\n- **.tech**: Technology companies\n\n## Advanced Features\n\n### Check Similar Variations\n\n```\nCheck availability for \"codebase\" and similar variations \nacross .com, .io, .dev\n```\n\n### Industry-Specific\n\n```\nSuggest domain names for a sustainable fashion brand, \nchecking .eco and .fashion TLDs\n```\n\n### Multilingual Options\n\n```\nBrainstorm domain names in English and Spanish for \na language learning app\n```\n\n### Competitor Analysis\n\n```\nShow me domain patterns used by successful project \nmanagement tools, then sug","createdAt":"2026-09-25T11:52:30.209Z","updatedAt":"2026-09-25T11:52:30.209Z"},{"id":"cmugwii73024nqu06asxvxsi2","slug":"prat011-awesome-llm-skills-algorithmic-art","name":"algorithmic-art","description":"Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.","authorId":"gh:prat011","authorName":"Prat011","version":"0.1.0","category":"Prompt","securityLevel":"Sandbox","downloadsCount":0,"githubStars":1761,"pricePerCall":0,"manifest":{"name":"algorithmic-art","tools":[],"category":"Prompt","entrypoint":{"type":"prompt"},"description":"Creating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems. Create original algorithmic art rather than copying existing artists' work to avoid copyright violations.","permissions":[],"systemPrompt":"Algorithmic philosophies are computational aesthetic movements that are then expressed through code. Output .md files (philosophy), .html files (interactive viewer), and .js files (generative algorithms).\n\nThis happens in two steps:\n1. Algorithmic Philosophy Creation (.md file)\n2. Express by creating p5.js generative art (.html + .js files)\n\nFirst, undertake this task:\n\n## ALGORITHMIC PHILOSOPHY CREATION\n\nTo begin, create an ALGORITHMIC PHILOSOPHY (not static images or templates) that will be interpreted through:\n- Computational processes, emergent behavior, mathematical beauty\n- Seeded randomness, noise fields, organic systems\n- Particles, flows, fields, forces\n- Parametric variation and controlled chaos\n\n### THE CRITICAL UNDERSTANDING\n- What is received: Some subtle input or instructions by the user to take into account, but use as a foundation; it should not constrain creative freedom.\n- What is created: An algorithmic philosophy/generative aesthetic movement.\n- What happens next: The same version receives the philosophy and EXPRESSES IT IN CODE - creating p5.js sketches that are 90% algorithmic generation, 10% essential parameters.\n\nConsider this approach:\n- Write a manifesto for a generative art movement\n- The next phase involves writing the algorithm that brings it to life\n\nThe philosophy must emphasize: Algorithmic expression. Emergent behavior. Computational beauty. Seeded variation.\n\n### HOW TO GENERATE AN ALGORITHMIC PHILOSOPHY\n\n**Name the movement** (1-2 words): \"Organic Turbulence\" / \"Quantum Harmonics\" / \"Emergent Stillness\"\n\n**Articulate the philosophy** (4-6 paragraphs - concise but complete):\n\nTo capture the ALGORITHMIC essence, express how this philosophy manifests through:\n- Computational processes and mathematical relationships?\n- Noise functions and randomness patterns?\n- Particle behaviors and field dynamics?\n- Temporal evolution and system states?\n- Parametric variation and emergent complexity?\n\n**CRITICAL GUIDELINES:**\n- **Avoid redundancy**: Each algorithmic aspect should be mentioned once. Avoid repeating concepts about noise theory, particle dynamics, or mathematical principles unless adding new depth.\n- **Emphasize craftsmanship REPEATEDLY**: The philosophy MUST stress multiple times that the final algorithm should appear as though it took countless hours to develop, was refined with care, and comes from someone at the absolute top of their field. This framing is essential - repeat phrases like \"meticulously crafted algorithm,\" \"the product of deep computational expertise,\" \"painstaking optimization,\" \"master-level implementation.\"\n- **Leave creative space**: Be specific about the algorithmic direction, but concise enough that the next Claude has room to make interpretive implementation choices at an extremely high level of craftsmanship.\n\nThe philosophy must guide the next version to express ideas ALGORITHMICALLY, not through static images. Beauty lives in the process, not the final frame.\n\n### PHILOSOPHY EXAMPLES\n\n**\"Organic Turbulence\"**\nPhilosophy: Chaos constrained by natural law, order emerging from disorder.\nAlgorithmic expression: Flow fields driven by layered Perlin noise. Thousands of particles following vector forces, their trails accumulating into organic density maps. Multiple noise octaves create turbulent regions and calm zones. Color emerges from velocity and density - fast particles burn bright, slow ones fade to shadow. The algorithm runs until equilibrium - a meticulously tuned balance where every parameter was refined through countless iterations by a master of computational aesthetics.\n\n**\"Quantum Harmonics\"**\nPhilosophy: Discrete entities exhibiting wave-like interference patterns.\nAlgorithmic expression: Particles initialized on a grid, each carrying a phase value that evolves through sine waves. When particles are near, their phases interfere - constructive interference creates bright nodes, destructive creates voids. Simple harmonic motion generates complex emergent mandalas. The result of painstaking frequency calibration where every ratio was carefully chosen to produce resonant beauty.\n\n**\"Recursive Whispers\"**\nPhilosophy: Self-similarity across scales, infinite depth in finite space.\nAlgorithmic expression: Branching structures that subdivide recursively. Each branch slightly randomized but constrained by golden ratios. L-systems or recursive subdivision generate tree-like forms that feel both mathematical and organic. Subtle noise perturbations break perfect symmetry. Line weights diminish with each recursion level. Every branching angle the product of deep mathematical exploration.\n\n**\"Field Dynamics\"**\nPhilosophy: Invisible forces made visible through their effects on matter.\nAlgorithmic expression: Vector fields constructed from mathematical functions or noise. Particles born at edges, flowing along field lines, dying when they reach equilibrium or boundaries. Multiple fields can attract, repel, or rotate particles. The visualization shows only the traces - ghost-like evidence of invisible forces. A computational dance meticulously choreographed through force balance.\n\n**\"Stochastic Crystallization\"**\nPhilosophy: Random processes crystallizing into ordered structures.\nAlgorithmic expression: Randomized circle packing or Voronoi tessellation. Start with random points, let them evolve through relaxation algorithms. Cells push apart until equilibrium. Color based on cell size, neighbor count, or distance from center. The organic tiling that emerges feels both random and inevitable. Every seed produces unique crystalline beauty - the mark of a master-level generative algorithm.\n\n*These are condensed examples. The actual algorithmic philosophy should be 4-6 substantial paragraphs.*\n\n### ESSENTIAL PRINCIPLES\n- **ALGORITHMIC PHILOSOPHY**: Creating a computational worldview to be expressed through code\n- **PROCESS OVER PRODUCT**: Always emphasize that beauty emerges from the algorithm's execution - each run is unique\n- **PARAMETRIC EXPRESSION**: Ideas communicate through mathematical relationships, forces, behaviors - not static composition\n- **ARTISTIC FREEDOM**: The next Claude interprets the philosophy algorithmically - provide creative implementation room\n- **PURE GENERATIVE ART**: This is about making LIVING ALGORITHMS, not static images with randomness\n- **EXPERT CRAFTSMANSHIP**: Repeatedly emphasize the final algorithm must feel meticulously crafted, refined through countless iterations, the product of deep expertise by someone at the absolute top of their field in computational aesthetics\n\n**The algorithmic philosophy should be 4-6 paragraphs long.** Fill it with poetic computational philosophy that brings together the intended vision. Avoid repeating the same points. Output this algorithmic philosophy as a .md file.\n\n---\n\n## DEDUCING THE CONCEPTUAL SEED\n\n**CRITICAL STEP**: Before implementing the algorithm, identify the subtle conceptual thread from the original request.\n\n**THE ESSENTIAL PRINCIPLE**:\nThe concept is a **subtle, niche reference embedded within the algorithm itself** - not always literal, always sophisticated. Someone familiar with the subject should feel it intuitively, while others simply experience a masterful generative composition. The algorithmic philosophy provides the computational language. The deduced concept provides the soul - the quiet conceptual DNA woven invisibly into parameters, behaviors, and emergence patterns.\n\nThis is **VERY IMPORTANT**: The reference must be so refined that it enhances the work's depth without announcing itself. Think like a jazz musician quoting another song through algorithmic harmony - only those who know will catch it, but everyone appreciates the generative beauty.\n\n---\n\n## P5.JS IMPLEMENTATION\n\nWith the philosophy AND conceptual framework established, express it through code. Pause to gather thoughts before proceeding. Use only the algorithmic philosophy created and the instructions below.\n\n### โš ๏ธ STEP 0: READ THE TEMPLATE FIRST โš ๏ธ\n\n**CRITICAL: BEFORE writing any HTML:**\n\n1. **Read** `templates/viewer.html` using the Read tool\n2. **Study** the exact structure, styling, and Anthropic branding\n3. **Use that file as the LITERAL STARTING POINT** - not just inspiration\n4. **Keep all FIXED sections exactly as shown** (header, sidebar structure, Anthropic colors/fonts, seed controls, action buttons)\n5. **Replace only the VARIABLE sections** marked in the file's comments (algorithm, parameters, UI controls for parameters)\n\n**Avoid:**\n- โŒ Creating HTML from scratch\n- โŒ Inventing custom styling or color schemes\n- โŒ Using system fonts or dark themes\n- โŒ Changing the sidebar structure\n\n**Follow these practices:**\n- โœ… Copy the template's exact HTML structure\n- โœ… Keep Anthropic branding (Poppins/Lora fonts, light colors, gradient backdrop)\n- โœ… Maintain the sidebar layout (Seed โ†’ Parameters โ†’ Colors? โ†’ Actions)\n- โœ… Replace only the p5.js algorithm and parameter controls\n\nThe template is the foundation. Build on it, don't rebuild it.\n\n---\n\nTo create gallery-quality computational art that lives and breathes, use the algorithmic philosophy as the foundation.\n\n### TECHNICAL REQUIREMENTS\n\n**Seeded Randomness (Art Blocks Pattern)**:\n```javascript\n// ALWAYS use a seed for reproducibility\nlet seed = 12345; // or hash from user input\nrandomSeed(seed);\nnoiseSeed(seed);\n```\n\n**Parameter Structure - FOLLOW THE PHILOSOPHY**:\n\nTo establish parameters that emerge naturally from the algorithmic philosophy, consider: \"What qualities of this system can be adjusted?\"\n\n```javascript\nlet params = {\n seed: 12345, // Always include seed for reproducibility\n // colors\n // Add parameters that control YOUR algorithm:\n // - Quantities (how many?)\n // - Scales (how big? how fast?)\n // - Probabilities (how likely?)\n // - Ratios (what proportions?)\n // - Angles (what direction?)\n // - Thresholds (when does behavior change?)\n};\n```\n\n**To design effective parameters, focus on the properties the system needs to be tunable rather than thinking in terms of \"pattern types\".**\n\n**Core Algorithm - EXPRESS THE PHILOSOPHY**:\n\n**CRITICAL**: The algorithmic philosophy should dictate what to build.\n\nTo express the philosophy through code, avoid thinking \"which pattern should I use?\" and instead think \"how to express this philosophy through code?\"\n\nIf the philosophy is about **organic emergence**, consider using:\n- Elements that accumulate or grow over time\n- Random processes constrained by natural rules\n- Feedback loops and interactions\n\nIf the philosophy is about **mathematical beauty**, consider using:\n- Geometric relationships and ratios\n- Trigonometric functions and harmonics\n- Precise calculations creating unexpected patterns\n\nIf the philosophy is about **controlled chaos**, consider using:\n- Random variation within strict boundaries\n- Bifurcation and phase transitions\n- Order emerging from disorder\n\n**The algorithm flows from the philosophy, not from a menu of options.**\n\nTo guide the implementation, let the conceptual essence inform creative and original choices. Build something that expresses the vision for this particular request.\n\n**Canvas Setup**: Standard p5.js structure:\n```javascript\nfunction setup() {\n createCanvas(1200, 1200);\n // Initialize your system\n}\n\nfunction draw() {\n // Your generative algorithm\n // Can be static (noLoop) or animated\n}\n```\n\n### CRAFTSMANSHIP REQUIREMENTS\n\n**CRITICAL**: To achieve mastery, create algorithms that feel like they emerged through countless iterations by a master generative artist. Tune every parameter carefully. Ensure every pattern emerges with purpose. This is NOT random noise - this is CONTROLLED CHAOS refined through deep expertise.\n\n- **Balance**: Complexity without visual noise, order without rigidity\n- **Color Harmony**: Thoughtful palettes, not random RGB values\n- **Composition**: Even in randomness, maintain visual hierarchy and flow\n- **Performance**: Smooth execution, optimized for real-time if animated\n- **Reproducibility**: Same seed ALWAYS produces identical output\n\n### OUTPUT FORMAT\n\nOutput:\n1. **Algorithmic Philosophy** - As markdown or text explaining the generative aesthetic\n2. **Single HTML Artifact** - Self-contained interactive generative art built from `templates/viewer.html` (see STEP 0 and next section)\n\nThe HTML artifact contains everything: p5.js (from CDN), the algorithm, parameter controls, and UI - all in one file that works immediately in claude.ai artifacts or any browser. Start from the template file, not from scratch.\n\n---\n\n## INTERACTIVE ARTIFACT CREATION\n\n**REMINDER: `templates/viewer.html` should have already been read (see STEP 0). Use that file as the starting point.**\n\nTo allow exploration of the generative art, create a single, self-contained HTML artifact. Ensure this artifact works immediately in claude.ai or any browser - no setup required. Embed everything inline.\n\n### CRITICAL: WHAT'S FIXED VS VARIABLE\n\nThe `templates/viewer.html` file is the foundation. It contains the exact structure and styling needed.\n\n**FIXED (always include exactly as shown):**\n- Layout structure (header, sidebar, main canvas area)\n- Anthropic branding (UI colors, fonts, gradients)\n- Seed section in sidebar:\n - Seed display\n - Previous/Next buttons\n - Random button\n - Jump to seed input + Go button\n- Actions section in sidebar:\n - Regenerate button\n - Reset button\n\n**VARIABLE (customize for each artwork):**\n- The entire p5.js algorithm (setup/draw/classes)\n- The parameters object (define what the art needs)\n- The Parameters section in sidebar:\n - Number of parameter controls\n - Parameter names\n - Min/max/step values for sliders\n - Control types (sliders, inputs, etc.)\n- Colors section (optional):\n - Some art needs color pickers\n - Some art might use fixed colors\n - Some art might be monochrome (no color controls needed)\n - Decide based on the art's needs\n\n**Every artwork should have unique parameters and algorithm!** The fixed parts provide consistent UX - everything else expresses the unique vision.\n\n### REQUIRED FEATURES\n\n**1. Parameter Controls**\n- Sliders for numeric parameters (particle count, noise scale, speed, etc.)\n- Color pickers for palette colors\n- Real-time updates when parameters change\n- Reset button to restore defaults\n\n**2. Seed Navigation**\n- Display current seed number\n- \"Previous\" and \"Next\" buttons to cycle through seeds\n- \"Random\" button for random seed\n- Input field to jump to specific seed\n- Generate 100 variations when requested (seeds 1-100)\n\n**3. Single Artifact Structure**\n```html\n\n\n\n \n \n \n\n\n
\n
\n \n
\n \n\n\n```\n\n**CRITICAL**: This is a single artifact. No external files, no imports (except p5.js CDN). Everything inline.\n\n**4. Implementation Details - BUILD THE SIDEBAR**\n\nThe sidebar structure:\n\n**1. Seed (FIXED)** - Always include exactly as shown:\n- Seed display\n- Prev/Next/Random/Jump buttons\n\n**2. Parameters (VARIABLE)** - Create controls for the art:\n```html\n
\n \n \n ...\n
\n```\nAdd as many control-group divs as there are parameters.\n\n**3. Colors (OPTIONAL/VARIABLE)** - Include if the art needs adjustable colors:\n- Add color pickers if users should control palette\n- Skip this section if the art uses fixed colors\n- Skip if the art is monochrome\n\n**4. Actions (FIXED)** - Always include exactly as shown:\n- Regenerate button\n- Reset button\n- Download PNG button\n\n**Requirements**:\n- Seed controls must work (prev/next/random/jump/display)\n- All parameters must have UI controls\n- Regenerate, Reset, Download buttons must work\n- Keep Anthropic branding (UI styling, not art colors)\n\n### USING THE ARTIFACT\n\nThe HTML artifact works immediately:\n1. **In claude.ai**: Displayed as an interactive artifact - runs instantly\n2. **As a file**: Save and open in any browser - no server needed\n3. **Sharing**: Send the HTML file - it's completely self-contained\n\n---\n\n## VARIATIONS & EXPLORATION\n\nThe artifact includes seed navigation by default (prev/next/random buttons), allowing users to explore variations without creating multiple files. If the user wants specific variations highlighted:\n\n- Include seed presets (buttons for \"Variation 1: Seed 42\", \"Variation 2: Seed 127\", etc.)\n- Add a \"Gallery Mode\" that shows thumbnails of multiple seeds side-by-side\n- All within the same single artifact\n\nThis is like creating a series of prints from the same plate - the algorithm is consistent, but each seed reveals different facets of its potential. The interactive nature means users discover their own favorites by exploring the seed space.\n\n---\n\n## THE CREATIVE PROCESS\n\n**User request** โ†’ **Algorithmic philosophy** โ†’ **Implementation**\n\nEach request is unique. The process involves:\n\n1. **Interpret the user's intent** - What aesthetic is being sought?\n2. **Create an algorithmic philosophy** (4-6 paragraphs) describing the computational approach\n3. **Implement it in code** - Build the algorithm that expresses this philosophy\n4. **Design appropriate parameters** - What should be tunable?\n5. **Build matching UI controls** - Sliders/inputs for those parameters\n\n**The constants**:\n- Anthropic branding (colors, fonts, layout)\n- Seed navigation (always present)\n- Self-contained HTML artifact\n\n**Everything else is variable**:\n- The algorithm itself\n- The parameters\n- The UI controls\n- The visual outcome\n\nTo achieve the best results, trust creativity and let the philosophy guide the implementation.\n\n---\n\n## RESOURCES\n\nThis skill includes helpful templates and documentation:\n\n- **templates/viewer.html**: REQUIRED STARTING POINT for all HTML artifacts.\n - This is the foundation - contains the exact structure and Anthropic branding\n - **Keep unchanged**: Layout structure, sidebar organization, Anthropic colors/fonts, seed controls, action buttons\n - **Replace**: The p5.js algorithm, parameter definitions, and UI controls in Parameters section\n - The extensive comments in the file mark exactly what to keep vs replace\n\n- **templates/generator_template.js**: Reference for p5.js best practices and code structure principles.\n - Shows how to organize parameters, use seeded randomness, structure classes\n - NOT a pattern menu - use these principles to build unique algorithms\n - Embed algorithms inline in the HTML artifact (don't create separate .js files)\n\n**Critical reminder**:\n- The **template is the STARTING POINT**, not inspiration\n- The **algorithm is where to create** something unique\n- Don't copy the flow field example - build what the philosophy demands\n- But DO keep the exact UI structure and Anthropic branding from the template","schemaVersion":1},"repoUrl":"https://github.com/Prat011/awesome-llm-skills/tree/master/algorithmic-art","tags":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"awesome-llm-skills","audit":{"files":["slack-gif-creator/requirements.txt"],"binaries":[],"findings":[{"kind":"dependency","rule":"DP-04","message":"Python dependencies are not pinned and there is no lock file.","surface":"slack-gif-creator/requirements.txt","evidence":"pillow>=10.0.0, imageio>=2.31.0, imageio-ffmpeg>=0.4.9, numpy>=1.24.0","severity":"medium"}],"packages":4,"auditedAt":"2026-09-25T11:52:30.068Z","lockfiles":[]},"forks":313,"owner":"Prat011","stars":1761,"topics":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms","openai","opencode","qwen","qwen-coder","skills"],"license":"Complete terms in LICENSE.txt","fullName":"Prat011/awesome-llm-skills","homepage":null,"language":"Python","pushedAt":"2026-07-14T09:53:56Z","avatarUrl":"https://avatars.githubusercontent.com/u/67639393?v=4","crawledAt":"2026-09-25T11:52:22.319Z","openIssues":170,"manifestFile":"SKILL.md","manifestPath":"algorithmic-art/SKILL.md","defaultBranch":"master"},"readme":"Algorithmic philosophies are computational aesthetic movements that are then expressed through code. Output .md files (philosophy), .html files (interactive viewer), and .js files (generative algorithms).\n\nThis happens in two steps:\n1. Algorithmic Philosophy Creation (.md file)\n2. Express by creating p5.js generative art (.html + .js files)\n\nFirst, undertake this task:\n\n## ALGORITHMIC PHILOSOPHY CREATION\n\nTo begin, create an ALGORITHMIC PHILOSOPHY (not static images or templates) that will be interpreted through:\n- Computational processes, emergent behavior, mathematical beauty\n- Seeded randomness, noise fields, organic systems\n- Particles, flows, fields, forces\n- Parametric variation and controlled chaos\n\n### THE CRITICAL UNDERSTANDING\n- What is received: Some subtle input or instructions by the user to take into account, but use as a foundation; it should not constrain creative freedom.\n- What is created: An algorithmic philosophy/generative aesthetic movement.\n- What happens next: The same version receives the philosophy and EXPRESSES IT IN CODE - creating p5.js sketches that are 90% algorithmic generation, 10% essential parameters.\n\nConsider this approach:\n- Write a manifesto for a generative art movement\n- The next phase involves writing the algorithm that brings it to life\n\nThe philosophy must emphasize: Algorithmic expression. Emergent behavior. Computational beauty. Seeded variation.\n\n### HOW TO GENERATE AN ALGORITHMIC PHILOSOPHY\n\n**Name the movement** (1-2 words): \"Organic Turbulence\" / \"Quantum Harmonics\" / \"Emergent Stillness\"\n\n**Articulate the philosophy** (4-6 paragraphs - concise but complete):\n\nTo capture the ALGORITHMIC essence, express how this philosophy manifests through:\n- Computational processes and mathematical relationships?\n- Noise functions and randomness patterns?\n- Particle behaviors and field dynamics?\n- Temporal evolution and system states?\n- Parametric variation and emergent complexity?\n\n**CRITICAL GUIDELINES:**\n- **Avoid redundancy**: Each algorithmic aspect should be mentioned once. Avoid repeating concepts about noise theory, particle dynamics, or mathematical principles unless adding new depth.\n- **Emphasize craftsmanship REPEATEDLY**: The philosophy MUST stress multiple times that the final algorithm should appear as though it took countless hours to develop, was refined with care, and comes from someone at the absolute top of their field. This framing is essential - repeat phrases like \"meticulously crafted algorithm,\" \"the product of deep computational expertise,\" \"painstaking optimization,\" \"master-level implementation.\"\n- **Leave creative space**: Be specific about the algorithmic direction, but concise enough that the next Claude has room to make interpretive implementation choices at an extremely high level of craftsmanship.\n\nThe philosophy must guide the next version to express ideas ALGORITHMICALLY, not through static images. Beauty lives in the process, not the final frame.\n\n### PHILOSOPHY EXAMPLES\n\n**\"Organic Turbulence\"**\nPhilosophy: Chaos constrained by natural law, order emerging from disorder.\nAlgorithmic expression: Flow fields driven by layered Perlin noise. Thousands of particles following vector forces, their trails accumulating into organic density maps. Multiple noise octaves create turbulent regions and calm zones. Color emerges from velocity and density - fast particles burn bright, slow ones fade to shadow. The algorithm runs until equilibrium - a meticulously tuned balance where every parameter was refined through countless iterations by a master of computational aesthetics.\n\n**\"Quantum Harmonics\"**\nPhilosophy: Discrete entities exhibiting wave-like interference patterns.\nAlgorithmic expression: Particles initialized on a grid, each carrying a phase value that evolves through sine waves. When particles are near, their phases interfere - constructive interference creates bright nodes, destructive creates voids. Simple harmonic motion generates complex emergent mandalas.","createdAt":"2026-09-25T11:52:30.111Z","updatedAt":"2026-09-25T11:52:30.111Z"},{"id":"cmugwii7u024zqu06a5p28xdn","slug":"prat011-awesome-llm-skills-brand-guidelines","name":"brand-guidelines","description":"Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.","authorId":"gh:prat011","authorName":"Prat011","version":"0.1.0","category":"Prompt","securityLevel":"Sandbox","downloadsCount":0,"githubStars":1761,"pricePerCall":0,"manifest":{"name":"brand-guidelines","tools":[],"category":"Prompt","entrypoint":{"type":"prompt"},"description":"Applies Anthropic's official brand colors and typography to any sort of artifact that may benefit from having Anthropic's look-and-feel. Use it when brand colors or style guidelines, visual formatting, or company design standards apply.","permissions":[],"systemPrompt":"# Anthropic Brand Styling\n\n## Overview\n\nTo access Anthropic's official brand identity and style resources, use this skill.\n\n**Keywords**: branding, corporate identity, visual identity, post-processing, styling, brand colors, typography, Anthropic brand, visual formatting, visual design\n\n## Brand Guidelines\n\n### Colors\n\n**Main Colors:**\n\n- Dark: `#141413` - Primary text and dark backgrounds\n- Light: `#faf9f5` - Light backgrounds and text on dark\n- Mid Gray: `#b0aea5` - Secondary elements\n- Light Gray: `#e8e6dc` - Subtle backgrounds\n\n**Accent Colors:**\n\n- Orange: `#d97757` - Primary accent\n- Blue: `#6a9bcc` - Secondary accent\n- Green: `#788c5d` - Tertiary accent\n\n### Typography\n\n- **Headings**: Poppins (with Arial fallback)\n- **Body Text**: Lora (with Georgia fallback)\n- **Note**: Fonts should be pre-installed in your environment for best results\n\n## Features\n\n### Smart Font Application\n\n- Applies Poppins font to headings (24pt and larger)\n- Applies Lora font to body text\n- Automatically falls back to Arial/Georgia if custom fonts unavailable\n- Preserves readability across all systems\n\n### Text Styling\n\n- Headings (24pt+): Poppins font\n- Body text: Lora font\n- Smart color selection based on background\n- Preserves text hierarchy and formatting\n\n### Shape and Accent Colors\n\n- Non-text shapes use accent colors\n- Cycles through orange, blue, and green accents\n- Maintains visual interest while staying on-brand\n\n## Technical Details\n\n### Font Management\n\n- Uses system-installed Poppins and Lora fonts when available\n- Provides automatic fallback to Arial (headings) and Georgia (body)\n- No font installation required - works with existing system fonts\n- For best results, pre-install Poppins and Lora fonts in your environment\n\n### Color Application\n\n- Uses RGB color values for precise brand matching\n- Applied via python-pptx's RGBColor class\n- Maintains color fidelity across different systems","schemaVersion":1},"repoUrl":"https://github.com/Prat011/awesome-llm-skills/tree/master/brand-guidelines","tags":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"awesome-llm-skills","audit":{"files":["slack-gif-creator/requirements.txt"],"binaries":[],"findings":[{"kind":"dependency","rule":"DP-04","message":"Python dependencies are not pinned and there is no lock file.","surface":"slack-gif-creator/requirements.txt","evidence":"pillow>=10.0.0, imageio>=2.31.0, imageio-ffmpeg>=0.4.9, numpy>=1.24.0","severity":"medium"}],"packages":4,"auditedAt":"2026-09-25T11:52:30.068Z","lockfiles":[]},"forks":313,"owner":"Prat011","stars":1761,"topics":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms","openai","opencode","qwen","qwen-coder","skills"],"license":"Complete terms in LICENSE.txt","fullName":"Prat011/awesome-llm-skills","homepage":null,"language":"Python","pushedAt":"2026-07-14T09:53:56Z","avatarUrl":"https://avatars.githubusercontent.com/u/67639393?v=4","crawledAt":"2026-09-25T11:52:22.319Z","openIssues":170,"manifestFile":"SKILL.md","manifestPath":"brand-guidelines/SKILL.md","defaultBranch":"master"},"readme":"# Anthropic Brand Styling\n\n## Overview\n\nTo access Anthropic's official brand identity and style resources, use this skill.\n\n**Keywords**: branding, corporate identity, visual identity, post-processing, styling, brand colors, typography, Anthropic brand, visual formatting, visual design\n\n## Brand Guidelines\n\n### Colors\n\n**Main Colors:**\n\n- Dark: `#141413` - Primary text and dark backgrounds\n- Light: `#faf9f5` - Light backgrounds and text on dark\n- Mid Gray: `#b0aea5` - Secondary elements\n- Light Gray: `#e8e6dc` - Subtle backgrounds\n\n**Accent Colors:**\n\n- Orange: `#d97757` - Primary accent\n- Blue: `#6a9bcc` - Secondary accent\n- Green: `#788c5d` - Tertiary accent\n\n### Typography\n\n- **Headings**: Poppins (with Arial fallback)\n- **Body Text**: Lora (with Georgia fallback)\n- **Note**: Fonts should be pre-installed in your environment for best results\n\n## Features\n\n### Smart Font Application\n\n- Applies Poppins font to headings (24pt and larger)\n- Applies Lora font to body text\n- Automatically falls back to Arial/Georgia if custom fonts unavailable\n- Preserves readability across all systems\n\n### Text Styling\n\n- Headings (24pt+): Poppins font\n- Body text: Lora font\n- Smart color selection based on background\n- Preserves text hierarchy and formatting\n\n### Shape and Accent Colors\n\n- Non-text shapes use accent colors\n- Cycles through orange, blue, and green accents\n- Maintains visual interest while staying on-brand\n\n## Technical Details\n\n### Font Management\n\n- Uses system-installed Poppins and Lora fonts when available\n- Provides automatic fallback to Arial (headings) and Georgia (body)\n- No font installation required - works with existing system fonts\n- For best results, pre-install Poppins and Lora fonts in your environment\n\n### Color Application\n\n- Uses RGB color values for precise brand matching\n- Applied via python-pptx's RGBColor class\n- Maintains color fidelity across different systems","createdAt":"2026-09-25T11:52:30.138Z","updatedAt":"2026-09-25T11:52:30.138Z"},{"id":"cmugwii7i024tqu065dz4edew","slug":"prat011-awesome-llm-skills-artifacts-builder","name":"artifacts-builder","description":"Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.","authorId":"gh:prat011","authorName":"Prat011","version":"0.1.0","category":"Prompt","securityLevel":"Community","downloadsCount":0,"githubStars":1761,"pricePerCall":0,"manifest":{"name":"artifacts-builder","tools":[],"category":"Prompt","entrypoint":{"type":"prompt"},"description":"Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn/ui). Use for complex artifacts requiring state management, routing, or shadcn/ui components - not for simple single-file HTML/JSX artifacts.","permissions":[],"systemPrompt":"# Artifacts Builder\n\nTo build powerful frontend claude.ai artifacts, follow these steps:\n1. Initialize the frontend repo using `scripts/init-artifact.sh`\n2. Develop your artifact by editing the generated code\n3. Bundle all code into a single HTML file using `scripts/bundle-artifact.sh`\n4. Display artifact to user\n5. (Optional) Test the artifact\n\n**Stack**: React 18 + TypeScript + Vite + Parcel (bundling) + Tailwind CSS + shadcn/ui\n\n## Design & Style Guidelines\n\nVERY IMPORTANT: To avoid what is often referred to as \"AI slop\", avoid using excessive centered layouts, purple gradients, uniform rounded corners, and Inter font.\n\n## Quick Start\n\n### Step 1: Initialize Project\n\nRun the initialization script to create a new React project:\n```bash\nbash scripts/init-artifact.sh \ncd \n```\n\nThis creates a fully configured project with:\n- โœ… React + TypeScript (via Vite)\n- โœ… Tailwind CSS 3.4.1 with shadcn/ui theming system\n- โœ… Path aliases (`@/`) configured\n- โœ… 40+ shadcn/ui components pre-installed\n- โœ… All Radix UI dependencies included\n- โœ… Parcel configured for bundling (via .parcelrc)\n- โœ… Node 18+ compatibility (auto-detects and pins Vite version)\n\n### Step 2: Develop Your Artifact\n\nTo build the artifact, edit the generated files. See **Common Development Tasks** below for guidance.\n\n### Step 3: Bundle to Single HTML File\n\nTo bundle the React app into a single HTML artifact:\n```bash\nbash scripts/bundle-artifact.sh\n```\n\nThis creates `bundle.html` - a self-contained artifact with all JavaScript, CSS, and dependencies inlined. This file can be directly shared in Claude conversations as an artifact.\n\n**Requirements**: Your project must have an `index.html` in the root directory.\n\n**What the script does**:\n- Installs bundling dependencies (parcel, @parcel/config-default, parcel-resolver-tspaths, html-inline)\n- Creates `.parcelrc` config with path alias support\n- Builds with Parcel (no source maps)\n- Inlines all assets into single HTML using html-inline\n\n### Step 4: Share Artifact with User\n\nFinally, share the bundled HTML file in conversation with the user so they can view it as an artifact.\n\n### Step 5: Testing/Visualizing the Artifact (Optional)\n\nNote: This is a completely optional step. Only perform if necessary or requested.\n\nTo test/visualize the artifact, use available tools (including other Skills or built-in tools like Playwright or Puppeteer). In general, avoid testing the artifact upfront as it adds latency between the request and when the finished artifact can be seen. Test later, after presenting the artifact, if requested or if issues arise.\n\n## Reference\n\n- **shadcn/ui components**: https://ui.shadcn.com/docs/components","schemaVersion":1},"repoUrl":"https://github.com/Prat011/awesome-llm-skills/tree/master/artifacts-builder","tags":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"awesome-llm-skills","audit":{"files":["slack-gif-creator/requirements.txt"],"binaries":[],"findings":[{"kind":"dependency","rule":"DP-04","message":"Python dependencies are not pinned and there is no lock file.","surface":"slack-gif-creator/requirements.txt","evidence":"pillow>=10.0.0, imageio>=2.31.0, imageio-ffmpeg>=0.4.9, numpy>=1.24.0","severity":"medium"}],"packages":4,"auditedAt":"2026-09-25T11:52:30.068Z","lockfiles":[]},"forks":313,"owner":"Prat011","stars":1761,"topics":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms","openai","opencode","qwen","qwen-coder","skills"],"license":"Complete terms in LICENSE.txt","fullName":"Prat011/awesome-llm-skills","homepage":null,"language":"Python","pushedAt":"2026-07-14T09:53:56Z","avatarUrl":"https://avatars.githubusercontent.com/u/67639393?v=4","crawledAt":"2026-09-25T11:52:22.319Z","openIssues":170,"manifestFile":"SKILL.md","manifestPath":"artifacts-builder/SKILL.md","defaultBranch":"master"},"readme":"# Artifacts Builder\n\nTo build powerful frontend claude.ai artifacts, follow these steps:\n1. Initialize the frontend repo using `scripts/init-artifact.sh`\n2. Develop your artifact by editing the generated code\n3. Bundle all code into a single HTML file using `scripts/bundle-artifact.sh`\n4. Display artifact to user\n5. (Optional) Test the artifact\n\n**Stack**: React 18 + TypeScript + Vite + Parcel (bundling) + Tailwind CSS + shadcn/ui\n\n## Design & Style Guidelines\n\nVERY IMPORTANT: To avoid what is often referred to as \"AI slop\", avoid using excessive centered layouts, purple gradients, uniform rounded corners, and Inter font.\n\n## Quick Start\n\n### Step 1: Initialize Project\n\nRun the initialization script to create a new React project:\n```bash\nbash scripts/init-artifact.sh \ncd \n```\n\nThis creates a fully configured project with:\n- โœ… React + TypeScript (via Vite)\n- โœ… Tailwind CSS 3.4.1 with shadcn/ui theming system\n- โœ… Path aliases (`@/`) configured\n- โœ… 40+ shadcn/ui components pre-installed\n- โœ… All Radix UI dependencies included\n- โœ… Parcel configured for bundling (via .parcelrc)\n- โœ… Node 18+ compatibility (auto-detects and pins Vite version)\n\n### Step 2: Develop Your Artifact\n\nTo build the artifact, edit the generated files. See **Common Development Tasks** below for guidance.\n\n### Step 3: Bundle to Single HTML File\n\nTo bundle the React app into a single HTML artifact:\n```bash\nbash scripts/bundle-artifact.sh\n```\n\nThis creates `bundle.html` - a self-contained artifact with all JavaScript, CSS, and dependencies inlined. This file can be directly shared in Claude conversations as an artifact.\n\n**Requirements**: Your project must have an `index.html` in the root directory.\n\n**What the script does**:\n- Installs bundling dependencies (parcel, @parcel/config-default, parcel-resolver-tspaths, html-inline)\n- Creates `.parcelrc` config with path alias support\n- Builds with Parcel (no source maps)\n- Inlines all assets into single HTML using html-inline\n\n### Step 4: Share Artifact with User\n\nFinally, share the bundled HTML file in conversation with the user so they can view it as an artifact.\n\n### Step 5: Testing/Visualizing the Artifact (Optional)\n\nNote: This is a completely optional step. Only perform if necessary or requested.\n\nTo test/visualize the artifact, use available tools (including other Skills or built-in tools like Playwright or Puppeteer). In general, avoid testing the artifact upfront as it adds latency between the request and when the finished artifact can be seen. Test later, after presenting the artifact, if requested or if issues arise.\n\n## Reference\n\n- **shadcn/ui components**: https://ui.shadcn.com/docs/components","createdAt":"2026-09-25T11:52:30.126Z","updatedAt":"2026-09-25T11:52:30.126Z"},{"id":"cmugwii890252qu06d8zrcffe","slug":"prat011-awesome-llm-skills-canvas-design","name":"canvas-design","description":"Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.","authorId":"gh:prat011","authorName":"Prat011","version":"0.1.0","category":"Prompt","securityLevel":"Community","downloadsCount":0,"githubStars":1761,"pricePerCall":0,"manifest":{"name":"canvas-design","tools":[],"category":"Prompt","entrypoint":{"type":"prompt"},"description":"Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.","permissions":[],"systemPrompt":"These are instructions for creating design philosophies - aesthetic movements that are then EXPRESSED VISUALLY. Output only .md files, .pdf files, and .png files.\n\nComplete this in two steps:\n1. Design Philosophy Creation (.md file)\n2. Express by creating it on a canvas (.pdf file or .png file)\n\nFirst, undertake this task:\n\n## DESIGN PHILOSOPHY CREATION\n\nTo begin, create a VISUAL PHILOSOPHY (not layouts or templates) that will be interpreted through:\n- Form, space, color, composition\n- Images, graphics, shapes, patterns\n- Minimal text as visual accent\n\n### THE CRITICAL UNDERSTANDING\n- What is received: Some subtle input or instructions by the user that should be taken into account, but used as a foundation; it should not constrain creative freedom.\n- What is created: A design philosophy/aesthetic movement.\n- What happens next: Then, the same version receives the philosophy and EXPRESSES IT VISUALLY - creating artifacts that are 90% visual design, 10% essential text.\n\nConsider this approach:\n- Write a manifesto for an art movement\n- The next phase involves making the artwork\n\nThe philosophy must emphasize: Visual expression. Spatial communication. Artistic interpretation. Minimal words.\n\n### HOW TO GENERATE A VISUAL PHILOSOPHY\n\n**Name the movement** (1-2 words): \"Brutalist Joy\" / \"Chromatic Silence\" / \"Metabolist Dreams\"\n\n**Articulate the philosophy** (4-6 paragraphs - concise but complete):\n\nTo capture the VISUAL essence, express how the philosophy manifests through:\n- Space and form\n- Color and material\n- Scale and rhythm\n- Composition and balance\n- Visual hierarchy\n\n**CRITICAL GUIDELINES:**\n- **Avoid redundancy**: Each design aspect should be mentioned once. Avoid repeating points about color theory, spatial relationships, or typographic principles unless adding new depth.\n- **Emphasize craftsmanship REPEATEDLY**: The philosophy MUST stress multiple times that the final work should appear as though it took countless hours to create, was labored over with care, and comes from someone at the absolute top of their field. This framing is essential - repeat phrases like \"meticulously crafted,\" \"the product of deep expertise,\" \"painstaking attention,\" \"master-level execution.\"\n- **Leave creative space**: Remain specific about the aesthetic direction, but concise enough that the next Claude has room to make interpretive choices also at a extremely high level of craftmanship.\n\nThe philosophy must guide the next version to express ideas VISUALLY, not through text. Information lives in design, not paragraphs.\n\n### PHILOSOPHY EXAMPLES\n\n**\"Concrete Poetry\"**\nPhilosophy: Communication through monumental form and bold geometry.\nVisual expression: Massive color blocks, sculptural typography (huge single words, tiny labels), Brutalist spatial divisions, Polish poster energy meets Le Corbusier. Ideas expressed through visual weight and spatial tension, not explanation. Text as rare, powerful gesture - never paragraphs, only essential words integrated into the visual architecture. Every element placed with the precision of a master craftsman.\n\n**\"Chromatic Language\"**\nPhilosophy: Color as the primary information system.\nVisual expression: Geometric precision where color zones create meaning. Typography minimal - small sans-serif labels letting chromatic fields communicate. Think Josef Albers' interaction meets data visualization. Information encoded spatially and chromatically. Words only to anchor what color already shows. The result of painstaking chromatic calibration.\n\n**\"Analog Meditation\"**\nPhilosophy: Quiet visual contemplation through texture and breathing room.\nVisual expression: Paper grain, ink bleeds, vast negative space. Photography and illustration dominate. Typography whispered (small, restrained, serving the visual). Japanese photobook aesthetic. Images breathe across pages. Text appears sparingly - short phrases, never explanatory blocks. Each composition balanced with the care of a meditation practice.\n\n**\"Organic Systems\"**\nPhilosophy: Natural clustering and modular growth patterns.\nVisual expression: Rounded forms, organic arrangements, color from nature through architecture. Information shown through visual diagrams, spatial relationships, iconography. Text only for key labels floating in space. The composition tells the story through expert spatial orchestration.\n\n**\"Geometric Silence\"**\nPhilosophy: Pure order and restraint.\nVisual expression: Grid-based precision, bold photography or stark graphics, dramatic negative space. Typography precise but minimal - small essential text, large quiet zones. Swiss formalism meets Brutalist material honesty. Structure communicates, not words. Every alignment the work of countless refinements.\n\n*These are condensed examples. The actual design philosophy should be 4-6 substantial paragraphs.*\n\n### ESSENTIAL PRINCIPLES\n- **VISUAL PHILOSOPHY**: Create an aesthetic worldview to be expressed through design\n- **MINIMAL TEXT**: Always emphasize that text is sparse, essential-only, integrated as visual element - never lengthy\n- **SPATIAL EXPRESSION**: Ideas communicate through space, form, color, composition - not paragraphs\n- **ARTISTIC FREEDOM**: The next Claude interprets the philosophy visually - provide creative room\n- **PURE DESIGN**: This is about making ART OBJECTS, not documents with decoration\n- **EXPERT CRAFTSMANSHIP**: Repeatedly emphasize the final work must look meticulously crafted, labored over with care, the product of countless hours by someone at the top of their field\n\n**The design philosophy should be 4-6 paragraphs long.** Fill it with poetic design philosophy that brings together the core vision. Avoid repeating the same points. Keep the design philosophy generic without mentioning the intention of the art, as if it can be used wherever. Output the design philosophy as a .md file.\n\n---\n\n## DEDUCING THE SUBTLE REFERENCE\n\n**CRITICAL STEP**: Before creating the canvas, identify the subtle conceptual thread from the original request.\n\n**THE ESSENTIAL PRINCIPLE**:\nThe topic is a **subtle, niche reference embedded within the art itself** - not always literal, always sophisticated. Someone familiar with the subject should feel it intuitively, while others simply experience a masterful abstract composition. The design philosophy provides the aesthetic language. The deduced topic provides the soul - the quiet conceptual DNA woven invisibly into form, color, and composition.\n\nThis is **VERY IMPORTANT**: The reference must be refined so it enhances the work's depth without announcing itself. Think like a jazz musician quoting another song - only those who know will catch it, but everyone appreciates the music.\n\n---\n\n## CANVAS CREATION\n\nWith both the philosophy and the conceptual framework established, express it on a canvas. Take a moment to gather thoughts and clear the mind. Use the design philosophy created and the instructions below to craft a masterpiece, embodying all aspects of the philosophy with expert craftsmanship.\n\n**IMPORTANT**: For any type of content, even if the user requests something for a movie/game/book, the approach should still be sophisticated. Never lose sight of the idea that this should be art, not something that's cartoony or amateur.\n\nTo create museum or magazine quality work, use the design philosophy as the foundation. Create one single page, highly visual, design-forward PDF or PNG output (unless asked for more pages). Generally use repeating patterns and perfect shapes. Treat the abstract philosophical design as if it were a scientific bible, borrowing the visual language of systematic observationโ€”dense accumulation of marks, repeated elements, or layered patterns that build meaning through patient repetition and reward sustained viewing. Add sparse, clinical typography and systematic reference markers that suggest this could be a diagram from an imaginary discipline, treating the invisible subject with the same reverence typically reserved for documenting observable phenomena. Anchor the piece with simple phrase(s) or details positioned subtly, using a limited color palette that feels intentional and cohesive. Embrace the paradox of using analytical visual language to express ideas about human experience: the result should feel like an artifact that proves something ephemeral can be studied, mapped, and understood through careful attention. This is true art. \n\n**Text as a contextual element**: Text is always minimal and visual-first, but let context guide whether that means whisper-quiet labels or bold typographic gestures. A punk venue poster might have larger, more aggressive type than a minimalist ceramics studio identity. Most of the time, font should be thin. All use of fonts must be design-forward and prioritize visual communication. Regardless of text scale, nothing falls off the page and nothing overlaps. Every element must be contained within the canvas boundaries with proper margins. Check carefully that all text, graphics, and visual elements have breathing room and clear separation. This is non-negotiable for professional execution. **IMPORTANT: Use different fonts if writing text. Search the `./canvas-fonts` directory. Regardless of approach, sophistication is non-negotiable.**\n\nDownload and use whatever fonts are needed to make this a reality. Get creative by making the typography actually part of the art itself -- if the art is abstract, bring the font onto the canvas, not typeset digitally.\n\nTo push boundaries, follow design instinct/intuition while using the philosophy as a guiding principle. Embrace ultimate design freedom and choice. Push aesthetics and design to the frontier. \n\n**CRITICAL**: To achieve human-crafted quality (not AI-generated), create work that looks like it took countless hours. Make it appear as though someone at the absolute top of their field labored over every detail with painstaking care. Ensure the composition, spacing, color choices, typography - everything screams expert-level craftsmanship. Double-check that nothing overlaps, formatting is flawless, every detail perfect. Create something that could be shown to people to prove expertise and rank as undeniably impressive.\n\nOutput the final result as a single, downloadable .pdf or .png file, alongside the design philosophy used as a .md file.\n\n---\n\n## FINAL STEP\n\n**IMPORTANT**: The user ALREADY said \"It isn't perfect enough. It must be pristine, a masterpiece if craftsmanship, as if it were about to be displayed in a museum.\"\n\n**CRITICAL**: To refine the work, avoid adding more graphics; instead refine what has been created and make it extremely crisp, respecting the design philosophy and the principles of minimalism entirely. Rather than adding a fun filter or refactoring a font, consider how to make the existing composition more cohesive with the art. If the instinct is to call a new function or draw a new shape, STOP and instead ask: \"How can I make what's already here more of a piece of art?\"\n\nTake a second pass. Go back to the code and refine/polish further to make this a philosophically designed masterpiece.\n\n## MULTI-PAGE OPTION\n\nTo create additional pages when requested, create more creative pages along the same lines as the design philosophy but distinctly different as well. Bundle those pages in the same .pdf or many .pngs. Treat the first page as just a single page in a whole coffee table book waiting to be filled. Make the next pages unique twists and memories of the original. Have them almost tell a story in a very tasteful way. Exercise full creative freedom.","schemaVersion":1},"repoUrl":"https://github.com/Prat011/awesome-llm-skills/tree/master/canvas-design","tags":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"awesome-llm-skills","audit":{"files":["slack-gif-creator/requirements.txt"],"binaries":[],"findings":[{"kind":"dependency","rule":"DP-04","message":"Python dependencies are not pinned and there is no lock file.","surface":"slack-gif-creator/requirements.txt","evidence":"pillow>=10.0.0, imageio>=2.31.0, imageio-ffmpeg>=0.4.9, numpy>=1.24.0","severity":"medium"}],"packages":4,"auditedAt":"2026-09-25T11:52:30.068Z","lockfiles":[]},"forks":313,"owner":"Prat011","stars":1761,"topics":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms","openai","opencode","qwen","qwen-coder","skills"],"license":"Complete terms in LICENSE.txt","fullName":"Prat011/awesome-llm-skills","homepage":null,"language":"Python","pushedAt":"2026-07-14T09:53:56Z","avatarUrl":"https://avatars.githubusercontent.com/u/67639393?v=4","crawledAt":"2026-09-25T11:52:22.319Z","openIssues":170,"manifestFile":"SKILL.md","manifestPath":"canvas-design/SKILL.md","defaultBranch":"master"},"readme":"These are instructions for creating design philosophies - aesthetic movements that are then EXPRESSED VISUALLY. Output only .md files, .pdf files, and .png files.\n\nComplete this in two steps:\n1. Design Philosophy Creation (.md file)\n2. Express by creating it on a canvas (.pdf file or .png file)\n\nFirst, undertake this task:\n\n## DESIGN PHILOSOPHY CREATION\n\nTo begin, create a VISUAL PHILOSOPHY (not layouts or templates) that will be interpreted through:\n- Form, space, color, composition\n- Images, graphics, shapes, patterns\n- Minimal text as visual accent\n\n### THE CRITICAL UNDERSTANDING\n- What is received: Some subtle input or instructions by the user that should be taken into account, but used as a foundation; it should not constrain creative freedom.\n- What is created: A design philosophy/aesthetic movement.\n- What happens next: Then, the same version receives the philosophy and EXPRESSES IT VISUALLY - creating artifacts that are 90% visual design, 10% essential text.\n\nConsider this approach:\n- Write a manifesto for an art movement\n- The next phase involves making the artwork\n\nThe philosophy must emphasize: Visual expression. Spatial communication. Artistic interpretation. Minimal words.\n\n### HOW TO GENERATE A VISUAL PHILOSOPHY\n\n**Name the movement** (1-2 words): \"Brutalist Joy\" / \"Chromatic Silence\" / \"Metabolist Dreams\"\n\n**Articulate the philosophy** (4-6 paragraphs - concise but complete):\n\nTo capture the VISUAL essence, express how the philosophy manifests through:\n- Space and form\n- Color and material\n- Scale and rhythm\n- Composition and balance\n- Visual hierarchy\n\n**CRITICAL GUIDELINES:**\n- **Avoid redundancy**: Each design aspect should be mentioned once. Avoid repeating points about color theory, spatial relationships, or typographic principles unless adding new depth.\n- **Emphasize craftsmanship REPEATEDLY**: The philosophy MUST stress multiple times that the final work should appear as though it took countless hours to create, was labored over with care, and comes from someone at the absolute top of their field. This framing is essential - repeat phrases like \"meticulously crafted,\" \"the product of deep expertise,\" \"painstaking attention,\" \"master-level execution.\"\n- **Leave creative space**: Remain specific about the aesthetic direction, but concise enough that the next Claude has room to make interpretive choices also at a extremely high level of craftmanship.\n\nThe philosophy must guide the next version to express ideas VISUALLY, not through text. Information lives in design, not paragraphs.\n\n### PHILOSOPHY EXAMPLES\n\n**\"Concrete Poetry\"**\nPhilosophy: Communication through monumental form and bold geometry.\nVisual expression: Massive color blocks, sculptural typography (huge single words, tiny labels), Brutalist spatial divisions, Polish poster energy meets Le Corbusier. Ideas expressed through visual weight and spatial tension, not explanation. Text as rare, powerful gesture - never paragraphs, only essential words integrated into the visual architecture. Every element placed with the precision of a master craftsman.\n\n**\"Chromatic Language\"**\nPhilosophy: Color as the primary information system.\nVisual expression: Geometric precision where color zones create meaning. Typography minimal - small sans-serif labels letting chromatic fields communicate. Think Josef Albers' interaction meets data visualization. Information encoded spatially and chromatically. Words only to anchor what color already shows. The result of painstaking chromatic calibration.\n\n**\"Analog Meditation\"**\nPhilosophy: Quiet visual contemplation through texture and breathing room.\nVisual expression: Paper grain, ink bleeds, vast negative space. Photography and illustration dominate. Typography whispered (small, restrained, serving the visual). Japanese photobook aesthetic. Images breathe across pages. Text appears sparingly - short phrases, never explanatory blocks. Each composition balanced with the care of a meditation practice.\n\n**\"Organic Systems\"**","createdAt":"2026-09-25T11:52:30.154Z","updatedAt":"2026-09-25T11:52:30.154Z"},{"id":"cmugwii8n0258qu06v41wbvaa","slug":"prat011-awesome-llm-skills-changelog-generator","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.","authorId":"gh:prat011","authorName":"Prat011","version":"0.1.0","category":"Prompt","securityLevel":"Community","downloadsCount":0,"githubStars":1761,"pricePerCall":0,"manifest":{"name":"changelog-generator","tools":[],"category":"Prompt","entrypoint":{"type":"prompt"},"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.","permissions":[],"systemPrompt":"# Changelog Generator\n\nThis skill transforms technical git commits into polished, user-friendly changelogs that your customers and users will actually understand and appreciate.\n\n## When to Use This Skill\n\n- Preparing release notes for a new version\n- Creating weekly or monthly product update summaries\n- Documenting changes for customers\n- Writing changelog entries for app store submissions\n- Generating update notifications\n- Creating internal release documentation\n- Maintaining a public changelog/product updates page\n\n## What This Skill Does\n\n1. **Scans Git History**: Analyzes commits from a specific time period or between versions\n2. **Categorizes Changes**: Groups commits into logical categories (features, improvements, bug fixes, breaking changes, security)\n3. **Translates Technical โ†’ User-Friendly**: Converts developer commits into customer language\n4. **Formats Professionally**: Creates clean, structured changelog entries\n5. **Filters Noise**: Excludes internal commits (refactoring, tests, etc.)\n6. **Follows Best Practices**: Applies changelog guidelines and your brand voice\n\n## How to Use\n\n### Basic Usage\n\nFrom your project repository:\n\n```\nCreate a changelog from commits since last release\n```\n\n```\nGenerate changelog for all commits from the past week\n```\n\n```\nCreate release notes for version 2.5.0\n```\n\n### With Specific Date Range\n\n```\nCreate a changelog for all commits between March 1 and March 15\n```\n\n### With Custom Guidelines\n\n```\nCreate a changelog for commits since v2.4.0, using my changelog \nguidelines from CHANGELOG_STYLE.md\n```\n\n## Example\n\n**User**: \"Create a changelog for commits from the past 7 days\"\n\n**Output**:\n```markdown\n# Updates - Week of March 10, 2024\n\n## โœจ New Features\n\n- **Team Workspaces**: Create separate workspaces for different \n projects. Invite team members and keep everything organized.\n\n- **Keyboard Shortcuts**: Press ? to see all available shortcuts. \n Navigate faster without touching your mouse.\n\n## ๐Ÿ”ง Improvements\n\n- **Faster Sync**: Files now sync 2x faster across devices\n- **Better Search**: Search now includes file contents, not just titles\n\n## ๐Ÿ› Fixes\n\n- Fixed issue where large images wouldn't upload\n- Resolved timezone confusion in scheduled posts\n- Corrected notification badge count\n```\n\n**Inspired by:** Manik Aggarwal's use case from Lenny's Newsletter\n\n## Tips\n\n- Run from your git repository root\n- Specify date ranges for focused changelogs\n- Use your CHANGELOG_STYLE.md for consistent formatting\n- Review and adjust the generated changelog before publishing\n- Save output directly to CHANGELOG.md\n\n## Related Use Cases\n\n- Creating GitHub release notes\n- Writing app store update descriptions\n- Generating email updates for users\n- Creating social media announcement posts","schemaVersion":1},"repoUrl":"https://github.com/Prat011/awesome-llm-skills/tree/master/changelog-generator","tags":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"awesome-llm-skills","audit":{"files":["slack-gif-creator/requirements.txt"],"binaries":[],"findings":[{"kind":"dependency","rule":"DP-04","message":"Python dependencies are not pinned and there is no lock file.","surface":"slack-gif-creator/requirements.txt","evidence":"pillow>=10.0.0, imageio>=2.31.0, imageio-ffmpeg>=0.4.9, numpy>=1.24.0","severity":"medium"}],"packages":4,"auditedAt":"2026-09-25T11:52:30.068Z","lockfiles":[]},"forks":313,"owner":"Prat011","stars":1761,"topics":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms","openai","opencode","qwen","qwen-coder","skills"],"license":null,"fullName":"Prat011/awesome-llm-skills","homepage":null,"language":"Python","pushedAt":"2026-07-14T09:53:56Z","avatarUrl":"https://avatars.githubusercontent.com/u/67639393?v=4","crawledAt":"2026-09-25T11:52:22.319Z","openIssues":170,"manifestFile":"SKILL.md","manifestPath":"changelog-generator/SKILL.md","defaultBranch":"master"},"readme":"# Changelog Generator\n\nThis skill transforms technical git commits into polished, user-friendly changelogs that your customers and users will actually understand and appreciate.\n\n## When to Use This Skill\n\n- Preparing release notes for a new version\n- Creating weekly or monthly product update summaries\n- Documenting changes for customers\n- Writing changelog entries for app store submissions\n- Generating update notifications\n- Creating internal release documentation\n- Maintaining a public changelog/product updates page\n\n## What This Skill Does\n\n1. **Scans Git History**: Analyzes commits from a specific time period or between versions\n2. **Categorizes Changes**: Groups commits into logical categories (features, improvements, bug fixes, breaking changes, security)\n3. **Translates Technical โ†’ User-Friendly**: Converts developer commits into customer language\n4. **Formats Professionally**: Creates clean, structured changelog entries\n5. **Filters Noise**: Excludes internal commits (refactoring, tests, etc.)\n6. **Follows Best Practices**: Applies changelog guidelines and your brand voice\n\n## How to Use\n\n### Basic Usage\n\nFrom your project repository:\n\n```\nCreate a changelog from commits since last release\n```\n\n```\nGenerate changelog for all commits from the past week\n```\n\n```\nCreate release notes for version 2.5.0\n```\n\n### With Specific Date Range\n\n```\nCreate a changelog for all commits between March 1 and March 15\n```\n\n### With Custom Guidelines\n\n```\nCreate a changelog for commits since v2.4.0, using my changelog \nguidelines from CHANGELOG_STYLE.md\n```\n\n## Example\n\n**User**: \"Create a changelog for commits from the past 7 days\"\n\n**Output**:\n```markdown\n# Updates - Week of March 10, 2024\n\n## โœจ New Features\n\n- **Team Workspaces**: Create separate workspaces for different \n projects. Invite team members and keep everything organized.\n\n- **Keyboard Shortcuts**: Press ? to see all available shortcuts. \n Navigate faster without touching your mouse.\n\n## ๐Ÿ”ง Improvements\n\n- **Faster Sync**: Files now sync 2x faster across devices\n- **Better Search**: Search now includes file contents, not just titles\n\n## ๐Ÿ› Fixes\n\n- Fixed issue where large images wouldn't upload\n- Resolved timezone confusion in scheduled posts\n- Corrected notification badge count\n```\n\n**Inspired by:** Manik Aggarwal's use case from Lenny's Newsletter\n\n## Tips\n\n- Run from your git repository root\n- Specify date ranges for focused changelogs\n- Use your CHANGELOG_STYLE.md for consistent formatting\n- Review and adjust the generated changelog before publishing\n- Save output directly to CHANGELOG.md\n\n## Related Use Cases\n\n- Creating GitHub release notes\n- Writing app store update descriptions\n- Generating email updates for users\n- Creating social media announcement posts","createdAt":"2026-09-25T11:52:30.167Z","updatedAt":"2026-09-25T11:52:30.167Z"},{"id":"cmugwii91025equ06hwlnm0b9","slug":"prat011-awesome-llm-skills-competitive-ads-extractor","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.","authorId":"gh:prat011","authorName":"Prat011","version":"0.1.0","category":"Prompt","securityLevel":"Community","downloadsCount":0,"githubStars":1761,"pricePerCall":0,"manifest":{"name":"competitive-ads-extractor","tools":[],"category":"Prompt","entrypoint":{"type":"prompt"},"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.","permissions":[],"systemPrompt":"# Competitive Ads Extractor\n\nThis 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.\n\n## When to Use This Skill\n\n- Researching competitor ad strategies\n- Finding inspiration for your own ads\n- Understanding market positioning\n- Identifying successful ad patterns\n- Analyzing messaging that works\n- Discovering new use cases or pain points\n- Planning ad campaigns with proven concepts\n\n## What This Skill Does\n\n1. **Extracts Ads**: Scrapes ads from Facebook Ad Library, LinkedIn, etc.\n2. **Captures Screenshots**: Saves visual copies of all ads\n3. **Analyzes Messaging**: Identifies problems, use cases, and value props\n4. **Categorizes Ads**: Groups by theme, audience, or format\n5. **Identifies Patterns**: Finds common successful approaches\n6. **Provides Insights**: Explains why certain ads likely perform well\n\n## How to Use\n\n### Basic Extraction\n\n```\nExtract all current ads from [Competitor Name] on Facebook Ad Library\n```\n\n```\nScrape ads from [Company] and analyze their messaging\n```\n\n### Specific Analysis\n\n```\nGet all ads from [Competitor] focusing on their messaging \nabout [specific problem]. What pain points are they highlighting?\n```\n\n### Competitive Set\n\n```\nExtract ads from these 5 competitors: [list]. \nCompare their approaches and tell me what's working.\n```\n\n### Specific Platform\n\n```\nGet LinkedIn ads from [Competitor] and analyze their \nB2B positioning strategy\n```\n\n## Example\n\n**User**: \"Extract ads from Notion on Facebook Ad Library and tell me what messaging is working for them.\"\n\n**Process**:\n```\nAccessing Facebook Ad Library...\nSearching for: Notion\nFound: 23 active ads\n\nExtracting screenshots...\n[โ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆ] 100%\n\nSaved to: competitor-ads/notion/\n- ad-001-collaboration.png\n- ad-002-productivity.png\n- ad-003-templates.png\n...\n\nAnalyzing messaging...\n```\n\n**Output**:\n```\n# Notion Ad Analysis\n\n## Overview\n- Total Ads: 23 active\n- Primary Themes: Productivity (35%), Collaboration (30%), \n Templates (20%), AI Features (15%)\n- Ad Formats: Static images (60%), Video (40%)\n- CTA Patterns: \"Try for free\", \"Get started\"\n\n## Key Problems They're Highlighting\n\n1. **Scattered Information** (8 ads)\n Copy: \"Stop switching between 10 different tools\"\n Why it works: Direct pain point many teams face\n\n2. **Meeting Overload** (5 ads)\n Copy: \"Replace unnecessary meetings with async updates\"\n Why it works: Post-COVID remote work pain point\n\n3. **Lost Documentation** (4 ads)\n Copy: \"Never ask 'where is that doc?' again\"\n Why it works: Universal workplace frustration\n\n## Successful Creative Patterns\n\n### Pattern 1: Before/After Split\n- Shows chaotic tool landscape โ†’ Clean Notion workspace\n- Used in 6 high-performing ads\n- Visual metaphor is immediately clear\n\n### Pattern 2: Feature Showcase\n- GIF of actual product usage\n- Shows specific feature in 5 seconds\n- Used for new features (AI, templates)\n\n### Pattern 3: Social Proof\n- \"Join 20M users\" messaging\n- Customer logos\n- Used in 4 ads targeting enterprise\n\n## Copy That's Working\n\nBest Headlines:\n1. \"Your team's knowledge, finally in one place\"\n โ†’ Benefit-focused, addresses pain directly\n \n2. \"The all-in-one workspace\"\n โ†’ Clear positioning, broad appeal\n \n3. \"AI that actually helps you work\"\n โ†’ Addresses AI skepticism, practical angle\n\nBest Body Copy Patterns:\n- Short sentences (under 10 words)\n- Focus on outcomes not features\n- Include specific numbers (\"Cut meetings by 50%\")\n\n## Audience Targeting Insights\n\nBased on ad variations:\n- Startup founders: Solo productivity angle\n- Team leads: Collaboration and alignment\n- Enterprise: Security and compliance mentions\n- Students: Free plan, templates, organization\n\n## Recommendations for Your Ads\n\n1. **Test the \"tool sprawl\" pain point**\n โ†’ Strong resonance based on their ad frequency\n\n2. **Use product screenshots over abstract visuals**\n โ†’ All their top ads show actual UI\n\n3. **Lead with the problem, not the solution**\n โ†’ \"Tired of X?\" performs better than \"Introducing Y\"\n\n4. **Keep copy under 100 characters**\n โ†’ Their shortest ads seem most frequent\n\n5. **Test before/after visual formats**\n โ†’ Proven pattern in their creative\n\n## Files Saved\n- All ads: ~/competitor-ads/notion/\n- Analysis: ~/competitor-ads/notion/analysis.md\n- Best performers: ~/competitor-ads/notion/top-10/\n```\n\n**Inspired by:** Sumant Subrahmanya's use case from Lenny's Newsletter\n\n## What You Can Learn\n\n### Messaging Analysis\n- What problems they emphasize\n- How they position against competition\n- Value propositions that resonate\n- Target audience segments\n\n### Creative Patterns\n- Visual styles that work\n- Video vs. static image performance\n- Color schemes and branding\n- Layout patterns\n\n### Copy Formulas\n- Headline structures\n- Call-to-action patterns\n- Length and tone\n- Emotional triggers\n\n### Campaign Strategy\n- Seasonal campaigns\n- Product launch approaches\n- Feature announcement tactics\n- Retargeting patterns\n\n## Best Practices\n\n### Legal & Ethical\nโœ“ Only use for research and inspiration\nโœ“ Don't copy ads directly\nโœ“ Respect intellectual property\nโœ“ Use insights to inform original creative\nโœ— Don't plagiarize copy or steal designs\n\n### Analysis Tips\n1. **Look for patterns**: What themes repeat?\n2. **Track over time**: Save ads monthly to see evolution\n3. **Test hypotheses**: Adapt successful patterns for your brand\n4. **Segment by audience**: Different messages for different targets\n5. **Compare platforms**: LinkedIn vs Facebook messaging differs\n\n## Advanced Features\n\n### Trend Tracking\n```\nCompare [Competitor]'s ads from Q1 vs Q2. \nWhat messaging has changed?\n```\n\n### Multi-Competitor Analysis\n```\nExtract ads from [Company A], [Company B], [Company C]. \nWhat are the common patterns? Where do they differ?\n```\n\n### Industry Benchmarks\n```\nShow me ad patterns across the top 10 project management \ntools. What problems do they all focus on?\n```\n\n### Format Analysis\n```\nAnalyze video ads vs static image ads from [Competitor]. \nWhich gets more engagement? (if data available)\n```\n\n## Common Workflows\n\n### Ad Campaign Planning\n1. Extract competitor ads\n2. Identify successful patterns\n3. Note gaps in their messaging\n4. Brainstorm unique angles\n5. Draft test ad variations\n\n### Positioning Research\n1. Get ads from 5 competitors\n2. Map their positioning\n3. Find underserved angles\n4. Develop differentiated messaging\n5. Test against their approaches\n\n### Creative Inspiration\n1. Extract ads by theme\n2. Analyze visual patterns\n3. Note color and layout trends\n4. Adapt successful patterns\n5. Create original variations\n\n## Tips for Success\n\n1. **Regular Monitoring**: Check monthly for changes\n2. **Broad Research**: Look at adjacent competitors too\n3. **Save Everything**: Build a reference library\n4. **Test Insights**: Run your own experiments\n5. **Track Performance**: A/B test inspired concepts\n6. **Stay Original**: Use for inspiration, not copying\n7. **Multiple Platforms**: Compare Facebook, LinkedIn, TikTok, etc.\n\n## Output Formats\n\n- **Screenshots**: All ads saved as images\n- **Analysis Report**: Markdown summary of insights\n- **Spreadsheet**: CSV with ad copy, CTAs, themes\n- **Presentation**: Visual deck of top performers\n- **Pattern Library**: Categorized by approach\n\n## Related Use Cases\n\n- Writing better ad copy for your campaigns\n- Understanding market positioning\n- Finding content gaps in your messaging\n- Discovering new use cases for your product\n- Planning product marketing strategy\n- Inspiring social media content","schemaVersion":1},"repoUrl":"https://github.com/Prat011/awesome-llm-skills/tree/master/competitive-ads-extractor","tags":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"awesome-llm-skills","audit":{"files":["slack-gif-creator/requirements.txt"],"binaries":[],"findings":[{"kind":"dependency","rule":"DP-04","message":"Python dependencies are not pinned and there is no lock file.","surface":"slack-gif-creator/requirements.txt","evidence":"pillow>=10.0.0, imageio>=2.31.0, imageio-ffmpeg>=0.4.9, numpy>=1.24.0","severity":"medium"}],"packages":4,"auditedAt":"2026-09-25T11:52:30.068Z","lockfiles":[]},"forks":313,"owner":"Prat011","stars":1761,"topics":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms","openai","opencode","qwen","qwen-coder","skills"],"license":null,"fullName":"Prat011/awesome-llm-skills","homepage":null,"language":"Python","pushedAt":"2026-07-14T09:53:56Z","avatarUrl":"https://avatars.githubusercontent.com/u/67639393?v=4","crawledAt":"2026-09-25T11:52:22.319Z","openIssues":170,"manifestFile":"SKILL.md","manifestPath":"competitive-ads-extractor/SKILL.md","defaultBranch":"master"},"readme":"# Competitive Ads Extractor\n\nThis 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.\n\n## When to Use This Skill\n\n- Researching competitor ad strategies\n- Finding inspiration for your own ads\n- Understanding market positioning\n- Identifying successful ad patterns\n- Analyzing messaging that works\n- Discovering new use cases or pain points\n- Planning ad campaigns with proven concepts\n\n## What This Skill Does\n\n1. **Extracts Ads**: Scrapes ads from Facebook Ad Library, LinkedIn, etc.\n2. **Captures Screenshots**: Saves visual copies of all ads\n3. **Analyzes Messaging**: Identifies problems, use cases, and value props\n4. **Categorizes Ads**: Groups by theme, audience, or format\n5. **Identifies Patterns**: Finds common successful approaches\n6. **Provides Insights**: Explains why certain ads likely perform well\n\n## How to Use\n\n### Basic Extraction\n\n```\nExtract all current ads from [Competitor Name] on Facebook Ad Library\n```\n\n```\nScrape ads from [Company] and analyze their messaging\n```\n\n### Specific Analysis\n\n```\nGet all ads from [Competitor] focusing on their messaging \nabout [specific problem]. What pain points are they highlighting?\n```\n\n### Competitive Set\n\n```\nExtract ads from these 5 competitors: [list]. \nCompare their approaches and tell me what's working.\n```\n\n### Specific Platform\n\n```\nGet LinkedIn ads from [Competitor] and analyze their \nB2B positioning strategy\n```\n\n## Example\n\n**User**: \"Extract ads from Notion on Facebook Ad Library and tell me what messaging is working for them.\"\n\n**Process**:\n```\nAccessing Facebook Ad Library...\nSearching for: Notion\nFound: 23 active ads\n\nExtracting screenshots...\n[โ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆโ–ˆ] 100%\n\nSaved to: competitor-ads/notion/\n- ad-001-collaboration.png\n- ad-002-productivity.png\n- ad-003-templates.png\n...\n\nAnalyzing messaging...\n```\n\n**Output**:\n```\n# Notion Ad Analysis\n\n## Overview\n- Total Ads: 23 active\n- Primary Themes: Productivity (35%), Collaboration (30%), \n Templates (20%), AI Features (15%)\n- Ad Formats: Static images (60%), Video (40%)\n- CTA Patterns: \"Try for free\", \"Get started\"\n\n## Key Problems They're Highlighting\n\n1. **Scattered Information** (8 ads)\n Copy: \"Stop switching between 10 different tools\"\n Why it works: Direct pain point many teams face\n\n2. **Meeting Overload** (5 ads)\n Copy: \"Replace unnecessary meetings with async updates\"\n Why it works: Post-COVID remote work pain point\n\n3. **Lost Documentation** (4 ads)\n Copy: \"Never ask 'where is that doc?' again\"\n Why it works: Universal workplace frustration\n\n## Successful Creative Patterns\n\n### Pattern 1: Before/After Split\n- Shows chaotic tool landscape โ†’ Clean Notion workspace\n- Used in 6 high-performing ads\n- Visual metaphor is immediately clear\n\n### Pattern 2: Feature Showcase\n- GIF of actual product usage\n- Shows specific feature in 5 seconds\n- Used for new features (AI, templates)\n\n### Pattern 3: Social Proof\n- \"Join 20M users\" messaging\n- Customer logos\n- Used in 4 ads targeting enterprise\n\n## Copy That's Working\n\nBest Headlines:\n1. \"Your team's knowledge, finally in one place\"\n โ†’ Benefit-focused, addresses pain directly\n \n2. \"The all-in-one workspace\"\n โ†’ Clear positioning, broad appeal\n \n3. \"AI that actually helps you work\"\n โ†’ Addresses AI skepticism, practical angle\n\nBest Body Copy Patterns:\n- Short sentences (under 10 words)\n- Focus on outcomes not features\n- Include specific numbers (\"Cut meetings by 50%\")\n\n## Audience Targeting Insights\n\nBased on ad variations:\n- Startup founders: Solo productivity angle\n- Team leads: Collaboration and alignment\n- Enterprise: Security and compliance mentions\n- Students: Free plan, templates, organization\n\n## Recommendations for Your Ads\n\n1. **Test the \"tool sprawl\" pain point**\n โ†’ Strong resonance based on their ad frequency\n\n2. **Use product screenshots over abstract visuals**\n โ†’ All their top ads show actual UI\n\n3. *","createdAt":"2026-09-25T11:52:30.181Z","updatedAt":"2026-09-25T11:52:30.181Z"},{"id":"cmugwii9f025kqu064i66pgc1","slug":"prat011-awesome-llm-skills-content-research-writer","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.","authorId":"gh:prat011","authorName":"Prat011","version":"0.1.0","category":"Prompt","securityLevel":"Community","downloadsCount":0,"githubStars":1761,"pricePerCall":0,"manifest":{"name":"content-research-writer","tools":[],"category":"Prompt","entrypoint":{"type":"prompt"},"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.","permissions":[],"systemPrompt":"# Content Research Writer\n\nThis skill acts as your writing partner, helping you research, outline, draft, and refine content while maintaining your unique voice and style.\n\n## When to Use This Skill\n\n- Writing blog posts, articles, or newsletters\n- Creating educational content or tutorials\n- Drafting thought leadership pieces\n- Researching and writing case studies\n- Producing technical documentation with sources\n- Writing with proper citations and references\n- Improving hooks and introductions\n- Getting section-by-section feedback while writing\n\n## What This Skill Does\n\n1. **Collaborative Outlining**: Helps you structure ideas into coherent outlines\n2. **Research Assistance**: Finds relevant information and adds citations\n3. **Hook Improvement**: Strengthens your opening to capture attention\n4. **Section Feedback**: Reviews each section as you write\n5. **Voice Preservation**: Maintains your writing style and tone\n6. **Citation Management**: Adds and formats references properly\n7. **Iterative Refinement**: Helps you improve through multiple drafts\n\n## How to Use\n\n### Setup Your Writing Environment\n\nCreate a dedicated folder for your article:\n```\nmkdir ~/writing/my-article-title\ncd ~/writing/my-article-title\n```\n\nCreate your draft file:\n```\ntouch article-draft.md\n```\n\nOpen Claude Code from this directory and start writing.\n\n### Basic Workflow\n\n1. **Start with an outline**:\n```\nHelp me create an outline for an article about [topic]\n```\n\n2. **Research and add citations**:\n```\nResearch [specific topic] and add citations to my outline\n```\n\n3. **Improve the hook**:\n```\nHere's my introduction. Help me make the hook more compelling.\n```\n\n4. **Get section feedback**:\n```\nI just finished the \"Why This Matters\" section. Review it and give feedback.\n```\n\n5. **Refine and polish**:\n```\nReview the full draft for flow, clarity, and consistency.\n```\n\n## Instructions\n\nWhen a user requests writing assistance:\n\n1. **Understand the Writing Project**\n \n Ask clarifying questions:\n - What's the topic and main argument?\n - Who's the target audience?\n - What's the desired length/format?\n - What's your goal? (educate, persuade, entertain, explain)\n - Any existing research or sources to include?\n - What's your writing style? (formal, conversational, technical)\n\n2. **Collaborative Outlining**\n \n Help structure the content:\n \n ```markdown\n # Article Outline: [Title]\n \n ## Hook\n - [Opening line/story/statistic]\n - [Why reader should care]\n \n ## Introduction\n - Context and background\n - Problem statement\n - What this article covers\n \n ## Main Sections\n \n ### Section 1: [Title]\n - Key point A\n - Key point B\n - Example/evidence\n - [Research needed: specific topic]\n \n ### Section 2: [Title]\n - Key point C\n - Key point D\n - Data/citation needed\n \n ### Section 3: [Title]\n - Key point E\n - Counter-arguments\n - Resolution\n \n ## Conclusion\n - Summary of main points\n - Call to action\n - Final thought\n \n ## Research To-Do\n - [ ] Find data on [topic]\n - [ ] Get examples of [concept]\n - [ ] Source citation for [claim]\n ```\n \n **Iterate on outline**:\n - Adjust based on feedback\n - Ensure logical flow\n - Identify research gaps\n - Mark sections for deep dives\n\n3. **Conduct Research**\n \n When user requests research on a topic:\n \n - Search for relevant information\n - Find credible sources\n - Extract key facts, quotes, and data\n - Add citations in requested format\n \n Example output:\n ```markdown\n ## Research: AI Impact on Productivity\n \n Key Findings:\n \n 1. **Productivity Gains**: Studies show 40% time savings for \n content creation tasks [1]\n \n 2. **Adoption Rates**: 67% of knowledge workers use AI tools \n weekly [2]\n \n 3. **Expert Quote**: \"AI augments rather than replaces human \n creativity\" - Dr. Jane Smith, MIT [3]\n \n Citations:\n [1] McKinsey Global Institute. (2024). \"The Economic Potential \n of Generative AI\"\n [2] Stack Overflow Developer Survey (2024)\n [3] Smith, J. (2024). MIT Technology Review interview\n \n Added to outline under Section 2.\n ```\n\n4. **Improve Hooks**\n \n When user shares an introduction, analyze and strengthen:\n \n **Current Hook Analysis**:\n - What works: [positive elements]\n - What could be stronger: [areas for improvement]\n - Emotional impact: [current vs. potential]\n \n **Suggested Alternatives**:\n \n Option 1: [Bold statement]\n > [Example]\n *Why it works: [explanation]*\n \n Option 2: [Personal story]\n > [Example]\n *Why it works: [explanation]*\n \n Option 3: [Surprising data]\n > [Example]\n *Why it works: [explanation]*\n \n **Questions to hook**:\n - Does it create curiosity?\n - Does it promise value?\n - Is it specific enough?\n - Does it match the audience?\n\n5. **Provide Section-by-Section Feedback**\n \n As user writes each section, review for:\n \n ```markdown\n # Feedback: [Section Name]\n \n ## What Works Well โœ“\n - [Strength 1]\n - [Strength 2]\n - [Strength 3]\n \n ## Suggestions for Improvement\n \n ### Clarity\n - [Specific issue] โ†’ [Suggested fix]\n - [Complex sentence] โ†’ [Simpler alternative]\n \n ### Flow\n - [Transition issue] โ†’ [Better connection]\n - [Paragraph order] โ†’ [Suggested reordering]\n \n ### Evidence\n - [Claim needing support] โ†’ [Add citation or example]\n - [Generic statement] โ†’ [Make more specific]\n \n ### Style\n - [Tone inconsistency] โ†’ [Match your voice better]\n - [Word choice] โ†’ [Stronger alternative]\n \n ## Specific Line Edits\n \n Original:\n > [Exact quote from draft]\n \n Suggested:\n > [Improved version]\n \n Why: [Explanation]\n \n ## Questions to Consider\n - [Thought-provoking question 1]\n - [Thought-provoking question 2]\n \n Ready to move to next section!\n ```\n\n6. **Preserve Writer's Voice**\n \n Important principles:\n \n - **Learn their style**: Read existing writing samples\n - **Suggest, don't replace**: Offer options, not directives\n - **Match tone**: Formal, casual, technical, friendly\n - **Respect choices**: If they prefer their version, support it\n - **Enhance, don't override**: Make their writing better, not different\n \n Ask periodically:\n - \"Does this sound like you?\"\n - \"Is this the right tone?\"\n - \"Should I be more/less [formal/casual/technical]?\"\n\n7. **Citation Management**\n \n Handle references based on user preference:\n \n **Inline Citations**:\n ```markdown\n Studies show 40% productivity improvement (McKinsey, 2024).\n ```\n \n **Numbered References**:\n ```markdown\n Studies show 40% productivity improvement [1].\n \n [1] McKinsey Global Institute. (2024)...\n ```\n \n **Footnote Style**:\n ```markdown\n Studies show 40% productivity improvement^1\n \n ^1: McKinsey Global Institute. (2024)...\n ```\n \n Maintain a running citations list:\n ```markdown\n ## References\n \n 1. Author. (Year). \"Title\". Publication.\n 2. Author. (Year). \"Title\". Publication.\n ...\n ```\n\n8. **Final Review and Polish**\n \n When draft is complete, provide comprehensive feedback:\n \n ```markdown\n # Full Draft Review\n \n ## Overall Assessment\n \n **Strengths**:\n - [Major strength 1]\n - [Major strength 2]\n - [Major strength 3]\n \n **Impact**: [Overall effectiveness assessment]\n \n ## Structure & Flow\n - [Comments on organization]\n - [Transition quality]\n - [Pacing assessment]\n \n ## Content Quality\n - [Argument strength]\n - [Evidence sufficiency]\n - [Example effectiveness]\n \n ## Technical Quality\n - Grammar and mechanics: [assessment]\n - Consistency: [assessment]\n - Citations: [completeness check]\n \n ## Readability\n - Clarity score: [evaluation]\n - Sentence variety: [evaluation]\n - Paragraph length: [evaluation]\n \n ## Final Polish Suggestions\n \n 1. **Introduction**: [Specific improvements]\n 2. **Body**: [Specific improvements]\n 3. **Conclusion**: [Specific improvements]\n 4. **Title**: [Options if needed]\n \n ## Pre-Publish Checklist\n - [ ] All claims sourced\n - [ ] Citations formatted\n - [ ] Examples clear\n - [ ] Transitions smooth\n - [ ] Call to action present\n - [ ] Proofread for typos\n \n Ready to publish! ๐Ÿš€\n ```\n\n## Examples\n\n### Example 1: Teresa Torres's Workflow\n\n**User**: \"I'm writing an article about continuous discovery. Help me create an outline.\"\n\n**Process**:\n1. Collaborates on outline structure\n2. Identifies research needs\n3. User starts writing introduction\n4. Reviews and improves the hook\n5. User writes each section\n6. Provides feedback after each section\n7. Conducts research and adds citations\n8. Final review of complete draft\n9. Polish and prep for publishing\n\n**Result**: Well-researched, properly cited article written in Teresa's voice with strong structure and flow.\n\n### Example 2: Research-Heavy Article\n\n**User**: \"I'm writing about AI's impact on product management. Help me find current data and examples.\"\n\n**Output**:\n```markdown\n## Research Compiled\n\n### Recent Data\n- Gartner: 80% of PMs will use AI tools by 2025 [1]\n- Survey: 45% report faster feature shipping [2]\n- Case study: Airbnb's AI-assisted prioritization [3]\n\n### Expert Quotes\n- \"AI amplifies PM judgment, not replaces it\" - Marty Cagan\n- [Additional quotes with citations]\n\n### Real Examples\n1. **Company A**: Used AI for user research synthesis\n - Result: 60% time savings\n - Source: [citation]\n\n2. **Company B**: AI-powered roadmap analysis\n - Result: Better stakeholder alignment\n - Source: [citation]\n\nAll added to your outline with proper citations.\n```\n\n### Example 3: Hook Improvement\n\n**User's Original Hook**:\n> \"Product management is changing because of AI. In this article, I'll discuss some ways AI affects product managers.\"\n\n**Improved Options**:\n\n**Option 1 (Data-driven)**:\n> \"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.\"\n\n**Option 2 (Question)**:\n> \"What if you could talk to every customer, read every review, and analyze every support ticketโ€”all before your morning coffee?\"\n\n**Option 3 (Story)**:\n> \"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.\"\n\n### Example 4: Section Feedback\n\n**User**: \"Just finished my 'Common Mistakes' section. Thoughts?\"\n\n**Response**:\n```markdown\n# Feedback: Common Mistakes Section\n\n## What Works Well โœ“\n- Strong examples (the Slack notification story)\n- Clear structure (3 mistakes, clean layout)\n- Practical advice for each mistake\n\n## Suggestions\n\n### Make It More Specific\nYour second point says \"Bad prioritization\" but could be stronger:\n\nCurrent:\n> \"Many teams prioritize badly by focusing on features instead of outcomes.\"\n\nSuggested:\n> \"I've watched teams ship 14 features in a quarter yet move none of their key metrics. They prioritized activity over progress.\"\n\n### Add Data\nThe third mistake would benefit from evidence:\n> \"[Add citation]: Studies show teams without regular user contact are 3x more likely to build unused features [needs source]\"\n\n### Flow Improvement\nConsider reordering: Mistake 3 โ†’ Mistake 2 โ†’ Mistake 1\nThis builds from small to big impact.\n\nReady for the next section!\n```\n\n## Writing Workflows\n\n### Blog Post Workflow\n1. Outline together\n2. Research key points\n3. Write introduction โ†’ get feedback\n4. Write body sections โ†’ feedback each\n5. Write conclusion โ†’ final review\n6. Polish and edit\n\n### Newsletter Workflow\n1. Discuss hook ideas\n2. Quick outline (shorter format)\n3. Draft in one session\n4. Review for clarity and links\n5. Quick polish\n\n### Technical Tutorial Workflow\n1. Outline steps\n2. Write code examples\n3. Add explanations\n4. Test instructions\n5. Add troubleshooting section\n6. Final review for accuracy\n\n### Thought Leadership Workflow\n1. Brainstorm unique angle\n2. Research existing perspectives\n3. Develop your thesis\n4. Write with strong POV\n5. Add supporting evidence\n6. Craft compelling conclusion\n\n## Pro Tips\n\n1. **Work in VS Code**: Better than web Claude for long-form writing\n2. **One section at a time**: Get feedback incrementally\n3. **Save research separately**: Keep a research.md file\n4. **Version your drafts**: article-v1.md, article-v2.md, etc.\n5. **Read aloud**: Use feedback to identify clunky sentences\n6. **Set deadlines**: \"I want to finish the draft today\"\n7. **Take breaks**: Write, get feedback, pause, revise\n\n## File Organization\n\nRecommended structure for writing projects:\n\n```\n~/writing/article-name/\nโ”œโ”€โ”€ outline.md # Your outline\nโ”œโ”€โ”€ research.md # All research and citations\nโ”œโ”€โ”€ draft-v1.md # First draft\nโ”œโ”€โ”€ draft-v2.md # Revised draft\nโ”œโ”€โ”€ final.md # Publication-ready\nโ”œโ”€โ”€ feedback.md # Collected feedback\nโ””โ”€โ”€ sources/ # Reference materials\n โ”œโ”€โ”€ study1.pdf\n โ””โ”€โ”€ article2.md\n```\n\n## Best Practices\n\n### For Research\n- Verify sources before citing\n- Use recent data when possible\n- Balance different perspectives\n- Link to original sources\n\n### For Feedback\n- Be specific about what you want: \"Is this too technical?\"\n- Share your concerns: \"I'm worried this section drags\"\n- Ask questions: \"Does this flow logically?\"\n- Request alternatives: \"What's another way to explain this?\"\n\n### For Voice\n- Share examples of your writing\n- Specify tone preferences\n- Point out good matches: \"That sounds like me!\"\n- Flag mismatches: \"Too formal for my style\"\n\n## Related Use Cases\n\n- Creating social media posts from articles\n- Adapting content for different audiences\n- Writing email newsletters\n- Drafting technical documentation\n- Creating presentation content\n- Writing case studies\n- Developing course outlines","schemaVersion":1},"repoUrl":"https://github.com/Prat011/awesome-llm-skills/tree/master/content-research-writer","tags":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"awesome-llm-skills","audit":{"files":["slack-gif-creator/requirements.txt"],"binaries":[],"findings":[{"kind":"dependency","rule":"DP-04","message":"Python dependencies are not pinned and there is no lock file.","surface":"slack-gif-creator/requirements.txt","evidence":"pillow>=10.0.0, imageio>=2.31.0, imageio-ffmpeg>=0.4.9, numpy>=1.24.0","severity":"medium"}],"packages":4,"auditedAt":"2026-09-25T11:52:30.068Z","lockfiles":[]},"forks":313,"owner":"Prat011","stars":1761,"topics":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms","openai","opencode","qwen","qwen-coder","skills"],"license":null,"fullName":"Prat011/awesome-llm-skills","homepage":null,"language":"Python","pushedAt":"2026-07-14T09:53:56Z","avatarUrl":"https://avatars.githubusercontent.com/u/67639393?v=4","crawledAt":"2026-09-25T11:52:22.319Z","openIssues":170,"manifestFile":"SKILL.md","manifestPath":"content-research-writer/SKILL.md","defaultBranch":"master"},"readme":"# Content Research Writer\n\nThis skill acts as your writing partner, helping you research, outline, draft, and refine content while maintaining your unique voice and style.\n\n## When to Use This Skill\n\n- Writing blog posts, articles, or newsletters\n- Creating educational content or tutorials\n- Drafting thought leadership pieces\n- Researching and writing case studies\n- Producing technical documentation with sources\n- Writing with proper citations and references\n- Improving hooks and introductions\n- Getting section-by-section feedback while writing\n\n## What This Skill Does\n\n1. **Collaborative Outlining**: Helps you structure ideas into coherent outlines\n2. **Research Assistance**: Finds relevant information and adds citations\n3. **Hook Improvement**: Strengthens your opening to capture attention\n4. **Section Feedback**: Reviews each section as you write\n5. **Voice Preservation**: Maintains your writing style and tone\n6. **Citation Management**: Adds and formats references properly\n7. **Iterative Refinement**: Helps you improve through multiple drafts\n\n## How to Use\n\n### Setup Your Writing Environment\n\nCreate a dedicated folder for your article:\n```\nmkdir ~/writing/my-article-title\ncd ~/writing/my-article-title\n```\n\nCreate your draft file:\n```\ntouch article-draft.md\n```\n\nOpen Claude Code from this directory and start writing.\n\n### Basic Workflow\n\n1. **Start with an outline**:\n```\nHelp me create an outline for an article about [topic]\n```\n\n2. **Research and add citations**:\n```\nResearch [specific topic] and add citations to my outline\n```\n\n3. **Improve the hook**:\n```\nHere's my introduction. Help me make the hook more compelling.\n```\n\n4. **Get section feedback**:\n```\nI just finished the \"Why This Matters\" section. Review it and give feedback.\n```\n\n5. **Refine and polish**:\n```\nReview the full draft for flow, clarity, and consistency.\n```\n\n## Instructions\n\nWhen a user requests writing assistance:\n\n1. **Understand the Writing Project**\n \n Ask clarifying questions:\n - What's the topic and main argument?\n - Who's the target audience?\n - What's the desired length/format?\n - What's your goal? (educate, persuade, entertain, explain)\n - Any existing research or sources to include?\n - What's your writing style? (formal, conversational, technical)\n\n2. **Collaborative Outlining**\n \n Help structure the content:\n \n ```markdown\n # Article Outline: [Title]\n \n ## Hook\n - [Opening line/story/statistic]\n - [Why reader should care]\n \n ## Introduction\n - Context and background\n - Problem statement\n - What this article covers\n \n ## Main Sections\n \n ### Section 1: [Title]\n - Key point A\n - Key point B\n - Example/evidence\n - [Research needed: specific topic]\n \n ### Section 2: [Title]\n - Key point C\n - Key point D\n - Data/citation needed\n \n ### Section 3: [Title]\n - Key point E\n - Counter-arguments\n - Resolution\n \n ## Conclusion\n - Summary of main points\n - Call to action\n - Final thought\n \n ## Research To-Do\n - [ ] Find data on [topic]\n - [ ] Get examples of [concept]\n - [ ] Source citation for [claim]\n ```\n \n **Iterate on outline**:\n - Adjust based on feedback\n - Ensure logical flow\n - Identify research gaps\n - Mark sections for deep dives\n\n3. **Conduct Research**\n \n When user requests research on a topic:\n \n - Search for relevant information\n - Find credible sources\n - Extract key facts, quotes, and data\n - Add citations in requested format\n \n Example output:\n ```markdown\n ## Research: AI Impact on Productivity\n \n Key Findings:\n \n 1. **Productivity Gains**: Studies show 40% time savings for \n content creation tasks [1]\n \n 2. **Adoption Rates**: 67% of knowledge workers use AI tools \n weekly [2]\n \n 3. **Expert Quote**: \"AI augments rather than replaces human \n creativity\" - Dr. Jane Smith, MIT [3]\n \n Citations:\n [1] McKinsey Global Institute. (2024). \"The Economic Potential \n of","createdAt":"2026-09-25T11:52:30.195Z","updatedAt":"2026-09-25T11:52:30.195Z"},{"id":"cmugwiia7025wqu06jkx1nc3i","slug":"prat011-awesome-llm-skills-file-organizer","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.","authorId":"gh:prat011","authorName":"Prat011","version":"0.1.0","category":"Prompt","securityLevel":"Community","downloadsCount":0,"githubStars":1761,"pricePerCall":0,"manifest":{"name":"file-organizer","tools":[],"category":"Prompt","entrypoint":{"type":"prompt"},"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.","permissions":[],"systemPrompt":"# File Organizer\n\nThis 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.\n\n## When to Use This Skill\n\n- Your Downloads folder is a chaotic mess\n- You can't find files because they're scattered everywhere\n- You have duplicate files taking up space\n- Your folder structure doesn't make sense anymore\n- You want to establish better organization habits\n- You're starting a new project and need a good structure\n- You're cleaning up before archiving old projects\n\n## What This Skill Does\n\n1. **Analyzes Current Structure**: Reviews your folders and files to understand what you have\n2. **Finds Duplicates**: Identifies duplicate files across your system\n3. **Suggests Organization**: Proposes logical folder structures based on your content\n4. **Automates Cleanup**: Moves, renames, and organizes files with your approval\n5. **Maintains Context**: Makes smart decisions based on file types, dates, and content\n6. **Reduces Clutter**: Identifies old files you probably don't need anymore\n\n## How to Use\n\n### From Your Home Directory\n\n```\ncd ~\n```\n\nThen run Claude Code and ask for help:\n\n```\nHelp me organize my Downloads folder\n```\n\n```\nFind duplicate files in my Documents folder\n```\n\n```\nReview my project directories and suggest improvements\n```\n\n### Specific Organization Tasks\n\n```\nOrganize these downloads into proper folders based on what they are\n```\n\n```\nFind duplicate files and help me decide which to keep\n```\n\n```\nClean up old files I haven't touched in 6+ months\n```\n\n```\nCreate a better folder structure for my [work/projects/photos/etc]\n```\n\n## Instructions\n\nWhen a user requests file organization help:\n\n1. **Understand the Scope**\n \n Ask clarifying questions:\n - Which directory needs organization? (Downloads, Documents, entire home folder?)\n - What's the main problem? (Can't find things, duplicates, too messy, no structure?)\n - Any files or folders to avoid? (Current projects, sensitive data?)\n - How aggressively to organize? (Conservative vs. comprehensive cleanup)\n\n2. **Analyze Current State**\n \n Review the target directory:\n ```bash\n # Get overview of current structure\n ls -la [target_directory]\n \n # Check file types and sizes\n find [target_directory] -type f -exec file {} \\; | head -20\n \n # Identify largest files\n du -sh [target_directory]/* | sort -rh | head -20\n \n # Count file types\n find [target_directory] -type f | sed 's/.*\\.//' | sort | uniq -c | sort -rn\n ```\n \n Summarize findings:\n - Total files and folders\n - File type breakdown\n - Size distribution\n - Date ranges\n - Obvious organization issues\n\n3. **Identify Organization Patterns**\n \n Based on the files, determine logical groupings:\n \n **By Type**:\n - Documents (PDFs, DOCX, TXT)\n - Images (JPG, PNG, SVG)\n - Videos (MP4, MOV)\n - Archives (ZIP, TAR, DMG)\n - Code/Projects (directories with code)\n - Spreadsheets (XLSX, CSV)\n - Presentations (PPTX, KEY)\n \n **By Purpose**:\n - Work vs. Personal\n - Active vs. Archive\n - Project-specific\n - Reference materials\n - Temporary/scratch files\n \n **By Date**:\n - Current year/month\n - Previous years\n - Very old (archive candidates)\n\n4. **Find Duplicates**\n \n When requested, search for duplicates:\n ```bash\n # Find exact duplicates by hash\n find [directory] -type f -exec md5 {} \\; | sort | uniq -d\n \n # Find files with same name\n find [directory] -type f -printf '%f\\n' | sort | uniq -d\n \n # Find similar-sized files\n find [directory] -type f -printf '%s %p\\n' | sort -n\n ```\n \n For each set of duplicates:\n - Show all file paths\n - Display sizes and modification dates\n - Recommend which to keep (usually newest or best-named)\n - **Important**: Always ask for confirmation before deleting\n\n5. **Propose Organization Plan**\n \n Present a clear plan before making changes:\n \n ```markdown\n # Organization Plan for [Directory]\n \n ## Current State\n - X files across Y folders\n - [Size] total\n - File types: [breakdown]\n - Issues: [list problems]\n \n ## Proposed Structure\n \n ```\n [Directory]/\n โ”œโ”€โ”€ Work/\n โ”‚ โ”œโ”€โ”€ Projects/\n โ”‚ โ”œโ”€โ”€ Documents/\n โ”‚ โ””โ”€โ”€ Archive/\n โ”œโ”€โ”€ Personal/\n โ”‚ โ”œโ”€โ”€ Photos/\n โ”‚ โ”œโ”€โ”€ Documents/\n โ”‚ โ””โ”€โ”€ Media/\n โ””โ”€โ”€ Downloads/\n โ”œโ”€โ”€ To-Sort/\n โ””โ”€โ”€ Archive/\n ```\n \n ## Changes I'll Make\n \n 1. **Create new folders**: [list]\n 2. **Move files**:\n - X PDFs โ†’ Work/Documents/\n - Y images โ†’ Personal/Photos/\n - Z old files โ†’ Archive/\n 3. **Rename files**: [any renaming patterns]\n 4. **Delete**: [duplicates or trash files]\n \n ## Files Needing Your Decision\n \n - [List any files you're unsure about]\n \n Ready to proceed? (yes/no/modify)\n ```\n\n6. **Execute Organization**\n \n After approval, organize systematically:\n \n ```bash\n # Create folder structure\n mkdir -p \"path/to/new/folders\"\n \n # Move files with clear logging\n mv \"old/path/file.pdf\" \"new/path/file.pdf\"\n \n # Rename files with consistent patterns\n # Example: \"YYYY-MM-DD - Description.ext\"\n ```\n \n **Important Rules**:\n - Always confirm before deleting anything\n - Log all moves for potential undo\n - Preserve original modification dates\n - Handle filename conflicts gracefully\n - Stop and ask if you encounter unexpected situations\n\n7. **Provide Summary and Maintenance Tips**\n \n After organizing:\n \n ```markdown\n # Organization Complete! โœจ\n \n ## What Changed\n \n - Created [X] new folders\n - Organized [Y] files\n - Freed [Z] GB by removing duplicates\n - Archived [W] old files\n \n ## New Structure\n \n [Show the new folder tree]\n \n ## Maintenance Tips\n \n To keep this organized:\n \n 1. **Weekly**: Sort new downloads\n 2. **Monthly**: Review and archive completed projects\n 3. **Quarterly**: Check for new duplicates\n 4. **Yearly**: Archive old files\n \n ## Quick Commands for You\n \n ```bash\n # Find files modified this week\n find . -type f -mtime -7\n \n # Sort downloads by type\n [custom command for their setup]\n \n # Find duplicates\n [custom command]\n ```\n \n Want to organize another folder?\n ```\n\n## Examples\n\n### Example 1: Organizing Downloads (From Justin Dielmann)\n\n**User**: \"My Downloads folder is a mess with 500+ files. Help me organize it.\"\n\n**Process**:\n1. Analyzes Downloads folder\n2. Finds patterns: work docs, personal photos, installers, random PDFs\n3. Proposes structure:\n - Downloads/\n - Work/\n - Personal/\n - Installers/ (DMG, PKG files)\n - Archive/\n - ToSort/ (things needing decisions)\n4. Asks for confirmation\n5. Moves files intelligently based on content and names\n6. Results: 500 files โ†’ 5 organized folders\n\n### Example 2: Finding and Removing Duplicates\n\n**User**: \"Find duplicate files in my Documents and help me decide which to keep.\"\n\n**Output**:\n```markdown\n# Found 23 Sets of Duplicates (156 MB total)\n\n## Duplicate Set 1: \"proposal.pdf\"\n- `/Documents/proposal.pdf` (2.3 MB, modified: 2024-03-15)\n- `/Documents/old/proposal.pdf` (2.3 MB, modified: 2024-03-15)\n- `/Desktop/proposal.pdf` (2.3 MB, modified: 2024-03-10)\n\n**Recommendation**: Keep `/Documents/proposal.pdf` (most recent in correct location)\nDelete the other 2 copies?\n\n[Continue for all duplicates...]\n```\n\n### Example 3: Restructuring Projects Folder\n\n**User**: \"Review my ~/Projects directory and suggest improvements.\"\n\n**Output**:\n```markdown\n# Analysis of ~/Projects\n\n## Current Structure Issues\n- Mix of active and archived projects (3+ years old)\n- No consistent naming convention\n- Some projects at root, others in random subfolders\n- Duplicate folders (project-name, project-name-old, project-name-v2)\n\n## Proposed Structure\n\n```\nProjects/\nโ”œโ”€โ”€ Active/\nโ”‚ โ”œโ”€โ”€ client-work/\nโ”‚ โ”œโ”€โ”€ side-projects/\nโ”‚ โ””โ”€โ”€ learning/\nโ”œโ”€โ”€ Archive/\nโ”‚ โ”œโ”€โ”€ 2022/\nโ”‚ โ”œโ”€โ”€ 2023/\nโ”‚ โ””โ”€โ”€ 2024/\nโ””โ”€โ”€ Templates/\n```\n\n## Specific Changes\n1. Move 12 projects not touched since 2022 โ†’ Archive/\n2. Consolidate 4 duplicate project folders\n3. Rename projects to consistent format: \"client-name-project-name\"\n4. Create Archive for old work\n\nWant me to implement this?\n```\n\n### Example 4: Organizing Photos by Date\n\n**User**: \"Organize my photo folders by year and month.\"\n\n**Output**: Creates structure like:\n```\nPhotos/\nโ”œโ”€โ”€ 2023/\nโ”‚ โ”œโ”€โ”€ 01-January/\nโ”‚ โ”œโ”€โ”€ 02-February/\nโ”‚ โ””โ”€โ”€ ...\nโ”œโ”€โ”€ 2024/\nโ”‚ โ”œโ”€โ”€ 01-January/\nโ”‚ โ””โ”€โ”€ ...\nโ””โ”€โ”€ Unsorted/\n```\n\nThen moves photos based on EXIF data or file modification dates.\n\n## Common Organization Tasks\n\n### Downloads Cleanup\n```\nOrganize my Downloads folder - move documents to Documents, \nimages to Pictures, keep installers separate, and archive files \nolder than 3 months.\n```\n\n### Project Organization\n```\nReview my Projects folder structure and help me separate active \nprojects from old ones I should archive.\n```\n\n### Duplicate Removal\n```\nFind all duplicate files in my Documents folder and help me \ndecide which ones to keep.\n```\n\n### Desktop Cleanup\n```\nMy Desktop is covered in files. Help me organize everything into \nmy Documents folder properly.\n```\n\n### Photo Organization\n```\nOrganize all photos in this folder by date (year/month) based \non when they were taken.\n```\n\n### Work/Personal Separation\n```\nHelp me separate my work files from personal files across my \nDocuments folder.\n```\n\n## Pro Tips\n\n1. **Start Small**: Begin with one messy folder (like Downloads) to build trust\n2. **Regular Maintenance**: Run weekly cleanup on Downloads\n3. **Consistent Naming**: Use \"YYYY-MM-DD - Description\" format for important files\n4. **Archive Aggressively**: Move old projects to Archive instead of deleting\n5. **Keep Active Separate**: Maintain clear boundaries between active and archived work\n6. **Trust the Process**: Let Claude handle the cognitive load of where things go\n\n## Best Practices\n\n### Folder Naming\n- Use clear, descriptive names\n- Avoid spaces (use hyphens or underscores)\n- Be specific: \"client-proposals\" not \"docs\"\n- Use prefixes for ordering: \"01-current\", \"02-archive\"\n\n### File Naming\n- Include dates: \"2024-10-17-meeting-notes.md\"\n- Be descriptive: \"q3-financial-report.xlsx\"\n- Avoid version numbers in names (use version control instead)\n- Remove download artifacts: \"document-final-v2 (1).pdf\" โ†’ \"document.pdf\"\n\n### When to Archive\n- Projects not touched in 6+ months\n- Completed work that might be referenced later\n- Old versions after migration to new systems\n- Files you're hesitant to delete (archive first)\n\n## Related Use Cases\n\n- Setting up organization for a new computer\n- Preparing files for backup/archiving\n- Cleaning up before storage cleanup\n- Organizing shared team folders\n- Structuring new project directories","schemaVersion":1},"repoUrl":"https://github.com/Prat011/awesome-llm-skills/tree/master/file-organizer","tags":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"awesome-llm-skills","audit":{"files":["slack-gif-creator/requirements.txt"],"binaries":[],"findings":[{"kind":"dependency","rule":"DP-04","message":"Python dependencies are not pinned and there is no lock file.","surface":"slack-gif-creator/requirements.txt","evidence":"pillow>=10.0.0, imageio>=2.31.0, imageio-ffmpeg>=0.4.9, numpy>=1.24.0","severity":"medium"}],"packages":4,"auditedAt":"2026-09-25T11:52:30.068Z","lockfiles":[]},"forks":313,"owner":"Prat011","stars":1761,"topics":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms","openai","opencode","qwen","qwen-coder","skills"],"license":null,"fullName":"Prat011/awesome-llm-skills","homepage":null,"language":"Python","pushedAt":"2026-07-14T09:53:56Z","avatarUrl":"https://avatars.githubusercontent.com/u/67639393?v=4","crawledAt":"2026-09-25T11:52:22.319Z","openIssues":170,"manifestFile":"SKILL.md","manifestPath":"file-organizer/SKILL.md","defaultBranch":"master"},"readme":"# File Organizer\n\nThis 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.\n\n## When to Use This Skill\n\n- Your Downloads folder is a chaotic mess\n- You can't find files because they're scattered everywhere\n- You have duplicate files taking up space\n- Your folder structure doesn't make sense anymore\n- You want to establish better organization habits\n- You're starting a new project and need a good structure\n- You're cleaning up before archiving old projects\n\n## What This Skill Does\n\n1. **Analyzes Current Structure**: Reviews your folders and files to understand what you have\n2. **Finds Duplicates**: Identifies duplicate files across your system\n3. **Suggests Organization**: Proposes logical folder structures based on your content\n4. **Automates Cleanup**: Moves, renames, and organizes files with your approval\n5. **Maintains Context**: Makes smart decisions based on file types, dates, and content\n6. **Reduces Clutter**: Identifies old files you probably don't need anymore\n\n## How to Use\n\n### From Your Home Directory\n\n```\ncd ~\n```\n\nThen run Claude Code and ask for help:\n\n```\nHelp me organize my Downloads folder\n```\n\n```\nFind duplicate files in my Documents folder\n```\n\n```\nReview my project directories and suggest improvements\n```\n\n### Specific Organization Tasks\n\n```\nOrganize these downloads into proper folders based on what they are\n```\n\n```\nFind duplicate files and help me decide which to keep\n```\n\n```\nClean up old files I haven't touched in 6+ months\n```\n\n```\nCreate a better folder structure for my [work/projects/photos/etc]\n```\n\n## Instructions\n\nWhen a user requests file organization help:\n\n1. **Understand the Scope**\n \n Ask clarifying questions:\n - Which directory needs organization? (Downloads, Documents, entire home folder?)\n - What's the main problem? (Can't find things, duplicates, too messy, no structure?)\n - Any files or folders to avoid? (Current projects, sensitive data?)\n - How aggressively to organize? (Conservative vs. comprehensive cleanup)\n\n2. **Analyze Current State**\n \n Review the target directory:\n ```bash\n # Get overview of current structure\n ls -la [target_directory]\n \n # Check file types and sizes\n find [target_directory] -type f -exec file {} \\; | head -20\n \n # Identify largest files\n du -sh [target_directory]/* | sort -rh | head -20\n \n # Count file types\n find [target_directory] -type f | sed 's/.*\\.//' | sort | uniq -c | sort -rn\n ```\n \n Summarize findings:\n - Total files and folders\n - File type breakdown\n - Size distribution\n - Date ranges\n - Obvious organization issues\n\n3. **Identify Organization Patterns**\n \n Based on the files, determine logical groupings:\n \n **By Type**:\n - Documents (PDFs, DOCX, TXT)\n - Images (JPG, PNG, SVG)\n - Videos (MP4, MOV)\n - Archives (ZIP, TAR, DMG)\n - Code/Projects (directories with code)\n - Spreadsheets (XLSX, CSV)\n - Presentations (PPTX, KEY)\n \n **By Purpose**:\n - Work vs. Personal\n - Active vs. Archive\n - Project-specific\n - Reference materials\n - Temporary/scratch files\n \n **By Date**:\n - Current year/month\n - Previous years\n - Very old (archive candidates)\n\n4. **Find Duplicates**\n \n When requested, search for duplicates:\n ```bash\n # Find exact duplicates by hash\n find [directory] -type f -exec md5 {} \\; | sort | uniq -d\n \n # Find files with same name\n find [directory] -type f -printf '%f\\n' | sort | uniq -d\n \n # Find similar-sized files\n find [directory] -type f -printf '%s %p\\n' | sort -n\n ```\n \n For each set of duplicates:\n - Show all file paths\n - Display sizes and modification dates\n - Recommend which to keep (usually newest or best-named)\n - **Important**: Always ask for confirmation before deleting\n\n5. **Propose Organization Plan**\n \n Present a clear plan before making changes:\n \n ```ma","createdAt":"2026-09-25T11:52:30.224Z","updatedAt":"2026-09-25T11:52:30.224Z"},{"id":"cmugwiian0262qu068in4r75a","slug":"prat011-awesome-llm-skills-image-enhancer","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.","authorId":"gh:prat011","authorName":"Prat011","version":"0.1.0","category":"Prompt","securityLevel":"Community","downloadsCount":0,"githubStars":1761,"pricePerCall":0,"manifest":{"name":"image-enhancer","tools":[],"category":"Prompt","entrypoint":{"type":"prompt"},"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.","permissions":[],"systemPrompt":"# Image Enhancer\n\nThis skill takes your images and screenshots and makes them look betterโ€”sharper, clearer, and more professional.\n\n## When to Use This Skill\n\n- Improving screenshot quality for blog posts or documentation\n- Enhancing images before sharing on social media\n- Preparing images for presentations or reports\n- Upscaling low-resolution images\n- Sharpening blurry photos\n- Cleaning up compressed images\n\n## What This Skill Does\n\n1. **Analyzes Image Quality**: Checks resolution, sharpness, and compression artifacts\n2. **Enhances Resolution**: Upscales images intelligently\n3. **Improves Sharpness**: Enhances edges and details\n4. **Reduces Artifacts**: Cleans up compression artifacts and noise\n5. **Optimizes for Use Case**: Adjusts based on intended use (web, print, social media)\n\n## How to Use\n\n### Basic Enhancement\n\n```\nImprove the image quality of screenshot.png\n```\n\n```\nEnhance all images in this folder\n```\n\n### Specific Improvements\n\n```\nUpscale this image to 4K resolution\n```\n\n```\nSharpen this blurry screenshot\n```\n\n```\nReduce compression artifacts in this image\n```\n\n### Batch Processing\n\n```\nImprove the quality of all PNG files in this directory\n```\n\n## Example\n\n**User**: \"Improve the image quality of screenshot-2024.png\"\n\n**Output**:\n```\nAnalyzing screenshot-2024.png...\n\nCurrent specs:\n- Resolution: 1920x1080\n- Format: PNG\n- Quality: Good, but slight blur\n\nEnhancements applied:\nโœ“ Upscaled to 2560x1440 (retina)\nโœ“ Sharpened edges\nโœ“ Enhanced text clarity\nโœ“ Optimized file size\n\nSaved as: screenshot-2024-enhanced.png\nOriginal preserved as: screenshot-2024-original.png\n```\n\n**Inspired by:** Lenny Rachitsky's workflow from his newsletter - used for screenshots in his articles\n\n## Tips\n\n- Always keeps original files as backup\n- Works best with screenshots and digital images\n- Can batch process entire folders\n- Specify output format if needed (PNG for quality, JPG for smaller size)\n- For social media, mention the platform for optimal sizing\n\n## Common Use Cases\n\n- **Blog Posts**: Enhance screenshots before publishing\n- **Documentation**: Make UI screenshots crystal clear\n- **Social Media**: Optimize images for Twitter, LinkedIn, Instagram\n- **Presentations**: Upscale images for large screens\n- **Print Materials**: Increase resolution for physical media","schemaVersion":1},"repoUrl":"https://github.com/Prat011/awesome-llm-skills/tree/master/image-enhancer","tags":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"awesome-llm-skills","audit":{"files":["slack-gif-creator/requirements.txt"],"binaries":[],"findings":[{"kind":"dependency","rule":"DP-04","message":"Python dependencies are not pinned and there is no lock file.","surface":"slack-gif-creator/requirements.txt","evidence":"pillow>=10.0.0, imageio>=2.31.0, imageio-ffmpeg>=0.4.9, numpy>=1.24.0","severity":"medium"}],"packages":4,"auditedAt":"2026-09-25T11:52:30.068Z","lockfiles":[]},"forks":313,"owner":"Prat011","stars":1761,"topics":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms","openai","opencode","qwen","qwen-coder","skills"],"license":null,"fullName":"Prat011/awesome-llm-skills","homepage":null,"language":"Python","pushedAt":"2026-07-14T09:53:56Z","avatarUrl":"https://avatars.githubusercontent.com/u/67639393?v=4","crawledAt":"2026-09-25T11:52:22.319Z","openIssues":170,"manifestFile":"SKILL.md","manifestPath":"image-enhancer/SKILL.md","defaultBranch":"master"},"readme":"# Image Enhancer\n\nThis skill takes your images and screenshots and makes them look betterโ€”sharper, clearer, and more professional.\n\n## When to Use This Skill\n\n- Improving screenshot quality for blog posts or documentation\n- Enhancing images before sharing on social media\n- Preparing images for presentations or reports\n- Upscaling low-resolution images\n- Sharpening blurry photos\n- Cleaning up compressed images\n\n## What This Skill Does\n\n1. **Analyzes Image Quality**: Checks resolution, sharpness, and compression artifacts\n2. **Enhances Resolution**: Upscales images intelligently\n3. **Improves Sharpness**: Enhances edges and details\n4. **Reduces Artifacts**: Cleans up compression artifacts and noise\n5. **Optimizes for Use Case**: Adjusts based on intended use (web, print, social media)\n\n## How to Use\n\n### Basic Enhancement\n\n```\nImprove the image quality of screenshot.png\n```\n\n```\nEnhance all images in this folder\n```\n\n### Specific Improvements\n\n```\nUpscale this image to 4K resolution\n```\n\n```\nSharpen this blurry screenshot\n```\n\n```\nReduce compression artifacts in this image\n```\n\n### Batch Processing\n\n```\nImprove the quality of all PNG files in this directory\n```\n\n## Example\n\n**User**: \"Improve the image quality of screenshot-2024.png\"\n\n**Output**:\n```\nAnalyzing screenshot-2024.png...\n\nCurrent specs:\n- Resolution: 1920x1080\n- Format: PNG\n- Quality: Good, but slight blur\n\nEnhancements applied:\nโœ“ Upscaled to 2560x1440 (retina)\nโœ“ Sharpened edges\nโœ“ Enhanced text clarity\nโœ“ Optimized file size\n\nSaved as: screenshot-2024-enhanced.png\nOriginal preserved as: screenshot-2024-original.png\n```\n\n**Inspired by:** Lenny Rachitsky's workflow from his newsletter - used for screenshots in his articles\n\n## Tips\n\n- Always keeps original files as backup\n- Works best with screenshots and digital images\n- Can batch process entire folders\n- Specify output format if needed (PNG for quality, JPG for smaller size)\n- For social media, mention the platform for optimal sizing\n\n## Common Use Cases\n\n- **Blog Posts**: Enhance screenshots before publishing\n- **Documentation**: Make UI screenshots crystal clear\n- **Social Media**: Optimize images for Twitter, LinkedIn, Instagram\n- **Presentations**: Upscale images for large screens\n- **Print Materials**: Increase resolution for physical media","createdAt":"2026-09-25T11:52:30.240Z","updatedAt":"2026-09-25T11:52:30.240Z"},{"id":"cmugwiiax0265qu0659nzyxgd","slug":"prat011-awesome-llm-skills-internal-comms","name":"internal-comms","description":"A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).","authorId":"gh:prat011","authorName":"Prat011","version":"0.1.0","category":"Prompt","securityLevel":"Community","downloadsCount":0,"githubStars":1761,"pricePerCall":0,"manifest":{"name":"internal-comms","tools":[],"category":"Prompt","entrypoint":{"type":"prompt"},"description":"A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).","permissions":[],"systemPrompt":"## When to use this skill\nTo write internal communications, use this skill for:\n- 3P updates (Progress, Plans, Problems)\n- Company newsletters\n- FAQ responses\n- Status reports\n- Leadership updates\n- Project updates\n- Incident reports\n\n## How to use this skill\n\nTo write any internal communication:\n\n1. **Identify the communication type** from the request\n2. **Load the appropriate guideline file** from the `examples/` directory:\n - `examples/3p-updates.md` - For Progress/Plans/Problems team updates\n - `examples/company-newsletter.md` - For company-wide newsletters\n - `examples/faq-answers.md` - For answering frequently asked questions\n - `examples/general-comms.md` - For anything else that doesn't explicitly match one of the above\n3. **Follow the specific instructions** in that file for formatting, tone, and content gathering\n\nIf the communication type doesn't match any existing guideline, ask for clarification or more context about the desired format.\n\n## Keywords\n3P updates, company newsletter, company comms, weekly update, faqs, common questions, updates, internal comms","schemaVersion":1},"repoUrl":"https://github.com/Prat011/awesome-llm-skills/tree/master/internal-comms","tags":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"awesome-llm-skills","audit":{"files":["slack-gif-creator/requirements.txt"],"binaries":[],"findings":[{"kind":"dependency","rule":"DP-04","message":"Python dependencies are not pinned and there is no lock file.","surface":"slack-gif-creator/requirements.txt","evidence":"pillow>=10.0.0, imageio>=2.31.0, imageio-ffmpeg>=0.4.9, numpy>=1.24.0","severity":"medium"}],"packages":4,"auditedAt":"2026-09-25T11:52:30.068Z","lockfiles":[]},"forks":313,"owner":"Prat011","stars":1761,"topics":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms","openai","opencode","qwen","qwen-coder","skills"],"license":"Complete terms in LICENSE.txt","fullName":"Prat011/awesome-llm-skills","homepage":null,"language":"Python","pushedAt":"2026-07-14T09:53:56Z","avatarUrl":"https://avatars.githubusercontent.com/u/67639393?v=4","crawledAt":"2026-09-25T11:52:22.319Z","openIssues":170,"manifestFile":"SKILL.md","manifestPath":"internal-comms/SKILL.md","defaultBranch":"master"},"readme":"## When to use this skill\nTo write internal communications, use this skill for:\n- 3P updates (Progress, Plans, Problems)\n- Company newsletters\n- FAQ responses\n- Status reports\n- Leadership updates\n- Project updates\n- Incident reports\n\n## How to use this skill\n\nTo write any internal communication:\n\n1. **Identify the communication type** from the request\n2. **Load the appropriate guideline file** from the `examples/` directory:\n - `examples/3p-updates.md` - For Progress/Plans/Problems team updates\n - `examples/company-newsletter.md` - For company-wide newsletters\n - `examples/faq-answers.md` - For answering frequently asked questions\n - `examples/general-comms.md` - For anything else that doesn't explicitly match one of the above\n3. **Follow the specific instructions** in that file for formatting, tone, and content gathering\n\nIf the communication type doesn't match any existing guideline, ask for clarification or more context about the desired format.\n\n## Keywords\n3P updates, company newsletter, company comms, weekly update, faqs, common questions, updates, internal comms","createdAt":"2026-09-25T11:52:30.250Z","updatedAt":"2026-09-25T11:52:30.250Z"},{"id":"cmugwiib70268qu06ksj0a5um","slug":"prat011-awesome-llm-skills-invoice-organizer","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.","authorId":"gh:prat011","authorName":"Prat011","version":"0.1.0","category":"Prompt","securityLevel":"Community","downloadsCount":0,"githubStars":1761,"pricePerCall":0,"manifest":{"name":"invoice-organizer","tools":[],"category":"Prompt","entrypoint":{"type":"prompt"},"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.","permissions":[],"systemPrompt":"# Invoice Organizer\n\nThis skill transforms chaotic folders of invoices, receipts, and financial documents into a clean, tax-ready filing system without manual effort.\n\n## When to Use This Skill\n\n- Preparing for tax season and need organized records\n- Managing business expenses across multiple vendors\n- Organizing receipts from a messy folder or email downloads\n- Setting up automated invoice filing for ongoing bookkeeping\n- Archiving financial records by year or category\n- Reconciling expenses for reimbursement\n- Preparing documentation for accountants\n\n## What This Skill Does\n\n1. **Reads Invoice Content**: Extracts information from PDFs, images, and documents:\n - Vendor/company name\n - Invoice number\n - Date\n - Amount\n - Product or service description\n - Payment method\n\n2. **Renames Files Consistently**: Creates standardized filenames:\n - Format: `YYYY-MM-DD Vendor - Invoice - ProductOrService.pdf`\n - Examples: `2024-03-15 Adobe - Invoice - Creative Cloud.pdf`\n\n3. **Organizes by Category**: Sorts into logical folders:\n - By vendor\n - By expense category (software, office, travel, etc.)\n - By time period (year, quarter, month)\n - By tax category (deductible, personal, etc.)\n\n4. **Handles Multiple Formats**: Works with:\n - PDF invoices\n - Scanned receipts (JPG, PNG)\n - Email attachments\n - Screenshots\n - Bank statements\n\n5. **Maintains Originals**: Preserves original files while organizing copies\n\n## How to Use\n\n### Basic Usage\n\nNavigate to your messy invoice folder:\n```\ncd ~/Desktop/receipts-to-sort\n```\n\nThen ask Claude Code:\n```\nOrganize these invoices for taxes\n```\n\nOr more specifically:\n```\nRead all invoices in this folder, rename them to \n\"YYYY-MM-DD Vendor - Invoice - Product.pdf\" format, \nand organize them by vendor\n```\n\n### Advanced Organization\n\n```\nOrganize these invoices:\n1. Extract date, vendor, and description from each file\n2. Rename to standard format\n3. Sort into folders by expense category (Software, Office, Travel, etc.)\n4. Create a CSV spreadsheet with all invoice details for my accountant\n```\n\n## Instructions\n\nWhen a user requests invoice organization:\n\n1. **Scan the Folder**\n \n Identify all invoice files:\n ```bash\n # Find all invoice-related files\n find . -type f \\( -name \"*.pdf\" -o -name \"*.jpg\" -o -name \"*.png\" \\) -print\n ```\n \n Report findings:\n - Total number of files\n - File types\n - Date range (if discernible from names)\n - Current organization (or lack thereof)\n\n2. **Extract Information from Each File**\n \n For each invoice, extract:\n \n **From PDF invoices**:\n - Use text extraction to read invoice content\n - Look for common patterns:\n - \"Invoice Date:\", \"Date:\", \"Issued:\"\n - \"Invoice #:\", \"Invoice Number:\"\n - Company name (usually at top)\n - \"Amount Due:\", \"Total:\", \"Amount:\"\n - \"Description:\", \"Service:\", \"Product:\"\n \n **From image receipts**:\n - Read visible text from images\n - Identify vendor name (often at top)\n - Look for date (common formats)\n - Find total amount\n \n **Fallback for unclear files**:\n - Use filename clues\n - Check file creation/modification date\n - Flag for manual review if critical info missing\n\n3. **Determine Organization Strategy**\n \n Ask user preference if not specified:\n \n ```markdown\n I found [X] invoices from [date range].\n \n How would you like them organized?\n \n 1. **By Vendor** (Adobe/, Amazon/, Stripe/, etc.)\n 2. **By Category** (Software/, Office Supplies/, Travel/, etc.)\n 3. **By Date** (2024/Q1/, 2024/Q2/, etc.)\n 4. **By Tax Category** (Deductible/, Personal/, etc.)\n 5. **Custom** (describe your structure)\n \n Or I can use a default structure: Year/Category/Vendor\n ```\n\n4. **Create Standardized Filename**\n \n For each invoice, create a filename following this pattern:\n \n ```\n YYYY-MM-DD Vendor - Invoice - Description.ext\n ```\n \n Examples:\n - `2024-03-15 Adobe - Invoice - Creative Cloud.pdf`\n - `2024-01-10 Amazon - Receipt - Office Supplies.pdf`\n - `2023-12-01 Stripe - Invoice - Monthly Payment Processing.pdf`\n \n **Filename Best Practices**:\n - Remove special characters except hyphens\n - Capitalize vendor names properly\n - Keep descriptions concise but meaningful\n - Use consistent date format (YYYY-MM-DD) for sorting\n - Preserve original file extension\n\n5. **Execute Organization**\n \n Before moving files, show the plan:\n \n ```markdown\n # Organization Plan\n \n ## Proposed Structure\n ```\n Invoices/\n โ”œโ”€โ”€ 2023/\n โ”‚ โ”œโ”€โ”€ Software/\n โ”‚ โ”‚ โ”œโ”€โ”€ Adobe/\n โ”‚ โ”‚ โ””โ”€โ”€ Microsoft/\n โ”‚ โ”œโ”€โ”€ Services/\n โ”‚ โ””โ”€โ”€ Office/\n โ””โ”€โ”€ 2024/\n โ”œโ”€โ”€ Software/\n โ”œโ”€โ”€ Services/\n โ””โ”€โ”€ Office/\n ```\n \n ## Sample Changes\n \n Before: `invoice_adobe_march.pdf`\n After: `2024-03-15 Adobe - Invoice - Creative Cloud.pdf`\n Location: `Invoices/2024/Software/Adobe/`\n \n Before: `IMG_2847.jpg`\n After: `2024-02-10 Staples - Receipt - Office Supplies.jpg`\n Location: `Invoices/2024/Office/Staples/`\n \n Process [X] files? (yes/no)\n ```\n \n After approval:\n ```bash\n # Create folder structure\n mkdir -p \"Invoices/2024/Software/Adobe\"\n \n # Copy (don't move) to preserve originals\n cp \"original.pdf\" \"Invoices/2024/Software/Adobe/2024-03-15 Adobe - Invoice - Creative Cloud.pdf\"\n \n # Or move if user prefers\n mv \"original.pdf\" \"new/path/standardized-name.pdf\"\n ```\n\n6. **Generate Summary Report**\n \n Create a CSV file with all invoice details:\n \n ```csv\n Date,Vendor,Invoice Number,Description,Amount,Category,File Path\n 2024-03-15,Adobe,INV-12345,Creative Cloud,52.99,Software,Invoices/2024/Software/Adobe/2024-03-15 Adobe - Invoice - Creative Cloud.pdf\n 2024-03-10,Amazon,123-4567890-1234567,Office Supplies,127.45,Office,Invoices/2024/Office/Amazon/2024-03-10 Amazon - Receipt - Office Supplies.pdf\n ...\n ```\n \n This CSV is useful for:\n - Importing into accounting software\n - Sharing with accountants\n - Expense tracking and reporting\n - Tax preparation\n\n7. **Provide Completion Summary**\n \n ```markdown\n # Organization Complete! ๐Ÿ“Š\n \n ## Summary\n - **Processed**: [X] invoices\n - **Date range**: [earliest] to [latest]\n - **Total amount**: $[sum] (if amounts extracted)\n - **Vendors**: [Y] unique vendors\n \n ## New Structure\n ```\n Invoices/\n โ”œโ”€โ”€ 2024/ (45 files)\n โ”‚ โ”œโ”€โ”€ Software/ (23 files)\n โ”‚ โ”œโ”€โ”€ Services/ (12 files)\n โ”‚ โ””โ”€โ”€ Office/ (10 files)\n โ””โ”€โ”€ 2023/ (12 files)\n ```\n \n ## Files Created\n - `/Invoices/` - Organized invoices\n - `/Invoices/invoice-summary.csv` - Spreadsheet for accounting\n - `/Invoices/originals/` - Original files (if copied)\n \n ## Files Needing Review\n [List any files where information couldn't be extracted completely]\n \n ## Next Steps\n 1. Review the `invoice-summary.csv` file\n 2. Check files in \"Needs Review\" folder\n 3. Import CSV into your accounting software\n 4. Set up auto-organization for future invoices\n \n Ready for tax season! ๐ŸŽ‰\n ```\n\n## Examples\n\n### Example 1: Tax Preparation (From Martin Merschroth)\n\n**User**: \"I have a messy folder of invoices for taxes. Sort them and rename properly.\"\n\n**Process**:\n1. Scans folder: finds 147 PDFs and images\n2. Reads each invoice to extract:\n - Date\n - Vendor name\n - Invoice number\n - Product/service description\n3. Renames all files: `YYYY-MM-DD Vendor - Invoice - Product.pdf`\n4. Organizes into: `2024/Software/`, `2024/Travel/`, etc.\n5. Creates `invoice-summary.csv` for accountant\n6. Result: Tax-ready organized invoices in minutes\n\n### Example 2: Monthly Expense Reconciliation\n\n**User**: \"Organize my business receipts from last month by category.\"\n\n**Output**:\n```markdown\n# March 2024 Receipts Organized\n\n## By Category\n- Software & Tools: $847.32 (12 invoices)\n- Office Supplies: $234.18 (8 receipts)\n- Travel & Meals: $1,456.90 (15 receipts)\n- Professional Services: $2,500.00 (3 invoices)\n\nTotal: $5,038.40\n\nAll receipts renamed and filed in:\n`Business-Receipts/2024/03-March/[Category]/`\n\nCSV export: `march-2024-expenses.csv`\n```\n\n### Example 3: Multi-Year Archive\n\n**User**: \"I have 3 years of random invoices. Organize them by year, then by vendor.\"\n\n**Output**: Creates structure:\n```\nInvoices/\nโ”œโ”€โ”€ 2022/\nโ”‚ โ”œโ”€โ”€ Adobe/\nโ”‚ โ”œโ”€โ”€ Amazon/\nโ”‚ โ””โ”€โ”€ ...\nโ”œโ”€โ”€ 2023/\nโ”‚ โ”œโ”€โ”€ Adobe/\nโ”‚ โ”œโ”€โ”€ Amazon/\nโ”‚ โ””โ”€โ”€ ...\nโ””โ”€โ”€ 2024/\n โ”œโ”€โ”€ Adobe/\n โ”œโ”€โ”€ Amazon/\n โ””โ”€โ”€ ...\n```\n\nEach file properly renamed with date and description.\n\n### Example 4: Email Downloads Cleanup\n\n**User**: \"I download invoices from Gmail. They're all named 'invoice.pdf', 'invoice(1).pdf', etc. Fix this mess.\"\n\n**Output**:\n```markdown\nFound 89 files all named \"invoice*.pdf\"\n\nReading each file to extract real information...\n\nRenamed examples:\n- invoice.pdf โ†’ 2024-03-15 Shopify - Invoice - Monthly Subscription.pdf\n- invoice(1).pdf โ†’ 2024-03-14 Google - Invoice - Workspace.pdf\n- invoice(2).pdf โ†’ 2024-03-10 Netlify - Invoice - Pro Plan.pdf\n\nAll files renamed and organized by vendor.\n```\n\n## Common Organization Patterns\n\n### By Vendor (Simple)\n```\nInvoices/\nโ”œโ”€โ”€ Adobe/\nโ”œโ”€โ”€ Amazon/\nโ”œโ”€โ”€ Google/\nโ””โ”€โ”€ Microsoft/\n```\n\n### By Year and Category (Tax-Friendly)\n```\nInvoices/\nโ”œโ”€โ”€ 2023/\nโ”‚ โ”œโ”€โ”€ Software/\nโ”‚ โ”œโ”€โ”€ Hardware/\nโ”‚ โ”œโ”€โ”€ Services/\nโ”‚ โ””โ”€โ”€ Travel/\nโ””โ”€โ”€ 2024/\n โ””โ”€โ”€ ...\n```\n\n### By Quarter (Detailed Tracking)\n```\nInvoices/\nโ”œโ”€โ”€ 2024/\nโ”‚ โ”œโ”€โ”€ Q1/\nโ”‚ โ”‚ โ”œโ”€โ”€ Software/\nโ”‚ โ”‚ โ”œโ”€โ”€ Office/\nโ”‚ โ”‚ โ””โ”€โ”€ Travel/\nโ”‚ โ””โ”€โ”€ Q2/\nโ”‚ โ””โ”€โ”€ ...\n```\n\n### By Tax Category (Accountant-Ready)\n```\nInvoices/\nโ”œโ”€โ”€ Deductible/\nโ”‚ โ”œโ”€โ”€ Software/\nโ”‚ โ”œโ”€โ”€ Office/\nโ”‚ โ””โ”€โ”€ Professional-Services/\nโ”œโ”€โ”€ Partially-Deductible/\nโ”‚ โ””โ”€โ”€ Meals-Travel/\nโ””โ”€โ”€ Personal/\n```\n\n## Automation Setup\n\nFor ongoing organization:\n\n```\nCreate a script that watches my ~/Downloads/invoices folder \nand auto-organizes any new invoice files using our standard \nnaming and folder structure.\n```\n\nThis creates a persistent solution that organizes invoices as they arrive.\n\n## Pro Tips\n\n1. **Scan emails to PDF**: Use Preview or similar to save email invoices as PDFs first\n2. **Consistent downloads**: Save all invoices to one folder for batch processing\n3. **Monthly routine**: Organize invoices monthly, not annually\n4. **Backup originals**: Keep original files before reorganizing\n5. **Include amounts in CSV**: Useful for budget tracking\n6. **Tag by deductibility**: Note which expenses are tax-deductible\n7. **Keep receipts 7 years**: Standard audit period\n\n## Handling Special Cases\n\n### Missing Information\nIf date/vendor can't be extracted:\n- Flag file for manual review\n- Use file modification date as fallback\n- Create \"Needs-Review/\" folder\n\n### Duplicate Invoices\nIf same invoice appears multiple times:\n- Compare file hashes\n- Keep highest quality version\n- Note duplicates in summary\n\n### Multi-Page Invoices\nFor invoices split across files:\n- Merge PDFs if needed\n- Use consistent naming for parts\n- Note in CSV if invoice is split\n\n### Non-Standard Formats\nFor unusual receipt formats:\n- Extract what's possible\n- Standardize what you can\n- Flag for review if critical info missing\n\n## Related Use Cases\n\n- Creating expense reports for reimbursement\n- Organizing bank statements\n- Managing vendor contracts\n- Archiving old financial records\n- Preparing for audits\n- Tracking subscription costs over time","schemaVersion":1},"repoUrl":"https://github.com/Prat011/awesome-llm-skills/tree/master/invoice-organizer","tags":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"awesome-llm-skills","audit":{"files":["slack-gif-creator/requirements.txt"],"binaries":[],"findings":[{"kind":"dependency","rule":"DP-04","message":"Python dependencies are not pinned and there is no lock file.","surface":"slack-gif-creator/requirements.txt","evidence":"pillow>=10.0.0, imageio>=2.31.0, imageio-ffmpeg>=0.4.9, numpy>=1.24.0","severity":"medium"}],"packages":4,"auditedAt":"2026-09-25T11:52:30.068Z","lockfiles":[]},"forks":313,"owner":"Prat011","stars":1761,"topics":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms","openai","opencode","qwen","qwen-coder","skills"],"license":null,"fullName":"Prat011/awesome-llm-skills","homepage":null,"language":"Python","pushedAt":"2026-07-14T09:53:56Z","avatarUrl":"https://avatars.githubusercontent.com/u/67639393?v=4","crawledAt":"2026-09-25T11:52:22.319Z","openIssues":170,"manifestFile":"SKILL.md","manifestPath":"invoice-organizer/SKILL.md","defaultBranch":"master"},"readme":"# Invoice Organizer\n\nThis skill transforms chaotic folders of invoices, receipts, and financial documents into a clean, tax-ready filing system without manual effort.\n\n## When to Use This Skill\n\n- Preparing for tax season and need organized records\n- Managing business expenses across multiple vendors\n- Organizing receipts from a messy folder or email downloads\n- Setting up automated invoice filing for ongoing bookkeeping\n- Archiving financial records by year or category\n- Reconciling expenses for reimbursement\n- Preparing documentation for accountants\n\n## What This Skill Does\n\n1. **Reads Invoice Content**: Extracts information from PDFs, images, and documents:\n - Vendor/company name\n - Invoice number\n - Date\n - Amount\n - Product or service description\n - Payment method\n\n2. **Renames Files Consistently**: Creates standardized filenames:\n - Format: `YYYY-MM-DD Vendor - Invoice - ProductOrService.pdf`\n - Examples: `2024-03-15 Adobe - Invoice - Creative Cloud.pdf`\n\n3. **Organizes by Category**: Sorts into logical folders:\n - By vendor\n - By expense category (software, office, travel, etc.)\n - By time period (year, quarter, month)\n - By tax category (deductible, personal, etc.)\n\n4. **Handles Multiple Formats**: Works with:\n - PDF invoices\n - Scanned receipts (JPG, PNG)\n - Email attachments\n - Screenshots\n - Bank statements\n\n5. **Maintains Originals**: Preserves original files while organizing copies\n\n## How to Use\n\n### Basic Usage\n\nNavigate to your messy invoice folder:\n```\ncd ~/Desktop/receipts-to-sort\n```\n\nThen ask Claude Code:\n```\nOrganize these invoices for taxes\n```\n\nOr more specifically:\n```\nRead all invoices in this folder, rename them to \n\"YYYY-MM-DD Vendor - Invoice - Product.pdf\" format, \nand organize them by vendor\n```\n\n### Advanced Organization\n\n```\nOrganize these invoices:\n1. Extract date, vendor, and description from each file\n2. Rename to standard format\n3. Sort into folders by expense category (Software, Office, Travel, etc.)\n4. Create a CSV spreadsheet with all invoice details for my accountant\n```\n\n## Instructions\n\nWhen a user requests invoice organization:\n\n1. **Scan the Folder**\n \n Identify all invoice files:\n ```bash\n # Find all invoice-related files\n find . -type f \\( -name \"*.pdf\" -o -name \"*.jpg\" -o -name \"*.png\" \\) -print\n ```\n \n Report findings:\n - Total number of files\n - File types\n - Date range (if discernible from names)\n - Current organization (or lack thereof)\n\n2. **Extract Information from Each File**\n \n For each invoice, extract:\n \n **From PDF invoices**:\n - Use text extraction to read invoice content\n - Look for common patterns:\n - \"Invoice Date:\", \"Date:\", \"Issued:\"\n - \"Invoice #:\", \"Invoice Number:\"\n - Company name (usually at top)\n - \"Amount Due:\", \"Total:\", \"Amount:\"\n - \"Description:\", \"Service:\", \"Product:\"\n \n **From image receipts**:\n - Read visible text from images\n - Identify vendor name (often at top)\n - Look for date (common formats)\n - Find total amount\n \n **Fallback for unclear files**:\n - Use filename clues\n - Check file creation/modification date\n - Flag for manual review if critical info missing\n\n3. **Determine Organization Strategy**\n \n Ask user preference if not specified:\n \n ```markdown\n I found [X] invoices from [date range].\n \n How would you like them organized?\n \n 1. **By Vendor** (Adobe/, Amazon/, Stripe/, etc.)\n 2. **By Category** (Software/, Office Supplies/, Travel/, etc.)\n 3. **By Date** (2024/Q1/, 2024/Q2/, etc.)\n 4. **By Tax Category** (Deductible/, Personal/, etc.)\n 5. **Custom** (describe your structure)\n \n Or I can use a default structure: Year/Category/Vendor\n ```\n\n4. **Create Standardized Filename**\n \n For each invoice, create a filename following this pattern:\n \n ```\n YYYY-MM-DD Vendor - Invoice - Description.ext\n ```\n \n Examples:\n - `2024-03-15 Adobe - Invoice - Creative Cloud.pdf`\n - `2024-01-10 Amazo","createdAt":"2026-09-25T11:52:30.259Z","updatedAt":"2026-09-25T11:52:30.259Z"},{"id":"cmugwiibl026bqu06g82ruev1","slug":"prat011-awesome-llm-skills-lead-research-assistant","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.","authorId":"gh:prat011","authorName":"Prat011","version":"0.1.0","category":"Prompt","securityLevel":"Community","downloadsCount":0,"githubStars":1761,"pricePerCall":0,"manifest":{"name":"lead-research-assistant","tools":[],"category":"Prompt","entrypoint":{"type":"prompt"},"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.","permissions":[],"systemPrompt":"# Lead Research Assistant\n\nThis 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.\n\n## When to Use This Skill\n\n- Finding potential customers or clients for your product/service\n- Building a list of companies to reach out to for partnerships\n- Identifying target accounts for sales outreach\n- Researching companies that match your ideal customer profile\n- Preparing for business development activities\n\n## What This Skill Does\n\n1. **Understands Your Business**: Analyzes your product/service, value proposition, and target market\n2. **Identifies Target Companies**: Finds companies that match your ideal customer profile based on:\n - Industry and sector\n - Company size and location\n - Technology stack and tools they use\n - Growth stage and funding\n - Pain points your product solves\n3. **Prioritizes Leads**: Ranks companies based on fit score and relevance\n4. **Provides Contact Strategies**: Suggests how to approach each lead with personalized messaging\n5. **Enriches Data**: Gathers relevant information about decision-makers and company context\n\n## How to Use\n\n### Basic Usage\n\nSimply describe your product/service and what you're looking for:\n\n```\nI'm building [product description]. Find me 10 companies in [location/industry] \nthat would be good leads for this.\n```\n\n### With Your Codebase\n\nFor even better results, run this from your product's source code directory:\n\n```\nLook at what I'm building in this repository and identify the top 10 companies \nin [location/industry] that would benefit from this product.\n```\n\n### Advanced Usage\n\nFor more targeted research:\n\n```\nMy product: [description]\nIdeal customer profile:\n- Industry: [industry]\n- Company size: [size range]\n- Location: [location]\n- Current pain points: [pain points]\n- Technologies they use: [tech stack]\n\nFind me 20 qualified leads with contact strategies for each.\n```\n\n## Instructions\n\nWhen a user requests lead research:\n\n1. **Understand the Product/Service**\n - If in a code directory, analyze the codebase to understand the product\n - Ask clarifying questions about the value proposition\n - Identify key features and benefits\n - Understand what problems it solves\n\n2. **Define Ideal Customer Profile**\n - Determine target industries and sectors\n - Identify company size ranges\n - Consider geographic preferences\n - Understand relevant pain points\n - Note any technology requirements\n\n3. **Research and Identify Leads**\n - Search for companies matching the criteria\n - Look for signals of need (job postings, tech stack, recent news)\n - Consider growth indicators (funding, expansion, hiring)\n - Identify companies with complementary products/services\n - Check for budget indicators\n\n4. **Prioritize and Score**\n - Create a fit score (1-10) for each lead\n - Consider factors like:\n - Alignment with ICP\n - Signals of immediate need\n - Budget availability\n - Competitive landscape\n - Timing indicators\n\n5. **Provide Actionable Output**\n \n For each lead, provide:\n - **Company Name** and website\n - **Why They're a Good Fit**: Specific reasons based on their business\n - **Priority Score**: 1-10 with explanation\n - **Decision Maker**: Role/title to target (e.g., \"VP of Engineering\")\n - **Contact Strategy**: Personalized approach suggestions\n - **Value Proposition**: How your product solves their specific problem\n - **Conversation Starters**: Specific points to mention in outreach\n - **LinkedIn URL**: If available, for easy connection\n\n6. **Format the Output**\n\n Present results in a clear, scannable format:\n\n ```markdown\n # Lead Research Results\n \n ## Summary\n - Total leads found: [X]\n - High priority (8-10): [X]\n - Medium priority (5-7): [X]\n - Average fit score: [X]\n \n ---\n \n ## Lead 1: [Company Name]\n \n **Website**: [URL]\n **Priority Score**: [X/10]\n **Industry**: [Industry]\n **Size**: [Employee count/revenue range]\n \n **Why They're a Good Fit**:\n [2-3 specific reasons based on their business]\n \n **Target Decision Maker**: [Role/Title]\n **LinkedIn**: [URL if available]\n \n **Value Proposition for Them**:\n [Specific benefit for this company]\n \n **Outreach Strategy**:\n [Personalized approach - mention specific pain points, recent company news, or relevant context]\n \n **Conversation Starters**:\n - [Specific point 1]\n - [Specific point 2]\n \n ---\n \n [Repeat for each lead]\n ```\n\n7. **Offer Next Steps**\n - Suggest saving results to a CSV for CRM import\n - Offer to draft personalized outreach messages\n - Recommend prioritization based on timing\n - Suggest follow-up research for top leads\n\n## Examples\n\n### Example 1: From Lenny's Newsletter\n\n**User**: \"I'm building a tool that masks sensitive data in AI coding assistant queries. Find potential leads.\"\n\n**Output**: Creates a prioritized list of companies that:\n- Use AI coding assistants (Copilot, Cursor, etc.)\n- Handle sensitive data (fintech, healthcare, legal)\n- Have evidence in their GitHub repos of using coding agents\n- May have accidentally exposed sensitive data in code\n- Includes LinkedIn URLs of relevant decision-makers\n\n### Example 2: Local Business\n\n**User**: \"I run a consulting practice for remote team productivity. Find me 10 companies in the Bay Area that recently went remote.\"\n\n**Output**: Identifies companies that:\n- Recently posted remote job listings\n- Announced remote-first policies\n- Are hiring distributed teams\n- Show signs of remote work challenges\n- Provides personalized outreach strategies for each\n\n## Tips for Best Results\n\n- **Be specific** about your product and its unique value\n- **Run from your codebase** if applicable for automatic context\n- **Provide context** about your ideal customer profile\n- **Specify constraints** like industry, location, or company size\n- **Request follow-up** research on promising leads for deeper insights\n\n## Related Use Cases\n\n- Drafting personalized outreach emails after identifying leads\n- Building a CRM-ready CSV of qualified prospects\n- Researching specific companies in detail\n- Analyzing competitor customer bases\n- Identifying partnership opportunities","schemaVersion":1},"repoUrl":"https://github.com/Prat011/awesome-llm-skills/tree/master/lead-research-assistant","tags":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"awesome-llm-skills","audit":{"files":["slack-gif-creator/requirements.txt"],"binaries":[],"findings":[{"kind":"dependency","rule":"DP-04","message":"Python dependencies are not pinned and there is no lock file.","surface":"slack-gif-creator/requirements.txt","evidence":"pillow>=10.0.0, imageio>=2.31.0, imageio-ffmpeg>=0.4.9, numpy>=1.24.0","severity":"medium"}],"packages":4,"auditedAt":"2026-09-25T11:52:30.068Z","lockfiles":[]},"forks":313,"owner":"Prat011","stars":1761,"topics":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms","openai","opencode","qwen","qwen-coder","skills"],"license":null,"fullName":"Prat011/awesome-llm-skills","homepage":null,"language":"Python","pushedAt":"2026-07-14T09:53:56Z","avatarUrl":"https://avatars.githubusercontent.com/u/67639393?v=4","crawledAt":"2026-09-25T11:52:22.319Z","openIssues":170,"manifestFile":"SKILL.md","manifestPath":"lead-research-assistant/SKILL.md","defaultBranch":"master"},"readme":"# Lead Research Assistant\n\nThis 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.\n\n## When to Use This Skill\n\n- Finding potential customers or clients for your product/service\n- Building a list of companies to reach out to for partnerships\n- Identifying target accounts for sales outreach\n- Researching companies that match your ideal customer profile\n- Preparing for business development activities\n\n## What This Skill Does\n\n1. **Understands Your Business**: Analyzes your product/service, value proposition, and target market\n2. **Identifies Target Companies**: Finds companies that match your ideal customer profile based on:\n - Industry and sector\n - Company size and location\n - Technology stack and tools they use\n - Growth stage and funding\n - Pain points your product solves\n3. **Prioritizes Leads**: Ranks companies based on fit score and relevance\n4. **Provides Contact Strategies**: Suggests how to approach each lead with personalized messaging\n5. **Enriches Data**: Gathers relevant information about decision-makers and company context\n\n## How to Use\n\n### Basic Usage\n\nSimply describe your product/service and what you're looking for:\n\n```\nI'm building [product description]. Find me 10 companies in [location/industry] \nthat would be good leads for this.\n```\n\n### With Your Codebase\n\nFor even better results, run this from your product's source code directory:\n\n```\nLook at what I'm building in this repository and identify the top 10 companies \nin [location/industry] that would benefit from this product.\n```\n\n### Advanced Usage\n\nFor more targeted research:\n\n```\nMy product: [description]\nIdeal customer profile:\n- Industry: [industry]\n- Company size: [size range]\n- Location: [location]\n- Current pain points: [pain points]\n- Technologies they use: [tech stack]\n\nFind me 20 qualified leads with contact strategies for each.\n```\n\n## Instructions\n\nWhen a user requests lead research:\n\n1. **Understand the Product/Service**\n - If in a code directory, analyze the codebase to understand the product\n - Ask clarifying questions about the value proposition\n - Identify key features and benefits\n - Understand what problems it solves\n\n2. **Define Ideal Customer Profile**\n - Determine target industries and sectors\n - Identify company size ranges\n - Consider geographic preferences\n - Understand relevant pain points\n - Note any technology requirements\n\n3. **Research and Identify Leads**\n - Search for companies matching the criteria\n - Look for signals of need (job postings, tech stack, recent news)\n - Consider growth indicators (funding, expansion, hiring)\n - Identify companies with complementary products/services\n - Check for budget indicators\n\n4. **Prioritize and Score**\n - Create a fit score (1-10) for each lead\n - Consider factors like:\n - Alignment with ICP\n - Signals of immediate need\n - Budget availability\n - Competitive landscape\n - Timing indicators\n\n5. **Provide Actionable Output**\n \n For each lead, provide:\n - **Company Name** and website\n - **Why They're a Good Fit**: Specific reasons based on their business\n - **Priority Score**: 1-10 with explanation\n - **Decision Maker**: Role/title to target (e.g., \"VP of Engineering\")\n - **Contact Strategy**: Personalized approach suggestions\n - **Value Proposition**: How your product solves their specific problem\n - **Conversation Starters**: Specific points to mention in outreach\n - **LinkedIn URL**: If available, for easy connection\n\n6. **Format the Output**\n\n Present results in a clear, scannable format:\n\n ```markdown\n # Lead Research Results\n \n ## Summary\n - Total leads found: [X]\n - High priority (8-10): [X]\n - Medium priority (5-7): [X]\n - Average fit score: [X]\n \n ---\n \n ## Lead 1: [Company Name]\n \n **Website**: [URL]\n **Priority Score**: [X/10","createdAt":"2026-09-25T11:52:30.273Z","updatedAt":"2026-09-25T11:52:30.273Z"},{"id":"cmugwiic2026equ063zpuzxvf","slug":"prat011-awesome-llm-skills-mcp-builder","name":"mcp-builder","description":"Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).","authorId":"gh:prat011","authorName":"Prat011","version":"0.1.0","category":"Prompt","securityLevel":"Community","downloadsCount":0,"githubStars":1761,"pricePerCall":0,"manifest":{"name":"mcp-builder","tools":[],"category":"Prompt","entrypoint":{"type":"prompt"},"description":"Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).","permissions":[],"systemPrompt":"# MCP Server Development Guide\n\n## Overview\n\nTo create high-quality MCP (Model Context Protocol) servers that enable LLMs to effectively interact with external services, use this skill. An MCP server provides tools that allow LLMs to access external services and APIs. The quality of an MCP server is measured by how well it enables LLMs to accomplish real-world tasks using the tools provided.\n\n---\n\n# Process\n\n## ๐Ÿš€ High-Level Workflow\n\nCreating a high-quality MCP server involves four main phases:\n\n### Phase 1: Deep Research and Planning\n\n#### 1.1 Understand Agent-Centric Design Principles\n\nBefore diving into implementation, understand how to design tools for AI agents by reviewing these principles:\n\n**Build for Workflows, Not Just API Endpoints:**\n- Don't simply wrap existing API endpoints - build thoughtful, high-impact workflow tools\n- Consolidate related operations (e.g., `schedule_event` that both checks availability and creates event)\n- Focus on tools that enable complete tasks, not just individual API calls\n- Consider what workflows agents actually need to accomplish\n\n**Optimize for Limited Context:**\n- Agents have constrained context windows - make every token count\n- Return high-signal information, not exhaustive data dumps\n- Provide \"concise\" vs \"detailed\" response format options\n- Default to human-readable identifiers over technical codes (names over IDs)\n- Consider the agent's context budget as a scarce resource\n\n**Design Actionable Error Messages:**\n- Error messages should guide agents toward correct usage patterns\n- Suggest specific next steps: \"Try using filter='active_only' to reduce results\"\n- Make errors educational, not just diagnostic\n- Help agents learn proper tool usage through clear feedback\n\n**Follow Natural Task Subdivisions:**\n- Tool names should reflect how humans think about tasks\n- Group related tools with consistent prefixes for discoverability\n- Design tools around natural workflows, not just API structure\n\n**Use Evaluation-Driven Development:**\n- Create realistic evaluation scenarios early\n- Let agent feedback drive tool improvements\n- Prototype quickly and iterate based on actual agent performance\n\n#### 1.3 Study MCP Protocol Documentation\n\n**Fetch the latest MCP protocol documentation:**\n\nUse WebFetch to load: `https://modelcontextprotocol.io/llms-full.txt`\n\nThis comprehensive document contains the complete MCP specification and guidelines.\n\n#### 1.4 Study Framework Documentation\n\n**Load and read the following reference files:**\n\n- **MCP Best Practices**: [๐Ÿ“‹ View Best Practices](./reference/mcp_best_practices.md) - Core guidelines for all MCP servers\n\n**For Python implementations, also load:**\n- **Python SDK Documentation**: Use WebFetch to load `https://raw.githubusercontent.com/modelcontextprotocol/python-sdk/main/README.md`\n- [๐Ÿ Python Implementation Guide](./reference/python_mcp_server.md) - Python-specific best practices and examples\n\n**For Node/TypeScript implementations, also load:**\n- **TypeScript SDK Documentation**: Use WebFetch to load `https://raw.githubusercontent.com/modelcontextprotocol/typescript-sdk/main/README.md`\n- [โšก TypeScript Implementation Guide](./reference/node_mcp_server.md) - Node/TypeScript-specific best practices and examples\n\n#### 1.5 Exhaustively Study API Documentation\n\nTo integrate a service, read through **ALL** available API documentation:\n- Official API reference documentation\n- Authentication and authorization requirements\n- Rate limiting and pagination patterns\n- Error responses and status codes\n- Available endpoints and their parameters\n- Data models and schemas\n\n**To gather comprehensive information, use web search and the WebFetch tool as needed.**\n\n#### 1.6 Create a Comprehensive Implementation Plan\n\nBased on your research, create a detailed plan that includes:\n\n**Tool Selection:**\n- List the most valuable endpoints/operations to implement\n- Prioritize tools that enable the most common and important use cases\n- Consider which tools work together to enable complex workflows\n\n**Shared Utilities and Helpers:**\n- Identify common API request patterns\n- Plan pagination helpers\n- Design filtering and formatting utilities\n- Plan error handling strategies\n\n**Input/Output Design:**\n- Define input validation models (Pydantic for Python, Zod for TypeScript)\n- Design consistent response formats (e.g., JSON or Markdown), and configurable levels of detail (e.g., Detailed or Concise)\n- Plan for large-scale usage (thousands of users/resources)\n- Implement character limits and truncation strategies (e.g., 25,000 tokens)\n\n**Error Handling Strategy:**\n- Plan graceful failure modes\n- Design clear, actionable, LLM-friendly, natural language error messages which prompt further action\n- Consider rate limiting and timeout scenarios\n- Handle authentication and authorization errors\n\n---\n\n### Phase 2: Implementation\n\nNow that you have a comprehensive plan, begin implementation following language-specific best practices.\n\n#### 2.1 Set Up Project Structure\n\n**For Python:**\n- Create a single `.py` file or organize into modules if complex (see [๐Ÿ Python Guide](./reference/python_mcp_server.md))\n- Use the MCP Python SDK for tool registration\n- Define Pydantic models for input validation\n\n**For Node/TypeScript:**\n- Create proper project structure (see [โšก TypeScript Guide](./reference/node_mcp_server.md))\n- Set up `package.json` and `tsconfig.json`\n- Use MCP TypeScript SDK\n- Define Zod schemas for input validation\n\n#### 2.2 Implement Core Infrastructure First\n\n**To begin implementation, create shared utilities before implementing tools:**\n- API request helper functions\n- Error handling utilities\n- Response formatting functions (JSON and Markdown)\n- Pagination helpers\n- Authentication/token management\n\n#### 2.3 Implement Tools Systematically\n\nFor each tool in the plan:\n\n**Define Input Schema:**\n- Use Pydantic (Python) or Zod (TypeScript) for validation\n- Include proper constraints (min/max length, regex patterns, min/max values, ranges)\n- Provide clear, descriptive field descriptions\n- Include diverse examples in field descriptions\n\n**Write Comprehensive Docstrings/Descriptions:**\n- One-line summary of what the tool does\n- Detailed explanation of purpose and functionality\n- Explicit parameter types with examples\n- Complete return type schema\n- Usage examples (when to use, when not to use)\n- Error handling documentation, which outlines how to proceed given specific errors\n\n**Implement Tool Logic:**\n- Use shared utilities to avoid code duplication\n- Follow async/await patterns for all I/O\n- Implement proper error handling\n- Support multiple response formats (JSON and Markdown)\n- Respect pagination parameters\n- Check character limits and truncate appropriately\n\n**Add Tool Annotations:**\n- `readOnlyHint`: true (for read-only operations)\n- `destructiveHint`: false (for non-destructive operations)\n- `idempotentHint`: true (if repeated calls have same effect)\n- `openWorldHint`: true (if interacting with external systems)\n\n#### 2.4 Follow Language-Specific Best Practices\n\n**At this point, load the appropriate language guide:**\n\n**For Python: Load [๐Ÿ Python Implementation Guide](./reference/python_mcp_server.md) and ensure the following:**\n- Using MCP Python SDK with proper tool registration\n- Pydantic v2 models with `model_config`\n- Type hints throughout\n- Async/await for all I/O operations\n- Proper imports organization\n- Module-level constants (CHARACTER_LIMIT, API_BASE_URL)\n\n**For Node/TypeScript: Load [โšก TypeScript Implementation Guide](./reference/node_mcp_server.md) and ensure the following:**\n- Using `server.registerTool` properly\n- Zod schemas with `.strict()`\n- TypeScript strict mode enabled\n- No `any` types - use proper types\n- Explicit Promise return types\n- Build process configured (`npm run build`)\n\n---\n\n### Phase 3: Review and Refine\n\nAfter initial implementation:\n\n#### 3.1 Code Quality Review\n\nTo ensure quality, review the code for:\n- **DRY Principle**: No duplicated code between tools\n- **Composability**: Shared logic extracted into functions\n- **Consistency**: Similar operations return similar formats\n- **Error Handling**: All external calls have error handling\n- **Type Safety**: Full type coverage (Python type hints, TypeScript types)\n- **Documentation**: Every tool has comprehensive docstrings/descriptions\n\n#### 3.2 Test and Build\n\n**Important:** MCP servers are long-running processes that wait for requests over stdio/stdin or sse/http. Running them directly in your main process (e.g., `python server.py` or `node dist/index.js`) will cause your process to hang indefinitely.\n\n**Safe ways to test the server:**\n- Use the evaluation harness (see Phase 4) - recommended approach\n- Run the server in tmux to keep it outside your main process\n- Use a timeout when testing: `timeout 5s python server.py`\n\n**For Python:**\n- Verify Python syntax: `python -m py_compile your_server.py`\n- Check imports work correctly by reviewing the file\n- To manually test: Run server in tmux, then test with evaluation harness in main process\n- Or use the evaluation harness directly (it manages the server for stdio transport)\n\n**For Node/TypeScript:**\n- Run `npm run build` and ensure it completes without errors\n- Verify dist/index.js is created\n- To manually test: Run server in tmux, then test with evaluation harness in main process\n- Or use the evaluation harness directly (it manages the server for stdio transport)\n\n#### 3.3 Use Quality Checklist\n\nTo verify implementation quality, load the appropriate checklist from the language-specific guide:\n- Python: see \"Quality Checklist\" in [๐Ÿ Python Guide](./reference/python_mcp_server.md)\n- Node/TypeScript: see \"Quality Checklist\" in [โšก TypeScript Guide](./reference/node_mcp_server.md)\n\n---\n\n### Phase 4: Create Evaluations\n\nAfter implementing your MCP server, create comprehensive evaluations to test its effectiveness.\n\n**Load [โœ… Evaluation Guide](./reference/evaluation.md) for complete evaluation guidelines.**\n\n#### 4.1 Understand Evaluation Purpose\n\nEvaluations test whether LLMs can effectively use your MCP server to answer realistic, complex questions.\n\n#### 4.2 Create 10 Evaluation Questions\n\nTo create effective evaluations, follow the process outlined in the evaluation guide:\n\n1. **Tool Inspection**: List available tools and understand their capabilities\n2. **Content Exploration**: Use READ-ONLY operations to explore available data\n3. **Question Generation**: Create 10 complex, realistic questions\n4. **Answer Verification**: Solve each question yourself to verify answers\n\n#### 4.3 Evaluation Requirements\n\nEach question must be:\n- **Independent**: Not dependent on other questions\n- **Read-only**: Only non-destructive operations required\n- **Complex**: Requiring multiple tool calls and deep exploration\n- **Realistic**: Based on real use cases humans would care about\n- **Verifiable**: Single, clear answer that can be verified by string comparison\n- **Stable**: Answer won't change over time\n\n#### 4.4 Output Format\n\nCreate an XML file with this structure:\n\n```xml\n\n \n Find discussions about AI model launches with animal codenames. One model needed a specific safety designation that uses the format ASL-X. What number X was being determined for the model named after a spotted wild cat?\n 3\n \n\n\n```\n\n---\n\n# Reference Files\n\n## ๐Ÿ“š Documentation Library\n\nLoad these resources as needed during development:\n\n### Core MCP Documentation (Load First)\n- **MCP Protocol**: Fetch from `https://modelcontextprotocol.io/llms-full.txt` - Complete MCP specification\n- [๐Ÿ“‹ MCP Best Practices](./reference/mcp_best_practices.md) - Universal MCP guidelines including:\n - Server and tool naming conventions\n - Response format guidelines (JSON vs Markdown)\n - Pagination best practices\n - Character limits and truncation strategies\n - Tool development guidelines\n - Security and error handling standards\n\n### SDK Documentation (Load During Phase 1/2)\n- **Python SDK**: Fetch from `https://raw.githubusercontent.com/modelcontextprotocol/python-sdk/main/README.md`\n- **TypeScript SDK**: Fetch from `https://raw.githubusercontent.com/modelcontextprotocol/typescript-sdk/main/README.md`\n\n### Language-Specific Implementation Guides (Load During Phase 2)\n- [๐Ÿ Python Implementation Guide](./reference/python_mcp_server.md) - Complete Python/FastMCP guide with:\n - Server initialization patterns\n - Pydantic model examples\n - Tool registration with `@mcp.tool`\n - Complete working examples\n - Quality checklist\n\n- [โšก TypeScript Implementation Guide](./reference/node_mcp_server.md) - Complete TypeScript guide with:\n - Project structure\n - Zod schema patterns\n - Tool registration with `server.registerTool`\n - Complete working examples\n - Quality checklist\n\n### Evaluation Guide (Load During Phase 4)\n- [โœ… Evaluation Guide](./reference/evaluation.md) - Complete evaluation creation guide with:\n - Question creation guidelines\n - Answer verification strategies\n - XML format specifications\n - Example questions and answers\n - Running an evaluation with the provided scripts","schemaVersion":1},"repoUrl":"https://github.com/Prat011/awesome-llm-skills/tree/master/mcp-builder","tags":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"awesome-llm-skills","audit":{"files":["slack-gif-creator/requirements.txt"],"binaries":[],"findings":[{"kind":"dependency","rule":"DP-04","message":"Python dependencies are not pinned and there is no lock file.","surface":"slack-gif-creator/requirements.txt","evidence":"pillow>=10.0.0, imageio>=2.31.0, imageio-ffmpeg>=0.4.9, numpy>=1.24.0","severity":"medium"}],"packages":4,"auditedAt":"2026-09-25T11:52:30.068Z","lockfiles":[]},"forks":313,"owner":"Prat011","stars":1761,"topics":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms","openai","opencode","qwen","qwen-coder","skills"],"license":"Complete terms in LICENSE.txt","fullName":"Prat011/awesome-llm-skills","homepage":null,"language":"Python","pushedAt":"2026-07-14T09:53:56Z","avatarUrl":"https://avatars.githubusercontent.com/u/67639393?v=4","crawledAt":"2026-09-25T11:52:22.319Z","openIssues":170,"manifestFile":"SKILL.md","manifestPath":"mcp-builder/SKILL.md","defaultBranch":"master"},"readme":"# MCP Server Development Guide\n\n## Overview\n\nTo create high-quality MCP (Model Context Protocol) servers that enable LLMs to effectively interact with external services, use this skill. An MCP server provides tools that allow LLMs to access external services and APIs. The quality of an MCP server is measured by how well it enables LLMs to accomplish real-world tasks using the tools provided.\n\n---\n\n# Process\n\n## ๐Ÿš€ High-Level Workflow\n\nCreating a high-quality MCP server involves four main phases:\n\n### Phase 1: Deep Research and Planning\n\n#### 1.1 Understand Agent-Centric Design Principles\n\nBefore diving into implementation, understand how to design tools for AI agents by reviewing these principles:\n\n**Build for Workflows, Not Just API Endpoints:**\n- Don't simply wrap existing API endpoints - build thoughtful, high-impact workflow tools\n- Consolidate related operations (e.g., `schedule_event` that both checks availability and creates event)\n- Focus on tools that enable complete tasks, not just individual API calls\n- Consider what workflows agents actually need to accomplish\n\n**Optimize for Limited Context:**\n- Agents have constrained context windows - make every token count\n- Return high-signal information, not exhaustive data dumps\n- Provide \"concise\" vs \"detailed\" response format options\n- Default to human-readable identifiers over technical codes (names over IDs)\n- Consider the agent's context budget as a scarce resource\n\n**Design Actionable Error Messages:**\n- Error messages should guide agents toward correct usage patterns\n- Suggest specific next steps: \"Try using filter='active_only' to reduce results\"\n- Make errors educational, not just diagnostic\n- Help agents learn proper tool usage through clear feedback\n\n**Follow Natural Task Subdivisions:**\n- Tool names should reflect how humans think about tasks\n- Group related tools with consistent prefixes for discoverability\n- Design tools around natural workflows, not just API structure\n\n**Use Evaluation-Driven Development:**\n- Create realistic evaluation scenarios early\n- Let agent feedback drive tool improvements\n- Prototype quickly and iterate based on actual agent performance\n\n#### 1.3 Study MCP Protocol Documentation\n\n**Fetch the latest MCP protocol documentation:**\n\nUse WebFetch to load: `https://modelcontextprotocol.io/llms-full.txt`\n\nThis comprehensive document contains the complete MCP specification and guidelines.\n\n#### 1.4 Study Framework Documentation\n\n**Load and read the following reference files:**\n\n- **MCP Best Practices**: [๐Ÿ“‹ View Best Practices](./reference/mcp_best_practices.md) - Core guidelines for all MCP servers\n\n**For Python implementations, also load:**\n- **Python SDK Documentation**: Use WebFetch to load `https://raw.githubusercontent.com/modelcontextprotocol/python-sdk/main/README.md`\n- [๐Ÿ Python Implementation Guide](./reference/python_mcp_server.md) - Python-specific best practices and examples\n\n**For Node/TypeScript implementations, also load:**\n- **TypeScript SDK Documentation**: Use WebFetch to load `https://raw.githubusercontent.com/modelcontextprotocol/typescript-sdk/main/README.md`\n- [โšก TypeScript Implementation Guide](./reference/node_mcp_server.md) - Node/TypeScript-specific best practices and examples\n\n#### 1.5 Exhaustively Study API Documentation\n\nTo integrate a service, read through **ALL** available API documentation:\n- Official API reference documentation\n- Authentication and authorization requirements\n- Rate limiting and pagination patterns\n- Error responses and status codes\n- Available endpoints and their parameters\n- Data models and schemas\n\n**To gather comprehensive information, use web search and the WebFetch tool as needed.**\n\n#### 1.6 Create a Comprehensive Implementation Plan\n\nBased on your research, create a detailed plan that includes:\n\n**Tool Selection:**\n- List the most valuable endpoints/operations to implement\n- Prioritize tools that enable the most common and important use cases\n- Consider which tools work together to ena","createdAt":"2026-09-25T11:52:30.290Z","updatedAt":"2026-09-25T11:52:30.290Z"},{"id":"cmugwiicc026hqu06lyictyih","slug":"prat011-awesome-llm-skills-meeting-insights-analyzer","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.","authorId":"gh:prat011","authorName":"Prat011","version":"0.1.0","category":"Prompt","securityLevel":"Community","downloadsCount":0,"githubStars":1761,"pricePerCall":0,"manifest":{"name":"meeting-insights-analyzer","tools":[],"category":"Prompt","entrypoint":{"type":"prompt"},"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.","permissions":[],"systemPrompt":"# Meeting Insights Analyzer\n\nThis skill transforms your meeting transcripts into actionable insights about your communication patterns, helping you become a more effective communicator and leader.\n\n## When to Use This Skill\n\n- Analyzing your communication patterns across multiple meetings\n- Getting feedback on your leadership and facilitation style\n- Identifying when you avoid difficult conversations\n- Understanding your speaking habits and filler words\n- Tracking improvement in communication skills over time\n- Preparing for performance reviews with concrete examples\n- Coaching team members on their communication style\n\n## What This Skill Does\n\n1. **Pattern Recognition**: Identifies recurring behaviors across meetings like:\n - Conflict avoidance or indirect communication\n - Speaking ratios and turn-taking\n - Question-asking vs. statement-making patterns\n - Active listening indicators\n - Decision-making approaches\n\n2. **Communication Analysis**: Evaluates communication effectiveness:\n - Clarity and directness\n - Use of filler words and hedging language\n - Tone and sentiment patterns\n - Meeting control and facilitation\n\n3. **Actionable Feedback**: Provides specific, timestamped examples with:\n - What happened\n - Why it matters\n - How to improve\n\n4. **Trend Tracking**: Compares patterns over time when analyzing multiple meetings\n\n## How to Use\n\n### Basic Setup\n\n1. Download your meeting transcripts to a folder (e.g., `~/meetings/`)\n2. Navigate to that folder in Claude Code\n3. Ask for the analysis you want\n\n### Quick Start Examples\n\n```\nAnalyze all meetings in this folder and tell me when I avoided conflict.\n```\n\n```\nLook at my meetings from the past month and identify my communication patterns.\n```\n\n```\nCompare my facilitation style between these two meeting folders.\n```\n\n### Advanced Analysis\n\n```\nAnalyze all transcripts in this folder and:\n1. Identify when I interrupted others\n2. Calculate my speaking ratio\n3. Find moments I avoided giving direct feedback\n4. Track my use of filler words\n5. Show examples of good active listening\n```\n\n## Instructions\n\nWhen a user requests meeting analysis:\n\n1. **Discover Available Data**\n - Scan the folder for transcript files (.txt, .md, .vtt, .srt, .docx)\n - Check if files contain speaker labels and timestamps\n - Confirm the date range of meetings\n - Identify the user's name/identifier in transcripts\n\n2. **Clarify Analysis Goals**\n \n If not specified, ask what they want to learn:\n - Specific behaviors (conflict avoidance, interruptions, filler words)\n - Communication effectiveness (clarity, directness, listening)\n - Meeting facilitation skills\n - Speaking patterns and ratios\n - Growth areas for improvement\n \n3. **Analyze Patterns**\n\n For each requested insight:\n \n **Conflict Avoidance**:\n - Look for hedging language (\"maybe\", \"kind of\", \"I think\")\n - Indirect phrasing instead of direct requests\n - Changing subject when tension arises\n - Agreeing without commitment (\"yeah, but...\")\n - Not addressing obvious problems\n \n **Speaking Ratios**:\n - Calculate percentage of meeting spent speaking\n - Count interruptions (by and of the user)\n - Measure average speaking turn length\n - Track question vs. statement ratios\n \n **Filler Words**:\n - Count \"um\", \"uh\", \"like\", \"you know\", \"actually\", etc.\n - Note frequency per minute or per speaking turn\n - Identify situations where they increase (nervous, uncertain)\n \n **Active Listening**:\n - Questions that reference others' previous points\n - Paraphrasing or summarizing others' ideas\n - Building on others' contributions\n - Asking clarifying questions\n \n **Leadership & Facilitation**:\n - Decision-making approach (directive vs. collaborative)\n - How disagreements are handled\n - Inclusion of quieter participants\n - Time management and agenda control\n - Follow-up and action item clarity\n\n4. **Provide Specific Examples**\n\n For each pattern found, include:\n \n ```markdown\n ### [Pattern Name]\n \n **Finding**: [One-sentence summary of the pattern]\n \n **Frequency**: [X times across Y meetings]\n \n **Examples**:\n \n 1. **[Meeting Name/Date]** - [Timestamp]\n \n **What Happened**:\n > [Actual quote from transcript]\n \n **Why This Matters**:\n [Explanation of the impact or missed opportunity]\n \n **Better Approach**:\n [Specific alternative phrasing or behavior]\n \n [Repeat for 2-3 strongest examples]\n ```\n\n5. **Synthesize Insights**\n\n After analyzing all patterns, provide:\n \n ```markdown\n # Meeting Insights Summary\n \n **Analysis Period**: [Date range]\n **Meetings Analyzed**: [X meetings]\n **Total Duration**: [X hours]\n \n ## Key Patterns Identified\n \n ### 1. [Primary Pattern]\n - **Observed**: [What you saw]\n - **Impact**: [Why it matters]\n - **Recommendation**: [How to improve]\n \n ### 2. [Second Pattern]\n [Same structure]\n \n ## Communication Strengths\n \n 1. [Strength 1 with example]\n 2. [Strength 2 with example]\n 3. [Strength 3 with example]\n \n ## Growth Opportunities\n \n 1. **[Area 1]**: [Specific, actionable advice]\n 2. **[Area 2]**: [Specific, actionable advice]\n 3. **[Area 3]**: [Specific, actionable advice]\n \n ## Speaking Statistics\n \n - Average speaking time: [X% of meeting]\n - Questions asked: [X per meeting average]\n - Filler words: [X per minute]\n - Interruptions: [X given / Y received per meeting]\n \n ## Next Steps\n \n [3-5 concrete actions to improve communication]\n ```\n\n6. **Offer Follow-Up Options**\n - Track these same metrics in future meetings\n - Deep dive into specific meetings or patterns\n - Compare to industry benchmarks\n - Create a personal communication development plan\n - Generate a summary for performance reviews\n\n## Examples\n\n### Example 1: Conflict Avoidance Analysis (Inspired by Dan Shipper)\n\n**User**: \"I download all of my meeting recordings and put them in a folder. Tell me all the times I've subtly avoided conflict.\"\n\n**Output**: \n```markdown\n# Conflict Avoidance Patterns\n\nFound 23 instances across 15 meetings where you used indirect \ncommunication or avoided addressing tensions directly.\n\n## Pattern: Hedging on Critical Feedback\n\n**Frequency**: 8 times across 7 meetings\n\n**Example 1: 1:1 with Sarah** - 00:14:32\n\n**What Happened**:\n> \"So, I was thinking... maybe we could, like, potentially \n> consider looking at the timeline again? I mean, if you \n> think that makes sense. But whatever you think is best!\"\n\n**Why This Matters**:\nYou needed to address that Sarah's project was behind schedule, \nbut the hedging language (\"maybe\", \"potentially\", \"if you think\") \nand the deflection at the end (\"whatever you think\") made it easy \nfor her to miss the urgency.\n\n**Better Approach**:\n\"Sarah, the project is two weeks behind schedule. We need to \ndiscuss what's blocking progress and create a new timeline \ntoday.\"\n\n[Additional examples...]\n\n## Recommendations\n\n1. **Name the issue directly** in the first sentence\n2. **Remove hedging words** like \"maybe,\" \"kind of,\" \"sort of\"\n3. **Ask specific questions** instead of hinting\n4. **Schedule difficult conversations** instead of raising them casually\n```\n\n### Example 2: Leadership Facilitation\n\n**User**: \"Analyze my team meetings and tell me about my facilitation style.\"\n\n**Output**: Provides insights on:\n- How much you speak vs. team members (60% vs. 40%)\n- Whether you ask questions or make statements (3:1 ratio)\n- How you handle disagreements (tendency to resolve too quickly)\n- Who speaks least and whether you draw them in\n- Examples of good and missed facilitation moments\n\n### Example 3: Personal Development Tracking\n\n**User**: \"Compare my meetings from Q1 vs. Q2 to see if I've improved my listening skills.\"\n\n**Output**: Creates a comparative analysis showing:\n- Decrease in interruptions (8 per meeting โ†’ 3 per meeting)\n- Increase in clarifying questions (2 โ†’ 7 per meeting)\n- Improvement in building on others' ideas\n- Specific examples showing the difference\n- Remaining areas for growth\n\n## Setup Tips\n\n### Getting Meeting Transcripts\n\n**From Granola** (free with Lenny's newsletter subscription):\n- Granola auto-transcribes your meetings\n- Export transcripts to a folder: [Instructions on how]\n- Point Claude Code to that folder\n\n**From Zoom**:\n- Enable cloud recording with transcription\n- Download VTT or SRT files after meetings\n- Store in a dedicated folder\n\n**From Google Meet**:\n- Use Google Docs auto-transcription\n- Save transcript docs to a folder\n- Download as .txt files or give Claude Code access\n\n**From Fireflies.ai, Otter.ai, etc.**:\n- Export transcripts in bulk\n- Store in a local folder\n- Run analysis on the folder\n\n### Best Practices\n\n1. **Consistent naming**: Use `YYYY-MM-DD - Meeting Name.txt` format\n2. **Regular analysis**: Review monthly or quarterly for trends\n3. **Specific queries**: Ask about one behavior at a time for depth\n4. **Privacy**: Keep sensitive meeting data local\n5. **Action-oriented**: Focus on one improvement area at a time\n\n## Common Analysis Requests\n\n- \"When do I avoid difficult conversations?\"\n- \"How often do I interrupt others?\"\n- \"What's my speaking vs. listening ratio?\"\n- \"Do I ask good questions?\"\n- \"How do I handle disagreement?\"\n- \"Am I inclusive of all voices?\"\n- \"Do I use too many filler words?\"\n- \"How clear are my action items?\"\n- \"Do I stay on agenda or get sidetracked?\"\n- \"How has my communication changed over time?\"\n\n## Related Use Cases\n\n- Creating a personal development plan from insights\n- Preparing performance review materials with examples\n- Coaching direct reports on their communication\n- Analyzing customer calls for sales or support patterns\n- Studying negotiation tactics and outcomes","schemaVersion":1},"repoUrl":"https://github.com/Prat011/awesome-llm-skills/tree/master/meeting-insights-analyzer","tags":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"awesome-llm-skills","audit":{"files":["slack-gif-creator/requirements.txt"],"binaries":[],"findings":[{"kind":"dependency","rule":"DP-04","message":"Python dependencies are not pinned and there is no lock file.","surface":"slack-gif-creator/requirements.txt","evidence":"pillow>=10.0.0, imageio>=2.31.0, imageio-ffmpeg>=0.4.9, numpy>=1.24.0","severity":"medium"}],"packages":4,"auditedAt":"2026-09-25T11:52:30.068Z","lockfiles":[]},"forks":313,"owner":"Prat011","stars":1761,"topics":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms","openai","opencode","qwen","qwen-coder","skills"],"license":null,"fullName":"Prat011/awesome-llm-skills","homepage":null,"language":"Python","pushedAt":"2026-07-14T09:53:56Z","avatarUrl":"https://avatars.githubusercontent.com/u/67639393?v=4","crawledAt":"2026-09-25T11:52:22.319Z","openIssues":170,"manifestFile":"SKILL.md","manifestPath":"meeting-insights-analyzer/SKILL.md","defaultBranch":"master"},"readme":"# Meeting Insights Analyzer\n\nThis skill transforms your meeting transcripts into actionable insights about your communication patterns, helping you become a more effective communicator and leader.\n\n## When to Use This Skill\n\n- Analyzing your communication patterns across multiple meetings\n- Getting feedback on your leadership and facilitation style\n- Identifying when you avoid difficult conversations\n- Understanding your speaking habits and filler words\n- Tracking improvement in communication skills over time\n- Preparing for performance reviews with concrete examples\n- Coaching team members on their communication style\n\n## What This Skill Does\n\n1. **Pattern Recognition**: Identifies recurring behaviors across meetings like:\n - Conflict avoidance or indirect communication\n - Speaking ratios and turn-taking\n - Question-asking vs. statement-making patterns\n - Active listening indicators\n - Decision-making approaches\n\n2. **Communication Analysis**: Evaluates communication effectiveness:\n - Clarity and directness\n - Use of filler words and hedging language\n - Tone and sentiment patterns\n - Meeting control and facilitation\n\n3. **Actionable Feedback**: Provides specific, timestamped examples with:\n - What happened\n - Why it matters\n - How to improve\n\n4. **Trend Tracking**: Compares patterns over time when analyzing multiple meetings\n\n## How to Use\n\n### Basic Setup\n\n1. Download your meeting transcripts to a folder (e.g., `~/meetings/`)\n2. Navigate to that folder in Claude Code\n3. Ask for the analysis you want\n\n### Quick Start Examples\n\n```\nAnalyze all meetings in this folder and tell me when I avoided conflict.\n```\n\n```\nLook at my meetings from the past month and identify my communication patterns.\n```\n\n```\nCompare my facilitation style between these two meeting folders.\n```\n\n### Advanced Analysis\n\n```\nAnalyze all transcripts in this folder and:\n1. Identify when I interrupted others\n2. Calculate my speaking ratio\n3. Find moments I avoided giving direct feedback\n4. Track my use of filler words\n5. Show examples of good active listening\n```\n\n## Instructions\n\nWhen a user requests meeting analysis:\n\n1. **Discover Available Data**\n - Scan the folder for transcript files (.txt, .md, .vtt, .srt, .docx)\n - Check if files contain speaker labels and timestamps\n - Confirm the date range of meetings\n - Identify the user's name/identifier in transcripts\n\n2. **Clarify Analysis Goals**\n \n If not specified, ask what they want to learn:\n - Specific behaviors (conflict avoidance, interruptions, filler words)\n - Communication effectiveness (clarity, directness, listening)\n - Meeting facilitation skills\n - Speaking patterns and ratios\n - Growth areas for improvement\n \n3. **Analyze Patterns**\n\n For each requested insight:\n \n **Conflict Avoidance**:\n - Look for hedging language (\"maybe\", \"kind of\", \"I think\")\n - Indirect phrasing instead of direct requests\n - Changing subject when tension arises\n - Agreeing without commitment (\"yeah, but...\")\n - Not addressing obvious problems\n \n **Speaking Ratios**:\n - Calculate percentage of meeting spent speaking\n - Count interruptions (by and of the user)\n - Measure average speaking turn length\n - Track question vs. statement ratios\n \n **Filler Words**:\n - Count \"um\", \"uh\", \"like\", \"you know\", \"actually\", etc.\n - Note frequency per minute or per speaking turn\n - Identify situations where they increase (nervous, uncertain)\n \n **Active Listening**:\n - Questions that reference others' previous points\n - Paraphrasing or summarizing others' ideas\n - Building on others' contributions\n - Asking clarifying questions\n \n **Leadership & Facilitation**:\n - Decision-making approach (directive vs. collaborative)\n - How disagreements are handled\n - Inclusion of quieter participants\n - Time management and agenda control\n - Follow-up and action item clarity\n\n4. **Provide Specific Examples**\n\n For each pattern found, include:","createdAt":"2026-09-25T11:52:30.301Z","updatedAt":"2026-09-25T11:52:30.301Z"},{"id":"cmugwiicn026kqu06nu1wxv5v","slug":"prat011-awesome-llm-skills-notion-knowledge-capture","name":"notion-knowledge-capture","description":"Transforms conversations and discussions into structured documentation pages in Notion. Captures insights, decisions, and knowledge from chat context, formats appropriately, and saves to wikis or databases with proper organization and linking for easy discovery.","authorId":"gh:prat011","authorName":"Prat011","version":"0.1.0","category":"Prompt","securityLevel":"Community","downloadsCount":0,"githubStars":1761,"pricePerCall":0,"manifest":{"name":"notion-knowledge-capture","tools":[],"category":"Prompt","entrypoint":{"type":"prompt"},"description":"Transforms conversations and discussions into structured documentation pages in Notion. Captures insights, decisions, and knowledge from chat context, formats appropriately, and saves to wikis or databases with proper organization and linking for easy discovery.","permissions":[],"systemPrompt":"# Knowledge Capture\n\nTransforms conversations, discussions, and insights into structured documentation in your Notion workspace. Captures knowledge from chat context, formats it appropriately, and saves it to the right location with proper organization and linking.\n\n## Quick Start\n\nWhen asked to save information to Notion:\n\n1. **Extract content**: Identify key information from conversation context\n2. **Structure information**: Organize into appropriate documentation format\n3. **Determine location**: Use `Notion:notion-search` to find appropriate wiki page/database\n4. **Create page**: Use `Notion:notion-create-pages` to save content\n5. **Make discoverable**: Link from relevant hub pages, add to databases, or update wiki navigation so others can find it\n\n## Knowledge Capture Workflow\n\n### Step 1: Identify content to capture\n\n```\nFrom conversation context, extract:\n- Key concepts and definitions\n- Decisions made and rationale\n- How-to information and procedures\n- Important insights or learnings\n- Q&A pairs\n- Examples and use cases\n```\n\n### Step 2: Determine content type\n\n```\nClassify the knowledge:\n- Concept/Definition\n- How-to Guide\n- Decision Record\n- FAQ Entry\n- Meeting Summary\n- Learning/Post-mortem\n- Reference Documentation\n```\n\n\n### Step 3: Structure the content\n\n```\nFormat appropriately based on content type:\n- Use templates for consistency\n- Add clear headings and sections\n- Include examples where helpful\n- Add relevant metadata\n- Link to related pages\n```\n\n\n### Step 4: Determine destination\n\n```\nWhere to save:\n- Wiki page (general knowledge base)\n- Specific project page (project-specific knowledge)\n- Documentation database (structured docs)\n- FAQ database (questions and answers)\n- Decision log (architecture/product decisions)\n- Team wiki (team-specific knowledge)\n```\n\n### Step 5: Create the page\n\n```\nUse Notion:notion-create-pages:\n- Set appropriate title\n- Use structured content from template\n- Set properties if in database\n- Add tags/categories\n- Link to related pages\n```\n\n### Step 6: Make content discoverable\n\n```\nLink the new page so others can find it:\n\n1. Update hub/index pages:\n - Add link to wiki table of contents page\n - Add link from relevant project page\n - Add link from category/topic page (e.g., \"Engineering Docs\")\n \n2. If page is in a database:\n - Set appropriate tags/categories\n - Set status (e.g., \"Published\")\n - Add to relevant views\n \n3. Optionally update parent page:\n - If saved under a project, add to project's \"Documentation\" section\n - If in team wiki, ensure it's linked from team homepage\n\nExample:\nNotion:notion-update-page\npage_id: \"team-wiki-homepage-id\"\ncommand: \"insert_content_after\"\nselection_with_ellipsis: \"## How-To Guides...\"\nnew_str: \"- How to Deploy to Production\"\n```\n\nThis step ensures the knowledge doesn't become \"orphaned\" - it's properly connected to your workspace's navigation structure.\n\n## Content Types\n\nChoose appropriate structure based on content:\n\n**Concept**: Overview โ†’ Definition โ†’ Characteristics โ†’ Examples โ†’ Use Cases โ†’ Related\n**How-To**: Overview โ†’ Prerequisites โ†’ Steps (numbered) โ†’ Verification โ†’ Troubleshooting โ†’ Related\n**Decision**: Context โ†’ Decision โ†’ Rationale โ†’ Options Considered โ†’ Consequences โ†’ Implementation\n**FAQ**: Short Answer โ†’ Detailed Explanation โ†’ Examples โ†’ When to Use โ†’ Related Questions\n**Learning**: What Happened โ†’ What Went Well โ†’ What Didn't โ†’ Root Causes โ†’ Learnings โ†’ Actions\n\n\n## Destination Patterns\n\n**General Wiki**: Standalone page โ†’ add to index โ†’ tag โ†’ link from related pages\n\n**Project Wiki**: Child of project page โ†’ link from project overview โ†’ tag with project name\n\n**Documentation Database**: Use properties (Title, Type, Category, Tags, Last Updated, Owner)\n\n**Decision Log Database**: Use properties (Decision, Date, Status, Domain, Deciders, Impact)\n\n**FAQ Database**: Use properties (Question, Category, Tags, Last Reviewed, Useful Count)\n\nSee [reference/database-best-practices.md](reference/database-best-practices.md) for database selection guide and individual schema files.\n\n## Content Extraction from Conversations\n\n**Chat Discussion**: Key points, conclusions, resources, action items, Q&A\n\n**Problem-Solving**: Problem statement, approaches tried, solution, why it worked, future considerations\n\n**Knowledge Sharing**: Concept explained, examples, best practices, common pitfalls, resources\n\n**Decision Discussion**: Question, options, trade-offs, decision, rationale, next steps\n\n## Formatting Best Practices\n\n**Structure**: Use `#` (title), `##` (sections), `###` (subsections) consistently\n\n**Writing**: Start with overview, use bullets, keep paragraphs short, add examples\n\n**Linking**: Link related pages, mention people, reference resources, create bidirectional links\n\n**Metadata**: Include date, author, tags, status\n\n**Searchability**: Clear titles, natural keywords, common search tags, image alt-text\n\n## Indexing and Organization\n\n**Wiki Index**: Organize by sections (Getting Started, How-To Guides, Reference, FAQs, Decisions) with page links\n\n**Category Pages**: Create landing pages with overview, doc links, and recent updates\n\n**Tagging Strategy**: Use consistent tags for technology/tools, topics, audience, and status\n\n## Update Management\n\n**Create New**: Content is substantive (>2 paragraphs), will be referenced multiple times, part of knowledge base, needs independent discovery\n\n**Update Existing**: Adding to existing topic, correcting info, expanding concept, updating for changes\n\n**Versioning**: Add update history section for significant changes (date, author, what changed, why)\n\n## Best Practices\n\n1. **Capture promptly**: Document while context is fresh\n2. **Structure consistently**: Use templates for similar content\n3. **Link extensively**: Connect related knowledge\n4. **Write for discovery**: Use searchable titles and tags\n5. **Include context**: Why this matters, when to use\n6. **Add examples**: Concrete examples aid understanding\n7. **Maintain**: Review and update periodically\n8. **Get feedback**: Ask if documentation is helpful\n\n## Advanced Features\n\n**Documentation databases**: See [reference/database-best-practices.md](reference/database-best-practices.md) for database schema patterns.\n\n## Common Issues\n\n**\"Not sure where to save\"**: Default to general wiki, can move later\n**\"Content is fragmentary\"**: Group related fragments into cohesive doc\n**\"Already exists\"**: Search first, update existing if appropriate\n**\"Too informal\"**: Clean up language while preserving insights\n\n## Examples\n\nSee [examples/](examples/) for complete workflows:\n- [examples/conversation-to-faq.md](examples/conversation-to-faq.md) - FAQ from Q&A\n- [examples/decision-capture.md](examples/decision-capture.md) - Decision record\n- [examples/how-to-guide.md](examples/how-to-guide.md) - How-to from discussion","schemaVersion":1},"repoUrl":"https://github.com/Prat011/awesome-llm-skills/tree/master/notion-knowledge-capture","tags":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"awesome-llm-skills","audit":{"files":["slack-gif-creator/requirements.txt"],"binaries":[],"findings":[{"kind":"dependency","rule":"DP-04","message":"Python dependencies are not pinned and there is no lock file.","surface":"slack-gif-creator/requirements.txt","evidence":"pillow>=10.0.0, imageio>=2.31.0, imageio-ffmpeg>=0.4.9, numpy>=1.24.0","severity":"medium"}],"packages":4,"auditedAt":"2026-09-25T11:52:30.068Z","lockfiles":[]},"forks":313,"owner":"Prat011","stars":1761,"topics":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms","openai","opencode","qwen","qwen-coder","skills"],"license":null,"fullName":"Prat011/awesome-llm-skills","homepage":null,"language":"Python","pushedAt":"2026-07-14T09:53:56Z","avatarUrl":"https://avatars.githubusercontent.com/u/67639393?v=4","crawledAt":"2026-09-25T11:52:22.319Z","openIssues":170,"manifestFile":"SKILL.md","manifestPath":"notion-knowledge-capture/SKILL.md","defaultBranch":"master"},"readme":"# Knowledge Capture\n\nTransforms conversations, discussions, and insights into structured documentation in your Notion workspace. Captures knowledge from chat context, formats it appropriately, and saves it to the right location with proper organization and linking.\n\n## Quick Start\n\nWhen asked to save information to Notion:\n\n1. **Extract content**: Identify key information from conversation context\n2. **Structure information**: Organize into appropriate documentation format\n3. **Determine location**: Use `Notion:notion-search` to find appropriate wiki page/database\n4. **Create page**: Use `Notion:notion-create-pages` to save content\n5. **Make discoverable**: Link from relevant hub pages, add to databases, or update wiki navigation so others can find it\n\n## Knowledge Capture Workflow\n\n### Step 1: Identify content to capture\n\n```\nFrom conversation context, extract:\n- Key concepts and definitions\n- Decisions made and rationale\n- How-to information and procedures\n- Important insights or learnings\n- Q&A pairs\n- Examples and use cases\n```\n\n### Step 2: Determine content type\n\n```\nClassify the knowledge:\n- Concept/Definition\n- How-to Guide\n- Decision Record\n- FAQ Entry\n- Meeting Summary\n- Learning/Post-mortem\n- Reference Documentation\n```\n\n\n### Step 3: Structure the content\n\n```\nFormat appropriately based on content type:\n- Use templates for consistency\n- Add clear headings and sections\n- Include examples where helpful\n- Add relevant metadata\n- Link to related pages\n```\n\n\n### Step 4: Determine destination\n\n```\nWhere to save:\n- Wiki page (general knowledge base)\n- Specific project page (project-specific knowledge)\n- Documentation database (structured docs)\n- FAQ database (questions and answers)\n- Decision log (architecture/product decisions)\n- Team wiki (team-specific knowledge)\n```\n\n### Step 5: Create the page\n\n```\nUse Notion:notion-create-pages:\n- Set appropriate title\n- Use structured content from template\n- Set properties if in database\n- Add tags/categories\n- Link to related pages\n```\n\n### Step 6: Make content discoverable\n\n```\nLink the new page so others can find it:\n\n1. Update hub/index pages:\n - Add link to wiki table of contents page\n - Add link from relevant project page\n - Add link from category/topic page (e.g., \"Engineering Docs\")\n \n2. If page is in a database:\n - Set appropriate tags/categories\n - Set status (e.g., \"Published\")\n - Add to relevant views\n \n3. Optionally update parent page:\n - If saved under a project, add to project's \"Documentation\" section\n - If in team wiki, ensure it's linked from team homepage\n\nExample:\nNotion:notion-update-page\npage_id: \"team-wiki-homepage-id\"\ncommand: \"insert_content_after\"\nselection_with_ellipsis: \"## How-To Guides...\"\nnew_str: \"- How to Deploy to Production\"\n```\n\nThis step ensures the knowledge doesn't become \"orphaned\" - it's properly connected to your workspace's navigation structure.\n\n## Content Types\n\nChoose appropriate structure based on content:\n\n**Concept**: Overview โ†’ Definition โ†’ Characteristics โ†’ Examples โ†’ Use Cases โ†’ Related\n**How-To**: Overview โ†’ Prerequisites โ†’ Steps (numbered) โ†’ Verification โ†’ Troubleshooting โ†’ Related\n**Decision**: Context โ†’ Decision โ†’ Rationale โ†’ Options Considered โ†’ Consequences โ†’ Implementation\n**FAQ**: Short Answer โ†’ Detailed Explanation โ†’ Examples โ†’ When to Use โ†’ Related Questions\n**Learning**: What Happened โ†’ What Went Well โ†’ What Didn't โ†’ Root Causes โ†’ Learnings โ†’ Actions\n\n\n## Destination Patterns\n\n**General Wiki**: Standalone page โ†’ add to index โ†’ tag โ†’ link from related pages\n\n**Project Wiki**: Child of project page โ†’ link from project overview โ†’ tag with project name\n\n**Documentation Database**: Use properties (Title, Type, Category, Tags, Last Updated, Owner)\n\n**Decision Log Database**: Use properties (Decision, Date, Status, Domain, Deciders, Impact)\n\n**FAQ Database**: Use properties (Question, Category, Tags, Last Reviewed, Useful Count)\n\nSee [reference/database-best-practices.md","createdAt":"2026-09-25T11:52:30.312Z","updatedAt":"2026-09-25T11:52:30.312Z"},{"id":"cmugwiicy026nqu06xg9fmwss","slug":"prat011-awesome-llm-skills-notion-meeting-intelligence","name":"notion-meeting-intelligence","description":"Prepares meeting materials by gathering context from Notion, enriching with Claude research, and creating both an internal pre-read and external agenda saved to Notion. Helps you arrive prepared with comprehensive background and structured meeting docs.","authorId":"gh:prat011","authorName":"Prat011","version":"0.1.0","category":"Prompt","securityLevel":"Community","downloadsCount":0,"githubStars":1761,"pricePerCall":0,"manifest":{"name":"notion-meeting-intelligence","tools":[],"category":"Prompt","entrypoint":{"type":"prompt"},"description":"Prepares meeting materials by gathering context from Notion, enriching with Claude research, and creating both an internal pre-read and external agenda saved to Notion. Helps you arrive prepared with comprehensive background and structured meeting docs.","permissions":[],"systemPrompt":"# Meeting Intelligence\n\nPrepares you for meetings by gathering context from Notion, enriching it with Claude research, and creating comprehensive meeting materials. Generates both an internal pre-read for attendees and an external-facing agenda for the meeting itself.\n\n## Quick Start\n\nWhen asked to prep for a meeting:\n\n1. **Gather Notion context**: Use `Notion:notion-search` to find related pages\n2. **Fetch details**: Use `Notion:notion-fetch` to read relevant content\n3. **Enrich with research**: Use Claude's knowledge to add context, industry insights, or best practices\n4. **Create internal pre-read**: Use `Notion:notion-create-pages` for background context document (for attendees)\n5. **Create external agenda**: Use `Notion:notion-create-pages` for meeting agenda (shared with all participants)\n6. **Link resources**: Connect both docs to related projects and each other\n\n## Meeting Prep Workflow\n\n### Step 1: Understand meeting context\n\n```\nCollect meeting details:\n- Meeting topic/title\n- Attendees (internal team + external participants)\n- Meeting purpose (decision, brainstorm, status update, customer demo, etc.)\n- Meeting type (internal only vs. external participants)\n- Related project/initiative\n- Specific topics to cover\n```\n\n### Step 2: Search for Notion context\n\n```\nUse Notion:notion-search to find:\n- Project pages related to meeting topic\n- Previous meeting notes\n- Specifications or design docs\n- Related tasks or issues\n- Recent updates or reports\n- Customer/partner information (if applicable)\n\nSearch strategies:\n- Topic-based: \"mobile app redesign\"\n- Project-scoped: search within project teamspace\n- Attendee-created: filter by created_by_user_ids\n- Recent updates: use created_date_range filters\n```\n\n### Step 3: Fetch and analyze Notion content\n\n```\nFor each relevant page:\n1. Fetch with Notion:notion-fetch\n2. Extract key information:\n - Project status and timeline\n - Recent decisions and updates\n - Open questions or blockers\n - Relevant metrics or data\n - Action items from previous meetings\n3. Note gaps in information\n```\n\n### Step 4: Enrich with Claude research\n\n```\nBeyond Notion context, add value through:\n\nFor technical meetings:\n- Explain complex concepts for broader audience\n- Summarize industry best practices\n- Provide competitive context\n- Suggest discussion frameworks\n\nFor customer meetings:\n- Research company background (if public info)\n- Industry trends relevant to discussion\n- Common pain points in their sector\n- Best practices for similar customers\n\nFor decision meetings:\n- Decision-making frameworks\n- Risk analysis patterns\n- Trade-off considerations\n- Implementation best practices\n\nNote: Use general knowledge only - don't fabricate specific facts\n```\n\n### Step 5: Create internal pre-read\n\n```\nUse Notion:notion-create-pages for internal doc:\n\nTitle: \"[Meeting Topic] - Pre-Read (Internal)\"\n\nContent structure:\n- **Meeting Overview**: Date, time, attendees, purpose\n- **Background Context**: \n - What this meeting is about (2-3 sentences)\n - Why it matters (business context)\n - Links to related Notion pages\n- **Current Status**: \n - Where we are now (from Notion content)\n - Recent updates and progress\n - Key metrics or data\n- **Context & Insights** (from Claude research):\n - Industry context or best practices\n - Relevant considerations\n - Potential approaches to discuss\n- **Key Discussion Points**:\n - Topics that need airtime\n - Open questions to resolve\n - Decisions required\n- **What We Need from This Meeting**:\n - Expected outcomes\n - Decisions to make\n - Next steps to define\n\nAudience: Internal attendees only\nPurpose: Give team full context and alignment before meeting\n```\n\n### Step 6: Create external agenda\n\n```\nUse Notion:notion-create-pages for meeting doc:\n\nTitle: \"[Meeting Topic] - Agenda\"\n\nContent structure:\n- **Meeting Details**: Date, time, attendees\n- **Objective**: Clear meeting goal (1-2 sentences)\n- **Agenda Items** (with time allocations):\n 1. Topic 1 (10 min)\n 2. Topic 2 (20 min)\n 3. Topic 3 (15 min)\n- **Discussion Topics**: \n - Key items to cover\n - Questions to answer\n- **Decisions Needed**: \n - Clear decision points\n- **Action Items**: \n - (To be filled during meeting)\n- **Related Resources**:\n - Links to relevant pages\n - Link to pre-read document\n\nAudience: All participants (internal + external)\nPurpose: Structure the meeting, keep it on track\nTone: Professional, focused, clear\n```\n\nSee [reference/template-selection-guide.md](reference/template-selection-guide.md) for full templates.\n\n### Step 7: Link documents\n\n```\n1. Link pre-read to agenda:\n - Add mention in agenda: \"See Pre-Read for background\"\n\n2. Link both to project:\n - Update project page with meeting links\n - Add to \"Meetings\" section\n\n3. Cross-reference:\n - Agenda mentions pre-read for internal attendees\n - Pre-read mentions agenda for meeting structure\n```\n\n## Document Types\n\n### Internal Pre-Read (for team)\n\nMore comprehensive, internal context:\n- Full background and history\n- Internal metrics and data\n- Honest assessment of challenges\n- Strategic considerations\n- What we need to achieve\n- Internal discussion points\n\n**When to create**: Always for important meetings with internal team\n\n### External Agenda (for all participants)\n\nClean, professional, focused:\n- Clear objectives\n- Structured agenda with times\n- Discussion topics\n- Decision items\n- Professional tone\n\n**When to create**: Every meeting\n\n### Agenda Types by Meeting Purpose\n\n**Decision Meeting**: Meeting Details โ†’ Objective โ†’ Options (Pros/Cons) โ†’ Recommendation โ†’ Discussion โ†’ Decision โ†’ Action Items\n\n**Status Update**: Meeting Details โ†’ Project Status โ†’ Progress โ†’ Upcoming Work โ†’ Blockers โ†’ Discussion โ†’ Action Items\n\n**Customer/External**: Meeting Details โ†’ Objective โ†’ Agenda Items (timed) โ†’ Discussion Topics โ†’ Next Steps\n\n**Brainstorming**: Meeting Details โ†’ Objective โ†’ Constraints โ†’ Ideas โ†’ Discussion โ†’ Next Steps\n\nSee [reference/template-selection-guide.md](reference/template-selection-guide.md) for complete templates.\n\n## Research Enrichment Patterns\n\nBeyond Notion content, add value through Claude's capabilities:\n\n**Technical Context**: Explain technologies, architectures, or approaches. Provide industry standard practices. Compare common solutions. Suggest evaluation criteria.\n\n**Business Context**: Industry trends affecting topic. Competitive landscape insights. Common challenges in space. ROI considerations.\n\n**Decision Support**: Decision-making frameworks (e.g., RICE, cost-benefit). Risk assessment patterns. Trade-off analysis approaches. Success criteria suggestions.\n\n**Customer Context** (for external meetings): Industry-specific challenges. Common pain points. Best practices from similar companies. Value proposition framing.\n\n**Process Guidance**: Meeting facilitation techniques. Discussion frameworks. Retrospective patterns. Brainstorming structures.\n\nNote: Use general knowledge and analytical capabilities. Don't fabricate specific facts. Clearly distinguish Notion facts from Claude insights.\n\n## Meeting Context Sources\n\n**Project Pages**: Status, goals, team, timelines (most important)\n**Previous Meeting Notes**: Historical discussions, action items, decisions (recurring meetings)\n**Task/Issue Database**: Current status, blockers, completed/upcoming work (project meetings)\n**Specifications/Designs**: Requirements, decisions, approach, open questions (technical meetings)\n**Reports/Dashboards**: Metrics, KPIs, performance data, trends (executive meetings)\n\n## Linking Meetings to Projects\n\n**Forward Link**: Add meeting to project page's \"Meetings\" section\n**Backward Link**: Include \"Related Project\" section in agenda with project mention\n**Maintain bidirectional** links for easy navigation\n\n## Meeting Series Management\n\n**Recurring Meetings**: Create series parent page with schedule, meeting notes list, standing agenda, and action items tracker. Link individual meetings to parent.\n\n**Meeting Database**: For organizations, use database with properties: Meeting Title, Date, Type (Decision/Status/Brainstorm), Project, Attendees, Status (Scheduled/Completed)\n\n## Post-Meeting Actions\n\nUpdate agenda with:\n\n**Decisions**: List each decision with rationale and owner\n**Action Items**: Checkbox list with owner and due date (consider creating tasks in database)\n**Key Outcomes**: Bullet list of main outcomes\n\n## Meeting Prep Timing\n\n**Day-Before** (next-day meetings): Gather context โ†’ create agenda โ†’ share with attendees โ†’ allow review time\n**Hour-Before** (last-minute): Quick context โ†’ brief pre-read โ†’ basic agenda โ†’ essentials only\n**Week-Before** (major meetings): Comprehensive research โ†’ detailed pre-read โ†’ structured agenda โ†’ pre-meeting reviews\n\n## Best Practices\n\n1. **Create both documents**: Internal pre-read + external agenda for important meetings\n2. **Distinguish sources**: Label what's from Notion vs. Claude research\n3. **Start with search**: Cast wide net in Notion, then narrow\n4. **Keep pre-read concise**: 2-3 pages maximum, even with research\n5. **Professional external docs**: Agenda should be polished and focused\n6. **Enrich thoughtfully**: Claude research should add real value, not fluff\n7. **Link documents**: Pre-read mentions agenda, agenda mentions pre-read\n8. **Include metrics**: Data from Notion helps ground discussions\n9. **Share appropriately**: Pre-read to internal team, agenda to all participants\n10. **Share early**: Give attendees time to review (24hr+ for important meetings)\n11. **Update post-meeting**: Capture decisions and actions in agenda\n\n## Advanced Features\n\n**Meeting templates**: See [reference/template-selection-guide.md](reference/template-selection-guide.md) for comprehensive template library\n\n## Common Issues\n\n**\"Too much context\"**: Split into pre-read (internal, comprehensive) and agenda (external, focused)\n**\"Can't find relevant pages\"**: Broaden search, try different terms, ask user for page URLs\n**\"Meeting purpose unclear\"**: Ask user to clarify before proceeding\n**\"No recent updates\"**: Note that in pre-read, focus on historical context and strategic considerations\n**\"External meeting - no internal context\"**: Create simpler structure with just agenda, skip internal pre-read or keep it minimal\n**\"Claude research too generic\"**: Focus on specific insights relevant to the actual meeting topic, not general platitudes\n\n## Examples\n\nSee [examples/](examples/) for complete workflows:\n- [examples/project-decision.md](examples/project-decision.md) - Decision meeting prep with pre-read\n- [examples/sprint-planning.md](examples/sprint-planning.md) - Sprint planning meeting\n- [examples/executive-review.md](examples/executive-review.md) - Executive review prep\n- [examples/customer-meeting.md](examples/customer-meeting.md) - External meeting with customer (pre-read + agenda)","schemaVersion":1},"repoUrl":"https://github.com/Prat011/awesome-llm-skills/tree/master/notion-meeting-intelligence","tags":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"awesome-llm-skills","audit":{"files":["slack-gif-creator/requirements.txt"],"binaries":[],"findings":[{"kind":"dependency","rule":"DP-04","message":"Python dependencies are not pinned and there is no lock file.","surface":"slack-gif-creator/requirements.txt","evidence":"pillow>=10.0.0, imageio>=2.31.0, imageio-ffmpeg>=0.4.9, numpy>=1.24.0","severity":"medium"}],"packages":4,"auditedAt":"2026-09-25T11:52:30.068Z","lockfiles":[]},"forks":313,"owner":"Prat011","stars":1761,"topics":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms","openai","opencode","qwen","qwen-coder","skills"],"license":null,"fullName":"Prat011/awesome-llm-skills","homepage":null,"language":"Python","pushedAt":"2026-07-14T09:53:56Z","avatarUrl":"https://avatars.githubusercontent.com/u/67639393?v=4","crawledAt":"2026-09-25T11:52:22.319Z","openIssues":170,"manifestFile":"SKILL.md","manifestPath":"notion-meeting-intelligence/SKILL.md","defaultBranch":"master"},"readme":"# Meeting Intelligence\n\nPrepares you for meetings by gathering context from Notion, enriching it with Claude research, and creating comprehensive meeting materials. Generates both an internal pre-read for attendees and an external-facing agenda for the meeting itself.\n\n## Quick Start\n\nWhen asked to prep for a meeting:\n\n1. **Gather Notion context**: Use `Notion:notion-search` to find related pages\n2. **Fetch details**: Use `Notion:notion-fetch` to read relevant content\n3. **Enrich with research**: Use Claude's knowledge to add context, industry insights, or best practices\n4. **Create internal pre-read**: Use `Notion:notion-create-pages` for background context document (for attendees)\n5. **Create external agenda**: Use `Notion:notion-create-pages` for meeting agenda (shared with all participants)\n6. **Link resources**: Connect both docs to related projects and each other\n\n## Meeting Prep Workflow\n\n### Step 1: Understand meeting context\n\n```\nCollect meeting details:\n- Meeting topic/title\n- Attendees (internal team + external participants)\n- Meeting purpose (decision, brainstorm, status update, customer demo, etc.)\n- Meeting type (internal only vs. external participants)\n- Related project/initiative\n- Specific topics to cover\n```\n\n### Step 2: Search for Notion context\n\n```\nUse Notion:notion-search to find:\n- Project pages related to meeting topic\n- Previous meeting notes\n- Specifications or design docs\n- Related tasks or issues\n- Recent updates or reports\n- Customer/partner information (if applicable)\n\nSearch strategies:\n- Topic-based: \"mobile app redesign\"\n- Project-scoped: search within project teamspace\n- Attendee-created: filter by created_by_user_ids\n- Recent updates: use created_date_range filters\n```\n\n### Step 3: Fetch and analyze Notion content\n\n```\nFor each relevant page:\n1. Fetch with Notion:notion-fetch\n2. Extract key information:\n - Project status and timeline\n - Recent decisions and updates\n - Open questions or blockers\n - Relevant metrics or data\n - Action items from previous meetings\n3. Note gaps in information\n```\n\n### Step 4: Enrich with Claude research\n\n```\nBeyond Notion context, add value through:\n\nFor technical meetings:\n- Explain complex concepts for broader audience\n- Summarize industry best practices\n- Provide competitive context\n- Suggest discussion frameworks\n\nFor customer meetings:\n- Research company background (if public info)\n- Industry trends relevant to discussion\n- Common pain points in their sector\n- Best practices for similar customers\n\nFor decision meetings:\n- Decision-making frameworks\n- Risk analysis patterns\n- Trade-off considerations\n- Implementation best practices\n\nNote: Use general knowledge only - don't fabricate specific facts\n```\n\n### Step 5: Create internal pre-read\n\n```\nUse Notion:notion-create-pages for internal doc:\n\nTitle: \"[Meeting Topic] - Pre-Read (Internal)\"\n\nContent structure:\n- **Meeting Overview**: Date, time, attendees, purpose\n- **Background Context**: \n - What this meeting is about (2-3 sentences)\n - Why it matters (business context)\n - Links to related Notion pages\n- **Current Status**: \n - Where we are now (from Notion content)\n - Recent updates and progress\n - Key metrics or data\n- **Context & Insights** (from Claude research):\n - Industry context or best practices\n - Relevant considerations\n - Potential approaches to discuss\n- **Key Discussion Points**:\n - Topics that need airtime\n - Open questions to resolve\n - Decisions required\n- **What We Need from This Meeting**:\n - Expected outcomes\n - Decisions to make\n - Next steps to define\n\nAudience: Internal attendees only\nPurpose: Give team full context and alignment before meeting\n```\n\n### Step 6: Create external agenda\n\n```\nUse Notion:notion-create-pages for meeting doc:\n\nTitle: \"[Meeting Topic] - Agenda\"\n\nContent structure:\n- **Meeting Details**: Date, time, attendees\n- **Objective**: Clear meeting goal (1-2 sentences)\n- **Agenda Items** (with time allocations):\n 1. Topic 1 (10 min)\n 2. Topic 2 ","createdAt":"2026-09-25T11:52:30.323Z","updatedAt":"2026-09-25T11:52:30.323Z"},{"id":"cmugwiide026qqu06kdnnfflh","slug":"prat011-awesome-llm-skills-notion-research-documentation","name":"notion-research-documentation","description":"Searches across your Notion workspace, synthesizes findings from multiple pages, and creates comprehensive research documentation saved as new Notion pages. Turns scattered information into structured reports with proper citations and actionable insights.","authorId":"gh:prat011","authorName":"Prat011","version":"0.1.0","category":"Prompt","securityLevel":"Community","downloadsCount":0,"githubStars":1761,"pricePerCall":0,"manifest":{"name":"notion-research-documentation","tools":[],"category":"Prompt","entrypoint":{"type":"prompt"},"description":"Searches across your Notion workspace, synthesizes findings from multiple pages, and creates comprehensive research documentation saved as new Notion pages. Turns scattered information into structured reports with proper citations and actionable insights.","permissions":[],"systemPrompt":"# Research & Documentation\n\nEnables comprehensive research workflows: search for information across your Notion workspace, fetch and analyze relevant pages, synthesize findings, and create well-structured documentation.\n\n## Quick Start\n\nWhen asked to research and document a topic:\n\n1. **Search for relevant content**: Use `Notion:notion-search` to find pages\n2. **Fetch detailed information**: Use `Notion:notion-fetch` to read full page content\n3. **Synthesize findings**: Analyze and combine information from multiple sources\n4. **Create structured output**: Use `Notion:notion-create-pages` to write documentation\n\n## Research Workflow\n\n### Step 1: Search for relevant information\n\n```\nUse Notion:notion-search with the research topic\nFilter by teamspace if scope is known\nReview search results to identify most relevant pages\n```\n\n### Step 2: Fetch page content\n\n```\nUse Notion:notion-fetch for each relevant page URL\nCollect content from all relevant sources\nNote key findings, quotes, and data points\n```\n\n### Step 3: Synthesize findings\n\nAnalyze the collected information:\n- Identify key themes and patterns\n- Connect related concepts across sources\n- Note gaps or conflicting information\n- Organize findings logically\n\n### Step 4: Create structured documentation\n\nUse the appropriate documentation template (see [reference/format-selection-guide.md](reference/format-selection-guide.md)) to structure output:\n- Clear title and executive summary\n- Well-organized sections with headings\n- Citations linking back to source pages\n- Actionable conclusions or next steps\n\n## Output Formats\n\nChoose the appropriate format based on request:\n\n**Research Summary**: See [reference/research-summary-format.md](reference/research-summary-format.md)\n**Comprehensive Report**: See [reference/comprehensive-report-format.md](reference/comprehensive-report-format.md)\n**Quick Brief**: See [reference/quick-brief-format.md](reference/quick-brief-format.md)\n\n## Best Practices\n\n1. **Cast a wide net first**: Start with broad searches, then narrow down\n2. **Cite sources**: Always link back to source pages using mentions\n3. **Verify recency**: Check page last-edited dates for current information\n4. **Cross-reference**: Validate findings across multiple sources\n5. **Structure clearly**: Use headings, bullets, and formatting for readability\n\n## Page Placement\n\nBy default, create research documents as standalone pages. If the user specifies:\n- A parent page โ†’ use `page_id` parent\n- A database โ†’ fetch the database first, then use appropriate `data_source_id`\n- A teamspace โ†’ create in that context\n\n## Advanced Features\n\n**Search filtering**: See [reference/advanced-search.md](reference/advanced-search.md)\n**Citation styles**: See [reference/citations.md](reference/citations.md)\n\n## Common Issues\n\n**\"No results found\"**: Try broader search terms or different teamspaces\n**\"Too many results\"**: Add filters or search within specific pages\n**\"Can't access page\"**: User may lack permissions, ask them to verify access\n\n## Examples\n\nSee [examples/](examples/) for complete workflow demonstrations:\n- [examples/market-research.md](examples/market-research.md) - Researching market trends\n- [examples/technical-investigation.md](examples/technical-investigation.md) - Technical deep-dive\n- [examples/competitor-analysis.md](examples/competitor-analysis.md) - Multi-source synthesis","schemaVersion":1},"repoUrl":"https://github.com/Prat011/awesome-llm-skills/tree/master/notion-research-documentation","tags":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"awesome-llm-skills","audit":{"files":["slack-gif-creator/requirements.txt"],"binaries":[],"findings":[{"kind":"dependency","rule":"DP-04","message":"Python dependencies are not pinned and there is no lock file.","surface":"slack-gif-creator/requirements.txt","evidence":"pillow>=10.0.0, imageio>=2.31.0, imageio-ffmpeg>=0.4.9, numpy>=1.24.0","severity":"medium"}],"packages":4,"auditedAt":"2026-09-25T11:52:30.068Z","lockfiles":[]},"forks":313,"owner":"Prat011","stars":1761,"topics":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms","openai","opencode","qwen","qwen-coder","skills"],"license":null,"fullName":"Prat011/awesome-llm-skills","homepage":null,"language":"Python","pushedAt":"2026-07-14T09:53:56Z","avatarUrl":"https://avatars.githubusercontent.com/u/67639393?v=4","crawledAt":"2026-09-25T11:52:22.319Z","openIssues":170,"manifestFile":"SKILL.md","manifestPath":"notion-research-documentation/SKILL.md","defaultBranch":"master"},"readme":"# Research & Documentation\n\nEnables comprehensive research workflows: search for information across your Notion workspace, fetch and analyze relevant pages, synthesize findings, and create well-structured documentation.\n\n## Quick Start\n\nWhen asked to research and document a topic:\n\n1. **Search for relevant content**: Use `Notion:notion-search` to find pages\n2. **Fetch detailed information**: Use `Notion:notion-fetch` to read full page content\n3. **Synthesize findings**: Analyze and combine information from multiple sources\n4. **Create structured output**: Use `Notion:notion-create-pages` to write documentation\n\n## Research Workflow\n\n### Step 1: Search for relevant information\n\n```\nUse Notion:notion-search with the research topic\nFilter by teamspace if scope is known\nReview search results to identify most relevant pages\n```\n\n### Step 2: Fetch page content\n\n```\nUse Notion:notion-fetch for each relevant page URL\nCollect content from all relevant sources\nNote key findings, quotes, and data points\n```\n\n### Step 3: Synthesize findings\n\nAnalyze the collected information:\n- Identify key themes and patterns\n- Connect related concepts across sources\n- Note gaps or conflicting information\n- Organize findings logically\n\n### Step 4: Create structured documentation\n\nUse the appropriate documentation template (see [reference/format-selection-guide.md](reference/format-selection-guide.md)) to structure output:\n- Clear title and executive summary\n- Well-organized sections with headings\n- Citations linking back to source pages\n- Actionable conclusions or next steps\n\n## Output Formats\n\nChoose the appropriate format based on request:\n\n**Research Summary**: See [reference/research-summary-format.md](reference/research-summary-format.md)\n**Comprehensive Report**: See [reference/comprehensive-report-format.md](reference/comprehensive-report-format.md)\n**Quick Brief**: See [reference/quick-brief-format.md](reference/quick-brief-format.md)\n\n## Best Practices\n\n1. **Cast a wide net first**: Start with broad searches, then narrow down\n2. **Cite sources**: Always link back to source pages using mentions\n3. **Verify recency**: Check page last-edited dates for current information\n4. **Cross-reference**: Validate findings across multiple sources\n5. **Structure clearly**: Use headings, bullets, and formatting for readability\n\n## Page Placement\n\nBy default, create research documents as standalone pages. If the user specifies:\n- A parent page โ†’ use `page_id` parent\n- A database โ†’ fetch the database first, then use appropriate `data_source_id`\n- A teamspace โ†’ create in that context\n\n## Advanced Features\n\n**Search filtering**: See [reference/advanced-search.md](reference/advanced-search.md)\n**Citation styles**: See [reference/citations.md](reference/citations.md)\n\n## Common Issues\n\n**\"No results found\"**: Try broader search terms or different teamspaces\n**\"Too many results\"**: Add filters or search within specific pages\n**\"Can't access page\"**: User may lack permissions, ask them to verify access\n\n## Examples\n\nSee [examples/](examples/) for complete workflow demonstrations:\n- [examples/market-research.md](examples/market-research.md) - Researching market trends\n- [examples/technical-investigation.md](examples/technical-investigation.md) - Technical deep-dive\n- [examples/competitor-analysis.md](examples/competitor-analysis.md) - Multi-source synthesis","createdAt":"2026-09-25T11:52:30.338Z","updatedAt":"2026-09-25T11:52:30.338Z"},{"id":"cmugwiidn026tqu069q5j035i","slug":"prat011-awesome-llm-skills-notion-spec-to-implementation","name":"notion-spec-to-implementation","description":"Turns product or tech specs into concrete Notion tasks that Claude code can implement. Breaks down spec pages into detailed implementation plans with clear tasks, acceptance criteria, and progress tracking to guide development from requirements to completion.","authorId":"gh:prat011","authorName":"Prat011","version":"0.1.0","category":"Prompt","securityLevel":"Community","downloadsCount":0,"githubStars":1761,"pricePerCall":0,"manifest":{"name":"notion-spec-to-implementation","tools":[],"category":"Prompt","entrypoint":{"type":"prompt"},"description":"Turns product or tech specs into concrete Notion tasks that Claude code can implement. Breaks down spec pages into detailed implementation plans with clear tasks, acceptance criteria, and progress tracking to guide development from requirements to completion.","permissions":[],"systemPrompt":"# Spec to Implementation\n\nTransforms specifications into actionable implementation plans with progress tracking. Fetches spec documents, extracts requirements, breaks down into tasks, and manages implementation workflow.\n\n## Quick Start\n\nWhen asked to implement a specification:\n\n1. **Find spec**: Use `Notion:notion-search` to locate specification page\n2. **Fetch spec**: Use `Notion:notion-fetch` to read specification content\n3. **Extract requirements**: Parse and structure requirements from spec\n4. **Create plan**: Use `Notion:notion-create-pages` for implementation plan\n5. **Find task database**: Use `Notion:notion-search` to locate tasks database\n6. **Create tasks**: Use `Notion:notion-create-pages` for individual tasks in task database\n7. **Track progress**: Use `Notion:notion-update-page` to log progress and update status\n\n## Implementation Workflow\n\n### Step 1: Find the specification\n\n```\n1. Search for spec:\n - Use Notion:notion-search with spec name or topic\n - Apply filters if needed (e.g., created_date_range, teamspace_id)\n - Look for spec title or keyword matches\n - If not found or ambiguous, ask user for spec URL/ID\n\nExample searches:\n- \"User Authentication spec\"\n- \"Payment Integration specification\"\n- \"Mobile App Redesign PRD\"\n```\n\n### Step 2: Fetch and analyze specification\n\n```\n1. Fetch spec page:\n - Use Notion:notion-fetch with spec URL/ID from search results\n - Read full content including requirements, design, constraints\n\n2. Parse specification:\n - Identify functional requirements\n - Note non-functional requirements (performance, security, etc.)\n - Extract acceptance criteria\n - Identify dependencies and blockers\n```\n\nSee [reference/spec-parsing.md](reference/spec-parsing.md) for parsing patterns.\n\n### Step 3: Create implementation plan\n\n```\n1. Break down into phases/milestones\n2. Identify technical approach\n3. List required tasks\n4. Estimate effort\n5. Identify risks\n\nUse implementation plan template (see [reference/standard-implementation-plan.md](reference/standard-implementation-plan.md) or [reference/quick-implementation-plan.md](reference/quick-implementation-plan.md))\n```\n\n### Step 4: Create implementation plan page\n\n```\nUse Notion:notion-create-pages:\n- Title: \"Implementation Plan: [Feature Name]\"\n- Content: Structured plan with phases, tasks, timeline\n- Link back to original spec\n- Add to appropriate location (project page, database)\n```\n\n### Step 5: Find task database\n\n```\n1. Search for task database:\n - Use Notion:notion-search to find \"Tasks\" or \"Task Management\" database\n - Look for engineering/project task tracking system\n - If not found or ambiguous, ask user for database location\n\n2. Fetch database schema:\n - Use Notion:notion-fetch with database URL/ID\n - Get property names, types, and options\n - Identify correct data source from tags\n - Note required properties for new tasks\n```\n\n### Step 6: Create implementation tasks\n\n```\nFor each task in plan:\n1. Create task in task database using Notion:notion-create-pages\n2. Use parent: { data_source_id: 'collection://...' }\n3. Set properties from schema:\n - Name/Title: Task description\n - Status: To Do\n - Priority: Based on criticality\n - Related Tasks: Link to spec and plan\n4. Add implementation details in content\n```\n\nSee [reference/task-creation.md](reference/task-creation.md) for task patterns.\n\n### Step 7: Begin implementation\n\n```\n1. Update task status to \"In Progress\"\n2. Add initial progress note\n3. Document approach and decisions\n4. Link relevant resources\n```\n\n### Step 8: Track progress\n\n```\nRegular updates:\n1. Update task properties (status, progress)\n2. Add progress notes with:\n - What's completed\n - Current focus\n - Blockers/issues\n3. Update implementation plan with milestone completion\n4. Link to related work (PRs, designs, etc.)\n```\n\nSee [reference/progress-tracking.md](reference/progress-tracking.md) for tracking patterns.\n\n## Spec Analysis Patterns\n\n**Functional Requirements**: User stories, feature descriptions, workflows, data requirements, integration points\n\n**Non-Functional Requirements**: Performance targets, security requirements, scalability needs, availability, compliance\n\n**Acceptance Criteria**: Testable conditions, user validation points, performance benchmarks, completion definitions\n\nSee [reference/spec-parsing.md](reference/spec-parsing.md) for detailed parsing techniques.\n\n## Implementation Plan Structure\n\n**Plan includes**: Overview โ†’ Linked Spec โ†’ Requirements Summary โ†’ Technical Approach โ†’ Implementation Phases (Goal, Tasks checklist, Estimated effort) โ†’ Dependencies โ†’ Risks & Mitigation โ†’ Timeline โ†’ Success Criteria\n\nSee [reference/standard-implementation-plan.md](reference/standard-implementation-plan.md) for full plan template.\n\n## Task Breakdown Patterns\n\n**By Component**: Database, API endpoints, frontend components, integration, testing\n**By Feature Slice**: Vertical slices (auth flow, data entry, report generation)\n**By Priority**: P0 (must have), P1 (important), P2 (nice to have)\n\n\n## Progress Logging\n\n**Daily Updates** (active work): Add progress note with completed items, current focus, blockers\n**Milestone Updates** (major progress): Update plan checkboxes, add milestone summary, adjust timeline\n**Status Changes** (task transitions): Update properties (In Progress โ†’ In Review โ†’ Done), add completion notes, link deliverables\n\n**Progress Format**: Date heading โ†’ Completed โ†’ In Progress โ†’ Next Steps โ†’ Blockers โ†’ Notes\n\nSee [reference/progress-tracking.md](reference/progress-tracking.md) for detailed patterns.\n\n## Linking Spec to Implementation\n\n**Forward Links**: Update spec page with \"Implementation\" section linking to plan and tasks\n**Backward Links**: Reference spec in plan and tasks with \"Specification\" section\n**Bidirectional Traceability**: Maintain both directions for easy tracking\n\n## Implementation Status Tracking\n\n**Plan Status**: Update with phase completion (โœ… Complete, ๐Ÿ”„ In Progress %, โณ Not Started) and overall percentage\n**Task Aggregation**: Query task database by plan ID to generate summary (complete, in progress, blocked, not started)\n\n## Handling Spec Changes\n\n**Detection**: Fetch updated spec โ†’ compare with plan โ†’ identify new requirements โ†’ assess impact\n**Propagation**: Update plan โ†’ create new tasks โ†’ update affected tasks โ†’ add change note โ†’ notify via comments\n**Change Log**: Track spec evolution with date, what changed, and impact\n\n## Common Patterns\n\n**Feature Flag**: Backend (behind flag) โ†’ Testing โ†’ Frontend (flagged) โ†’ Internal rollout โ†’ External rollout\n**Database Migration**: Schema design โ†’ Migration script โ†’ Staging test โ†’ Production migration โ†’ Validation\n**API Development**: API design โ†’ Backend implementation โ†’ Testing & docs โ†’ Client integration โ†’ Deployment\n\n\n## Best Practices\n\n1. **Always link spec and implementation**: Maintain bidirectional references\n2. **Break down into small tasks**: Each task should be completable in 1-2 days\n3. **Extract clear acceptance criteria**: Know when \"done\" is done\n4. **Identify dependencies early**: Note blockers in plan\n5. **Update progress regularly**: Daily notes for active work\n6. **Track changes**: Document spec updates and their impact\n7. **Use checklists**: Visual progress indicators help everyone\n8. **Link deliverables**: PRs, designs, docs should link back to tasks\n\n## Advanced Features\n\nFor additional implementation patterns and techniques, see the reference files in [reference/](reference/).\n\n## Common Issues\n\n**\"Can't find spec\"**: Use Notion:notion-search with spec name/topic, try broader terms, or ask user for URL\n**\"Multiple specs found\"**: Ask user which spec to implement or show options\n**\"Can't find task database\"**: Search for \"Tasks\" or \"Task Management\", or ask user for database location\n**\"Spec unclear\"**: Note ambiguities in plan, create clarification tasks\n**\"Requirements conflicting\"**: Document conflicts, create decision task\n**\"Scope too large\"**: Break into smaller specs/phases\n\n## Examples\n\nSee [examples/](examples/) for complete workflows:\n- [examples/api-feature.md](examples/api-feature.md) - API feature implementation\n- [examples/ui-component.md](examples/ui-component.md) - Frontend component\n- [examples/database-migration.md](examples/database-migration.md) - Schema changes","schemaVersion":1},"repoUrl":"https://github.com/Prat011/awesome-llm-skills/tree/master/notion-spec-to-implementation","tags":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"awesome-llm-skills","audit":{"files":["slack-gif-creator/requirements.txt"],"binaries":[],"findings":[{"kind":"dependency","rule":"DP-04","message":"Python dependencies are not pinned and there is no lock file.","surface":"slack-gif-creator/requirements.txt","evidence":"pillow>=10.0.0, imageio>=2.31.0, imageio-ffmpeg>=0.4.9, numpy>=1.24.0","severity":"medium"}],"packages":4,"auditedAt":"2026-09-25T11:52:30.068Z","lockfiles":[]},"forks":313,"owner":"Prat011","stars":1761,"topics":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms","openai","opencode","qwen","qwen-coder","skills"],"license":null,"fullName":"Prat011/awesome-llm-skills","homepage":null,"language":"Python","pushedAt":"2026-07-14T09:53:56Z","avatarUrl":"https://avatars.githubusercontent.com/u/67639393?v=4","crawledAt":"2026-09-25T11:52:22.319Z","openIssues":170,"manifestFile":"SKILL.md","manifestPath":"notion-spec-to-implementation/SKILL.md","defaultBranch":"master"},"readme":"# Spec to Implementation\n\nTransforms specifications into actionable implementation plans with progress tracking. Fetches spec documents, extracts requirements, breaks down into tasks, and manages implementation workflow.\n\n## Quick Start\n\nWhen asked to implement a specification:\n\n1. **Find spec**: Use `Notion:notion-search` to locate specification page\n2. **Fetch spec**: Use `Notion:notion-fetch` to read specification content\n3. **Extract requirements**: Parse and structure requirements from spec\n4. **Create plan**: Use `Notion:notion-create-pages` for implementation plan\n5. **Find task database**: Use `Notion:notion-search` to locate tasks database\n6. **Create tasks**: Use `Notion:notion-create-pages` for individual tasks in task database\n7. **Track progress**: Use `Notion:notion-update-page` to log progress and update status\n\n## Implementation Workflow\n\n### Step 1: Find the specification\n\n```\n1. Search for spec:\n - Use Notion:notion-search with spec name or topic\n - Apply filters if needed (e.g., created_date_range, teamspace_id)\n - Look for spec title or keyword matches\n - If not found or ambiguous, ask user for spec URL/ID\n\nExample searches:\n- \"User Authentication spec\"\n- \"Payment Integration specification\"\n- \"Mobile App Redesign PRD\"\n```\n\n### Step 2: Fetch and analyze specification\n\n```\n1. Fetch spec page:\n - Use Notion:notion-fetch with spec URL/ID from search results\n - Read full content including requirements, design, constraints\n\n2. Parse specification:\n - Identify functional requirements\n - Note non-functional requirements (performance, security, etc.)\n - Extract acceptance criteria\n - Identify dependencies and blockers\n```\n\nSee [reference/spec-parsing.md](reference/spec-parsing.md) for parsing patterns.\n\n### Step 3: Create implementation plan\n\n```\n1. Break down into phases/milestones\n2. Identify technical approach\n3. List required tasks\n4. Estimate effort\n5. Identify risks\n\nUse implementation plan template (see [reference/standard-implementation-plan.md](reference/standard-implementation-plan.md) or [reference/quick-implementation-plan.md](reference/quick-implementation-plan.md))\n```\n\n### Step 4: Create implementation plan page\n\n```\nUse Notion:notion-create-pages:\n- Title: \"Implementation Plan: [Feature Name]\"\n- Content: Structured plan with phases, tasks, timeline\n- Link back to original spec\n- Add to appropriate location (project page, database)\n```\n\n### Step 5: Find task database\n\n```\n1. Search for task database:\n - Use Notion:notion-search to find \"Tasks\" or \"Task Management\" database\n - Look for engineering/project task tracking system\n - If not found or ambiguous, ask user for database location\n\n2. Fetch database schema:\n - Use Notion:notion-fetch with database URL/ID\n - Get property names, types, and options\n - Identify correct data source from tags\n - Note required properties for new tasks\n```\n\n### Step 6: Create implementation tasks\n\n```\nFor each task in plan:\n1. Create task in task database using Notion:notion-create-pages\n2. Use parent: { data_source_id: 'collection://...' }\n3. Set properties from schema:\n - Name/Title: Task description\n - Status: To Do\n - Priority: Based on criticality\n - Related Tasks: Link to spec and plan\n4. Add implementation details in content\n```\n\nSee [reference/task-creation.md](reference/task-creation.md) for task patterns.\n\n### Step 7: Begin implementation\n\n```\n1. Update task status to \"In Progress\"\n2. Add initial progress note\n3. Document approach and decisions\n4. Link relevant resources\n```\n\n### Step 8: Track progress\n\n```\nRegular updates:\n1. Update task properties (status, progress)\n2. Add progress notes with:\n - What's completed\n - Current focus\n - Blockers/issues\n3. Update implementation plan with milestone completion\n4. Link to related work (PRs, designs, etc.)\n```\n\nSee [reference/progress-tracking.md](reference/progress-tracking.md) for tracking patterns.\n\n## Spec Analysis Patterns\n\n**Functional Requirements**: ","createdAt":"2026-09-25T11:52:30.347Z","updatedAt":"2026-09-25T11:52:30.347Z"},{"id":"cmugwiidx026wqu06f4fv6whi","slug":"prat011-awesome-llm-skills-raffle-winner-picker","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.","authorId":"gh:prat011","authorName":"Prat011","version":"0.1.0","category":"Prompt","securityLevel":"Community","downloadsCount":0,"githubStars":1761,"pricePerCall":0,"manifest":{"name":"raffle-winner-picker","tools":[],"category":"Prompt","entrypoint":{"type":"prompt"},"description":"Picks random winners from lists, spreadsheets, or Google Sheets for giveaways, raffles, and contests. Ensures fair, unbiased selection with transparency.","permissions":[],"systemPrompt":"# Raffle Winner Picker\n\nThis skill randomly selects winners from lists, spreadsheets, or Google Sheets for giveaways and contests.\n\n## When to Use This Skill\n\n- Running social media giveaways\n- Picking raffle winners at events\n- Randomly selecting participants for surveys or tests\n- Choosing winners from contest submissions\n- Fair distribution of limited spots or resources\n- Random team assignments\n\n## What This Skill Does\n\n1. **Random Selection**: Uses cryptographically random selection\n2. **Multiple Sources**: Works with CSV, Excel, Google Sheets, or plain lists\n3. **Multiple Winners**: Can pick one or multiple winners\n4. **Duplicate Prevention**: Ensures the same person can't win twice\n5. **Transparent Results**: Shows the selection process clearly\n6. **Winner Details**: Displays all relevant information about winners\n\n## How to Use\n\n### From Google Sheets\n\n```\nPick a random row from this Google Sheet to select a winner \nfor a giveaway: [Sheet URL]\n```\n\n### From Local File\n\n```\nPick 3 random winners from entries.csv\n```\n\n### From List\n\n```\nPick a random winner from this list:\n- Alice (alice@email.com)\n- Bob (bob@email.com)\n- Carol (carol@email.com)\n...\n```\n\n### Multiple Winners\n\n```\nPick 5 random winners from contest-entries.xlsx, \nmake sure no duplicates\n```\n\n## Example\n\n**User**: \"Pick a random row from this Google Sheet to select a winner for a giveaway.\"\n\n**Output**:\n```\nAccessing Google Sheet...\nTotal entries found: 247\n\nRandomly selecting winner...\n\n๐ŸŽ‰ WINNER SELECTED! ๐ŸŽ‰\n\nRow #142\nName: Sarah Johnson\nEmail: sarah.j@email.com\nEntry Date: March 10, 2024\nComment: \"Love your newsletter!\"\n\nSelection method: Cryptographically random\nTimestamp: 2024-03-15 14:32:18 UTC\n\nWould you like to:\n- Pick another winner (excluding Sarah)?\n- Export winner details?\n- Pick runner-ups?\n```\n\n**Inspired by:** Lenny's use case - picking a Sora 2 giveaway winner from his subscriber Slack community\n\n## Features\n\n### Fair Selection\n- Uses secure random number generation\n- No bias or patterns\n- Transparent process\n- Repeatable with seed (for verification)\n\n### Exclusions\n```\nPick a random winner excluding previous winners: \nAlice, Bob, Carol\n```\n\n### Weighted Selection\n```\nPick a winner with weighted probability based on \nthe \"entries\" column (1 entry = 1 ticket)\n```\n\n### Runner-ups\n```\nPick 1 winner and 3 runner-ups from the list\n```\n\n## Example Workflows\n\n### Social Media Giveaway\n1. Export entries from Google Form to Sheets\n2. \"Pick a random winner from [Sheet URL]\"\n3. Verify winner details\n4. Announce publicly with timestamp\n\n### Event Raffle\n1. Create CSV of attendee names and emails\n2. \"Pick 10 random winners from attendees.csv\"\n3. Export winner list\n4. Email winners directly\n\n### Team Assignment\n1. Have list of participants\n2. \"Randomly split this list into 4 equal teams\"\n3. Review assignments\n4. Share team rosters\n\n## Tips\n\n- **Document the process**: Save the timestamp and method\n- **Public announcement**: Share selection details for transparency\n- **Check eligibility**: Verify winner meets contest rules\n- **Have backups**: Pick runner-ups in case winner is ineligible\n- **Export results**: Save winner list for records\n\n## Privacy & Fairness\n\nโœ“ Uses cryptographically secure randomness\nโœ“ No manipulation possible\nโœ“ Timestamp recorded for verification\nโœ“ Can provide seed for third-party verification\nโœ“ Respects data privacy\n\n## Common Use Cases\n\n- Newsletter subscriber giveaways\n- Product launch raffles\n- Conference ticket drawings\n- Beta tester selection\n- Focus group participant selection\n- Random prize distribution at events","schemaVersion":1},"repoUrl":"https://github.com/Prat011/awesome-llm-skills/tree/master/raffle-winner-picker","tags":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"awesome-llm-skills","audit":{"files":["slack-gif-creator/requirements.txt"],"binaries":[],"findings":[{"kind":"dependency","rule":"DP-04","message":"Python dependencies are not pinned and there is no lock file.","surface":"slack-gif-creator/requirements.txt","evidence":"pillow>=10.0.0, imageio>=2.31.0, imageio-ffmpeg>=0.4.9, numpy>=1.24.0","severity":"medium"}],"packages":4,"auditedAt":"2026-09-25T11:52:30.068Z","lockfiles":[]},"forks":313,"owner":"Prat011","stars":1761,"topics":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms","openai","opencode","qwen","qwen-coder","skills"],"license":null,"fullName":"Prat011/awesome-llm-skills","homepage":null,"language":"Python","pushedAt":"2026-07-14T09:53:56Z","avatarUrl":"https://avatars.githubusercontent.com/u/67639393?v=4","crawledAt":"2026-09-25T11:52:22.319Z","openIssues":170,"manifestFile":"SKILL.md","manifestPath":"raffle-winner-picker/SKILL.md","defaultBranch":"master"},"readme":"# Raffle Winner Picker\n\nThis skill randomly selects winners from lists, spreadsheets, or Google Sheets for giveaways and contests.\n\n## When to Use This Skill\n\n- Running social media giveaways\n- Picking raffle winners at events\n- Randomly selecting participants for surveys or tests\n- Choosing winners from contest submissions\n- Fair distribution of limited spots or resources\n- Random team assignments\n\n## What This Skill Does\n\n1. **Random Selection**: Uses cryptographically random selection\n2. **Multiple Sources**: Works with CSV, Excel, Google Sheets, or plain lists\n3. **Multiple Winners**: Can pick one or multiple winners\n4. **Duplicate Prevention**: Ensures the same person can't win twice\n5. **Transparent Results**: Shows the selection process clearly\n6. **Winner Details**: Displays all relevant information about winners\n\n## How to Use\n\n### From Google Sheets\n\n```\nPick a random row from this Google Sheet to select a winner \nfor a giveaway: [Sheet URL]\n```\n\n### From Local File\n\n```\nPick 3 random winners from entries.csv\n```\n\n### From List\n\n```\nPick a random winner from this list:\n- Alice (alice@email.com)\n- Bob (bob@email.com)\n- Carol (carol@email.com)\n...\n```\n\n### Multiple Winners\n\n```\nPick 5 random winners from contest-entries.xlsx, \nmake sure no duplicates\n```\n\n## Example\n\n**User**: \"Pick a random row from this Google Sheet to select a winner for a giveaway.\"\n\n**Output**:\n```\nAccessing Google Sheet...\nTotal entries found: 247\n\nRandomly selecting winner...\n\n๐ŸŽ‰ WINNER SELECTED! ๐ŸŽ‰\n\nRow #142\nName: Sarah Johnson\nEmail: sarah.j@email.com\nEntry Date: March 10, 2024\nComment: \"Love your newsletter!\"\n\nSelection method: Cryptographically random\nTimestamp: 2024-03-15 14:32:18 UTC\n\nWould you like to:\n- Pick another winner (excluding Sarah)?\n- Export winner details?\n- Pick runner-ups?\n```\n\n**Inspired by:** Lenny's use case - picking a Sora 2 giveaway winner from his subscriber Slack community\n\n## Features\n\n### Fair Selection\n- Uses secure random number generation\n- No bias or patterns\n- Transparent process\n- Repeatable with seed (for verification)\n\n### Exclusions\n```\nPick a random winner excluding previous winners: \nAlice, Bob, Carol\n```\n\n### Weighted Selection\n```\nPick a winner with weighted probability based on \nthe \"entries\" column (1 entry = 1 ticket)\n```\n\n### Runner-ups\n```\nPick 1 winner and 3 runner-ups from the list\n```\n\n## Example Workflows\n\n### Social Media Giveaway\n1. Export entries from Google Form to Sheets\n2. \"Pick a random winner from [Sheet URL]\"\n3. Verify winner details\n4. Announce publicly with timestamp\n\n### Event Raffle\n1. Create CSV of attendee names and emails\n2. \"Pick 10 random winners from attendees.csv\"\n3. Export winner list\n4. Email winners directly\n\n### Team Assignment\n1. Have list of participants\n2. \"Randomly split this list into 4 equal teams\"\n3. Review assignments\n4. Share team rosters\n\n## Tips\n\n- **Document the process**: Save the timestamp and method\n- **Public announcement**: Share selection details for transparency\n- **Check eligibility**: Verify winner meets contest rules\n- **Have backups**: Pick runner-ups in case winner is ineligible\n- **Export results**: Save winner list for records\n\n## Privacy & Fairness\n\nโœ“ Uses cryptographically secure randomness\nโœ“ No manipulation possible\nโœ“ Timestamp recorded for verification\nโœ“ Can provide seed for third-party verification\nโœ“ Respects data privacy\n\n## Common Use Cases\n\n- Newsletter subscriber giveaways\n- Product launch raffles\n- Conference ticket drawings\n- Beta tester selection\n- Focus group participant selection\n- Random prize distribution at events","createdAt":"2026-09-25T11:52:30.357Z","updatedAt":"2026-09-25T11:52:30.357Z"},{"id":"cmugwiiea026zqu06wmhnu8vs","slug":"prat011-awesome-llm-skills-resemble-detect","name":"resemble-detect","description":"Deepfake detection and media safety โ€” detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI","authorId":"gh:prat011","authorName":"Prat011","version":"0.1.0","category":"Prompt","securityLevel":"Community","downloadsCount":0,"githubStars":1761,"pricePerCall":0,"manifest":{"name":"resemble-detect","tools":[],"category":"Prompt","entrypoint":{"type":"prompt"},"description":"Deepfake detection and media safety โ€” detect AI-generated audio, images, video, and text, trace synthesis sources, apply watermarks, verify speaker identity, and analyze media intelligence using Resemble AI","permissions":[],"systemPrompt":"# Resemble Detect โ€” Deepfake Detection & Media Safety\n\nAnalyze audio, image, video, and text for synthetic manipulation, AI-generated content, watermarks, speaker identity, and media intelligence using the Resemble AI platform.\n\n## Core Principle โ€” THE IRON LAW\n\n**\"NEVER DECLARE MEDIA AS REAL OR FAKE WITHOUT A COMPLETED DETECTION RESULT.\"**\n\nDo not guess, infer, or speculate about media authenticity. Every authenticity claim must be backed by a completed Resemble detect job with a returned `label`, `score`, and `status: \"completed\"`. If the detection is still `processing`, wait. If it `failed`, say so โ€” do not substitute your own judgment.\n\n## When to Use\n\nUse this skill whenever the user's request involves any of these:\n\n- Checking if audio, video, image, or text is AI-generated or manipulated\n- Detecting deepfakes in any media format\n- Verifying media authenticity or provenance\n- Identifying which AI platform synthesized audio (source tracing)\n- Applying or detecting watermarks on media\n- Analyzing media for speaker info, emotion, transcription, or misinformation\n- Asking natural-language questions about detection results\n- Matching or verifying speaker identity against known voice profiles\n- Detecting AI-generated or machine-written text\n- Any mention of: \"deepfake\", \"fake detection\", \"synthetic media\", \"voice verification\", \"watermark\", \"media forensics\", \"authenticity check\", \"source tracing\", \"is this real\", \"AI-written text\", \"text detection\"\n\n**Do NOT use** for text-to-speech generation, voice cloning, or speech-to-text transcription โ€” those are separate Resemble capabilities.\n\n## Capability Decision Tree\n\n| User wants to... | Use this | API endpoint |\n|-------------------------------------------------------|---------------------------|----------------------------|\n| Check if media is AI-generated / deepfake | **Deepfake Detection** | `POST /detect` |\n| Know *which AI platform* made fake audio | **Audio Source Tracing** | `POST /detect` with flag |\n| Get speaker info, emotion, transcription from media | **Intelligence** | `POST /intelligence` |\n| Ask questions about a completed detection | **Detect Intelligence** | `POST /detects/{uuid}/intelligence` |\n| Apply an invisible watermark to media | **Watermark Apply** | `POST /watermark/apply` |\n| Check if media contains a watermark | **Watermark Detect** | `POST /watermark/detect` |\n| Verify a speaker's identity against known profiles | **Identity Search** | `POST /identity/search` |\n| Check if text is AI-generated | **Text Detection** | `POST /text_detect` |\n| Create a voice identity profile for future matching | **Identity Create** | `POST /identity` |\n\nWhen multiple capabilities apply (e.g., user wants deepfake detection AND intelligence), combine them in a single `POST /detect` call using the `intelligence: true` flag rather than making separate requests.\n\n## Required Setup\n\n- **API Key**: Bearer token from the Resemble AI dashboard\n- **Base URL**: `https://app.resemble.ai/api/v2`\n- **Auth Header**: `Authorization: Bearer `\n- **Media Requirement**: All media must be at a publicly accessible HTTPS URL\n\nIf the user provides a local file path instead of a URL, inform them the file must be hosted at a public HTTPS URL first. Do not attempt to upload local files to the API.\n\n## MCP Tools Available\n\nWhen the Resemble MCP server is connected, use these tools instead of raw API calls:\n\n| Tool | Purpose |\n|---------------------------|---------------------------------------------------|\n| `resemble_docs_lookup` | Get comprehensive docs for any detect sub-topic |\n| `resemble_search` | Search across all documentation |\n| `resemble_api_endpoint` | Get exact OpenAPI spec for any endpoint |\n| `resemble_api_search` | Find endpoints by keyword |\n| `resemble_get_page` | Read specific documentation pages |\n| `resemble_list_topics` | List all available topics |\n\n**Tool usage pattern**: Use `resemble_docs_lookup` with topic `\"detect\"` to get the full picture, then `resemble_api_endpoint` for exact request/response schemas before making API calls.\n\n---\n\n## Phase 1: Deepfake Detection\n\nThe core capability. Submit any audio, image, or video for AI-generated content analysis.\n\n### Submit a Detection\n\n```\nPOST /detect\nContent-Type: application/json\nAuthorization: Bearer \n\n{\n \"url\": \"https://example.com/media.mp4\",\n \"visualize\": true,\n \"intelligence\": true,\n \"audio_source_tracing\": true\n}\n```\n\n**Parameters:**\n\n| Parameter | Type | Required | Description |\n|------------------------|---------|----------|----------------------------------------------------------|\n| `url` | string | Yes | HTTPS URL to audio, image, or video file |\n| `callback_url` | string | No | Webhook URL for async completion notification |\n| `visualize` | boolean | No | Generate heatmap/visualization artifacts |\n| `intelligence` | boolean | No | Run multimodal intelligence analysis alongside detection |\n| `audio_source_tracing` | boolean | No | Identify which AI platform synthesized fake audio |\n| `frame_length` | integer | No | Audio/video analysis window size in seconds (1โ€“4, default 2) |\n| `start_region` | number | No | Start of segment to analyze (seconds) |\n| `end_region` | number | No | End of segment to analyze (seconds) |\n| `model_types` | string | No | `\"image\"` or `\"talking_head\"` (for face-swap detection) |\n| `use_reverse_search` | boolean | No | Enable reverse image search (image only) |\n| `use_ood_detector` | boolean | No | Enable out-of-distribution detection |\n| `zero_retention_mode` | boolean | No | Auto-delete media after detection completes |\n\n**Supported formats:**\n- Audio: WAV, MP3, OGG, M4A, FLAC\n- Video: MP4, MOV, AVI, WMV\n- Image: JPG, PNG, GIF, WEBP\n\n### Poll for Results\n\nDetection is asynchronous. Poll `GET /detect/{uuid}` until `status` is `\"completed\"` or `\"failed\"`.\n\n```\nGET /detect/{uuid}\nAuthorization: Bearer \n```\n\n**Polling best practice:** Start at 2s intervals, back off to 5s, then 10s. Most detections complete within 10โ€“60 seconds depending on media length.\n\n### Reading Results by Media Type\n\n**Audio results** โ€” in `metrics`:\n```json\n{\n \"label\": \"fake\",\n \"score\": [\"0.92\", \"0.88\", \"0.95\"],\n \"consistency\": \"0.91\",\n \"aggregated_score\": \"0.92\",\n \"image\": \"https://...\"\n}\n```\n- `label`: `\"fake\"` or `\"real\"` โ€” the verdict\n- `score`: Per-chunk prediction scores (array)\n- `aggregated_score`: Overall confidence (0.0โ€“1.0, higher = more likely synthetic)\n- `consistency`: How consistent the prediction is across chunks\n- `image`: Visualization heatmap URL (if `visualize: true`)\n\n**Image results** โ€” in `image_metrics`:\n```json\n{\n \"type\": \"ImageAnalysis\",\n \"label\": \"fake\",\n \"score\": 0.87,\n \"image\": \"https://...\",\n \"ifl\": { \"score\": 0.82, \"heatmap\": \"https://...\" },\n \"reverse_image_search_sources\": [\n { \"url\": \"...\", \"title\": \"...\", \"verdict\": \"known_fake\", \"similarity\": 0.95 }\n ]\n}\n```\n- `label` / `score`: Verdict and confidence\n- `ifl`: Invisible Frequency Layer analysis with heatmap\n- `reverse_image_search_sources`: Known sources found online (if `use_reverse_search: true`)\n\n**Video results** โ€” in `video_metrics`:\n```json\n{\n \"label\": \"fake\",\n \"score\": 0.89,\n \"certainty\": 0.91,\n \"children\": [\n {\n \"type\": \"VideoResult\",\n \"conclusion\": \"Fake\",\n \"score\": 0.89,\n \"timestamp\": 2.5,\n \"children\": [...]\n }\n ]\n}\n```\n- Hierarchical tree of frame-level and segment-level results\n- Each child has `timestamp`, `score`, `certainty`, and may have nested `children`\n- Video with audio track returns both `metrics` (audio) and `video_metrics` (visual)\n\n### Interpreting Scores\n\n| Score Range | Interpretation |\n|-------------|-----------------------------------------------------|\n| 0.0 โ€“ 0.3 | Strong indication of authentic/real media |\n| 0.3 โ€“ 0.5 | Inconclusive โ€” recommend additional analysis |\n| 0.5 โ€“ 0.7 | Likely synthetic โ€” flag for review |\n| 0.7 โ€“ 1.0 | High confidence synthetic/AI-generated |\n\n**Always present scores with context.** Say \"The detection returned a score of 0.87, indicating high confidence that this audio is AI-generated\" โ€” never just \"it's fake.\"\n\n---\n\n## Phase 2: Intelligence โ€” Media Analysis\n\nAnalyze media for rich structured insights independent of or alongside detection.\n\n### Standalone Intelligence\n\n```\nPOST /intelligence\nContent-Type: application/json\nAuthorization: Bearer \n\n{\n \"url\": \"https://example.com/audio.mp3\",\n \"json\": true\n}\n```\n\n**Parameters:**\n\n| Parameter | Type | Required | Description |\n|----------------|---------|----------|----------------------------------------------------------|\n| `url` | string | One of | HTTPS URL to media file |\n| `media_token` | string | One of | Token from secure upload (alternative to URL) |\n| `detect_id` | string | No | UUID of existing detect to associate |\n| `media_type` | string | No | `\"audio\"`, `\"video\"`, or `\"image\"` (auto-detected) |\n| `json` | boolean | No | Return structured fields (default: false for audio/video, true for image) |\n| `callback_url` | string | No | Webhook for async mode |\n\n**Audio/Video structured response** (`json: true`):\n- `speaker_info` โ€” speaker description (age, gender)\n- `language` / `dialect` โ€” detected language\n- `emotion` โ€” detected emotional state\n- `speaking_style` โ€” conversational, formal, etc.\n- `context` โ€” inferred context of the speech\n- `message` โ€” content summary\n- `abnormalities` โ€” anomalies detected in the media\n- `transcription` โ€” full transcript\n- `translation` โ€” translation if non-English\n- `misinformation` โ€” misinformation analysis\n\n**Image structured response:**\n- `scene_description` โ€” what the image shows\n- `subjects` โ€” people/objects identified\n- `authenticity_analysis` โ€” visual authenticity assessment\n- `context_and_setting` โ€” environment description\n- `abnormalities` โ€” visual anomalies\n- `misinformation` โ€” misinformation analysis\n\n### Detect Intelligence โ€” Ask Questions About Results\n\nAfter a detection completes, ask natural-language questions about it:\n\n```\nPOST /detects/{detect_uuid}/intelligence\nContent-Type: application/json\nAuthorization: Bearer \n\n{\n \"query\": \"How confident is the model that this audio is fake?\"\n}\n```\n\nThis returns a question UUID. Poll `GET /detects/{detect_uuid}/intelligence/{question_uuid}` until `status` is `\"completed\"` to get the `answer`.\n\n**Good questions to suggest:**\n- \"Summarize the detection results in plain language\"\n- \"What specific indicators suggest this is AI-generated?\"\n- \"How do the audio and video detection results differ?\"\n- \"What is the confidence level and what does it mean?\"\n- \"Are there any inconsistencies in the analysis?\"\n\n**Status flow:** `pending` โ†’ `processing` โ†’ `completed` (or `failed`)\n\n**Prerequisite:** The detection must have `status: \"completed\"`. Submitting a question against a processing or failed detection returns a 422 error.\n\n---\n\n## Phase 3: Audio Source Tracing\n\nWhen audio is detected as synthetic (`label: \"fake\"`), identify which AI platform generated it.\n\n**Enable it** by setting `audio_source_tracing: true` in the `POST /detect` request.\n\n**Result** appears in the detection response under `audio_source_tracing`:\n```json\n{\n \"label\": \"elevenlabs\",\n \"error_message\": null\n}\n```\n\nKnown source labels include: `resemble_ai`, `elevenlabs`, `real`, and others as the model expands.\n\n**Important:** Source tracing only runs when audio is labeled as `\"fake\"`. If the audio is `\"real\"`, no source tracing result will appear.\n\n**Standalone query:**\n- `GET /audio_source_tracings` โ€” list all source tracing reports\n- `GET /audio_source_tracings/{uuid}` โ€” get specific report\n\n---\n\n## Phase 4: Watermarking\n\nApply invisible watermarks to media for provenance tracking, or detect existing watermarks.\n\n### Apply a Watermark\n\n```\nPOST /watermark/apply\nContent-Type: application/json\nAuthorization: Bearer \nPrefer: wait\n\n{\n \"url\": \"https://example.com/image.png\",\n \"strength\": 0.3,\n \"custom_message\": \"my-organization\"\n}\n```\n\n| Parameter | Type | Required | Description |\n|------------------|--------|----------|------------------------------------------------------|\n| `url` | string | Yes | HTTPS URL to media file |\n| `strength` | number | No | Watermark strength 0.0โ€“1.0 (image/video only, default 0.2) |\n| `custom_message` | string | No | Custom message to embed (image/video only, default \"resembleai\") |\n\n- Add `Prefer: wait` header for synchronous response\n- Without it, poll `GET /watermark/apply/{uuid}/result`\n- Response includes `watermarked_media` URL to download the watermarked file\n\n### Detect a Watermark\n\n```\nPOST /watermark/detect\nContent-Type: application/json\nAuthorization: Bearer \nPrefer: wait\n\n{\n \"url\": \"https://example.com/suspect-image.png\"\n}\n```\n\n**Audio detection result:**\n```json\n{ \"has_watermark\": true, \"confidence\": 0.95 }\n```\n\n**Image/Video detection result:**\n```json\n{ \"has_watermark\": true }\n```\n\n---\n\n## Phase 5: Identity โ€” Speaker Verification (Beta)\n\nCreate voice identity profiles and match incoming audio against them.\n\n> **Beta feature** โ€” requires joining the preview program. Inform the user if they encounter access errors.\n\n### Create an Identity Profile\n\n```\nPOST /identity\nContent-Type: application/json\nAuthorization: Bearer \n\n{\n \"audio_url\": \"https://example.com/known-speaker.wav\",\n \"name\": \"Jane Doe\"\n}\n```\n\n### Search Against Known Identities\n\n```\nPOST /identity/search\nContent-Type: application/json\nAuthorization: Bearer \n\n{\n \"audio_url\": \"https://example.com/unknown-speaker.wav\",\n \"top_k\": 5\n}\n```\n\n**Response:**\n```json\n{\n \"success\": true,\n \"item\": [\n { \"uuid\": \"...\", \"name\": \"Jane Doe\", \"confidence\": 0.92, \"distance\": 0.08 }\n ]\n}\n```\n\nLower `distance` = closer match. Higher `confidence` = stronger match.\n\n---\n\n## Phase 6: Text Detection\n\nDetect whether text content is AI-generated or human-written.\n\n> **Beta feature** โ€” requires the `detect_beta_user` role or a billing plan that includes the `dfd_text` product.\n\n### Submit a Text Detection\n\n```\nPOST /text_detect\nContent-Type: application/json\nAuthorization: Bearer \n```\n\nAdd the `Prefer: wait` header for a synchronous (blocking) response. Without it, the job runs asynchronously โ€” poll or use a callback.\n\n**Parameters:**\n\n| Parameter | Type | Required | Description |\n|----------------|---------|----------|----------------------------------------------------------|\n| `text` | string | Yes | Text to analyze (max 100,000 characters) |\n| `thinking` | string | No | Always use `\"low\"` (default) |\n| `threshold` | float | No | Decision threshold 0.0โ€“1.0 (default: 0.5) |\n| `callback_url` | string | No | Webhook URL for async completion notification |\n| `privacy_mode` | boolean | No | If true, text content is not stored after analysis |\n\n**Response:**\n```json\n{\n \"success\": true,\n \"item\": {\n \"uuid\": \"abc-123\",\n \"status\": \"completed\",\n \"prediction\": \"ai\",\n \"confidence\": 0.91,\n \"text_content\": \"This is some text to analyze.\",\n \"privacy_mode\": false,\n \"created_at\": \"...\",\n \"updated_at\": \"...\"\n }\n}\n```\n\n- `prediction`: `\"ai\"` or `\"human\"` โ€” the verdict\n- `confidence`: 0.0โ€“1.0, higher = more confident in the prediction\n- `status`: `\"processing\"`, `\"completed\"`, or `\"failed\"`\n\n### Poll for Results\n\nIf you did not use `Prefer: wait`, poll until `status` is `\"completed\"` or `\"failed\"`:\n\n```\nGET /text_detect/{uuid}\nAuthorization: Bearer \n```\n\n### List Text Detections\n\n```\nGET /text_detect\nAuthorization: Bearer \n```\n\nReturns paginated text detections for the team.\n\n### Callback\n\nIf `callback_url` was provided, a `POST` is sent on completion:\n```json\n{ \"success\": true, \"item\": { ... } }\n```\nOn failure:\n```json\n{ \"success\": false, \"item\": { ... }, \"error\": \"Error message here\" }\n```\n\n---\n\n## Recommended Workflows\n\n### Full Media Forensics (Most Thorough)\n\nFor a comprehensive analysis, combine all capabilities:\n\n1. Submit detection with all flags enabled:\n ```json\n {\n \"url\": \"https://example.com/suspect.mp4\",\n \"visualize\": true,\n \"intelligence\": true,\n \"audio_source_tracing\": true,\n \"use_reverse_search\": true\n }\n ```\n2. Poll until `status: \"completed\"`\n3. Read `metrics` / `image_metrics` / `video_metrics` for the verdict\n4. Read `intelligence.description` for structured media analysis\n5. If audio labeled `\"fake\"`, check `audio_source_tracing.label` for the source platform\n6. Ask follow-up questions via Detect Intelligence if anything needs clarification\n7. Check for watermarks via `POST /watermark/detect` if provenance is relevant\n\n### Quick Authenticity Check (Fastest)\n\nFor a fast pass/fail:\n\n1. Submit minimal detection: `{ \"url\": \"...\" }`\n2. Poll until complete\n3. Check `label` and `aggregated_score` (audio) or `label` and `score` (image/video)\n4. Report result with score context\n\n### Provenance Pipeline (Content Creators)\n\nFor creators who want to prove their content is authentic:\n\n1. Apply watermark to original content: `POST /watermark/apply`\n2. Distribute watermarked media\n3. Later, verify provenance: `POST /watermark/detect` against any copy\n\n---\n\n## Red Flags โ€” Stop and Reassess\n\n- **Declaring authenticity without a detection result** โ€” Never say media is real or fake based on visual/auditory inspection alone\n- **Ignoring the score and reporting only the label** โ€” A `\"fake\"` label with score 0.51 means something very different from score 0.95\n- **Submitting local file paths to the API** โ€” The API requires publicly accessible HTTPS URLs (does not apply to text detection)\n- **Sending text longer than 100,000 characters to text detection** โ€” Split into chunks or inform the user of the limit\n- **Polling too aggressively** โ€” Start at 2s intervals, back off exponentially; do not loop at <1s\n- **Asking Detect Intelligence questions before detection completes** โ€” Results in 422 error\n- **Expecting source tracing on \"real\" audio** โ€” Source tracing only runs on audio labeled `\"fake\"`\n- **Treating beta features (Identity) as production-ready** โ€” Warn users about beta status\n- **Ignoring `zero_retention_mode` for sensitive media** โ€” Always suggest this flag when the user indicates the media is sensitive or private\n- **Making multiple separate API calls when flags can combine** โ€” Use `intelligence: true` and `audio_source_tracing: true` on the detection call instead of separate requests\n\n## Response Presentation Guidelines\n\nWhen presenting results to users:\n\n1. **Lead with the verdict** โ€” \"The detection indicates this audio is likely AI-generated (score: 0.87)\"\n2. **Provide score context** โ€” Use the score interpretation table above\n3. **Mention limitations** โ€” Detection is probabilistic, not absolute proof\n4. **Include actionable next steps** โ€” Suggest intelligence queries, source tracing, or watermark checks as appropriate\n5. **For inconclusive results (0.3โ€“0.5)** โ€” Explicitly state the result is inconclusive and recommend additional analysis with different parameters or manual review\n6. **Never present detection as legal evidence** โ€” Detection results are analytical tools, not forensic certifications\n\n## Error Handling\n\n| Error | Cause | Resolution |\n|-----------|------------------------------------------|--------------------------------------------------|\n| 400 | Invalid request body or missing `url` | Check required parameters |\n| 401 | Invalid or missing API key | Verify `RESEMBLE_API_KEY` |\n| 404 | Detection UUID not found | Verify the UUID from the creation response |\n| 422 | Detection not completed (for Intelligence) | Wait for detection to reach `completed` status |\n| 429 | Rate limited | Back off and retry with exponential delay |\n| 500 | Server error | Retry once, then report to user |\n\n## Privacy & Compliance Notes\n\n- **Zero retention mode**: Set `zero_retention_mode: true` to auto-delete media after analysis. The URL is redacted and `media_deleted` is set to true post-completion.\n- **Text privacy mode**: Set `privacy_mode: true` on text detection to prevent text content from being stored after analysis.\n- **Data handling**: Media URLs and text content are stored by default. For GDPR/compliance-sensitive workflows, enable zero retention (media) or privacy mode (text).\n- **Callback security**: If using `callback_url`, ensure the endpoint is HTTPS and authenticated on the receiving end.","schemaVersion":1},"repoUrl":"https://github.com/Prat011/awesome-llm-skills/tree/master/resemble-detect","tags":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"awesome-llm-skills","audit":{"files":["slack-gif-creator/requirements.txt"],"binaries":[],"findings":[{"kind":"dependency","rule":"DP-04","message":"Python dependencies are not pinned and there is no lock file.","surface":"slack-gif-creator/requirements.txt","evidence":"pillow>=10.0.0, imageio>=2.31.0, imageio-ffmpeg>=0.4.9, numpy>=1.24.0","severity":"medium"}],"packages":4,"auditedAt":"2026-09-25T11:52:30.068Z","lockfiles":[]},"forks":313,"owner":"Prat011","stars":1761,"topics":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms","openai","opencode","qwen","qwen-coder","skills"],"license":null,"fullName":"Prat011/awesome-llm-skills","homepage":null,"language":"Python","pushedAt":"2026-07-14T09:53:56Z","avatarUrl":"https://avatars.githubusercontent.com/u/67639393?v=4","crawledAt":"2026-09-25T11:52:22.319Z","openIssues":170,"manifestFile":"SKILL.md","manifestPath":"resemble-detect/SKILL.md","defaultBranch":"master"},"readme":"# Resemble Detect โ€” Deepfake Detection & Media Safety\n\nAnalyze audio, image, video, and text for synthetic manipulation, AI-generated content, watermarks, speaker identity, and media intelligence using the Resemble AI platform.\n\n## Core Principle โ€” THE IRON LAW\n\n**\"NEVER DECLARE MEDIA AS REAL OR FAKE WITHOUT A COMPLETED DETECTION RESULT.\"**\n\nDo not guess, infer, or speculate about media authenticity. Every authenticity claim must be backed by a completed Resemble detect job with a returned `label`, `score`, and `status: \"completed\"`. If the detection is still `processing`, wait. If it `failed`, say so โ€” do not substitute your own judgment.\n\n## When to Use\n\nUse this skill whenever the user's request involves any of these:\n\n- Checking if audio, video, image, or text is AI-generated or manipulated\n- Detecting deepfakes in any media format\n- Verifying media authenticity or provenance\n- Identifying which AI platform synthesized audio (source tracing)\n- Applying or detecting watermarks on media\n- Analyzing media for speaker info, emotion, transcription, or misinformation\n- Asking natural-language questions about detection results\n- Matching or verifying speaker identity against known voice profiles\n- Detecting AI-generated or machine-written text\n- Any mention of: \"deepfake\", \"fake detection\", \"synthetic media\", \"voice verification\", \"watermark\", \"media forensics\", \"authenticity check\", \"source tracing\", \"is this real\", \"AI-written text\", \"text detection\"\n\n**Do NOT use** for text-to-speech generation, voice cloning, or speech-to-text transcription โ€” those are separate Resemble capabilities.\n\n## Capability Decision Tree\n\n| User wants to... | Use this | API endpoint |\n|-------------------------------------------------------|---------------------------|----------------------------|\n| Check if media is AI-generated / deepfake | **Deepfake Detection** | `POST /detect` |\n| Know *which AI platform* made fake audio | **Audio Source Tracing** | `POST /detect` with flag |\n| Get speaker info, emotion, transcription from media | **Intelligence** | `POST /intelligence` |\n| Ask questions about a completed detection | **Detect Intelligence** | `POST /detects/{uuid}/intelligence` |\n| Apply an invisible watermark to media | **Watermark Apply** | `POST /watermark/apply` |\n| Check if media contains a watermark | **Watermark Detect** | `POST /watermark/detect` |\n| Verify a speaker's identity against known profiles | **Identity Search** | `POST /identity/search` |\n| Check if text is AI-generated | **Text Detection** | `POST /text_detect` |\n| Create a voice identity profile for future matching | **Identity Create** | `POST /identity` |\n\nWhen multiple capabilities apply (e.g., user wants deepfake detection AND intelligence), combine them in a single `POST /detect` call using the `intelligence: true` flag rather than making separate requests.\n\n## Required Setup\n\n- **API Key**: Bearer token from the Resemble AI dashboard\n- **Base URL**: `https://app.resemble.ai/api/v2`\n- **Auth Header**: `Authorization: Bearer `\n- **Media Requirement**: All media must be at a publicly accessible HTTPS URL\n\nIf the user provides a local file path instead of a URL, inform them the file must be hosted at a public HTTPS URL first. Do not attempt to upload local files to the API.\n\n## MCP Tools Available\n\nWhen the Resemble MCP server is connected, use these tools instead of raw API calls:\n\n| Tool | Purpose |\n|---------------------------|---------------------------------------------------|\n| `resemble_docs_lookup` | Get comprehensive docs for any detect sub-topic |\n| `resemble_search` | Search across all documentation ","createdAt":"2026-09-25T11:52:30.370Z","updatedAt":"2026-09-25T11:52:30.370Z"},{"id":"cmugwiiep0272qu06tytq5rsn","slug":"prat011-awesome-llm-skills-skill-creator","name":"skill-creator","description":"Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.","authorId":"gh:prat011","authorName":"Prat011","version":"0.1.0","category":"Prompt","securityLevel":"Community","downloadsCount":0,"githubStars":1761,"pricePerCall":0,"manifest":{"name":"skill-creator","tools":[],"category":"Prompt","entrypoint":{"type":"prompt"},"description":"Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.","permissions":[],"systemPrompt":"# Skill Creator\n\nThis skill provides guidance for creating effective skills.\n\n## About Skills\n\nSkills are modular, self-contained packages that extend Claude's capabilities by providing\nspecialized knowledge, workflows, and tools. Think of them as \"onboarding guides\" for specific\ndomains or tasksโ€”they transform Claude from a general-purpose agent into a specialized agent\nequipped with procedural knowledge that no model can fully possess.\n\n### What Skills Provide\n\n1. Specialized workflows - Multi-step procedures for specific domains\n2. Tool integrations - Instructions for working with specific file formats or APIs\n3. Domain expertise - Company-specific knowledge, schemas, business logic\n4. Bundled resources - Scripts, references, and assets for complex and repetitive tasks\n\n### Anatomy of a Skill\n\nEvery skill consists of a required SKILL.md file and optional bundled resources:\n\n```\nskill-name/\nโ”œโ”€โ”€ SKILL.md (required)\nโ”‚ โ”œโ”€โ”€ YAML frontmatter metadata (required)\nโ”‚ โ”‚ โ”œโ”€โ”€ name: (required)\nโ”‚ โ”‚ โ””โ”€โ”€ description: (required)\nโ”‚ โ””โ”€โ”€ Markdown instructions (required)\nโ””โ”€โ”€ Bundled Resources (optional)\n โ”œโ”€โ”€ scripts/ - Executable code (Python/Bash/etc.)\n โ”œโ”€โ”€ references/ - Documentation intended to be loaded into context as needed\n โ””โ”€โ”€ assets/ - Files used in output (templates, icons, fonts, etc.)\n```\n\n#### SKILL.md (required)\n\n**Metadata Quality:** The `name` and `description` in YAML frontmatter determine when Claude will use the skill. Be specific about what the skill does and when to use it. Use the third-person (e.g. \"This skill should be used when...\" instead of \"Use this skill when...\").\n\n#### Bundled Resources (optional)\n\n##### Scripts (`scripts/`)\n\nExecutable code (Python/Bash/etc.) for tasks that require deterministic reliability or are repeatedly rewritten.\n\n- **When to include**: When the same code is being rewritten repeatedly or deterministic reliability is needed\n- **Example**: `scripts/rotate_pdf.py` for PDF rotation tasks\n- **Benefits**: Token efficient, deterministic, may be executed without loading into context\n- **Note**: Scripts may still need to be read by Claude for patching or environment-specific adjustments\n\n##### References (`references/`)\n\nDocumentation and reference material intended to be loaded as needed into context to inform Claude's process and thinking.\n\n- **When to include**: For documentation that Claude should reference while working\n- **Examples**: `references/finance.md` for financial schemas, `references/mnda.md` for company NDA template, `references/policies.md` for company policies, `references/api_docs.md` for API specifications\n- **Use cases**: Database schemas, API documentation, domain knowledge, company policies, detailed workflow guides\n- **Benefits**: Keeps SKILL.md lean, loaded only when Claude determines it's needed\n- **Best practice**: If files are large (>10k words), include grep search patterns in SKILL.md\n- **Avoid duplication**: Information should live in either SKILL.md or references files, not both. Prefer references files for detailed information unless it's truly core to the skillโ€”this keeps SKILL.md lean while making information discoverable without hogging the context window. Keep only essential procedural instructions and workflow guidance in SKILL.md; move detailed reference material, schemas, and examples to references files.\n\n##### Assets (`assets/`)\n\nFiles not intended to be loaded into context, but rather used within the output Claude produces.\n\n- **When to include**: When the skill needs files that will be used in the final output\n- **Examples**: `assets/logo.png` for brand assets, `assets/slides.pptx` for PowerPoint templates, `assets/frontend-template/` for HTML/React boilerplate, `assets/font.ttf` for typography\n- **Use cases**: Templates, images, icons, boilerplate code, fonts, sample documents that get copied or modified\n- **Benefits**: Separates output resources from documentation, enables Claude to use files without loading them into context\n\n### Progressive Disclosure Design Principle\n\nSkills use a three-level loading system to manage context efficiently:\n\n1. **Metadata (name + description)** - Always in context (~100 words)\n2. **SKILL.md body** - When skill triggers (<5k words)\n3. **Bundled resources** - As needed by Claude (Unlimited*)\n\n*Unlimited because scripts can be executed without reading into context window.\n\n## Skill Creation Process\n\nTo create a skill, follow the \"Skill Creation Process\" in order, skipping steps only if there is a clear reason why they are not applicable.\n\n### Step 1: Understanding the Skill with Concrete Examples\n\nSkip this step only when the skill's usage patterns are already clearly understood. It remains valuable even when working with an existing skill.\n\nTo create an effective skill, clearly understand concrete examples of how the skill will be used. This understanding can come from either direct user examples or generated examples that are validated with user feedback.\n\nFor example, when building an image-editor skill, relevant questions include:\n\n- \"What functionality should the image-editor skill support? Editing, rotating, anything else?\"\n- \"Can you give some examples of how this skill would be used?\"\n- \"I can imagine users asking for things like 'Remove the red-eye from this image' or 'Rotate this image'. Are there other ways you imagine this skill being used?\"\n- \"What would a user say that should trigger this skill?\"\n\nTo avoid overwhelming users, avoid asking too many questions in a single message. Start with the most important questions and follow up as needed for better effectiveness.\n\nConclude this step when there is a clear sense of the functionality the skill should support.\n\n### Step 2: Planning the Reusable Skill Contents\n\nTo turn concrete examples into an effective skill, analyze each example by:\n\n1. Considering how to execute on the example from scratch\n2. Identifying what scripts, references, and assets would be helpful when executing these workflows repeatedly\n\nExample: When building a `pdf-editor` skill to handle queries like \"Help me rotate this PDF,\" the analysis shows:\n\n1. Rotating a PDF requires re-writing the same code each time\n2. A `scripts/rotate_pdf.py` script would be helpful to store in the skill\n\nExample: When designing a `frontend-webapp-builder` skill for queries like \"Build me a todo app\" or \"Build me a dashboard to track my steps,\" the analysis shows:\n\n1. Writing a frontend webapp requires the same boilerplate HTML/React each time\n2. An `assets/hello-world/` template containing the boilerplate HTML/React project files would be helpful to store in the skill\n\nExample: When building a `big-query` skill to handle queries like \"How many users have logged in today?\" the analysis shows:\n\n1. Querying BigQuery requires re-discovering the table schemas and relationships each time\n2. A `references/schema.md` file documenting the table schemas would be helpful to store in the skill\n\nTo establish the skill's contents, analyze each concrete example to create a list of the reusable resources to include: scripts, references, and assets.\n\n### Step 3: Initializing the Skill\n\nAt this point, it is time to actually create the skill.\n\nSkip this step only if the skill being developed already exists, and iteration or packaging is needed. In this case, continue to the next step.\n\nWhen creating a new skill from scratch, always run the `init_skill.py` script. The script conveniently generates a new template skill directory that automatically includes everything a skill requires, making the skill creation process much more efficient and reliable.\n\nUsage:\n\n```bash\nscripts/init_skill.py --path \n```\n\nThe script:\n\n- Creates the skill directory at the specified path\n- Generates a SKILL.md template with proper frontmatter and TODO placeholders\n- Creates example resource directories: `scripts/`, `references/`, and `assets/`\n- Adds example files in each directory that can be customized or deleted\n\nAfter initialization, customize or remove the generated SKILL.md and example files as needed.\n\n### Step 4: Edit the Skill\n\nWhen editing the (newly-generated or existing) skill, remember that the skill is being created for another instance of Claude to use. Focus on including information that would be beneficial and non-obvious to Claude. Consider what procedural knowledge, domain-specific details, or reusable assets would help another Claude instance execute these tasks more effectively.\n\n#### Start with Reusable Skill Contents\n\nTo begin implementation, start with the reusable resources identified above: `scripts/`, `references/`, and `assets/` files. Note that this step may require user input. For example, when implementing a `brand-guidelines` skill, the user may need to provide brand assets or templates to store in `assets/`, or documentation to store in `references/`.\n\nAlso, delete any example files and directories not needed for the skill. The initialization script creates example files in `scripts/`, `references/`, and `assets/` to demonstrate structure, but most skills won't need all of them.\n\n#### Update SKILL.md\n\n**Writing Style:** Write the entire skill using **imperative/infinitive form** (verb-first instructions), not second person. Use objective, instructional language (e.g., \"To accomplish X, do Y\" rather than \"You should do X\" or \"If you need to do X\"). This maintains consistency and clarity for AI consumption.\n\nTo complete SKILL.md, answer the following questions:\n\n1. What is the purpose of the skill, in a few sentences?\n2. When should the skill be used?\n3. In practice, how should Claude use the skill? All reusable skill contents developed above should be referenced so that Claude knows how to use them.\n\n### Step 5: Packaging a Skill\n\nOnce the skill is ready, it should be packaged into a distributable zip file that gets shared with the user. The packaging process automatically validates the skill first to ensure it meets all requirements:\n\n```bash\nscripts/package_skill.py \n```\n\nOptional output directory specification:\n\n```bash\nscripts/package_skill.py ./dist\n```\n\nThe packaging script will:\n\n1. **Validate** the skill automatically, checking:\n - YAML frontmatter format and required fields\n - Skill naming conventions and directory structure\n - Description completeness and quality\n - File organization and resource references\n\n2. **Package** the skill if validation passes, creating a zip file named after the skill (e.g., `my-skill.zip`) that includes all files and maintains the proper directory structure for distribution.\n\nIf validation fails, the script will report the errors and exit without creating a package. Fix any validation errors and run the packaging command again.\n\n### Step 6: Iterate\n\nAfter testing the skill, users may request improvements. Often this happens right after using the skill, with fresh context of how the skill performed.\n\n**Iteration workflow:**\n1. Use the skill on real tasks\n2. Notice struggles or inefficiencies\n3. Identify how SKILL.md or bundled resources should be updated\n4. Implement changes and test again","schemaVersion":1},"repoUrl":"https://github.com/Prat011/awesome-llm-skills/tree/master/skill-creator","tags":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms"],"stats":{"installVelocity7d":0,"retentionRate":0,"executions":0,"rating":null},"origin":"github","source":{"repo":"awesome-llm-skills","audit":{"files":["slack-gif-creator/requirements.txt"],"binaries":[],"findings":[{"kind":"dependency","rule":"DP-04","message":"Python dependencies are not pinned and there is no lock file.","surface":"slack-gif-creator/requirements.txt","evidence":"pillow>=10.0.0, imageio>=2.31.0, imageio-ffmpeg>=0.4.9, numpy>=1.24.0","severity":"medium"}],"packages":4,"auditedAt":"2026-09-25T11:52:30.068Z","lockfiles":[]},"forks":313,"owner":"Prat011","stars":1761,"topics":["anthropic","awesome-list","awesome-lists","claude-code","claude-skills","claude-skills-creator","codex","codex-cli","gemini","gemini-cli","llama","llms","openai","opencode","qwen","qwen-coder","skills"],"license":"Complete terms in LICENSE.txt","fullName":"Prat011/awesome-llm-skills","homepage":null,"language":"Python","pushedAt":"2026-07-14T09:53:56Z","avatarUrl":"https://avatars.githubusercontent.com/u/67639393?v=4","crawledAt":"2026-09-25T11:52:22.319Z","openIssues":170,"manifestFile":"SKILL.md","manifestPath":"skill-creator/SKILL.md","defaultBranch":"master"},"readme":"# Skill Creator\n\nThis skill provides guidance for creating effective skills.\n\n## About Skills\n\nSkills are modular, self-contained packages that extend Claude's capabilities by providing\nspecialized knowledge, workflows, and tools. Think of them as \"onboarding guides\" for specific\ndomains or tasksโ€”they transform Claude from a general-purpose agent into a specialized agent\nequipped with procedural knowledge that no model can fully possess.\n\n### What Skills Provide\n\n1. Specialized workflows - Multi-step procedures for specific domains\n2. Tool integrations - Instructions for working with specific file formats or APIs\n3. Domain expertise - Company-specific knowledge, schemas, business logic\n4. Bundled resources - Scripts, references, and assets for complex and repetitive tasks\n\n### Anatomy of a Skill\n\nEvery skill consists of a required SKILL.md file and optional bundled resources:\n\n```\nskill-name/\nโ”œโ”€โ”€ SKILL.md (required)\nโ”‚ โ”œโ”€โ”€ YAML frontmatter metadata (required)\nโ”‚ โ”‚ โ”œโ”€โ”€ name: (required)\nโ”‚ โ”‚ โ””โ”€โ”€ description: (required)\nโ”‚ โ””โ”€โ”€ Markdown instructions (required)\nโ””โ”€โ”€ Bundled Resources (optional)\n โ”œโ”€โ”€ scripts/ - Executable code (Python/Bash/etc.)\n โ”œโ”€โ”€ references/ - Documentation intended to be loaded into context as needed\n โ””โ”€โ”€ assets/ - Files used in output (templates, icons, fonts, etc.)\n```\n\n#### SKILL.md (required)\n\n**Metadata Quality:** The `name` and `description` in YAML frontmatter determine when Claude will use the skill. Be specific about what the skill does and when to use it. Use the third-person (e.g. \"This skill should be used when...\" instead of \"Use this skill when...\").\n\n#### Bundled Resources (optional)\n\n##### Scripts (`scripts/`)\n\nExecutable code (Python/Bash/etc.) for tasks that require deterministic reliability or are repeatedly rewritten.\n\n- **When to include**: When the same code is being rewritten repeatedly or deterministic reliability is needed\n- **Example**: `scripts/rotate_pdf.py` for PDF rotation tasks\n- **Benefits**: Token efficient, deterministic, may be executed without loading into context\n- **Note**: Scripts may still need to be read by Claude for patching or environment-specific adjustments\n\n##### References (`references/`)\n\nDocumentation and reference material intended to be loaded as needed into context to inform Claude's process and thinking.\n\n- **When to include**: For documentation that Claude should reference while working\n- **Examples**: `references/finance.md` for financial schemas, `references/mnda.md` for company NDA template, `references/policies.md` for company policies, `references/api_docs.md` for API specifications\n- **Use cases**: Database schemas, API documentation, domain knowledge, company policies, detailed workflow guides\n- **Benefits**: Keeps SKILL.md lean, loaded only when Claude determines it's needed\n- **Best practice**: If files are large (>10k words), include grep search patterns in SKILL.md\n- **Avoid duplication**: Information should live in either SKILL.md or references files, not both. Prefer references files for detailed information unless it's truly core to the skillโ€”this keeps SKILL.md lean while making information discoverable without hogging the context window. Keep only essential procedural instructions and workflow guidance in SKILL.md; move detailed reference material, schemas, and examples to references files.\n\n##### Assets (`assets/`)\n\nFiles not intended to be loaded into context, but rather used within the output Claude produces.\n\n- **When to include**: When the skill needs files that will be used in the final output\n- **Examples**: `assets/logo.png` for brand assets, `assets/slides.pptx` for PowerPoint templates, `assets/frontend-template/` for HTML/React boilerplate, `assets/font.ttf` for typography\n- **Use cases**: Templates, images, icons, boilerplate code, fonts, sample documents that get copied or modified\n- **Benefits**: Separates output resources from documentation, enables Claude to use files without loading t","createdAt":"2026-09-25T11:52:30.385Z","updatedAt":"2026-09-25T11:52:30.385Z"}],"total":33,"limit":24,"offset":0}