본문으로 건너뛰기
cccskills
무료GitHub에 공개

academic-cv

Build or tailor an academic CV for faculty, postdoc, research or fellowship applications: publications, grants, teaching, supervision and service in the order the field expects, with consistent citations. Use when asked to write my academic CV, update my CV for a lectureship, tenure-track or postdoc application, format my publications list, or adapt my academic CV for an industry research role. Produces the full academic CV, a field-appropriate section order, a clean publications list in one citation style, and a two-page summary version when asked.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

설치 방법 보기

포함된 파일(1)

  • SKILL.md3.8 KB

SKILL.md(원문)

설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.

Academic CV

An academic CV is a complete record, not a summary. Hiring committees look for the same things in a fixed order: research, funding, teaching, service. Length is expected; inconsistency is not. This skill builds the record, orders it for the field and the post, and formats every citation the same way.

Part of the pm-cv bundle.

What This Skill Produces

  • The full academic CV
  • A section order for the field and post type, with the reason
  • A publications list in one citation style, with the person's name in bold
  • A short version (two pages) for fellowships or industry research roles, when asked

Required Inputs

Ask for these if not provided:

  • The post: lectureship or assistant professor, postdoc, research fellow, industry research, and the institution's country
  • The field, because conventions differ (author order, conference versus journal weight)
  • The record: publications, grants, teaching, supervision, talks, service, awards
  • The citation style the field uses, or permission to choose the common one

Framework

Typical order (adjust by field and post):

  1. Contact and current position
  2. Research interests (two lines)
  3. Education, with thesis title and supervisor
  4. Appointments
  5. Publications, split: peer-reviewed journal articles; conference papers; books and chapters; preprints and under review (labelled as such)
  6. Grants and funding: funder, title, role, amount, years
  7. Awards and fellowships
  8. Teaching: courses, level, role, student numbers
  9. Supervision: students, level, status
  10. Invited talks and conference presentations
  11. Service: reviewing, committees, organising
  12. Public engagement and impact, where the system values it
  13. References, if the country expects them on the CV

Rules:

  • Reverse chronological within each section.
  • One citation style throughout. The person's name in bold. Equal-contribution marks explained once.
  • "Under review" and "in preparation" are labelled honestly and never listed as published.
  • For computer science and similar fields, top conferences may outrank journals; put them first.

Output Format

Academic CV: [name], [post]

1. The CV 2. Section order and why 3. Citation check: inconsistencies found and fixed 4. Short version (if asked)

Quality Checks

  • Every publication uses the same citation style
  • Unpublished work is labelled as under review or in preparation
  • Grants show the person's role (principal investigator, co-investigator, named researcher)
  • Section order fits the field and post
  • Nothing is listed that the person did not provide

Anti-Patterns

  • Mixing citation styles. Committees notice and read it as carelessness.
  • Inflating status. A submitted paper is not "forthcoming".
  • Hiding teaching for a teaching-heavy post, or hiding research for a research post.
  • Using the full CV for industry. Industry research roles want the short version.

Example Trigger Phrases

  • "Update my academic CV for a lectureship application in the UK."
  • "Format my publications list properly."
  • "I'm applying for a postdoc. Help me order my CV."
  • "Turn my academic CV into a two-page version for an industry research role."

리뷰

아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.

댓글

로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.

아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.

보내면 바로 공개됩니다. 이메일 주소나 전화번호 같은 개인 정보는 쓰지 마세요. URL은 2개까지입니다.

0 / 1,000자

이 양식은 reCAPTCHA로 보호되며 Google 개인정보처리방침 및 서비스 약관이 적용됩니다.

같은 저장소의 스킬

Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 17일 업데이트

Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 17일 업데이트

Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 17일 업데이트

Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 17일 업데이트

Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 17일 업데이트

Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

mohitagw15856/pm-claude-skills1.5천2026년 10월 17일 업데이트

mohitagw15856의 스킬 모두 보기

이 스킬의 문제 신고