Curate and expand the awesome-autoresearch repository. Use when adding new autoresearch cases, collecting discussion evidence from X/Reddit/HN/blogs, promoting discussion items into main categories, refreshing README counts, or running periodic evidence sweeps.
Use when chatting in terminal, especially in terminal-first technical or business discussions, to ensure responses are terminal-friendly and visually structured.
- 📁 commands/
- 📁 memory/
- 📁 notes/
- 📄 .gitignore
- 📄 CLAUDE.md
- 📄 config.json
Academic paper reading system — find papers via Semantic Scholar, read with structured notes, discuss with auto-recording, track progress. 7 commands: /setup /feed /read /discuss /recap /update /sync
Post Q&A entries from office hours writeups as comments to a GitHub Discussion. Use when the user wants to post writeup content to a discussion thread.
Analyze GitHub issues, Pull Requests (PRs), Discussions, and repo health for an Open Source Software (OSS) project. For any specific item, casts a wide net — finds and lists all related open and closed issues/PRs/discussions, explicitly flags duplicates. Also summarizes long threads, assesses PR readiness, extracts reproduction steps, and generates repo health stats. Uses gh Command Line Interface (CLI) for GitHub Application Programming Interface (API) access. Complements oss-shepherd agent.
You MUST use this skill when the user wants to discuss, analyze, or explore ideas before making decisions. Triggers on: \"讨论一下\", \"我想聊聊\", \"帮我分析\", \"我们来探讨\", \"let's discuss\", \"I want to talk about\", or any request for in-depth conversation about architecture, design choices, or technical decisions. Usage: (1) Explicit - use slash command to select this skill; (2) Implicit - automatically triggered by keywords above. Provides structured discussion facilitation with decision precipitation.