[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EMHVHDTMH4JHRRPKF36MSX":3,"skill-same:01M7EMHVHDTMH4JHRRPKF36MSX":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},"01M7EMHVHDTMH4JHRRPKF36MSX","citation-manager",null,"Manage citations and references — collecting sources, organizing libraries, formatting bibliographies, and keeping reference integrity. Use when writing anything that cites sources.","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-citation-manager\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: citation-manager\ndescription: Manage citations and references — collecting sources, organizing libraries, formatting bibliographies, and keeping reference integrity. Use when writing anything that cites sources.\ncategory: ai-research\n---\n\n# Citation Manager\n\nCitations are the paper's supply chain: every claim traceable to its source. Managing them means \ncollecting sources systematically, organizing them so you can find anything, formatting \nconsistently, and — critically — verifying that every citation is real and says what you claim.\n\n## Overview\n\nThe workflow: capture sources as you read (never \"I'll find it later\"), store them with notes on \nwhy they matter, cite-while-you-write with keys instead of hand-typed references, and generate the \nbibliography from the library. The integrity rule: every in-text citation matches a real source \nyou've read, and every bibliography entry is cited. Reference managers automate formatting; they \ndon't automate honesty.\n\n## When to use\n\n- Writing papers, theses, reports, or any document with references.\n- Building a personal research library over time.\n- Collaborating: shared libraries keep everyone's citations consistent.\n- Cleaning up a manuscript's references before submission.\n\n## Core concepts\n\n- **Capture at reading time**: save the full citation + PDF + your notes the moment you read \nsomething useful. \"I'll relocate it later\" fails reliably.\n- **Cite keys**: stable keys (`smith2024attention`) used in drafts; the formatted reference is \ngenerated, never hand-typed. Renumbering-proof.\n- **Annotated library**: each entry with a one-line note — what it claims, why you cited it. \nFuture you will thank present you.\n- **Style consistency**: one citation style per document (APA, IEEE, Chicago…), applied by the \ntool, not by hand. Switching styles should be one setting.\n- **Reference integrity**: every citation verified — the source exists, you read the relevant \npart, it supports your claim. AI-generated citations must be checked individually.\n- **Deduplication**: the same source saved three ways creates triple entries. Merge duplicates; \nkeep one canonical record.\n\n## Practical workflow\n\n1. Set up the library before writing: folder structure or tags by project\u002Ftopic.\n2. For each source read: save citation metadata, the file, and a 2-line note (claim + relevance).\n3. Write with cite keys; never type a formatted reference by hand.\n4. Before submission: run the integrity check — every key resolves, every entry is cited, no \nduplicates, style consistent.\n5. Verify AI-suggested citations individually: confirm the source exists and supports the claim.\n6. Archive the library with the manuscript version so the reference set is reproducible.\n\n```text\nSource note template:\nKEY:   smith2024attention\nCLAIM: \u003Cwhat the paper shows, in your words>\nUSE:   \u003Cwhy you're citing it — which argument it supports>\nREAD:  \u003Cwhich sections you actually read>\nLIMIT: \u003Ccaveats relevant to your use>\n```\n\n## Common pitfalls\n\n- **Phantom citations**: references that don't exist — the classic AI failure mode. Verify every \nsingle one.\n- **Citation without reading**: citing the abstract or a citation-of-a-citation. Read the part you \nrely on.\n- **Hand-formatted references**: typed bibliographies that break on every edit. Generate from keys.\n- **No notes**: a library of 500 PDFs with no memory of why each mattered. Annotate at capture time.\n- **Style drift**: mixed formats in one document. Set the style once; let the tool enforce it.\n- **Uncited bibliography entries**: sources in the list that nothing cites (or claims nothing \nsupports). Audit both directions.\n","# Citation Manager\n\nCitations are the paper's supply chain: every claim traceable to its source. Managing them means \ncollecting sources systematically, organizing them so you can find anything, formatting \nconsistently, and — critically — verifying that every citation is real and says what you claim.\n\n## Overview\n\nThe workflow: capture sources as you read (never \"I'll find it later\"), store them with notes on \nwhy they matter, cite-while-you-write with keys instead of hand-typed references, and generate the \nbibliography from the library. The integrity rule: every in-text citation matches a real source \nyou've read, and every bibliography entry is cited. Reference managers automate formatting; they \ndon't automate honesty.\n\n## When to use\n\n- Writing papers, theses, reports, or any document with references.\n- Building a personal research library over time.\n- Collaborating: shared libraries keep everyone's citations consistent.\n- Cleaning up a manuscript's references before submission.\n\n## Core concepts\n\n- **Capture at reading time**: save the full citation + PDF + your notes the moment you read \nsomething useful. \"I'll relocate it later\" fails reliably.\n- **Cite keys**: stable keys (`smith2024attention`) used in drafts; the formatted reference is \ngenerated, never hand-typed. Renumbering-proof.\n- **Annotated library**: each entry with a one-line note — what it claims, why you cited it. \nFuture you will thank present you.\n- **Style consistency**: one citation style per document (APA, IEEE, Chicago…), applied by the \ntool, not by hand. Switching styles should be one setting.\n- **Reference integrity**: every citation verified — the source exists, you read the relevant \npart, it supports your claim. AI-generated citations must be checked individually.\n- **Deduplication**: the same source saved three ways creates triple entries. Merge duplicates; \nkeep one canonical record.\n\n## Practical workflow\n\n1. Set up the library before writing: folder structure or tags by project\u002Ftopic.\n2. For each source read: save citation metadata, the file, and a 2-line note (claim + relevance).\n3. Write with cite keys; never type a formatted reference by hand.\n4. Before submission: run the integrity check — every key resolves, every entry is cited, no \nduplicates, style consistent.\n5. Verify AI-suggested citations individually: confirm the source exists and supports the claim.\n6. Archive the library with the manuscript version so the reference set is reproducible.\n\n```text\nSource note template:\nKEY:   smith2024attention\nCLAIM: \u003Cwhat the paper shows, in your words>\nUSE:   \u003Cwhy you're citing it — which argument it supports>\nREAD:  \u003Cwhich sections you actually read>\nLIMIT: \u003Ccaveats relevant to your use>\n```\n\n## Common pitfalls\n\n- **Phantom citations**: references that don't exist — the classic AI failure mode. Verify every \nsingle one.\n- **Citation without reading**: citing the abstract or a citation-of-a-citation. Read the part you \nrely on.\n- **Hand-formatted references**: typed bibliographies that break on every edit. Generate from keys.\n- **No notes**: a library of 500 PDFs with no memory of why each mattered. Annotate at capture time.\n- **Style drift**: mixed formats in one document. Set the style once; let the tool enforce it.\n- **Uncited bibliography entries**: sources in the list that nothing cites (or claims nothing \nsupports). Audit both directions.\n",{"name":5,"category":24,"description":7},"ai-research","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-citation-manager",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 citation-manager",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill citation-manager",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill citation-manager","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-citation-manager\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",[],[]]