[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EWA1PFTV53YKAR9MTSKP05":3,"skill-same:01M7EWA1PFTV53YKAR9MTSKP05":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},"01M7EWA1PFTV53YKAR9MTSKP05","video-pro",null,"Handle professional video tasks with codecs, compression, aspect ratios, and delivery specifications.","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-video-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: video-pro\ndescription: Handle professional video tasks with codecs, compression, aspect ratios, and delivery specifications.\ncategory: media\n---\n\n## Overview\n\nVideo is the heaviest medium — technically and logistically. Professional video handling means\nunderstanding codecs and containers, compression tradeoffs, aspect ratios for each platform, and\ndelivery specs that prevent rejections. This skill covers the technical pipeline from ingest to\ndelivery, complementing the creative side of editing.\n\n## When to use\n\n- Choosing codecs, containers, and export settings\n\n- Compressing video for web, social, or streaming\n\n- Converting between formats and frame rates\n\n- Preparing deliverables to platform specs (YouTube, broadcast, client)\n\n- Troubleshooting playback, quality, or file-size issues\n\n## Core concepts\n\n- - **Codec vs container.** The container (MP4, MOV, MKV) is the wrapper; the codec (H.264,\n  H.265\u002FHEVC, VP9, AV1) is the compression. MP4 + H.264 is the universal delivery combo;\n  ProRes\u002FDNxHR are editing intermediates (huge files, no generation loss).\n- - **The quality triangle.** Quality, file size, encoding time — pick two. H.264 is fast and\n  universal; H.265 halves file sizes but encodes slower and plays on fewer old devices; AV1 is the\n  future but still heavy to encode.\n- - **Bitrate is the real control.** For delivery, target bitrate matters more than codec choice:\n  1080p YouTube ~8-12 Mbps, 4K ~35-45 Mbps. Constant quality (CRF 18-23 for H.264) beats fixed\n  bitrate for most uses — it spends bits where they're needed.\n- - **Frame rates and standards.** 24fps (cinematic), 30fps (US broadcast\u002Fsocial default), 25fps\n  (PAL regions), 60fps (sports, gaming, smooth motion). Match the delivery spec; converting frame\n  rates introduces judder or requires interpolation.\n- - **Aspect ratios per platform.** 16:9 (YouTube, landscape), 9:16 (Reels\u002FShorts\u002FTikTok), 1:1 (feed\n  posts), 4:5 (Instagram portrait). Shoot and frame for the primary ratio; reframe (don't just\n  crop-center) for others.\n- - **Masters and proxies.** Keep a high-quality master (ProRes\u002FDNxHR or high-bitrate H.264). Edit\n  with proxies (low-res stand-ins) for smooth timelines, relink to full-res for export. Never\n  deliver the proxy.\n\n## Practical workflow\n\n1. 1. **Know the delivery spec.** Platform, resolution, codec, max file size, aspect ratio, frame\n   rate, audio specs. YouTube, broadcasters, and clients all publish specs — read them before\n   exporting.\n2. 2. **Organize the ingest.** Consistent folder structure, descriptive filenames, backup originals\n   before any transcoding. Verify integrity of transferred files (spot-check playback, check\n   durations).\n3. 3. **Choose the editing codec.** Transcode camera originals to an edit-friendly intermediate\n   (ProRes LT\u002FProxy, DNxHR LB) if the camera codec is heavy (H.265, RAW). Generate proxies for 4K+\n   timelines.\n4. 4. **Export deliberately.** Match timeline settings to delivery: resolution, frame rate (no\n   unnecessary conversions), codec per spec, CRF or target bitrate per the quality needed. Two-pass\n   encoding for fixed-bitrate targets.\n5. 5. **Handle audio properly.** 48kHz sample rate standard for video, AAC 192-320 kbps for\n   delivery, loudness normalized (YouTube ~-14 LUFS, broadcast often -24 LUFS). Peaking audio is the\n   fastest way to sound amateur.\n6. 6. **QC the export.** Watch it through: start to finish, on the target device if possible. Check\n   audio sync, no dropped frames, correct aspect (no stretching\u002Fblack bars unless intended),\n   captions burned in or sidecar as required.\n7. 7. **Deliver and archive.** Named per client convention, with checksums for large transfers.\n   Archive the project file, masters, and exports — storage is cheap, reshoots aren't.\n\n## Common pitfalls\n\n- - **Wrong frame rate conversion.** 24fps timeline exported at 30fps (or vice versa) without proper\n  handling causes judder. Decide frame rate at project setup, not export.\n- - **Over-compression.** Starving the bitrate produces blocky mush, especially in dark scenes and\n  fast motion. When in doubt, raise the bitrate — storage is cheaper than reshoots.\n- - **Audio as afterthought.** Great video with clipping, humming, or wildly varying levels. Monitor\n  on headphones, normalize loudness, and never let peaks hit 0 dBFS.\n- - **Stretching aspect ratios.** Squished or stretched video from mismatched pixel aspect ratios.\n  Check: do circles look like circles? Fix with proper interpretation, not eyeballing.\n- - **No backup of camera originals.** Transcoding over the only copy, or deleting originals after\n  proxy creation. Originals are irreplaceable — archive before anything else.\n- - **Ignoring platform recompression.** Uploading a 50 Mbps file to a platform that recompresses to\n  8 Mbps anyway. Upload slightly above the platform's target quality — massive files just waste\n  upload time.\n","## Overview\n\nVideo is the heaviest medium — technically and logistically. Professional video handling means\nunderstanding codecs and containers, compression tradeoffs, aspect ratios for each platform, and\ndelivery specs that prevent rejections. This skill covers the technical pipeline from ingest to\ndelivery, complementing the creative side of editing.\n\n## When to use\n\n- Choosing codecs, containers, and export settings\n\n- Compressing video for web, social, or streaming\n\n- Converting between formats and frame rates\n\n- Preparing deliverables to platform specs (YouTube, broadcast, client)\n\n- Troubleshooting playback, quality, or file-size issues\n\n## Core concepts\n\n- - **Codec vs container.** The container (MP4, MOV, MKV) is the wrapper; the codec (H.264,\n  H.265\u002FHEVC, VP9, AV1) is the compression. MP4 + H.264 is the universal delivery combo;\n  ProRes\u002FDNxHR are editing intermediates (huge files, no generation loss).\n- - **The quality triangle.** Quality, file size, encoding time — pick two. H.264 is fast and\n  universal; H.265 halves file sizes but encodes slower and plays on fewer old devices; AV1 is the\n  future but still heavy to encode.\n- - **Bitrate is the real control.** For delivery, target bitrate matters more than codec choice:\n  1080p YouTube ~8-12 Mbps, 4K ~35-45 Mbps. Constant quality (CRF 18-23 for H.264) beats fixed\n  bitrate for most uses — it spends bits where they're needed.\n- - **Frame rates and standards.** 24fps (cinematic), 30fps (US broadcast\u002Fsocial default), 25fps\n  (PAL regions), 60fps (sports, gaming, smooth motion). Match the delivery spec; converting frame\n  rates introduces judder or requires interpolation.\n- - **Aspect ratios per platform.** 16:9 (YouTube, landscape), 9:16 (Reels\u002FShorts\u002FTikTok), 1:1 (feed\n  posts), 4:5 (Instagram portrait). Shoot and frame for the primary ratio; reframe (don't just\n  crop-center) for others.\n- - **Masters and proxies.** Keep a high-quality master (ProRes\u002FDNxHR or high-bitrate H.264). Edit\n  with proxies (low-res stand-ins) for smooth timelines, relink to full-res for export. Never\n  deliver the proxy.\n\n## Practical workflow\n\n1. 1. **Know the delivery spec.** Platform, resolution, codec, max file size, aspect ratio, frame\n   rate, audio specs. YouTube, broadcasters, and clients all publish specs — read them before\n   exporting.\n2. 2. **Organize the ingest.** Consistent folder structure, descriptive filenames, backup originals\n   before any transcoding. Verify integrity of transferred files (spot-check playback, check\n   durations).\n3. 3. **Choose the editing codec.** Transcode camera originals to an edit-friendly intermediate\n   (ProRes LT\u002FProxy, DNxHR LB) if the camera codec is heavy (H.265, RAW). Generate proxies for 4K+\n   timelines.\n4. 4. **Export deliberately.** Match timeline settings to delivery: resolution, frame rate (no\n   unnecessary conversions), codec per spec, CRF or target bitrate per the quality needed. Two-pass\n   encoding for fixed-bitrate targets.\n5. 5. **Handle audio properly.** 48kHz sample rate standard for video, AAC 192-320 kbps for\n   delivery, loudness normalized (YouTube ~-14 LUFS, broadcast often -24 LUFS). Peaking audio is the\n   fastest way to sound amateur.\n6. 6. **QC the export.** Watch it through: start to finish, on the target device if possible. Check\n   audio sync, no dropped frames, correct aspect (no stretching\u002Fblack bars unless intended),\n   captions burned in or sidecar as required.\n7. 7. **Deliver and archive.** Named per client convention, with checksums for large transfers.\n   Archive the project file, masters, and exports — storage is cheap, reshoots aren't.\n\n## Common pitfalls\n\n- - **Wrong frame rate conversion.** 24fps timeline exported at 30fps (or vice versa) without proper\n  handling causes judder. Decide frame rate at project setup, not export.\n- - **Over-compression.** Starving the bitrate produces blocky mush, especially in dark scenes and\n  fast motion. When in doubt, raise the bitrate — storage is cheaper than reshoots.\n- - **Audio as afterthought.** Great video with clipping, humming, or wildly varying levels. Monitor\n  on headphones, normalize loudness, and never let peaks hit 0 dBFS.\n- - **Stretching aspect ratios.** Squished or stretched video from mismatched pixel aspect ratios.\n  Check: do circles look like circles? Fix with proper interpretation, not eyeballing.\n- - **No backup of camera originals.** Transcoding over the only copy, or deleting originals after\n  proxy creation. Originals are irreplaceable — archive before anything else.\n- - **Ignoring platform recompression.** Uploading a 50 Mbps file to a platform that recompresses to\n  8 Mbps anyway. Upload slightly above the platform's target quality — massive files just waste\n  upload time.\n",{"name":5,"category":24,"description":7},"media","main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-video-pro",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 video-pro",{"tool":39,"command":40},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill video-pro",{"tool":42,"command":43},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill video-pro","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-video-pro\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",[],[]]