Agent skill

Intake Project

A skill your agent uses when starting or inheriting a radiology research project and need to know what it is.

Install Intake Project

skills CLI

$ npx skills add Aperivue/medsci-skills --skill intake-project -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install Aperivue/medsci-skills intake-project --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/Aperivue/medsci-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/intake-project .claude/skills/intake-project && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "intake-project" agent skill from https://github.com/Aperivue/medsci-skills/tree/main/skills/intake-project into .claude/skills/intake-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "intake-project", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Aperivue/medsci-skills/tree/main/skills/intake-project

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Aperivue/medsci-skills --skill intake-project -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Aperivue/medsci-skills intake-project --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Aperivue/medsci-skills.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/intake-project .agents/skills/intake-project && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "intake-project" agent skill from https://github.com/Aperivue/medsci-skills/tree/main/skills/intake-project into .agents/skills/intake-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "intake-project", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Aperivue/medsci-skills --skill intake-project -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Aperivue/medsci-skills intake-project --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Aperivue/medsci-skills.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/intake-project .cursor/skills/intake-project && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "intake-project" agent skill from https://github.com/Aperivue/medsci-skills/tree/main/skills/intake-project into .cursor/skills/intake-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "intake-project", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Aperivue/medsci-skills.git --path skills/intake-project

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Aperivue/medsci-skills --skill intake-project -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Aperivue/medsci-skills intake-project --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Aperivue/medsci-skills.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/intake-project .gemini/skills/intake-project && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "intake-project" agent skill from https://github.com/Aperivue/medsci-skills/tree/main/skills/intake-project into .gemini/skills/intake-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "intake-project", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Aperivue/medsci-skills intake-project

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Aperivue/medsci-skills --skill intake-project -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/Aperivue/medsci-skills.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/intake-project .github/skills/intake-project && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "intake-project" agent skill from https://github.com/Aperivue/medsci-skills/tree/main/skills/intake-project into .github/skills/intake-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "intake-project", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Aperivue/medsci-skills --skill intake-project -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Aperivue/medsci-skills intake-project --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Aperivue/medsci-skills.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/intake-project .opencode/skills/intake-project && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "intake-project" agent skill from https://github.com/Aperivue/medsci-skills/tree/main/skills/intake-project into .opencode/skills/intake-project/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "intake-project", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: intake-project
GitHub stars: 331
Token cost: ~1.6k tokens
SKILL.md length: 506 words
Files: 3 (incl. references)
Skills in repo: 54
Repo updated: Oct 5, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

A skill your agent uses when starting or inheriting a radiology research project and need to know what it is.

