[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EWFFMB4HXNFDYRBJ0NREAT":3,"skill-same:01M7EWFFMB4HXNFDYRBJ0NREAT":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EWFFMB4HXNFDYRBJ0NREAT","ams-yeet",null,"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-yeet\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: yeet\ndescription: Ship fast with throwaway automation: quick scripts and one-off automations built in minutes, used, then discarded. Use when a small annoying task needs doing now, not a system designed.\ncategory: workflow-automation\n---\n\n# Yeet\n\n## Overview\n\nYeet is the discipline of fast, disposable automation: a 20-line script written in 15 minutes that saves hours this week — then gets deleted without ceremony.\n\nNot every automation deserves architecture. Some tasks need doing once, urgently, and perfectly is the enemy of done.\n\nThe yeet mindset: bias to action, timeboxed effort, good-enough correctness, and zero guilt about deleting it after.\n\n## When to use\n\n- A one-off data cleanup or migration needed today\n- Repetitive task you'll do 50 times this week then never again\n- Prototyping an automation before building it properly\n- Quick personal productivity hacks\n- When 'proper solution' estimates say 2 weeks and you need it now\n\n## Core concepts\n\n- **Timebox the build.**\n  15-60 minutes max. If it takes longer, it's not a yeet — it's a project. Set a timer; ship or stop.\n- **Good-enough correctness.**\n  Handle the 95% case visibly; log or skip the edge cases. A yeet that handles everything is just slow engineering.\n- **Read-only first.**\n  Prefer scripts that read and report over scripts that write. When writing: dry-run mode, backups, and a revert plan.\n- **Disposable by design.**\n  One file, inline config, minimal dependencies. If it needs a README and tests, it's graduated beyond yeet.\n- **The 3x rule.**\n  Yeet when: time to build \u003C (time saved \u002F 3). Rough math keeps you from gold-plating throwaways.\n- **Know when to graduate.**\n  Used three times? Promoted to a real script with error handling. Used by others? Now it's a tool with docs. Yeets have lifecycles.\n- **Delete without ceremony.**\n  Task done, yeet served its purpose: delete it. A graveyard of one-off scripts becomes unmaintainable clutter.\n- **Log what it did.**\n  Even throwaways should print what they changed. Future debugging (including 'what did that script do?') needs the trail.\n\n## Practical workflow\n\n1. **Identify the annoyance.**\n   What's the concrete, painful, repetitive thing? Name it in one sentence. Vague annoyances make vague scripts.\n2. **Timebox it.**\n   Decide upfront: 20 minutes? An hour? The box is the discipline — it forces the simple solution.\n3. **Write the smallest script.**\n   One file, standard library preferred, hardcoded values fine. Read the data, do the thing, print results.\n4. **Dry-run first.**\n   If it writes\u002Fdeletes: preview mode showing what would happen. Review the preview. Then run for real.\n5. **Run and verify.**\n   Check the output actually fixed the problem. Spot-check results; yeets earn trust through verification, not ceremony.\n6. **Decide: keep or delete.**\n   One-off done? Delete. Recurring? Graduate it (error handling, config, docs) or schedule the next yeet.\n7. **Note the pattern.**\n   Yeeted the same class of task twice? That's a signal — the third time, build it properly.\n8. **Share the trick.**\n   A yeet that helped you might help the team. Share the snippet; let usefulness decide if it graduates.\n\n## Common pitfalls\n\n- **Yeeting the irreversible.**\n  Throwaway scripts doing bulk deletes without dry-run or backup. Speed doesn't excuse recklessness with destructive ops.\n- **No timebox.**\n  'Quick script' becoming a 3-day project. The timebox is what makes it a yeet; without it, it's just sloppy engineering.\n- **Keeping every yeet.**\n  200 throwaway scripts in ~\u002Fscripts, none documented. Delete on completion or graduate deliberately.\n- **Yeeting the recurring.**\n  Manually re-running a 'one-off' script weekly for a year. Third use = graduate it properly.\n- **No verification.**\n  Assuming the script worked. Spot-check output — yeets are fast, not infallible.\n- **Secrets in throwaways.**\n  API keys pasted into quick scripts, then the script gets shared or committed. Even yeets use env vars.\n- **Yeeting what should be a product.**\n  Customer-facing or team-critical workflows built as throwaways. Yeets are for internal, reversible, timeboxed needs.\n- **Analysis paralysis.**\n  Spending an hour deciding whether to yeet. The whole point is speed — if the 3x rule says yes, start typing.\n","# Yeet\n\n## Overview\n\nYeet is the discipline of fast, disposable automation: a 20-line script written in 15 minutes that saves hours this week — then gets deleted without ceremony.\n\nNot every automation deserves architecture. Some tasks need doing once, urgently, and perfectly is the enemy of done.\n\nThe yeet mindset: bias to action, timeboxed effort, good-enough correctness, and zero guilt about deleting it after.\n\n## When to use\n\n- A one-off data cleanup or migration needed today\n- Repetitive task you'll do 50 times this week then never again\n- Prototyping an automation before building it properly\n- Quick personal productivity hacks\n- When 'proper solution' estimates say 2 weeks and you need it now\n\n## Core concepts\n\n- **Timebox the build.**\n  15-60 minutes max. If it takes longer, it's not a yeet — it's a project. Set a timer; ship or stop.\n- **Good-enough correctness.**\n  Handle the 95% case visibly; log or skip the edge cases. A yeet that handles everything is just slow engineering.\n- **Read-only first.**\n  Prefer scripts that read and report over scripts that write. When writing: dry-run mode, backups, and a revert plan.\n- **Disposable by design.**\n  One file, inline config, minimal dependencies. If it needs a README and tests, it's graduated beyond yeet.\n- **The 3x rule.**\n  Yeet when: time to build \u003C (time saved \u002F 3). Rough math keeps you from gold-plating throwaways.\n- **Know when to graduate.**\n  Used three times? Promoted to a real script with error handling. Used by others? Now it's a tool with docs. Yeets have lifecycles.\n- **Delete without ceremony.**\n  Task done, yeet served its purpose: delete it. A graveyard of one-off scripts becomes unmaintainable clutter.\n- **Log what it did.**\n  Even throwaways should print what they changed. Future debugging (including 'what did that script do?') needs the trail.\n\n## Practical workflow\n\n1. **Identify the annoyance.**\n   What's the concrete, painful, repetitive thing? Name it in one sentence. Vague annoyances make vague scripts.\n2. **Timebox it.**\n   Decide upfront: 20 minutes? An hour? The box is the discipline — it forces the simple solution.\n3. **Write the smallest script.**\n   One file, standard library preferred, hardcoded values fine. Read the data, do the thing, print results.\n4. **Dry-run first.**\n   If it writes\u002Fdeletes: preview mode showing what would happen. Review the preview. Then run for real.\n5. **Run and verify.**\n   Check the output actually fixed the problem. Spot-check results; yeets earn trust through verification, not ceremony.\n6. **Decide: keep or delete.**\n   One-off done? Delete. Recurring? Graduate it (error handling, config, docs) or schedule the next yeet.\n7. **Note the pattern.**\n   Yeeted the same class of task twice? That's a signal — the third time, build it properly.\n8. **Share the trick.**\n   A yeet that helped you might help the team. Share the snippet; let usefulness decide if it graduates.\n\n## Common pitfalls\n\n- **Yeeting the irreversible.**\n  Throwaway scripts doing bulk deletes without dry-run or backup. Speed doesn't excuse recklessness with destructive ops.\n- **No timebox.**\n  'Quick script' becoming a 3-day project. The timebox is what makes it a yeet; without it, it's just sloppy engineering.\n- **Keeping every yeet.**\n  200 throwaway scripts in ~\u002Fscripts, none documented. Delete on completion or graduate deliberately.\n- **Yeeting the recurring.**\n  Manually re-running a 'one-off' script weekly for a year. Third use = graduate it properly.\n- **No verification.**\n  Assuming the script worked. Spot-check output — yeets are fast, not infallible.\n- **Secrets in throwaways.**\n  API keys pasted into quick scripts, then the script gets shared or committed. Even yeets use env vars.\n- **Yeeting what should be a product.**\n  Customer-facing or team-critical workflows built as throwaways. Yeets are for internal, reversible, timeboxed needs.\n- **Analysis paralysis.**\n  Spending an hour deciding whether to yeet. The whole point is speed — if the 3x rule says yes, start typing.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-yeet",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-yeet",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-yeet",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-yeet","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-yeet\u002FSKILL.md",true,[],[46,53,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"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":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"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":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"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":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"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":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"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":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"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",[],[]]