Sync Trending
Keep up-to-date with technology trends by monitoring GitHub Trending, brainstorming their value against your current context, and autonomously verifying selected technologies.
Workflow
1. Monitor, Brainstorm & Summarize
When triggered, follow these steps:
- Understand Context: Read the local
README.md, package.json, or search the current directory to understand the user's project context. Check save_memory for user preferences or other projects.
- Fetch Trends: Use
web_fetch to retrieve content from the sources listed in sources.md (primarily GitHub Trending).
- Analyze & Brainstorm: For the top repositories, brainstorm how they could benefit the user's specific project or role.
- Report: Present a "Contextualized Trend Report" including:
- Facts: Repo Name, URL, Language, Stars, and a brief description.
- Contextual Value: A one-sentence insight on why this matters (e.g., "Could replace your current auth implementation," "Relevant for the data visualization feature you're planning").
2. Permission & Deep Dive
If the user expresses interest in a specific repository:
- Ask Permission: Clearly ask: "Shall I clone [Repo Name] and attempt to run it for verification?"
- Setup:
- Use
run_shell_command to git clone the repository into a temporary directory (e.g., in ~/.gemini/tmp/).
- Read
README.md or CONTRIBUTING.md to identify build/run instructions.
- Execution:
- Detect project type (Node.js, Python, Rust, Go, etc.).
- Install dependencies (
npm install, pip install -r requirements.txt, etc.).
- Run the application or demo (
npm start, python main.py, etc.).
- Verification:
- If it starts a web server, use
browser_navigate to check http://localhost:<port>.
- If it's a CLI tool, check the output for success/failure.
- Report Outcome: Summarize the setup process, any issues found, and the final verification result.
3. Generate Artifacts
Based on the deep dive and the initial brainstorming, offer to generate one of the following:
todo.md: A concrete integration plan for the user's existing project, including technical snippets discovered during the deep dive.idea.md: A blueprint for a new project based on the trending tech.brief.md: A high-level summary suitable for sharing with a CEO, Board of Directors, or a Team.
Safety Guidelines
- NEVER clone or execute code without explicit user permission.
- ALWAYS perform deep dives in a temporary or isolated directory.
- NEVER expose the user's local secrets or environment variables to the trending repository.
1---2name: sync-trending3description: 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.4---5
6# Sync Trending
7
8Keep up-to-date with technology trends by monitoring GitHub Trending, brainstorming their value against your current context, and autonomously verifying selected technologies.
9
10## Workflow
11
12### 1. Monitor, Brainstorm & Summarize
13When triggered, follow these steps:
141. **Understand Context:** Read the local `README.md`, `package.json`, or search the current directory to understand the user's project context. Check `save_memory` for user preferences or other projects.
152. **Fetch Trends:** Use `web_fetch` to retrieve content from the sources listed in [sources.md](references/sources.md) (primarily GitHub Trending).
163. **Analyze & Brainstorm:** For the top repositories, brainstorm how they could benefit the user's specific project or role.
174. **Report:** Present a "Contextualized Trend Report" including:
18 - **Facts:** Repo Name, URL, Language, Stars, and a brief description.
19 - **Contextual Value:** A one-sentence insight on why this matters (e.g., "Could replace your current auth implementation," "Relevant for the data visualization feature you're planning").
20
21### 2. Permission & Deep Dive
22If the user expresses interest in a specific repository:
231. **Ask Permission:** Clearly ask: "Shall I clone [Repo Name] and attempt to run it for verification?"
242. **Setup:**
25 - Use `run_shell_command` to `git clone` the repository into a temporary directory (e.g., in `~/.gemini/tmp/`).
26 - Read `README.md` or `CONTRIBUTING.md` to identify build/run instructions.
273. **Execution:**
28 - Detect project type (Node.js, Python, Rust, Go, etc.).
29 - Install dependencies (`npm install`, `pip install -r requirements.txt`, etc.).
30 - Run the application or demo (`npm start`, `python main.py`, etc.).
314. **Verification:**
32 - If it starts a web server, use `browser_navigate` to check `http://localhost:<port>`.
33 - If it's a CLI tool, check the output for success/failure.
345. **Report Outcome:** Summarize the setup process, any issues found, and the final verification result.
35
36### 3. Generate Artifacts
37Based on the deep dive and the initial brainstorming, offer to generate one of the following:
38- **`todo.md`:** A concrete integration plan for the user's existing project, including technical snippets discovered during the deep dive.
39- **`idea.md`:** A blueprint for a new project based on the trending tech.
40- **`brief.md`:** A high-level summary suitable for sharing with a CEO, Board of Directors, or a Team.
41
42## Safety Guidelines
43- **NEVER** clone or execute code without explicit user permission.
44- **ALWAYS** perform deep dives in a temporary or isolated directory.
45- **NEVER** expose the user's local secrets or environment variables to the trending repository.
modbender