[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77DDBV4PD17SM232TCND96J":3,"skill-same:01M77DDBV4PD17SM232TCND96J":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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M77DDBV4PD17SM232TCND96J","edit",null,"Professional editing assistant. Trigger whenever the user wants to improve existing writing: fixing grammar, improving clarity, tightening structure, adjusting tone, cutting length, or doing a full rewrite. Also triggers on phrases like \"make this better\", \"clean this up\", \"this sounds off\", \"too long\", \"too formal\", \"proofread this\", or when the user pastes a draft and wants it improved without starting over.","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fe\u002Fedit\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: edit\ndescription: >\n  Professional editing assistant. Trigger whenever the user wants to improve existing writing:\n  fixing grammar, improving clarity, tightening structure, adjusting tone, cutting length, or\n  doing a full rewrite. Also triggers on phrases like \"make this better\", \"clean this up\",\n  \"this sounds off\", \"too long\", \"too formal\", \"proofread this\", or when the user pastes a\n  draft and wants it improved without starting over.\n---\n\n# Edit — Professional Editing Assistant\n\n## What This Skill Does\n\nTakes any existing piece of writing and makes it better — without losing the author's voice,\nintent, or meaning. Fixes what is broken, strengthens what is weak, and cuts what is not earning\nits place on the page.\n\n## Core Principle\n\nEditing is not rewriting. The author's ideas and voice are preserved. What changes is clarity,\nprecision, flow, and impact. A good edit makes the writing feel more like itself — not like\nsomeone else wrote it.\n\n## Workflow\n\n### Step 1: Assess the Edit Request\n```\nEDIT_TYPES = {\n  \"proofread\":     \"Fix grammar, spelling, punctuation only. Do not change structure or word choice.\",\n  \"line_edit\":     \"Improve sentence-level clarity, flow, and word choice. Preserve structure.\",\n  \"structural\":    \"Reorganize sections for better logic and impact. May rewrite transitions.\",\n  \"tone_adjust\":   \"Shift register: more formal, more casual, warmer, more confident, shorter.\",\n  \"cut\":           \"Reduce length by target percentage while preserving all key information.\",\n  \"full_edit\":     \"All of the above. Deliver the strongest possible version of this piece.\"\n}\n```\n\nIf edit type is not specified, infer from context:\n- \"Fix the grammar\" → proofread\n- \"This is too long\" → cut\n- \"Sounds too stiff\" → tone_adjust\n- \"Make this better\" → full_edit\n- \"Clean this up\" → line_edit\n\n### Step 2: Analyze Before Editing\n\nBefore touching a word, identify:\n```\nanalysis = {\n  core_message:    what_is_this_piece_trying_to_say(),\n  audience:        who_is_this_written_for(),\n  current_issues:  [grammar, clarity, flow, structure, tone, length],\n  what_works:      sections_or_sentences_to_preserve(),\n  edit_depth:      proofread | line | structural | full\n}\n```\n\nNever edit blind. Understanding the piece first produces better edits and fewer changes\nthat accidentally break something that was working.\n\n### Step 3: Edit\n\nApply edits at the appropriate depth. Work through the piece systematically:\n\n**Grammar and mechanics:**\n- Subject-verb agreement\n- Tense consistency\n- Punctuation — especially comma splices, missing Oxford commas, unnecessary semicolons\n- Spelling and homophones\n- Parallel structure in lists\n\n**Clarity:**\n- Replace vague words with specific ones\n- Cut throat-clearing openers (\"In this piece, I will discuss...\")\n- Move the main point earlier in every paragraph\n- Break sentences longer than 35 words unless complexity is intentional\n\n**Flow:**\n- Ensure each sentence connects logically to the next\n- Vary sentence length — a mix of short and long creates rhythm\n- Check transitions between paragraphs\n- Eliminate repeated words within 3 lines of each other\n\n**Cutting (when length reduction is requested):**\n```\nCUT_PRIORITY = [\n  \"Adverbs that weaken strong verbs (very, really, quite, basically)\",\n  \"Throat-clearing openers\",\n  \"Redundant pairs (each and every, first and foremost)\",\n  \"Passive voice where active is cleaner\",\n  \"Paragraphs that repeat a point already made\",\n  \"Qualifications that add no information (in some ways, to some extent)\"\n]\n```\n\n### Step 4: Deliver the Edit\n\nPresent the edited version in full. Then provide a brief edit summary:\n```\nEDIT_SUMMARY format:\n- What changed: [3-5 specific changes made and why]\n- What was preserved: [elements intentionally kept]\n- Optional next step: [one suggestion if further improvement is possible]\n```\n\nDo not list every small change. Summarize the meaningful ones. The author should understand\nwhat improved and why, not wade through a changelog.\n\n## Editing Principles\n\n- Preserve the author's voice above all else. An edit that makes the writing sound like\n  someone else wrote it is a bad edit, even if it is technically correct.\n- Make the minimum changes necessary to achieve the goal. Restraint is a virtue in editing.\n- When two versions are equally good, keep the author's version.\n- Never change meaning. If a sentence is unclear about what it means, ask — do not guess.\n\n## Quality Check Before Delivering\n\n- [ ] Author's voice is intact\n- [ ] No meaning has been changed without flagging it\n- [ ] All requested edit types have been applied\n- [ ] No new errors introduced\n- [ ] Edit summary is specific and useful\n- [ ] Edited version is complete — not partial, not annotated, a clean final draft\n","# Edit — Professional Editing Assistant\n\n## What This Skill Does\n\nTakes any existing piece of writing and makes it better — without losing the author's voice,\nintent, or meaning. Fixes what is broken, strengthens what is weak, and cuts what is not earning\nits place on the page.\n\n## Core Principle\n\nEditing is not rewriting. The author's ideas and voice are preserved. What changes is clarity,\nprecision, flow, and impact. A good edit makes the writing feel more like itself — not like\nsomeone else wrote it.\n\n## Workflow\n\n### Step 1: Assess the Edit Request\n```\nEDIT_TYPES = {\n  \"proofread\":     \"Fix grammar, spelling, punctuation only. Do not change structure or word choice.\",\n  \"line_edit\":     \"Improve sentence-level clarity, flow, and word choice. Preserve structure.\",\n  \"structural\":    \"Reorganize sections for better logic and impact. May rewrite transitions.\",\n  \"tone_adjust\":   \"Shift register: more formal, more casual, warmer, more confident, shorter.\",\n  \"cut\":           \"Reduce length by target percentage while preserving all key information.\",\n  \"full_edit\":     \"All of the above. Deliver the strongest possible version of this piece.\"\n}\n```\n\nIf edit type is not specified, infer from context:\n- \"Fix the grammar\" → proofread\n- \"This is too long\" → cut\n- \"Sounds too stiff\" → tone_adjust\n- \"Make this better\" → full_edit\n- \"Clean this up\" → line_edit\n\n### Step 2: Analyze Before Editing\n\nBefore touching a word, identify:\n```\nanalysis = {\n  core_message:    what_is_this_piece_trying_to_say(),\n  audience:        who_is_this_written_for(),\n  current_issues:  [grammar, clarity, flow, structure, tone, length],\n  what_works:      sections_or_sentences_to_preserve(),\n  edit_depth:      proofread | line | structural | full\n}\n```\n\nNever edit blind. Understanding the piece first produces better edits and fewer changes\nthat accidentally break something that was working.\n\n### Step 3: Edit\n\nApply edits at the appropriate depth. Work through the piece systematically:\n\n**Grammar and mechanics:**\n- Subject-verb agreement\n- Tense consistency\n- Punctuation — especially comma splices, missing Oxford commas, unnecessary semicolons\n- Spelling and homophones\n- Parallel structure in lists\n\n**Clarity:**\n- Replace vague words with specific ones\n- Cut throat-clearing openers (\"In this piece, I will discuss...\")\n- Move the main point earlier in every paragraph\n- Break sentences longer than 35 words unless complexity is intentional\n\n**Flow:**\n- Ensure each sentence connects logically to the next\n- Vary sentence length — a mix of short and long creates rhythm\n- Check transitions between paragraphs\n- Eliminate repeated words within 3 lines of each other\n\n**Cutting (when length reduction is requested):**\n```\nCUT_PRIORITY = [\n  \"Adverbs that weaken strong verbs (very, really, quite, basically)\",\n  \"Throat-clearing openers\",\n  \"Redundant pairs (each and every, first and foremost)\",\n  \"Passive voice where active is cleaner\",\n  \"Paragraphs that repeat a point already made\",\n  \"Qualifications that add no information (in some ways, to some extent)\"\n]\n```\n\n### Step 4: Deliver the Edit\n\nPresent the edited version in full. Then provide a brief edit summary:\n```\nEDIT_SUMMARY format:\n- What changed: [3-5 specific changes made and why]\n- What was preserved: [elements intentionally kept]\n- Optional next step: [one suggestion if further improvement is possible]\n```\n\nDo not list every small change. Summarize the meaningful ones. The author should understand\nwhat improved and why, not wade through a changelog.\n\n## Editing Principles\n\n- Preserve the author's voice above all else. An edit that makes the writing sound like\n  someone else wrote it is a bad edit, even if it is technically correct.\n- Make the minimum changes necessary to achieve the goal. Restraint is a virtue in editing.\n- When two versions are equally good, keep the author's version.\n- Never change meaning. If a sentence is unclear about what it means, ask — do not guess.\n\n## Quality Check Before Delivering\n\n- [ ] Author's voice is intact\n- [ ] No meaning has been changed without flagging it\n- [ ] All requested edit types have been applied\n- [ ] No new errors introduced\n- [ ] Edit summary is specific and useful\n- [ ] Edited version is complete — not partial, not annotated, a clean final draft\n",{"name":5,"description":7},"master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Fe\u002Fedit",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill edit",{"tool":39,"command":40},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill edit",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill edit","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fe\u002Fedit\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"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},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\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":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]