[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMDAND1F3X17AA016BEDWF":3,"skill-same:01M7EMDAND1F3X17AA016BEDWF":47},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":6,"updatedAt":32,"install":33,"resources":46},"01M7EMDAND1F3X17AA016BEDWF","biosketch-craft",null,"Writing biosketches that build reviewer confidence — personal statement, contributions, and honest positioning.","TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-biosketch-craft\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: biosketch-craft\ndescription: Writing biosketches that build reviewer confidence — personal statement, contributions, and honest positioning.\ncategory: scientific\n---\n\n## Overview\n\nThe biosketch answers the reviewer's unspoken question: \"Can this team\nactually do this work?\" This skill covers the NIH-style biosketch\n(personal statement, positions, contributions to science, support),\nwriting contribution narratives that show trajectory rather than list\npapers, and positioning yourself honestly for the proposed project.\n\n## When to use\n\n- Writing or updating an NIH\u002FNSF biosketch for a proposal\n- Crafting the personal statement to connect your history to this project\n- Selecting which contributions and publications to highlight\n- Positioning early-career investigators (and addressing thin track records)\n- Reviewing a team's biosketches for gaps before submission\n\n## Core concepts\n\n- **The confidence question:** every element should build the case that you have the skills, track record, and resources for this specific project — generic excellence is less persuasive than specific fit.\n- **Personal statement as narrative:** 1 paragraph connecting your background to the proposed work — not a CV summary, a story: \"My lab developed X (refs), which positions us to do Y proposed here because Z.\"\n- **Contributions, not publications:** the \"Contributions to Science\" section wants 3–5 thematic contributions with your role made explicit — what you discovered\u002Fbuilt, why it mattered, with 3–4 key citations each.\n- **Role clarity:** \"led\", \"co-led\", \"developed the method\", \"supervised\" — reviewers discount middle-author papers without stated roles; claim your actual contribution precisely.\n- **Team completeness:** the set of biosketches must cover every method in the proposal — a missing expertise area is a feasibility ding; add collaborators or consultants to fill gaps deliberately.\n- **Honesty constraints:** no embellishment of roles, no double-counting, complete other support (overlap disclosure) — biosketch misrepresentation is misconduct territory, not marketing.\n\n- **The personal statement as narrative:** connect the dots — \"my work on X led to Y, which positions me to do Z in this proposal\" — not a list of positions; reviewers remember stories, not CVs.\n- **Contributions over publications:** the contributions section should show a trajectory of solving increasingly important problems — five disconnected papers read as five disconnected ideas.\n- **Synergistic activities:** service, mentoring, software, datasets, and community resources count — especially for early-career applicants, they show you're building the field, not just publishing in it.\n\n## Practical workflow\n\n### 1. Draft the personal statement\n\n1. Open with your relevant expertise in one sentence; connect 2–3 past achievements to the proposed work's specific demands.\n2. Name the unique assets you bring: methods you pioneered, datasets you control, collaborations you hold.\n3. For early-career: emphasize training, first-author work, and the mentor\u002Fcollaborator network that de-risks the project — acknowledge the stage, then neutralize it.\n\n### 2. Write contributions as stories\n\n1. Pick 4–5 contributions that collectively cover the proposal's methods — each with: the problem, what you did (your role explicit), the outcome\u002Fimpact, 3–4 citations.\n2. Order by relevance to this proposal, not chronology — the reviewer reads for fit.\n3. Include a methods\u002Ftool contribution if the proposal leans on your technical innovation — \"I built the instrument this project runs on\" is powerful.\n\n### 3. Assemble the supporting sections\n\n1. **Positions and honors:** reverse chronological, complete — gaps invite questions; explain career breaks briefly and factually if needed.\n2. **Publications:** selected, relevant, with your role clear — quality and relevance beat quantity; don't pad with unrelated papers.\n3. **Research support:** ongoing and completed (recent 3 years typically) — show it's related but not overlapping; disclose overlaps explicitly with explanations of distinct aims.\n\n### 4. Review as a team\n\n1. Lay all key-personnel biosketches side by side: does every proposed method have a named expert? Fill gaps with collaborators now, not after review.\n2. Check consistency: effort levels match the budget; roles match the narrative's description of who does what.\n3. Update or perish: a biosketch more than a year old signals staleness — refresh contributions and support every submission.\n\n### 5. Tailor the biosketch to the proposal\n\n1. Reorder contributions to lead with the work most relevant to this proposal — relevance beats chronology.\n2. In the personal statement, name the specific expertise each aim requires and map it to your (or the team's) track record — leave no aim's feasibility to implication.\n3. For team proposals, ensure complementary — not overlapping — expertise across biosketches; redundancy wastes space that could cover gaps.\n\n### 6. Quick-reference checklist\n\n- [ ] Personal statement tells the story: X → Y → positions me for Z\n- [ ] Contributions ordered by relevance to this proposal\n- [ ] Track record mapped explicitly to each aim's required expertise\n- [ ] Statement tailored to this proposal (not a generic swap)\n- [ ] Synergistic activities show field-building, not just publishing\n- [ ] Complementary (not overlapping) expertise across team biosketches\n- [ ] Roles clarified on large consortium papers\n- [ ] Current format requirements of the funder followed\n\n## Common pitfalls\n\n- **Generic personal statements:** \"Dr. X is an expert in Y with 50 publications\" — says nothing about fit to this project; rewrite as a targeted narrative.\n- **Contribution vagueness:** listing papers without stating what you contributed — reviewers can't credit what they can't see.\n- **Padding:** unrelated publications, honorary authorships presented as leadership — dilutes the real signal.\n- **Missing expertise:** proposing single-cell\u002Fspatial\u002FAI methods with no team member who's done them — the #1 feasibility killer.\n- **Stale biosketches:** 3-year-old support sections, missing recent key papers — suggests the application was assembled carelessly.\n- **Overlap blindness:** undisclosed scientific\u002Fbudgetary overlap across grants — disclose and differentiate proactively.\n- **The generic personal statement:** one statement reused across five proposals with the title swapped — reviewers can tell; tailor it.\n- **Padding with minor roles:** listing large consortium papers where your role was peripheral without clarifying — it dilutes the real contributions; be honest about roles.\n","## Overview\n\nThe biosketch answers the reviewer's unspoken question: \"Can this team\nactually do this work?\" This skill covers the NIH-style biosketch\n(personal statement, positions, contributions to science, support),\nwriting contribution narratives that show trajectory rather than list\npapers, and positioning yourself honestly for the proposed project.\n\n## When to use\n\n- Writing or updating an NIH\u002FNSF biosketch for a proposal\n- Crafting the personal statement to connect your history to this project\n- Selecting which contributions and publications to highlight\n- Positioning early-career investigators (and addressing thin track records)\n- Reviewing a team's biosketches for gaps before submission\n\n## Core concepts\n\n- **The confidence question:** every element should build the case that you have the skills, track record, and resources for this specific project — generic excellence is less persuasive than specific fit.\n- **Personal statement as narrative:** 1 paragraph connecting your background to the proposed work — not a CV summary, a story: \"My lab developed X (refs), which positions us to do Y proposed here because Z.\"\n- **Contributions, not publications:** the \"Contributions to Science\" section wants 3–5 thematic contributions with your role made explicit — what you discovered\u002Fbuilt, why it mattered, with 3–4 key citations each.\n- **Role clarity:** \"led\", \"co-led\", \"developed the method\", \"supervised\" — reviewers discount middle-author papers without stated roles; claim your actual contribution precisely.\n- **Team completeness:** the set of biosketches must cover every method in the proposal — a missing expertise area is a feasibility ding; add collaborators or consultants to fill gaps deliberately.\n- **Honesty constraints:** no embellishment of roles, no double-counting, complete other support (overlap disclosure) — biosketch misrepresentation is misconduct territory, not marketing.\n\n- **The personal statement as narrative:** connect the dots — \"my work on X led to Y, which positions me to do Z in this proposal\" — not a list of positions; reviewers remember stories, not CVs.\n- **Contributions over publications:** the contributions section should show a trajectory of solving increasingly important problems — five disconnected papers read as five disconnected ideas.\n- **Synergistic activities:** service, mentoring, software, datasets, and community resources count — especially for early-career applicants, they show you're building the field, not just publishing in it.\n\n## Practical workflow\n\n### 1. Draft the personal statement\n\n1. Open with your relevant expertise in one sentence; connect 2–3 past achievements to the proposed work's specific demands.\n2. Name the unique assets you bring: methods you pioneered, datasets you control, collaborations you hold.\n3. For early-career: emphasize training, first-author work, and the mentor\u002Fcollaborator network that de-risks the project — acknowledge the stage, then neutralize it.\n\n### 2. Write contributions as stories\n\n1. Pick 4–5 contributions that collectively cover the proposal's methods — each with: the problem, what you did (your role explicit), the outcome\u002Fimpact, 3–4 citations.\n2. Order by relevance to this proposal, not chronology — the reviewer reads for fit.\n3. Include a methods\u002Ftool contribution if the proposal leans on your technical innovation — \"I built the instrument this project runs on\" is powerful.\n\n### 3. Assemble the supporting sections\n\n1. **Positions and honors:** reverse chronological, complete — gaps invite questions; explain career breaks briefly and factually if needed.\n2. **Publications:** selected, relevant, with your role clear — quality and relevance beat quantity; don't pad with unrelated papers.\n3. **Research support:** ongoing and completed (recent 3 years typically) — show it's related but not overlapping; disclose overlaps explicitly with explanations of distinct aims.\n\n### 4. Review as a team\n\n1. Lay all key-personnel biosketches side by side: does every proposed method have a named expert? Fill gaps with collaborators now, not after review.\n2. Check consistency: effort levels match the budget; roles match the narrative's description of who does what.\n3. Update or perish: a biosketch more than a year old signals staleness — refresh contributions and support every submission.\n\n### 5. Tailor the biosketch to the proposal\n\n1. Reorder contributions to lead with the work most relevant to this proposal — relevance beats chronology.\n2. In the personal statement, name the specific expertise each aim requires and map it to your (or the team's) track record — leave no aim's feasibility to implication.\n3. For team proposals, ensure complementary — not overlapping — expertise across biosketches; redundancy wastes space that could cover gaps.\n\n### 6. Quick-reference checklist\n\n- [ ] Personal statement tells the story: X → Y → positions me for Z\n- [ ] Contributions ordered by relevance to this proposal\n- [ ] Track record mapped explicitly to each aim's required expertise\n- [ ] Statement tailored to this proposal (not a generic swap)\n- [ ] Synergistic activities show field-building, not just publishing\n- [ ] Complementary (not overlapping) expertise across team biosketches\n- [ ] Roles clarified on large consortium papers\n- [ ] Current format requirements of the funder followed\n\n## Common pitfalls\n\n- **Generic personal statements:** \"Dr. X is an expert in Y with 50 publications\" — says nothing about fit to this project; rewrite as a targeted narrative.\n- **Contribution vagueness:** listing papers without stating what you contributed — reviewers can't credit what they can't see.\n- **Padding:** unrelated publications, honorary authorships presented as leadership — dilutes the real signal.\n- **Missing expertise:** proposing single-cell\u002Fspatial\u002FAI methods with no team member who's done them — the #1 feasibility killer.\n- **Stale biosketches:** 3-year-old support sections, missing recent key papers — suggests the application was assembled carelessly.\n- **Overlap blindness:** undisclosed scientific\u002Fbudgetary overlap across grants — disclose and differentiate proactively.\n- **The generic personal statement:** one statement reused across five proposals with the title swapped — reviewers can tell; tailor it.\n- **Padding with minor roles:** listing large consortium papers where your role was peripheral without clarifying — it dilutes the real contributions; be honest about roles.\n",{"name":5,"category":24,"description":7},"scientific","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-biosketch-craft",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill biosketch-craft",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill biosketch-craft",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill biosketch-craft","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-biosketch-craft\u002FSKILL.md",true,[],[48,55,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]