[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVRCDPZXR93SR98C58YPFJ":3,"skill-same:01M7EVRCDPZXR93SR98C58YPFJ":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},"01M7EVRCDPZXR93SR98C58YPFJ","research-paper-writer",null,"Write academic papers with AI assistance — outlining, drafting sections, tightening arguments, managing citations, and responding to reviewers. Use when turning research into a publishable manuscript.","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-research-paper-writer\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: research-paper-writer\ndescription: Write academic papers with AI assistance — outlining, drafting sections, tightening arguments, managing citations, and responding to reviewers. Use when turning research into a publishable manuscript.\ncategory: ai-research\n---\n\n# Research Paper Writer\n\nWriting a paper is engineering an argument: the claim, the evidence, and the story that connects \nthem. AI assistance helps at every stage — but the researcher owns the argument, the evidence, \nand the honesty.\n\n## Overview\n\nWork section by section, not front to back. Start with the figures and results — the paper's \nskeleton. Write the methods from your lab notes while they're fresh. Draft the introduction last, \nwhen you know what story the results actually tell. Use AI for outlining, drafting, tightening \nprose, and checking consistency — never for inventing results, citations, or related work you \nhaven't read.\n\n## When to use\n\n- Turning completed research into a conference or journal manuscript.\n- Structuring a messy set of results into a coherent narrative.\n- Revising: tightening prose, fixing flow, responding to reviewers.\n- Writing related work honestly from papers you've actually read.\n\n## Core concepts\n\n- **Argument first**: one central claim per paper, supported by 2–4 sub-claims each tied to \nevidence. If you can't state the claim in one sentence, you're not ready to write.\n- **Results-driven structure**: figures and tables first; the text explains what the reader sees. \nWrite captions that stand alone.\n- **Methods reproducibility**: enough detail for an expert to replicate — parameters, data \nversions, code links. Written from notes, not memory.\n- **Honest related work**: cite what you read, characterize it fairly, position your contribution \nprecisely. No strawmen, no citation padding.\n- **Reviewer response**: address every comment — agree and change, or disagree with evidence. \nNever ignore; never be dismissive.\n- **Integrity boundaries**: AI drafts prose; humans verify every claim, number, and citation. \nFabricated references are career-ending — check each one.\n\n## Practical workflow\n\n1. State the one-sentence claim and list the evidence for each sub-claim. Cut results that don't \nserve the claim (save them for the next paper).\n2. Build figures and tables; write standalone captions.\n3. Outline section by section: the point of each paragraph in one line. Get feedback on the outline \nbefore drafting.\n4. Draft methods from lab notes; results describing the figures; discussion interpreting honestly \n— including what didn't work.\n5. Write the introduction last: the problem, why it matters, what you did, what you found — in \nthat order.\n6. Revise in passes: argument → structure → clarity → precision → proofread. Use AI for \ntightening, then verify every edit preserved meaning.\n\n```text\nRevision passes (one at a time):\n1. ARGUMENT:  does every section serve the central claim?\n2. STRUCTURE: does the order build the case logically?\n3. CLARITY:   would a non-specialist follow the story?\n4. PRECISION: are claims hedged correctly, numbers exact?\n5. PROOFREAD: grammar, formatting, reference integrity\n```\n\n## Common pitfalls\n\n- **Writing before the argument is clear**: drafting to discover what you think. Outline first; the \noutline is where thinking happens.\n- **AI-invented citations**: models fabricate plausible references. Verify every citation exists \nand says what you claim.\n- **Burying limitations**: hiding weaknesses reviewers will find anyway. State them; frame what \nthey imply for future work.\n- **Introduction first**: writing the intro before results are final produces fiction. Results \nfirst, intro last.\n- **Ignoring the rebuttal**: defensive or dismissive reviewer responses. Engage each point \nsubstantively — reviewers are doing you a favor.\n- **Salami slicing**: splitting one contribution across papers. One paper, one clear contribution, \nfully evidenced.\n","# Research Paper Writer\n\nWriting a paper is engineering an argument: the claim, the evidence, and the story that connects \nthem. AI assistance helps at every stage — but the researcher owns the argument, the evidence, \nand the honesty.\n\n## Overview\n\nWork section by section, not front to back. Start with the figures and results — the paper's \nskeleton. Write the methods from your lab notes while they're fresh. Draft the introduction last, \nwhen you know what story the results actually tell. Use AI for outlining, drafting, tightening \nprose, and checking consistency — never for inventing results, citations, or related work you \nhaven't read.\n\n## When to use\n\n- Turning completed research into a conference or journal manuscript.\n- Structuring a messy set of results into a coherent narrative.\n- Revising: tightening prose, fixing flow, responding to reviewers.\n- Writing related work honestly from papers you've actually read.\n\n## Core concepts\n\n- **Argument first**: one central claim per paper, supported by 2–4 sub-claims each tied to \nevidence. If you can't state the claim in one sentence, you're not ready to write.\n- **Results-driven structure**: figures and tables first; the text explains what the reader sees. \nWrite captions that stand alone.\n- **Methods reproducibility**: enough detail for an expert to replicate — parameters, data \nversions, code links. Written from notes, not memory.\n- **Honest related work**: cite what you read, characterize it fairly, position your contribution \nprecisely. No strawmen, no citation padding.\n- **Reviewer response**: address every comment — agree and change, or disagree with evidence. \nNever ignore; never be dismissive.\n- **Integrity boundaries**: AI drafts prose; humans verify every claim, number, and citation. \nFabricated references are career-ending — check each one.\n\n## Practical workflow\n\n1. State the one-sentence claim and list the evidence for each sub-claim. Cut results that don't \nserve the claim (save them for the next paper).\n2. Build figures and tables; write standalone captions.\n3. Outline section by section: the point of each paragraph in one line. Get feedback on the outline \nbefore drafting.\n4. Draft methods from lab notes; results describing the figures; discussion interpreting honestly \n— including what didn't work.\n5. Write the introduction last: the problem, why it matters, what you did, what you found — in \nthat order.\n6. Revise in passes: argument → structure → clarity → precision → proofread. Use AI for \ntightening, then verify every edit preserved meaning.\n\n```text\nRevision passes (one at a time):\n1. ARGUMENT:  does every section serve the central claim?\n2. STRUCTURE: does the order build the case logically?\n3. CLARITY:   would a non-specialist follow the story?\n4. PRECISION: are claims hedged correctly, numbers exact?\n5. PROOFREAD: grammar, formatting, reference integrity\n```\n\n## Common pitfalls\n\n- **Writing before the argument is clear**: drafting to discover what you think. Outline first; the \noutline is where thinking happens.\n- **AI-invented citations**: models fabricate plausible references. Verify every citation exists \nand says what you claim.\n- **Burying limitations**: hiding weaknesses reviewers will find anyway. State them; frame what \nthey imply for future work.\n- **Introduction first**: writing the intro before results are final produces fiction. Results \nfirst, intro last.\n- **Ignoring the rebuttal**: defensive or dismissive reviewer responses. Engage each point \nsubstantively — reviewers are doing you a favor.\n- **Salami slicing**: splitting one contribution across papers. One paper, one clear contribution, \nfully evidenced.\n",{"name":5,"category":24,"description":7},"ai-research","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-research-paper-writer",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 research-paper-writer",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill research-paper-writer",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill research-paper-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-research-paper-writer\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",[],[]]