agentleFS
art2urlart2url/career-agent-skills/skills/academic-research-cv/SKILL.md

academic-research-cv

Skill9 starsChanged 7 months agoMITView on GitHub

Build an academic CV for research and faculty roles — format publications, grants, teaching, and service sections by discipline convention

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use when the user is applying for faculty, research, or postdoc positions, or creating/updating a curriculum vitae.

    line 10
  2. Distinctive:

    Follow your discipline's conventions for citation style and author order

    line 81
  3. Distinctive:

    Update at least every 6 months

    line 82
  4. Distinctive:

    Do not use industry-style skills sections or objectives

    line 83

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Academic Research CV

Trigger

Use when the user is applying for faculty, research, or postdoc positions, or creating/updating a curriculum vitae.

Keywords: "academic CV", "research CV", "curriculum vitae", "faculty CV", "faculty position", "publications", "tenure-track", "postdoc CV", "professor resume", "academic job market", "grants section", "teaching portfolio", "ORCID", "publication list", "PhD CV", "researcher CV", "academic job application"

Key Differences from Industry Resumes

  • Comprehensive: include everything — length grows with career (grad student 2-4pp, senior faculty 15-30+pp)
  • Scholarship-focused: publications and grants are the currency
  • No page limit: completeness is expected, not brevity
  • Field conventions matter: author order, citation style, section emphasis vary by discipline

Section Order (adjust by position type)

Research-focused: Contact → Education → Publications → Grants → Research → Teaching → Service

Teaching-focused: Contact → Education → Teaching → Course Development → Publications → Service

Postdoc: Contact → Education → Publications → Research → Skills → Presentations

Process

Step 1: Contact

Name with credentials (Ph.D.), department, institution, email, website, ORCID.

Step 2: Education

Reverse chronological. Include: degree, field, institution, year, dissertation title, advisor, committee (for PhD).

Step 3: Publications (most critical for research positions)

  • Bold your name in author lists
  • Number entries (reverse chronological in sciences)
  • Include DOIs
  • Mark student co-authors with asterisk*
  • Separate: peer-reviewed articles, books/chapters, conference proceedings, under review, in preparation

Field notes:

  • Sciences: first author and last/senior author positions matter, impact factors sometimes relevant
  • Humanities: single-author work valued most, books are crucial
  • Social sciences: mix of solo and collaborative, funded research important

Step 4: Grants & Funding

Format: Agency + mechanism (PI/Co-PI) | "Title" | Dates | Amount (total + your share)

Separate: Awarded, Pending, and optionally Not Funded.

Step 5: Teaching

Course number + title, role (instructor/TA/guest), institution, dates, enrollment size, course development notes.

Step 6: Service, Mentoring, Presentations

  • Service: editorial boards, grant panels, committees (department/university/profession)
  • Mentoring: students and postdocs with current positions (shows pipeline success)
  • Presentations: invited talks separate from conference presentations

Output Format

## Academic CV: [Name]

### Recommended Section Order
[Based on position type and field]

### Formatted Sections
[Each section in proper format]

### Items to Add/Update
- [ ] [missing item]

Rules

  • Follow your discipline's conventions for citation style and author order
  • Update at least every 6 months
  • Do not use industry-style skills sections or objectives
  • Adjust section order to the specific position type

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.