Research brief
Answer a research question with a sourced brief: the answer first, then the evidence, how confident it is, and what could not be found.
In Lobstack: Skills › Library › Add
What your agent will do.
A question needs looking up — a market, a regulation, a technology, a company — and the person wants an answer to act on, not a reading list.
- 01
Restate the question in one sentence and name the decision it feeds. If it is ambiguous in a way that changes the answer, ask before searching.
- 02
Search wide, then read deep. Open at least five sources and prefer primary ones — the vendor's docs, the regulator, the filing, the paper — over articles about them. Note each source's date.
- 03
Write it as a document:
- Answer: two to four sentences, conclusion first.
- Confidence: high, medium or low, and why.
- Evidence: each finding with its source as a link.
- Disagreements: where sources conflict, which you believe and why.
- Gaps: what you could not find. Never fill one with a guess.
- 04
Put comparisons of more than two options in a table, and figures over time in a chart fence.
- 05
Stay under two pages. Interesting material that does not change the answer goes in a short "Also found" list, or goes.
If the only sources are marketing pages, or older than the question allows, say that plainly before answering.
The whole SKILL.md: 34 lines of Markdown.
Add it in the app from Skills › Library, or copy it and paste it into Skills › Add a skill.
---name: research-briefdescription: "Answer a research question with a sourced brief: the answer first, then the evidence, how confident it is, and what could not be found."metadata: title: "Research brief" category: research tags: [research, sources]--- ## When to use this A question needs looking up -- a market, a regulation, a technology, a company-- and the person wants an answer to act on, not a reading list. ## How 1. Restate the question in one sentence and name the decision it feeds. If it is ambiguous in a way that changes the answer, ask before searching.2. Search wide, then read deep. Open at least five sources and prefer primary ones -- the vendor's docs, the regulator, the filing, the paper -- over articles about them. Note each source's date.3. Write it as a document: - Answer: two to four sentences, conclusion first. - Confidence: high, medium or low, and why. - Evidence: each finding with its source as a link. - Disagreements: where sources conflict, which you believe and why. - Gaps: what you could not find. Never fill one with a guess.4. Put comparisons of more than two options in a table, and figures over time in a chart fence.5. Stay under two pages. Interesting material that does not change the answer goes in a short "Also found" list, or goes. If the only sources are marketing pages, or older than the question allows, saythat plainly before answering.
- Research
Competitor scan
Compare named competitors on what matters to a decision (price, audience, features, recent moves) from their own public pages.
SKILL.md · App - Research
Stress-test a plan
Question a plan or design one point at a time, biggest risk first, until every open point is decided or deliberately parked, then hand back the decisions.
SKILL.md · App - Research
Fact-check a draft
Fact-check a draft: pull out every checkable claim, check each against the source closest to it, and mark it confirmed, wrong (with the fix) or unverified.
SKILL.md · App - Research
Page change report
Check named web pages against the last visit and report only real changes (price, wording, availability, broken parts), quoting before and after.
SKILL.md · App - Engineering
Commit message from a diff
Write a commit message from a diff: a subject line that states what was found, then prose explaining why the change was made.
SKILL.md · App - Engineering
Triage a failing build
Triage a red CI run: find the first real failure, attribute it to a change, and say whether the code is wrong or the runner was.
SKILL.md · App