research-log
Skill4 starsChanged 20 days agoMITView on GitHub
Maintain a research log that acts as an advisor, not just a diary. Registers projects; records decisions with generalizable lesson extraction; saves session state; recalls cross-project lessons and prior solutions when stuck; checks proposed approaches against promoted anti-pattern rules; runs weekly review with lesson promotion and dashboard refresh. Use when the user asks to initialize a research-log project, record an experiment or decision, save session state, recall past lessons or how a blocker was solved before, check a planned approach against past mistakes, or review all projects.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- zi-yue-1129/research-lab-skillstheir own version, first seen Oct 27, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- zi-yue-1129/research-lab-skills★ 10same name
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.
In this repository38 other files it gives its agents.
- academic-cvSkill
- academic-jobsSkill
- academic-proseSkill
- adversarial-reviewSkill
- bibtex-genSkill
- chrome-sessionSkill
- clickup-cliSkill
- clickup-todaySkill
- commit-triageSkill
- concept-explainerSkill
- contact-emailSkill
- cover-letterSkill
- dropboxSkill
- handdrawn-schematicSkill
- hep-rumor-millSkill
- journal-club-reviewSkill
- magi-researchSkill
- md2pdf-typoraSkill
- morgenSkill
- overleaf-section-workflowSkill
- overleapSkill
- peer-agent-reviewSkill
- proton-mailSkill
- reference-searchSkill
- remarkable-syncSkill
- research-backupSkill
- research-boardSkill
- research-portalSkill
- research-proposalSkill
- research-reportSkill
- research-statementSkill
- scienceplot-pySkill
- vastaiSkill
- wide-slide-illustratorSkill
- workshop-paper-reviewSkill
- xkcd-pySkill
- zai-web-searchSkill
- zoom-summarySkill
The file
We split this skill into the rules it gives an agent
11 rules. About 0 are common, 7 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
M3 — recall when stuck: Search across all projects for prior lessons and solutions.
- Very specific: line 25
Read ~/.research/rules.md (small, promoted-rules-only.
- Distinctive: line 26
Check whether any Rule's trigger/Check matches the proposed action.
- Distinctive: line 27
If a Rule matches, surface it first: "You are about to {X}.
- Distinctive: line 29
If nothing matches, say nothing about rules and proceed normally.
- Distinctive: line 37
Read the matching workflow reference for the user's request:
- Very specific: line 54
Follow the file schemas defined in references/conventions.md exactly.
- Very specific: line 57
When recording a decision, always attempt lesson extraction.
- Distinctive: line 59
Treat dashboard updates as review-time derived data unless a workflow says otherwise.
- Distinctive: line 60
When a workflow requires user approval before writing, draft first and wait for approval.
- Very specific: line 61
Never write to a legacy ~/.research-log/ backup.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Research Log
This skill maintains a unified research-log workspace in ~/.research/ and uses it to actively
improve research, not merely to record it. The data model and all file schemas are defined in
references/conventions.md — read it first whenever you touch the store.
The skill earns its keep at three moments:
- M1 — decision-time guardrail. Surface relevant anti-patterns before the user commits to an approach. See "Decision guardrail" below — this fires from conversation, not only on command.
- M3 — recall when stuck. Search across all projects for prior lessons and solutions.
- M4 — real-time drift. Flag work that has drifted from the current Compass focus.
Decision guardrail (M1) — always active
Whenever the user proposes a research approach — an architecture, model, loss function, methodology, experimental design, or "let's do X" choice — before agreeing, elaborating, or helping execute it:
- Read
~/.research/rules.md(small, promoted-rules-only; cheap to load). - Check whether any Rule's trigger/Check matches the proposed action.
- If a Rule matches, surface it first: "You are about to {X}; this bit you in {projects} — {Check}." Include the evidence. Let the user decide; do not block.
- If nothing matches, say nothing about rules and proceed normally.
This is a behavioral directive, not a hook. It applies in any registered project's working directory. Keep it lightweight — only promoted Rules are checked, and only when an actual approach choice is on the table (not for routine edits or questions).
Workflow router
Read the matching workflow reference for the user's request:
- Project registration or onboarding →
references/initialize.md - Recording an experiment, debugging result, or design choice →
references/record.md - Saving current session context →
references/save-state.md - Recalling past lessons / how a blocker was solved before (M3) →
references/recall.md - Explicitly checking a planned approach against past mistakes (M1) →
references/check.md - Weekly review, dashboard refresh, lesson promotion, archive scan →
references/review.md - Current status of a hypothesis or experiment, the board, comparing experiments, attaching results or
plots, or resuming the session working on an experiment → the
research-boardskill (cards underprojects/{slug}/cards/). Decision reasoning and lessons stay here; when an entry concerns a card, add a**Card**: {slug}:Q{n}/E{m}line to the new journal entry.
Working rules
- Match the current working directory against the Project Registry in
~/.research/dashboard.mdbefore acting on an existing project. - Follow the file schemas defined in
references/conventions.mdexactly. - Acquire the per-project lock (
~/.research/.locks/{slug}.lock) before writing project state. - Compass
← current focusis the anchor for drift detection; keep exactly one. - When recording a decision, always attempt lesson extraction; when a lesson recurs across ≥ 2
projects, propose promoting it to a Rule and regenerate
rules.md. - Treat dashboard updates as review-time derived data unless a workflow says otherwise.
- When a workflow requires user approval before writing, draft first and wait for approval.
- Never write to a legacy
~/.research-log/backup; it is read-only.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
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.

