[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A82Y1BVWCT124V6HTZX2GV":3,"skill-same:01M7A82Y1BVWCT124V6HTZX2GV":48},{"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":26,"commitSha":27,"skillDirectory":28,"forksCount":14,"repositoryHtmlUrl":29,"repositoryHomepageUrl":6,"ownerHtmlUrl":30,"ownerBlogUrl":31,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M7A82Y1BVWCT124V6HTZX2GV","clean-copy",null,"Cut interface copy that shouldn't exist — captions that restate a label, hints that pre-empt a worry the user never had, warnings that are scar tissue from a fixed bug. Use when writing or reviewing any user-facing string (labels, hints, empty states, toasts, confirmations, button text), or when asked to clean up \u002F tighten copy.","nikhil-vytla\u002Fskills","nikhil-vytla","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F19198939?v=4","01M7A81BK9QTB61QN94WFR31MG","Nikhil Vytla","01M7A81BKZB6072KDJ81316N91",0,"MIT","https:\u002F\u002Fgithub.com\u002Fnikhil-vytla\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fexperimental\u002Fclean-copy\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: clean-copy\ndescription: Cut interface copy that shouldn't exist — captions that restate a label, hints that pre-empt a worry the user never had, warnings that are scar tissue from a fixed bug. Use when writing or reviewing any user-facing string (labels, hints, empty states, toasts, confirmations, button text), or when asked to clean up \u002F tighten copy.\nmetadata:\n  source: \"https:\u002F\u002Fpaste.rachel.systems\u002Fukogokijaz.md\"\n---\n\n# Cleaning copy\n\nMost bad copy isn't badly written. It's copy that shouldn't be on the screen. Editing it for\ntone just makes the wrong thing read better. So the first question is never \"how should this\nbe phrased\" — it's **should this exist**.\n\n## The ladder\n\nWalk a string down these in order. Stop at the first one that fires and delete.\n\n**1. Does this need to surface at all?**\nIs the thing being described something the user would ever have wondered about, unprompted? If\nthey'd never have thought to ask, you're not answering a question — you're planting one. Nobody\nopens an avatar cropper wondering whether the circle is a true circle. A caption reading \"the\npreview is rendered at the exact size used on your profile\" makes them wonder whether it might\nnot be.\n\n**2. Does the label need to exist?**\nA caption earns its place only when the value is meaningless without it. If the label, the\nfield, or the value beside it already says the thing, the caption is noise. A field labelled\n\"Retry limit\" does not need \"how many times we retry\" beneath it. A bare \"30\" does need\n\"seconds\" beside it — that one stays.\n\n**3. Is it pre-empting something the user would never have had to consider?**\nThe tell: copy that rules out a failure rather than describing a behaviour.\n\n> Cancel upload\n> *Always keeps the files already transferred — never wipes the folder like the old cancel did.*\n\nThat second clause exists because of a bug. The user doesn't know about the bug, doesn't share\nyour memory of fixing it, and now has a worry they arrived without. **The fix for a fixed bug\nis the fix. Not a caption about the fix.** Same for copy defending a design decision, or\nhedging about something that simply works: \"this may look slow but it is not\", \"don't worry if\nthe count seems off for a moment\".\n\n**4. Rewrite to remove the offending part. If nothing is left, delete the element.**\nDon't preserve a hint just because there was a hint there. An empty `hint` prop comes off the\ncomponent; an explanatory `\u003Cp>` gets deleted, not shortened to a stub.\n\n## What survives\n\nCopy stays when the user genuinely cannot act without it:\n\n- A real consequence at the moment of choosing. Under a destructive button: *\"Anything not yet\n  synced is lost.\"* They need it before they click, and they can't infer it.\n- A compatibility or scope fact they can't see. *\"Works with keys issued after March; older\n  keys need rotating first.\"* The checkbox alone doesn't tell them whether it applies to them.\n- What a blank state means and what to do next. *\"No projects yet. Create one and it will\n  appear here.\"*\n- Units, scale, or format on a bare value.\n\nNote the first example is one sentence. Had it continued *\"— only use this when a sync is\nstuck\"*, that half would go: it instructs the user on when they're allowed to press a button\nthey can already see. Keep the consequence, cut the permission slip.\n\n## Working style\n\n- Read the string next to what's actually on screen around it — the label, the value, the\n  button. Redundancy is invisible when you read the string alone.\n- Cut whole clauses, not words. Tightening \"Leave this blank to use the default setting for\n  your account\" into \"Leave blank for the default\" is a smaller win than noticing which half of\n  a two-sentence hint is doing no work.\n- When reviewing a batch, report as `file:line` with the current string and either the rewrite\n  or `cut` — and say in a few words which rung it failed. Don't rewrite copy that passes.\n- If a string is load-bearing but only in a rare state, consider whether it belongs in that\n  state rather than permanently on the page.\n","# Cleaning copy\n\nMost bad copy isn't badly written. It's copy that shouldn't be on the screen. Editing it for\ntone just makes the wrong thing read better. So the first question is never \"how should this\nbe phrased\" — it's **should this exist**.\n\n## The ladder\n\nWalk a string down these in order. Stop at the first one that fires and delete.\n\n**1. Does this need to surface at all?**\nIs the thing being described something the user would ever have wondered about, unprompted? If\nthey'd never have thought to ask, you're not answering a question — you're planting one. Nobody\nopens an avatar cropper wondering whether the circle is a true circle. A caption reading \"the\npreview is rendered at the exact size used on your profile\" makes them wonder whether it might\nnot be.\n\n**2. Does the label need to exist?**\nA caption earns its place only when the value is meaningless without it. If the label, the\nfield, or the value beside it already says the thing, the caption is noise. A field labelled\n\"Retry limit\" does not need \"how many times we retry\" beneath it. A bare \"30\" does need\n\"seconds\" beside it — that one stays.\n\n**3. Is it pre-empting something the user would never have had to consider?**\nThe tell: copy that rules out a failure rather than describing a behaviour.\n\n> Cancel upload\n> *Always keeps the files already transferred — never wipes the folder like the old cancel did.*\n\nThat second clause exists because of a bug. The user doesn't know about the bug, doesn't share\nyour memory of fixing it, and now has a worry they arrived without. **The fix for a fixed bug\nis the fix. Not a caption about the fix.** Same for copy defending a design decision, or\nhedging about something that simply works: \"this may look slow but it is not\", \"don't worry if\nthe count seems off for a moment\".\n\n**4. Rewrite to remove the offending part. If nothing is left, delete the element.**\nDon't preserve a hint just because there was a hint there. An empty `hint` prop comes off the\ncomponent; an explanatory `\u003Cp>` gets deleted, not shortened to a stub.\n\n## What survives\n\nCopy stays when the user genuinely cannot act without it:\n\n- A real consequence at the moment of choosing. Under a destructive button: *\"Anything not yet\n  synced is lost.\"* They need it before they click, and they can't infer it.\n- A compatibility or scope fact they can't see. *\"Works with keys issued after March; older\n  keys need rotating first.\"* The checkbox alone doesn't tell them whether it applies to them.\n- What a blank state means and what to do next. *\"No projects yet. Create one and it will\n  appear here.\"*\n- Units, scale, or format on a bare value.\n\nNote the first example is one sentence. Had it continued *\"— only use this when a sync is\nstuck\"*, that half would go: it instructs the user on when they're allowed to press a button\nthey can already see. Keep the consequence, cut the permission slip.\n\n## Working style\n\n- Read the string next to what's actually on screen around it — the label, the value, the\n  button. Redundancy is invisible when you read the string alone.\n- Cut whole clauses, not words. Tightening \"Leave this blank to use the default setting for\n  your account\" into \"Leave blank for the default\" is a smaller win than noticing which half of\n  a two-sentence hint is doing no work.\n- When reviewing a batch, report as `file:line` with the current string and either the rewrite\n  or `cut` — and say in a few words which rung it failed. Don't rewrite copy that passes.\n- If a string is load-bearing but only in a rare state, consider whether it belongs in that\n  state rather than permanently on the page.\n",{"name":5,"metadata":24,"description":7},{"source":25},"https:\u002F\u002Fpaste.rachel.systems\u002Fukogokijaz.md","main","1c4d5a73290d337d59d16c3794fdd6cdb011d575","skills\u002Fexperimental\u002Fclean-copy","https:\u002F\u002Fgithub.com\u002Fnikhil-vytla\u002Fskills","https:\u002F\u002Fgithub.com\u002Fnikhil-vytla","nikhilvytla.com","he\u002Fhim • multimodal agents @canva, ai @harvard, cs\u002Fstats @ unc • prev. @snowflakedb, @truera, @github, @aws, @ codeforequity","2026-10-05 04:22:50",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add nikhil-vytla\u002Fskills --skill clean-copy",{"tool":40,"command":41},"bunx","bunx skills add nikhil-vytla\u002Fskills --skill clean-copy",{"tool":43,"command":44},"pnpm","pnpm dlx skills add nikhil-vytla\u002Fskills --skill clean-copy","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnikhil-vytla\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fexperimental\u002Fclean-copy\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M7A83GMS0JFF05S34EJCA54E","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002Fnikhil-vytla\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fwriting-for-agents\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7A83BAWHMAWMMYBARBPEF18","unslop","Cut AI tells from any writing. Must always apply.","https:\u002F\u002Fgithub.com\u002Fnikhil-vytla\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Funslop\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},"01M7A8393JVTGP2N7G1ZZHSETF","show-me","Help the user understand the current topic visually with concise diagrams, code-shape sketches, and focused HTML artifacts.","https:\u002F\u002Fgithub.com\u002Fnikhil-vytla\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fshow-me\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},"01M7A836WE5GKD3VFTFPJXBZ2N","grilling","Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or uses any 'grill' trigger phrases.","https:\u002F\u002Fgithub.com\u002Fnikhil-vytla\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fgrilling\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},"01M7A835452XM9AE8EMB6JX1K7","grill-me","A relentless interview to sharpen a plan or design.","https:\u002F\u002Fgithub.com\u002Fnikhil-vytla\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fgrill-me\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},"01M7A833J2G38XH21XDZ4RQ2YW","bro","Restate the last message in plain human language, with no jargon.","https:\u002F\u002Fgithub.com\u002Fnikhil-vytla\u002Fskills\u002Fblob\u002Fmain\u002Fskills\u002Fproductivity\u002Fbro\u002FSKILL.md",[],[]]