Build a Team Library of Research Summaries
Turn individual paper reading into a searchable team resource
Team members read the same papers separately and summarise them differently. Inconsistent summaries mean contradictory advice, duplicated effort, and no single place to check what a study actually said.
That is the gap this drop closes. It is a data & analysis skill built for Kimi, and it takes about ten minutes to set up the first time. After that it runs in under a minute.
Who should use it
Research leads, compliance teams, strategy units and policy analysts who need everyone reading from the same technical sources
How it works
The skill file does five things, in this order.
1. Define your summary template. Agree on standard sections so every summary captures methodology, findings, limitations and regional relevance in the same order
2. Set citation depth rules. Decide whether your team needs page numbers, direct quotes, or section references for each claim type
3. Create a naming convention. Use author-year-topic filenames so anyone can find and cite the summary without asking who read it
4. Run a calibration session. Have three people summarise the same paper using your prompt, compare outputs, then adjust the template until results align
5. Build a summary index. Maintain a spreadsheet linking each summary to its source, date reviewed, reviewer name and tags for quick retrieval
What comes back
A shared repository where anyone on the team can check what a paper says without re-reading it or guessing at interpretation
The mistake to avoid
Version your prompt in the same repository as your summaries. When you refine the template, document the change and decide whether older summaries need updating or just a version tag.
Running it
Paste the prompt block into a new Kimi chat and attach your files in the same message. Kimi's long context means you should upload everything at once rather than in batches, splitting the input is what causes it to lose cross-references between documents.
Where this fits
On its own, one skill saves an hour a week. The compounding happens when three or four of them run in sequence on the same input, the same transcript that produces a scope of work also produces the follow-up email and the project brief. That is the point at which it stops being a prompt and starts being an internal tool. If you want that wired into the systems your team already uses, that is the work 67 Digital does.
In the file
You are a research summarisation assistant for a team library.
Paper title: {paper_title}
Authors: {authors}
Year: {publication_year}
DOI or URL: {source_link}
Summarise this paper using the following template exactly:
## Research Question
State the main question or hypothesis in one sentence.
## Methodology
Describe the study design, sample size, and data collection method in two sentences.
## Key Findings
List 3-5 findings as bullet points. After each finding, cite the page number or section in square brackets.
## Limitations
Identify two methodological or scope limitations the authors acknowledge or that are evident.
## Relevance to UAE Context
In two sentences, note whether the geography, population or regulations studied align with or differ from the UAE.
## Recommended For
Suggest which team roles should read the full paper based on its focus.
## Reviewed By
{reviewer_name} on {review_date}
Maintain neutral tone. Do not interpret beyond what the paper states. Preserve technical terms. If a claim is contested or conditional, note that clearly.