research-brief
Skill1 starsChanged 4 months agoMITView on GitHub
Define and answer a bounded research question with a source plan, evidence ledger, cross-checking, conclusions, unknowns, and next steps. Use when gathering or synthesizing evidence is the primary task; use report-writer when supplied material only needs a polished report, and never claim current research without accessible sources or network capability. 围绕有边界的研究问题制定来源计划、建立证据台账、交叉验证并输出结论、未知项和下一步。主要任务是搜集或综合证据时使用;已有材料只需形成正式报告时使用 report-writer;无法访问资料或网络时不得声称完成实时研究。
We split this skill into the rules it gives an agent
1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 18 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Read references/productivity-evidence-and-file-safety.md.
“Common” is measured: kept by at least 6 in 10 of the 18 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
English
Research Brief
Read references/productivity-evidence-and-file-safety.md. Use assets/research-brief-template.md when no format is supplied.
- Define the research question, intended decision, audience, scope, exclusions, deadline, freshness requirement, and evidence standard.
- Confirm whether supplied materials and network/search tools are actually accessible. If not, produce a source plan or limited brief and state that current research was not performed.
- Prioritize primary, official, and directly authoritative sources; use reputable secondary sources for context and independent corroboration.
- Record publisher, title, publication date, event date when different, locator, and access date. Keep short claims linked to their supporting sources.
- Cross-check material claims, investigate conflicting dates or figures, and distinguish facts, source assertions, inferences, and recommendations.
- Synthesize the answer, confidence, dissenting evidence, unknowns, limitations, and specific next research steps. Do not stretch conclusions beyond scope.
Hand polished long-form reporting from an already supplied evidence set to report-writer.
Output Contract
- Research question, scope, deadline, and evidence standard
- Key conclusions with confidence
- Evidence ledger with publication, event, and access dates
- Conflicts and alternative interpretations
- Unknowns, limitations, and next steps
简体中文
研究简报
读取 references/productivity-evidence-and-file-safety.md。用户未提供格式时使用 assets/research-brief-template.md。
- 明确研究问题、目标决策、读者、范围、排除项、截止时间、时效要求和证据标准。
- 确认材料与网络/搜索工具是否真实可用;不可用时只输出来源计划或受限简报,并明确没有完成实时研究。
- 优先原始、官方和直接权威来源,用高可信二手来源补充背景和独立验证。
- 记录发布者、标题、发布日期、不同情况下的事件日期、定位信息和访问日期,让关键结论可追溯。
- 交叉验证重要结论,调查日期或数字冲突,区分事实、来源主张、推断和建议。
- 输出结论、置信度、反方证据、未知项、限制和具体下一步,不让结论超出范围。
如果证据已经给全、主要任务是形成正式长报告,应转交 report-writer。
输出契约
- 研究问题、范围、截止时间和证据标准
- 带置信度的核心结论
- 含发布、事件和访问日期的证据台账
- 冲突与替代解释
- 未知项、限制和下一步
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- OpenHands/extensions★ 167same name
- duncan-buildroom/freeskills★ 65same name
- Mikefluff/skills★ 26same name
- charlie947/life-automation-skills★ 25same name
- Heuresis/YouTube-Agency★ 15same name
- TheCraigHewitt/cowork-starter-pack★ 5same name
- robertbradley-oss/skills★ 2same name
- alectivism/maven-template★ 1same name
- molly-diversifiedfun/claude-skills★ 1same name
- Nomanriaz786/claude-consulting-team★ 1same name
9 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use weekly-review.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
QuixiAISkillweekly-review
Review the past week across goals, tasks, calendar, journal, and commitments, then propose the next week
Also in 3 projects that use this
In this repository40 other files it gives its agents.
- api-contract-reviewSkill
- architecture-decision-recordSkill
- architecture-deepening-analysisSkill
- bug-root-cause-analysisSkill
- change-impact-analysisSkill
- ci-failure-diagnosisSkill
- configuration-auditSkill
- content-consistency-checkSkill
- database-migration-reviewSkill
- dead-code-verificationSkill
- decision-prototypeSkill
- dependency-upgrade-analysisSkill
- documentation-syncSkill
- document-reviewSkill
- excel-data-quality-check-basicSkill
- feature-implementationSkill
- meeting-notes-to-actionsSkill
- pdf-review-basicSkill
- pdf-reviewSkill
- performance-regression-analysisSkill
- presentation-outlineSkill
- project-health-checkSkill
- release-readiness-checkSkill
- repo-doctor-routerSkill
- repo-onboardingSkill
- report-writerSkill
- requirements-clarificationSkill
- requirements-to-specSkill
- safe-change-planSkill
- safe-code-reviewSkill
- safe-fix-implementationSkill
- safe-test-implementationSkill
- security-focused-reviewSkill
- session-handoffSkill
- skill-authoringSkill
- skill-quality-auditSkill
- spec-to-work-itemsSkill
- spreadsheet-data-cleaningSkill
- test-gap-analysisSkill
- word-document-review-basicSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

