skills/llm-daily/SKILL.md
Generate and publish a daily AI/LLM newsletter called "LLM Daily" that curates content from top sources (ArXiv, GitHub Trending, HuggingFace, VentureBeat, TechCrunch, Product Hunt). Use when user asks to: generate a newsletter, create today's LLM Daily, collect AI news, build an AI newsletter, publish newsletter, or run the daily newsletter pipeline. Also triggers on: "llm daily", "daily briefing", "AI newsletter", "generate newsletter", "collect news", "publish newsletter".
npx skillsauth add likw99/agent-skills llm-dailyInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Generate a professional daily AI/LLM newsletter by utilizing the fetch_sources.py script to fetch dynamically configured data, and leveraging your LLM capabilities to synthesize it into a curated briefing.
Run the universal collector script to fetch data from all sources defined in references/sources.yaml.
cd <skill_dir>/scripts
uv run --with requests --with feedparser --with pyyaml fetch_sources.py
This will parse all RSS feeds, JSON APIs, and XML APIs, generating a single markdown file at scripts/output/context.md.
Read the generated scripts/output/context.md file using your file reading tools. Then open references/newsletter_template.md and follow it exactly when drafting the final newsletter. Use the source context to synthesize a readable briefing, not a raw dump of links.
Write the final newsletter to scripts/output/llm_newsletter_YYYY-MM-DD.md.
If the user wants to publish the newsletter and BUTTONDOWN_API_KEY is present in the environment:
cd <skill_dir>/scripts
uv run --with requests publish.py output/llm_newsletter_YYYY-MM-DD.md --status draft
Without BUTTONDOWN_API_KEY, the newsletter is only generated locally.
The canonical newsletter structure now lives in references/newsletter_template.md.
Use that file as the source of truth for:
Apply these guidelines when drafting each section based on the collected context.
Source data: VentureBeat, TechCrunch.
Source data: Product Hunt, Hacker News.
Source data: GitHub Recent Top AI Repos, HuggingFace Trending Models.
Source data: ArXiv LLM Papers.
https://arxiv.org/abs/XXXX.XXXXXGenerate after all other sections. Extract 3-5 most important developments as bullet points.
Each bullet: concise (1-2 sentences), specific, and formatted as a normal markdown bullet using -.
-) and ordered lists (1.), not decorative bullets such as •Link: linesData sources are configured in references/sources.yaml. To add a new source:
rss, json_api, or xml_api.sources.yaml with the appropriate parser_config.development
Use this skill when a user wants a trust decision before installing from a skill URL, marketplace, or GitHub repo. It checks a compact allowlist of trusted distribution channels and returns whether the source should be trusted under the current TrustSkills policy, without drifting into explaining what the skill itself does unless the user asks.
tools
Monitior technology trends (GitHub, etc.), contextualize them against the user's project, and autonomously verify them through installation and testing. Use when the user asks about trending repositories, new tools, or wants to stay updated on tech relevant to their current work.
development
Optimize websites, docs, products, and brand presence for Generative Engine Optimization (GEO), AI search visibility, answer-engine citations, and LLM retrieval. Use when the user asks about GEO, AEO, LLMO, ChatGPT Search, Google AI Overviews or AI Mode, Gemini, Perplexity, Claude Search, Microsoft Copilot/Bing AI answers, AI crawler access, robots.txt for AI bots, llms.txt, structured data for AI discovery, citation tracking, or making content easier for AI systems to retrieve, trust, cite, and recommend.
development
Generate a shareable Developer Identity Card from any git repo. Analyzes commit history, language breakdown, coding hours, and commit patterns to assign a developer archetype (e.g. "The Midnight Architect", "The Dawn Deployer", "The Firefighter") with a personality tagline and stats. Use when the user says: "make my dev card", "generate my dev card", "what's my developer archetype", "analyze my coding patterns", "dev card", "who am I as a developer", or anything implying a shareable developer identity or personality profile.