菜单
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.
默认使用会先检查来源的 Prompt；你也可以切换为直接命令，或下载本地副本。
决定是否安装前，请先阅读 SKILL.md，以及 SkillsMP 当前展示的配套文件。
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt；运行前请先检查来源。
npx skills add https://github.com/yibie/awesome-autoresearch --skill autoresearch-curation命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地？可下载 SkillsMP 当前能够提供的文件。
基于 SOC 职业分类
正在显示 SKILL.md
| name | autoresearch-curation |
| description | 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 this skill to maintain awesome-autoresearch as a strict, high-signal list of direct autoresearch use cases.
Keep the repository focused on two questions:
This skill is for curation, not broad AI trend collection.
Read these files before making changes:
README.mdCONTRIBUTING.mdcategories/README.md is the homepage aggregate, not the primary editing surface.
Update category files first, then refresh README.md from the current category files.
If available, use scripts/build-readme.py instead of hand-editing the aggregate.
Only include items that satisfy at least one of these:
autoresearchmodify → verify → keep/discard → repeat loopAnd all of these:
Reject:
Use main category pages for stronger evidence such as:
Use categories/related-practices-discussions.md for:
when they show credible real practice signals but do not yet have a strong standalone repo or case page.
Use cross-platform searches, but keep inclusion strict.
Preferred evidence channels:
Prefer medium-complexity searches such as:
autoresearch tradingautoresearch benchmarkautoresearch debuggingKarpathy autoresearch roboticsAvoid very long advanced-search expressions when the adapter is unstable.
Search in both languages when useful.
Useful Chinese patterns:
autoresearch 回滚autoresearch 验证器autoresearch benchmarkKarpathy autoresearch 工程But keep Chinese queries narrow to avoid noisy generic matches.
Use this exact ladder:
categories/related-practices-discussions.md if it is credible and directly autoresearch-related.README.md counts if category totals changed.Format:
- [Name](URL) - Domain: one-sentence description of the autoresearch use case.
Rules:
applies, adapts, uses, iterates, keepsFormat:
- [Name or thread title](URL) - Source/platform: one-sentence description of the autoresearch-related practice or discussion.
Rules:
When invoked for a recurring sweep:
README.md so the homepage aggregate matches the current category files and counts.Count entries:
python - <<'PY'
from pathlib import Path
for p in sorted(Path('categories').glob('*.md')):
cnt=sum(1 for line in p.read_text().splitlines() if line.startswith('- ['))
print(f'{p}:{cnt}')
PY
Example searches:
bb-browser site twitter/search 'autoresearch benchmark' --json
bb-browser site twitter/search 'autoresearch debugging' --json
bb-browser site twitter/search 'autoresearch robotics' --json
bb-browser site google/search 'site:reddit.com autoresearch real codebase OR autoresearch debugging' | sed -n '1,220p'
bb-browser site google/search 'site:news.ycombinator.com autoresearch OR "Karpathy autoresearch"' | sed -n '1,220p'
bb-browser site google/search 'site:github.com "autoresearch" robotics' | sed -n '1,220p'
opencli gh api repos/<owner>/<repo>/readme
Promote slowly. Add discussions faster.
If evidence is good but not strong enough for a main case, keep it in discussions. Precision beats coverage.
Before finishing, verify:
This skill should be used for prompts like: