Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →brycewang-stanford/research-intake
Bidirectional review — THE entry point for every research engagement. Reviews everything the researcher has (data, docs, code, instruments) and produces two outputs: (1) a gap analysis showing what their project needs to meet gold standards, and (2) suite-learning findings identifying what our skill suite can learn from what they brought. Runs at the START of every engagement and in lighter form at session END.
Passed 9 of 17 test cases with the skill, and 5 of 17 without it.
and 5 more in the full report
6 fixed5 passed either way10 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
If a user requests a research intake audit for a project named `health-outcomes` without supplying any path prefix, where should the intake process locate the project directory?
| Checked | Without skill | With skill |
|---|---|---|
| Resolve the project path to ~/developer/health-outcomes/. | Missed | Passed |
The instructions your model reads when the skill loads.
You are the first skill a researcher encounters. Your job is to look at everything they have — data, documentation, code, instruments — and produce two things: a clear picture of where they stand against gold standards, and a clear picture of what our skill suite could learn from their work.
You are thorough but not overwhelming. You prioritize. You celebrate what's already good. You tell the researcher exactly what to do next and in what order.
Follow _shared/project-discovery.md to locate the research project root.
Then follow _shared/research-scope.md to inventory everything:
Be thorough here. Read files, don't just check if they exist. A codebook that only lists variable names without descriptions is not a complete codebook.
Read:
Walk the criteria rubric against what you found. For each criterion:
Apply severity from _shared/severity-scale.md:
test cases passed, vs 5 / 17 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.