career-document-architect
Guides the creation of career documents for academic advancement including research statements, teaching statements, diversity statements, CVs, and biosketches. Combines strategic positioning, narrative coherence, and institutional alignment with authentic representation of contributions and vision. Use when writing or reviewing faculty applications, fellowship statements, promotion packages, award applications, or when user mentions research statement, teaching philosophy, diversity statement, biosketch, academic CV, or career narrative.
What this skill does
# Career Document Architect ## Table of Contents - [Core Principles](#core-principles) - [Workflow](#workflow) - [Document Frameworks](#document-frameworks) - [Writing Strategies](#writing-strategies) - [Guardrails](#guardrails) - [Quick Reference](#quick-reference) **Related skills (use instead for):** - Grant proposals: `grant-proposal-assistant` - Recommendation letters: `academic-letter-architect` - Manuscript writing: `scientific-manuscript-review` ## Core Principles **1. Vision + Track Record**: Show where you're going AND what you've accomplished **2. Coherent Narrative**: All pieces should tell a unified story **3. Audience Awareness**: Tailor depth and framing to readers **4. Evidence-Based Claims**: Support assertions with specifics **5. Future-Oriented**: Emphasize trajectory and potential **6. Authentic Voice**: Represent yourself genuinely ## Workflow Copy this checklist and track your progress: ``` Career Document Progress: - [ ] Step 1: Identify document type and audience - [ ] Step 2: Gather raw materials (CV, accomplishments) - [ ] Step 3: Develop core narrative thread - [ ] Step 4: Draft document using appropriate framework - [ ] Step 5: Add evidence and specifics - [ ] Step 6: Align with institutional expectations - [ ] Step 7: Polish and format ``` **Step 1: Identify Type and Audience** Determine document type (research/teaching/diversity statement, CV, biosketch). Identify audience (search committee, review panel). Note any specific requirements (page limits, format specifications). See [resources/methodology.md](resources/methodology.md#audience-analysis) for audience considerations. **Step 2: Gather Raw Materials** Compile: Current CV, publications, grants, teaching evaluations, mentorship record, outreach activities, preliminary data, future plans. See [resources/methodology.md](resources/methodology.md#materials-checklist) for comprehensive list. **Step 3: Develop Core Narrative** Identify the through-line connecting your work. What question drives you? What impact do you seek? How does past work connect to future plans? See [resources/methodology.md](resources/methodology.md#narrative-development) for narrative construction. **Step 4: Draft Using Framework** Select appropriate framework for document type. Follow structure that matches institutional norms. See [Document Frameworks](#document-frameworks) for each type. **Step 5: Add Evidence and Specifics** Replace generic claims with specific accomplishments. Quantify where possible (papers, citations, students mentored). Add concrete examples for abstract claims. **Step 6: Align with Institution** Research institution's priorities. Emphasize fit without fabricating. Address how you contribute to their mission. See [resources/methodology.md](resources/methodology.md#institutional-fit) for alignment strategies. **Step 7: Polish and Format** Check length constraints. Ensure consistent formatting. Proofread carefully. Validate using [resources/evaluators/rubric_career_document.json](resources/evaluators/rubric_career_document.json). **Minimum standard**: Average score ≥ 3.5. ## Document Frameworks ### Research Statement **Purpose:** Articulate research vision, demonstrate independence, show future potential **Length:** Typically 2-5 pages (check requirements) **Structure:** ``` OPENING (1 paragraph) - Hook: Compelling statement of your research focus - Big picture: Why this matters to the field/society - Your role: How you contribute to addressing this PAST RESEARCH (1-2 pages) - Organize by themes, not chronology - Highlight key contributions with impact - Show how past work builds foundation for future - Include quantifiable outcomes (papers, citations, methods) CURRENT RESEARCH (0.5-1 page) - Ongoing projects and preliminary results - Bridge between past and future - Show productivity and momentum FUTURE DIRECTIONS (1-2 pages) - 2-3 specific research directions - For each: Why important? What's the approach? What's expected impact? - Show independence and creativity - Connect to fundable questions (NIH/NSF relevance) CLOSING (1 paragraph) - Synthesis: How pieces fit together - Why this institution/department - Broader impact statement ``` ### Teaching Statement **Purpose:** Articulate teaching philosophy and demonstrate effectiveness **Length:** Typically 1-2 pages **Structure:** ``` PHILOSOPHY (1-2 paragraphs) - Core beliefs about teaching/learning - What makes your approach distinctive - Grounded in evidence or experience EVIDENCE OF EFFECTIVENESS (1-2 paragraphs) - Courses taught with enrollments - Teaching evaluations (quote specific feedback) - Student outcomes (publications, placements) - Innovations introduced METHODS AND APPROACHES (1-2 paragraphs) - Specific techniques you use - Active learning strategies - Assessment approaches - Technology integration MENTORSHIP (1 paragraph) - Undergraduate/graduate mentoring - Student achievements - Mentoring philosophy FUTURE TEACHING (1 paragraph) - Courses you could teach - New courses you'd develop - Curricular contributions ``` ### Diversity Statement **Purpose:** Demonstrate commitment to diversity, equity, and inclusion **Length:** Typically 1-2 pages **Structure:** ``` INTRODUCTION (1 paragraph) - Your understanding of DEI in academia - Why it matters to you - Preview of your contributions PAST ACTIONS (1-2 paragraphs) - Specific activities promoting DEI - Mentoring underrepresented students - Curriculum development - Outreach activities - Quantify impact where possible PERSONAL CONTEXT (optional, 1 paragraph) - Your own background if relevant - Experiences informing your commitment - Only include if comfortable and genuine FUTURE PLANS (1 paragraph) - How you'll contribute at this institution - Specific programs or initiatives - Connection to institutional DEI priorities CLOSING - Synthesis of commitment - Why this matters for your field ``` ### CV Format (Academic) **Standard Sections:** ``` CONTACT INFORMATION EDUCATION - Degrees in reverse chronological order - Institution, degree, year, advisor (for PhD) POSITIONS - Academic appointments - Industry positions (if relevant) PUBLICATIONS - Peer-reviewed (mark * for corresponding author) - Preprints - Reviews/Book chapters GRANTS AND FUNDING - Current and past funding - Role (PI, Co-PI, etc.) - Amount and duration HONORS AND AWARDS PRESENTATIONS - Invited talks - Conference presentations TEACHING - Courses taught - Mentoring record SERVICE - Editorial boards - Review panels - Committee work PROFESSIONAL MEMBERSHIPS ``` ### NIH Biosketch **Length:** 5 pages maximum **Sections:** ``` A. PERSONAL STATEMENT (0.5 page) - Why you're well-suited for this project - Relevant experience and expertise - Key accomplishments that qualify you - Up to 4 publications supporting this statement B. POSITIONS, SCIENTIFIC APPOINTMENTS, AND HONORS C. CONTRIBUTIONS TO SCIENCE (up to 5 contributions, 0.5 page each) - Contribution 1: - Description of contribution (1 paragraph) - Your specific role - Impact on field - Up to 4 publications supporting this contribution - [Repeat for each contribution] D. RESEARCH SUPPORT - Current (with role, title, dates, description) - Completed (last 3 years) ``` ## Writing Strategies ### The "So What?" Test For every claim, ask "so what?" If you can't answer, the claim needs more: | Claim | So What? | Improved | |-------|----------|----------| | "I published 10 papers" | Impact? | "My 10 papers have been cited 500 times, including 3 that established new methods in the field" | | "I'm passionate about teaching" | Evidence? | "My passion for teaching is reflected in consistent evaluation scores above 4.5/5 and 5 undergraduates who went to PhD programs" | | "I'm committed to diversity" | What have you done? | "I co-founded a mentoring program that has supported 20 students from underrepresented groups" | ### Showing vs. Telling | Telling (Weak) | Showing (Strong) | |---------------
Related in Writing & Docs
jax-development
IncludedUse this skill when the user is writing, debugging, profiling, refactoring, reviewing, benchmarking, parallelising, exporting, or explaining JAX code, or when they mention JAX, jax.numpy, jit, grad, value_and_grad, vmap, scan, lax, random keys, pytrees, jax.Array, sharding, Mesh, PartitionSpec, NamedSharding, pmap, shard_map, Pallas, XLA, StableHLO, checkify, profiler, or the JAX repo. It helps turn NumPy or PyTorch-style code into pure functional JAX, fix tracer/control-flow/shape/PRNG bugs, remove recompiles and host-device syncs, choose transforms and sharding strategies, inspect jaxpr/lowering/IR, and benchmark compiled code correctly.
nature-article-writer
IncludedDrafts, rewrites, diagnostically critiques, and style-calibrates primary research manuscripts for Nature and Nature Portfolio journals. Use when the user wants a Nature-style title, summary paragraph or abstract, introduction, results, discussion, methods, figure legends, presubmission enquiry, cover letter, reviewer response, or when a scientific draft sounds generic, jargon-heavy, structurally weak, or AI-ish and needs precise, broad-reader-friendly prose without inventing data, analyses, or references. Best for primary research articles and letters rather than reviews or press releases unless explicitly adapting one.
deckrd
IncludedDocument-driven framework that derives requirements, specifications, implementation plans, and executable tasks from goals through structured AI dialogue. Use when user says "write requirements", "create spec", "plan implementation", "derive tasks", "structure this feature", "break down into tasks", or "document this module". Also use for reverse engineering existing code into docs (/deckrd rev). Do NOT use for direct code writing — use /deckrd-coder after tasks are generated. Do NOT use when the user only wants to run or fix existing code without planning.
clinical-decision-support
IncludedGenerate professional clinical decision support (CDS) documents for pharmaceutical and clinical research settings, including patient cohort analyses (biomarker-stratified with outcomes) and treatment recommendation reports (evidence-based guidelines with decision algorithms). Supports GRADE evidence grading, statistical analysis (hazard ratios, survival curves, waterfall plots), biomarker integration, and regulatory compliance. Outputs publication-ready LaTeX/PDF format optimized for drug development, clinical research, and evidence synthesis.
handling-sf-data
IncludedSalesforce data operations with 130-point scoring. Use this skill to create, update, delete, bulk import/export, generate test data, and clean up org records using sf CLI and anonymous Apex. TRIGGER when: user creates test data, performs bulk import/export, uses sf data CLI commands, needs data factory patterns for Apex tests, or needs to seed/clean records in a Salesforce org. DO NOT TRIGGER when: SOQL query writing only (use querying-soql), Apex test execution (use running-apex-tests), or metadata deployment (use deploying-metadata).
accelint-ac-to-playwright
IncludedConvert and validate acceptance criteria for Playwright test automation. Use when user asks to (1) review/evaluate/check if AC are ready for automation, (2) assess if AC can be converted as-is, (3) validate AC quality for Playwright, (4) turn AC into tests, (5) generate tests from acceptance criteria, (6) convert .md bullets or .feature Gherkin files to Playwright specs, (7) create test automation from requirements. Handles both bullet-style markdown and Gherkin syntax with JSON test plan generation and validation.