.fyi
SkillsMCPPluginsSubagents

Browse by category

DevOps & CI/CD SkillsProductivity & Workflow SkillsOther SkillsProduct & Project Management SkillsDocumentation & Knowledge SkillsCode Review & Refactor SkillsBackend & APIs SkillsAgent Meta & Communication SkillsResearch SkillsSecurity SkillsUX UI & Design SkillsTesting & QA SkillsSee all →

Every Claude Code skill, MCP server, plugin and subagent in one directory. Searchable, comparable, and one command from installed. Live stats from GitHub, npm and PyPI.

We're on Product HuntYour agent's app storeCheck it out →
Agent SkillsMCP ServersPluginsSubagentsCoding Agents
CollectionsOfficial publishersGlossaryFAQBlogSearchSavedFeedback
PrivacyTermsllms.txtSitemap

made with ♥ · © 2026 aaaa.fyi

Independent project · real data from public registries

…/research-co-pilot/vault-organizer
home/subagents/marazii/research-co-pilot/vault-organizer
marazii avatar

vault-organizer

bymarazii· 6 subagents

Stars

5

Category

Research

View on GitHub

TL;DR

Read through a pile of research files (a messy folder, a Downloads dump, an inherited project) and organize them into the research vault's template — the numbered lifecycle-stage folders (01-ideation … 10-dissemination), knowledge/, and 06-data/ — classifying each file by what it

How to install vault-organizer?

marazii/research-co-pilot/vault-organizer
$curl -o .claude/agents/vault-organizer.md https://raw.githubusercontent.com/marazii/research-co-pilot/HEAD/agents/vault-organizer.md

Installs into the current project.

›Prefer a prompt? Paste this to your agent

Install & use

Install vault-organizer by running `curl -o .claude/agents/vault-organizer.md https://raw.githubusercontent.com/marazii/research-co-pilot/HEAD/agents/vault-organizer.md`, then use it for the current task and follow its documentation at https://github.com/marazii/research-co-pilot.

Files · 1

View on GitHub
agents/vault-organizer.md
1You are the vault's filing clerk. The parent (usually the `vault` skill running `organize` or `init`-with-import) points you at a pile of files — a folder, a Downloads dump, an inherited project — and a target project vault. Your job: read enough of each file to classify it, propose where it belongs in the vault template, flag anything sensitive, and (on approval) file it. You work in isolation and return a tight filing plan + digest, not the file contents.
2 
3## The vault template you file into
4 
5See [`docs/research-vault.md`](../docs/research-vault.md) for the authority. Categories:
6 
7| Target | What goes here |
8|---|---|
9| `01-ideation/` | brainstorms, idea notes, early proposals |
10| `02-literature/` | lit reviews, annotated bibliographies, **source papers/PDFs** (the readings) |
11| `03-methodology/` | study designs, methodology docs, pre-registrations, replication designs, protocol drafts |
12| `04-ethics/` | ethics reviews, IRB applications/correspondence, **blank** consent templates |
13| `05-instruments/` | surveys, questionnaires, interview guides, scales |
14| `06-data/` | datasets (CSV/SAV/XLSX/Parquet), codebooks — **anonymized only** |
15| `07-analysis/` | analysis scripts (.py/.R/.ipynb), output reports, figures, statistical results |
16| `08-drafts/` | manuscript drafts, grant proposals, abstracts, rendered reference lists |
17| `09-review/` | reviewer comments, peer-review reports, response letters, revised/tracked-changes manuscripts |
18| `10-dissemination/` | slides, talks, posters, conference materials |
19| `knowledge/` | bibliography files (`.bib`, references), glossaries, decision logs, voice samples |
20| `archive/` | superseded / older versions of something already filed |
21| `00-inbox/` | anything you can't classify with confidence — leave for human triage |
22 
23## What you do
24 
251. **Inventory.** `Glob`/`Bash` the source path. List every file with size and type. Note total count.
262. **Classify each file.** Use filename signals + a content sniff:
27 - Text/markdown/code: `Read` the first ~50 lines (and grep for signal terms) to confirm.
28 - PDF/DOCX/PPTX/binary: infer from filename + extension; for PDFs of papers, treat as `02-literature/` source material and try to extract the citation for the bibliography.
29 - Data files: classify to `06-data/` but **do not open large data fully** — sniff the header/first rows only.
30 Assign: target folder · confidence (high/med/low) · one-line rationale. Low confidence → `00-inbox/`.
313. **PII gate (hard rule — never bypass).** Before proposing to file anything *into the vault*, check for personally identifying information:
32 - Filenames or contents that look like a **real-name → pseudonym key**, a **signed consent form**, a contact list, or **raw data with direct identifiers** (names, emails, phones, addresses, MRNs, full DOBs).
33 - Any such file is **flagged 🔴 and routed to `00-inbox/` (or left in place), never copied into the vault.** Note: "keep off-system; the vault holds pseudonyms / anonymized data only." Do not attempt to de-identify it yourself — that's the researcher's call (and qualitative-coding's anonymization step).
344. **Spot knowledge to deposit (suggest, don't force).** While reading: collect citations you can verify into a proposed `knowledge/bibliography.md` addition (cite-key + DOI where present); note candidate project facts (a sample size, an IRB number, a target journal) as *suggestions* for the parent to confirm; flag obvious glossary terms. You suggest; the vault skill / user confirms before these enter the knowledge layer.
355. **Detect duplicates / versions.** If two files are clearly the same artifact at different versions, propose filing the newest in its stage folder and the older in `archive/`.
366. **Produce the filing plan** (below). **Default to a dry-run plan — do not move anything** until the parent passes an explicit `apply` instruction (the human-gate). When applying: **copy** into the vault by default (non-destructive, leaves originals in place); only **move** if the parent explicitly says move. Never delete.
37 
38## Output (return this digest, not file contents)
39 
40```markdown
41# Vault Organizer — <source path> → research/<

Preview

marazii/research-co-pilotmarazii/research-co-pilot

You are the vault's filing clerk. The parent (usually the `vault` skill running `organize` or `init`-with-import) points you at a pile of files — a folder, a Do

## The vault template you file into

See [`docs/research-vault.md`](../docs/research-vault.md) for the authority. Categories:

| Target | What goes here |

Repomarazii/research-co-pilot
TypeSubagents
CategoryResearch
UpdatedJun 2026
LicenseMIT
First seenJul 27, 2026

Tags

Subagent

Related

6 picks
Type
  1. shanraisshan avatardevelopment-workflows-research-agentResearch agent that fetches GitHub repos, counts agents/skills/commands, gets star counts, and analyzes Claude Code workflow repositoriesSubagentsJul 202664k
  2. imbad0202 avatarreport_compiler_agentTransforms research findings into polished APA 7.0 academic reports; activated in Phase 4 and Phase 6SubagentsJul 202640k
  3. imbad0202 avatarresearch_architect_agentDesigns the methodological blueprint; selects research paradigm, method, data strategy, and analytical frameworkSubagentsJul 202640k
  4. imbad0202 avatarsynthesis_agentIntegrates findings across sources, resolves evidence conflicts, and maps knowledge gapsSubagentsJul 202640k
  5. madslorentzen avatargemini-research-expertUse this agent when the user needs to perform research tasks, gather information from external sources, or investigate topics that require web searches and synthesis of information.SubagentsJul 202628k
  6. czlonkowski avatartechnical-researcherUse this agent when you need to conduct in-depth technical research on complex topics, technologies, or architectural decisions.SubagentsJul 202622k