Menu
Fetch top trending GitHub repositories for the past week, format a ranked list, and deliver via email. Designed for weekly cron jobs.
Installer avec Codex ou Claude Copiez ce prompt, collez-le dans Codex, Claude ou un autre assistant, puis laissez-le vérifier la page du skill et l'installer pour vous.
Run AI coding agents on disposable repo clones. The agent works on a clone — it can't touch your real repo. An optional container (Podman or Docker) provides build/test isolation. You review the diff and decide what (if anything) to apply.
Create Deezer playlists programmatically from any query — similar artists, genre mixes, festival lineups, mood-based collections. Four-tier data pipeline: Deezer public REST API + Last.fm scrobble data for discovery, GQL Pipe API for smart mixes and playlist creation, web search for subjective curation. Uses ARL cookie auth — no OAuth app required.
Generate compact AI-readable context maps from codebases — tools like codesight, repomix, agentic-context that pre-compute project structure to save tokens in AI coding sessions.
Research-focused query handling with multi-source synthesis, citations, and Obsidian persistence. Like a self-hosted Perplexity/Vane but CLI-native. Best for quick-to-medium lookups using Kagi. Use when the user asks factual questions, needs citations, or wants a direct answer — not a full research report (use deep-research) or social sentiment (use last30days). Triggers on: research, look into, what's the latest on, compare, explain, investigate.
Write articles, guides, blog posts, tutorials, newsletter issues, research reports, and deep research outputs in a distinctive voice derived from supplied examples or brand guidance. Use when the user wants polished written content longer than a paragraph, deep research on a topic, or a research report — especially when voice consistency, structure, and credibility matter. Triggers on: 'write an article', 'research report', 'deep research', 'long-form', 'blog post', 'guide', 'newsletter', 'white paper', 'research paper'.
Systematic research methodology for major consumer durables (appliances, HVAC, power tools, outdoor equipment) and smart garden/outdoor devices (bird feeder cameras, bird baths, smart outdoor gadgets). Emphasis on real reliability data, failure mode analysis, and head-to-head comparison. Use when the user asks to research, review, compare, or evaluate major purchases where longevity and repair risk matter, or when researching smart bird feeders, bird bath cameras, and similar connected outdoor devices. Triggers on: washer/dryer, refrigerator, dishwasher, HVAC, furnace, AC, generator, power tool, appliance reviews, appliance reliability, which [appliance] to buy, compare models, bird feeder camera, bird bath camera, smart garden devices.
Basé sur la classification professionnelle SOC
| name | github-trending |
| description | Fetch top trending GitHub repositories for the past week, format a ranked list, and deliver via email. Designed for weekly cron jobs. |
| version | 1.0.0 |
| author | community |
| license | MIT |
| metadata | {"hermes":{"tags":["GitHub","Trending","Research","Cron","Email"],"triggers":["trending github repos","github weekly report","trending repositories"]}} |
Fetch the top trending GitHub repositories from the past week, filter for English-language, rank by weekly stars, and deliver via email.
Navigate to https://github.com/trending?since=weekly using the browser.
browser_navigate(url="https://github.com/trending?since=weekly")
Important: The GitHub trending page is JavaScript-rendered. web_extract returns only a summary, not structured data. browser_snapshot(full=true) truncates on long pages (25+ repos). The reliable approach is browser_vision.
browser_vision(question="List all trending repositories visible on this page. For each repo give: owner/repo name, description, total stars, language, and stars this week.")
This captures all repos visible in the viewport. If you need repos beyond the first screen, scroll down and call browser_vision again, or combine with browser_snapshot data from the first screenful.
Why vision over snapshot: The snapshot for this page is very large (~8000+ chars) and gets truncated. Vision processes the visual layout and returns structured data for all visible repos in one call. One vision call typically captures 15-20 repos.
TradingAgents-CN, or primarily Chinese repos like MoneyPrinterTurbo which has a bilingual but Chinese-primary description).For each repo, include:
Pick the email CLI that fits your stack. A himalaya example:
cat << 'EOF' | himalaya template send
From: you@example.com
To: you@example.com
Subject: 🔥 Top 10 Trending GitHub Repositories This Week (date range)
[formatted report body]
EOF
Or send via AgentMail / any SMTP CLI. The skill is delivery-agnostic — pick the tool you already have configured.
web_extract alone for the trending page — it returns an LLM-summarized paragraph, not structured repo data.browser_snapshot for the full list — the page is too large and gets truncated. Use browser_vision instead.