Works in 4 steps: Discover context → Classify project and stage → Surface missing inputs → …
Inheriting a radiology research project and need to know what it is
SKILL.md covers Canonical Manuscript Folder…, Workflow and Handoff Rules
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Intake Project is an agent skill from Aperivue/medsci-skills. Use when starting or inheriting a radiology research project and need to know what it is. Classifies the project type, summarizes its current state, lists missing inputs, recommends next steps and scaffolds lightweight project memory files.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/memory_templates.md` and `skill.yml`).

It sits in Research & Science, covering Project scaffolding and Agent memory. The repository describes itself as: Agent Skills for medical research — literature search, reporting-guideline & citation checks, statistics, publication figures, submission. Works with Claude Code, Codex, Cursor &… The licence is MIT.

When your agent uses it

Inheriting a radiology research project and need to know what it is
Tasks that involve Project scaffolding
Tasks that involve Agent memory

Example prompts

“/intake-project”

Workflow steps

4 steps, taken from the step headings in SKILL.md.

Discover context
Classify project and stage
Surface missing inputs
Produce normalized summary

What it can do on your machine

Read from SKILL.md and the folder at commit 3b14ae2. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md.
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Intake Project loads about 1.6k tokens when it runs, and up to ~1.7k if it reads all its reference files. Until then it costs about 64 tokens; SKILL.md has 506 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~64
When it runs · the whole SKILL.md, loaded when a task matches: ~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them: ~1.7k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Aperivue/medsci-skills at commit 3b14ae2, republished under its MIT licence (© Aperivue). 506 words, ~1,613 tokens.

Download SKILL.mdSave it as .claude/skills/intake-project/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.

name: intake-project
description: Use when starting or inheriting a radiology research project and need to know what it is. Classifies the project type, summarizes its current state, lists missing inputs, recommends next steps and scaffolds lightweight project memory files.
metadata.triggers: new project, intake project, project intake, classify project, organize project, what is this project

Intake-Project Skill

Canonical Manuscript Folder Structure

/manage-project init scaffolds new projects; its script is the source of truth for that tree, including the qc/ folder the QC skills write to. Use the layout below to reorganize an existing project that was never scaffolded, mapping each artifact into one of these slots or into a folder the init scaffold or another skill already writes to.

{project_root}/
├── HANDOFF.md                         # session handoff entry point
├── README.md                          # project overview
├── data/                              # raw data (NEVER edit; read-only)
├── analysis/                          # reproducible scripts (00_* → 04_*)
├── output/                            # analysis outputs: CSVs, PNGs, intermediates
├── qc/                                # QC reports the skills write (self-review, checklists, audits)
├── irb/                               # IRB/ethics docs
├── proposal/                          # original protocol / approved proposal
├── reviews/                           # external correspondence
├── manuscript/                        # SOURCE manuscript + drafting
│   ├── manuscript_v{N}.{md,docx,pdf}  # current canonical working version (top level)
│   ├── build_unified_docx.py          # or pandoc wrapper
│   ├── archive/                       # ALL prior versions v1 .. v{N-1}
│   ├── reviews/                       # review notes (QC reports go in qc/ at the root)
│   ├── figures/                       # figure scripts + rendered PNG/PDF
│   └── tables/                        # table scripts + rendered docx
└── submission/                        # per-journal packages
    └── {journal-slug}/                # e.g., chest/, kjr/
        ├── CHECKLIST.md
        ├── cover_letter.{md,docx,pdf}
        ├── title_page.docx            # separated for double-anonymized
        ├── manuscript_anonymized.{docx,pdf}
        ├── supplement.{docx,pdf}
        ├── strobe_checklist.md        # or PRISMA / CONSORT
        ├── circulation_email.md
        └── figures/                   # submission-ready DPI copies

Rules

manuscript/ = source; submission/{journal}/ = derived artifacts. Regenerate submission files from manuscript/manuscript_v{N}.md; never edit anonymized/title-page directly.
One canonical working version at manuscript/manuscript_v{N}.{md,docx,pdf}. Older versions move to manuscript/archive/ immediately on version bump.
No loose files at project root. Only HANDOFF.md, README.md, the project memory files (Phase 3), the contract files /manage-project init writes (SSOT.yaml or project.yaml, project_state.json, artifact_manifest.json), and folder entries.
QC artifacts (self-review, reporting checklists, cross-reference and reference audits) live in qc/ at the project root, where the skills that produce them write them, not at manuscript top level.
On rejection/retarget: cp -r submission/{old} submission/{new}, then rewrite cover letter and reformat.
Double-anonymized journals (Chest, AJRCCM): title page and anonymized manuscript MUST be separate files under submission/{journal}/.
Keep existing project labels and file names in the language the workspace already uses.

When to apply

At project intake: scaffold through /manage-project init — unless the user only wants a quick assessment.
At first submission prep: create submission/{journal}/ and populate.
Mid-project cleanup: when manuscript/ has >3 versioned files or QC docs at top level, reorganize.
Before session handoff: reorganize if structure is drifting.

Workflow

Phase 1: Discover context

Read top-level folder names and key files.
Detect manuscript-like files, tables, figures, protocols, and analysis outputs.
Extract:
- project title or working title
- study question
- dataset or cohort hints
- collaborators or institutions
- venue/journal hints

Show full SKILL.md (223 more words)Show less

Phase 2: Classify project and stage

Determine:

project type: original | review | meta-analysis | case report | technical note | grant | peer review | challenge | career-doc
primary domain: radiology | medical AI | multimodal LLM | intervention | survival/prognostic | diagnostic accuracy | workflow
target output: paper | abstract | grant | review | rebuttal | CV
likely target journal or venue — only if the files name one
one current stage: idea | data assembly | analysis planning | analysis in progress | drafting | revision | submission prep | archived/unclear

If the folder mixes several studies, say so rather than collapsing them into one.

Gate: Present the classification (project type, stage, target output) to the user. Confirm before creating any files — misclassification leads to wrong scaffold and wrong skill routing.

Phase 3: Surface missing inputs

Check for blocking dependencies and common gaps:

no explicit study question
no target journal
no analysis plan
no variable dictionary
no claims-to-results map
no review log for revised manuscripts

If missing, propose or create lightweight anchor files — PROJECT.md, STATUS.md, CLAIMS.md, DATA_DICTIONARY.md, ANALYSIS_PLAN.md, REVIEW_LOG.md — only those the project type justifies. Read ${CLAUDE_SKILL_DIR}/references/memory_templates.md when creating PROJECT.md or STATUS.md.

Phase 4: Produce normalized summary

Output this structure:

text

## Project Intake Summary
Project: ...
Type: ...
Current stage: ...
Likely target: ...

### What exists
- ...

### What is missing
- ...

### Risks / ambiguities
- ...

### Recommended next actions (3-5, in dependency order)
1. ...
2. ...
3. ...

Handoff Rules

After intake:

route to search-lit if the literature basis is weak
route to design-study if the research question exists but design logic is unclear
route to manage-project if the folder should be scaffolded
route to write-paper only after the project phase is clearly drafting

Files

SKILL.md and 2 other files (references) in skills/intake-project of Aperivue/medsci-skills.

SKILL.md
references/memory_templates.md
skill.yml

Open the folder on GitHubat commit 3b14ae2

Compare with similar skills

Intake Project next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Intake Project compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Intake Project this skillAperivue/medsci-skills	331	—	~1.6k	Automated safety check: Pass	MIT	3 days ago
Kmp Starter MemoryDevAtrii/Kmp-Starter-Template	167	—	~963	Automated safety check: Pass	MIT	1 mo ago
Project Docscoco-research/coco	503	—	~3.6k	Automated safety check: Pass	Custom licence	today
Agent App CreatorCraftOS-dev/CraftBot	392	—	~4.8k	Automated safety check: Pass	MIT	today
Satorisundial-org/awesome-openclaw-skills	663	—	~1.4k	Automated safety check: Pass	None	7 mo ago
Complexa DesignNVIDIA-BioNeMo/bionemo-agent-toolkit	478	—	~4.1k	Automated safety check: Notes	Custom licence	today

Similar skills

Kmp Starter Memory
DevAtrii/Kmp-Starter-Template
Persistent per-project memory for KMP Starter Template apps.
167 GitHub stars~963 tokensUpdated 1 mo ago
DevelopmentAuto-check passed
Project Docs
coco-research/coco
A skill your agent uses when starting a new project, onboarding to an existing product, or auditing an existing folder structure against the standard.
503 GitHub stars~3.6k tokensUpdated today
Productivity & AutomationAuto-check passed
Agent App Creator
CraftOS-dev/CraftBot
Create Agent App applications (PocketBase backend, React kit frontend).
392 GitHub stars~4.8k tokensUpdated today
DevelopmentAuto-check passed
Satori
sundial-org/awesome-openclaw-skills
Persistent long term memory for for continuity in ai sessions between providers and codegen tools.
663 GitHub stars~1.4k tokensUpdated 7 mo ago
DevelopmentAuto-check passed
Complexa Design
NVIDIA-BioNeMo/bionemo-agent-toolkit
End-to-end Proteina-Complexa design pipeline driver. An agent skill from NVIDIA-BioNeMo/bionemo-agent-toolkit.
478 GitHub stars~4.1k tokensUpdated today
Research & ScienceAuto-check: notes
Gtd
scunning1975/MixtapeTools
Warrant-first research GTD system. An agent skill from scunning1975/MixtapeTools.
473 GitHub stars~2.9k tokensUpdated 1 mo ago
Research & ScienceAuto-check: notes

Questions about Intake Project

What does Intake Project do?

A skill your agent uses when starting or inheriting a radiology research project and need to know what it is. Intake Project is an agent skill from Aperivue/medsci-skills. Use when starting or inheriting a radiology research project and need to know what it is.

When should I use Intake Project?

Intake Project fits situations like: inheriting a radiology research project and need to know what it is; tasks that involve Project scaffolding; tasks that involve Agent memory.

How do I install Intake Project in Claude Code?

Run `npx skills add Aperivue/medsci-skills --skill intake-project -a claude-code`. Or copy the skill folder (skills/intake-project in Aperivue/medsci-skills) into .claude/skills/intake-project in your project. Claude Code loads it when a task matches its description.

How do I install Intake Project in Codex?

Run `npx skills add Aperivue/medsci-skills --skill intake-project -a codex`. Or copy the skill folder (skills/intake-project in Aperivue/medsci-skills) into .agents/skills/intake-project in your project. Codex loads it when a task matches its description.

Can I use Intake Project in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Aperivue/medsci-skills --skill intake-project -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/intake-project, .gemini/skills/intake-project, .github/skills/intake-project and .opencode/skills/intake-project in your project.

What does Intake Project need to run?

SKILL.md names no scripts, command-line tools or credentials: Intake Project is instructions for the agent only.

Does Intake Project access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Intake Project safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Intake Project use?

Intake Project is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Intake Project use?

About 1.6k tokens (SKILL.md is roughly 6.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 74 tokens, read only when the agent opens those files.

What are the alternatives to Intake Project?

Skills that share tags, products or a category with Intake Project: Kmp Starter Memory (DevAtrii/Kmp-Starter-Template, 167 stars), Project Docs (coco-research/coco, 503 stars), Agent App Creator (CraftOS-dev/CraftBot, 392 stars) and Satori (sundial-org/awesome-openclaw-skills, 663 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Intake Project?

Aperivue (a GitHub organization) maintains it in Aperivue/medsci-skills, which has 331 GitHub stars. The repository holds 54 skills in this directory. The repository was last updated on October 5, 2026.

Source: Aperivue/medsci-skills on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Intake Project

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Intake-Project Skill

Canonical Manuscript Folder Structure

Rules

When to apply

Workflow

Phase 1: Discover context

Phase 2: Classify project and stage

Phase 3: Surface missing inputs

Phase 4: Produce normalized summary

Handoff Rules

Files

Compare with similar skills

Similar skills

More from Aperivue/medsci-skills

Related

Questions about Intake Project