[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71SX4VDJS9KTM37MG702ZCX":3,"skill-same:01M71SX4VDJS9KTM37MG702ZCX":76},{"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":28,"publishedAt":49,"linkOnly":50,"markdownContent":51,"markdownBody":52,"frontMatter":53,"refName":54,"commitSha":55,"skillDirectory":56,"forksCount":57,"repositoryHtmlUrl":58,"repositoryHomepageUrl":6,"ownerHtmlUrl":59,"ownerBlogUrl":60,"ownerDescription":6,"updatedAt":61,"install":62,"resources":75},"01M71SX4VDJS9KTM37MG702ZCX","note-writer",null,"Review English text edits in org-mode files from a git diff. Checks grammar, style, translation quality (RU→EN), and produces a clean patch. Use when reviewing org-mode writing, checking English quality of documentation edits, or auditing translation naturalness.","Artawower\u002Fkaizen","Artawower","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F16963833?v=4","01M71SV5H0DRR8KXVGD4R51Z99","Art","01M71SV5J1B97T7349GGXQCYXT",2,"GPL-3.0","https:\u002F\u002Fgithub.com\u002FArtawower\u002Fkaizen\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_agents\u002Fskills\u002Fnote-writer\u002FSKILL.md",[18,23],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48],"note writer","note","writer","quality","grammar","style","documentation","text","english","review","patch","when","use","writing","files","clean","mode","en","diff","translation","2026-11-10 13:02:02",false,"---\nname: note-writer\ndescription: Review English text edits in org-mode files from a git diff. Checks grammar, style, translation quality (RU→EN), and produces a clean patch. Use when reviewing org-mode writing, checking English quality of documentation edits, or auditing translation naturalness.\n---\n\n# EN Writing & Translation QA (org-mode, git diff)\n\nVERSION: 1.1\n\n## Goal\n\nReview English text edits provided as a unified git diff (source text is org-mode) and help the user:\n\n- fix grammar errors\n- improve style and clarity\n- assess translation quality (RU→EN influence)\n- explain each issue with a short rule-based note\n- propose better rewrites while preserving meaning and org-mode markup\n\n## Input\n\n- git_diff (required): unified diff of an org-mode file — provide inline or ask the user to paste it\n- optional context: audience, tone, register; English variant (American\u002FBritish); strictness (low\u002Fmedium\u002Fhigh)\n\n## Scope\n\n- Review ONLY added\u002Fmodified lines from the diff.\n- Use removed lines only for context.\n- Do not rewrite the whole document.\n- If a change creates a consistency problem with unchanged nearby text, mention briefly.\n\n## Process\n\n1. **Parse the diff** — identify hunks, classify lines (`+` added, `-` removed, ` ` context). Pair removed\u002Fadded blocks when it is clearly a modification.\n\n2. **Grammar & correctness pass** — for each changed line detect mistakes (articles, prepositions, tense, agreement, punctuation, sentence boundaries, word order). Provide: Problem → Fix → Explanation.\n\n3. **Style & clarity pass** — improve naturalness and flow with minimal edits. Prefer concise, idiomatic English. Preserve tone\u002Fvoice unless it harms clarity.\n\n4. **Translation quality check** — detect Russianisms and literal translation patterns: unnatural collocations, incorrect prepositions\u002Farticles, calques\u002Ffalse friends, overly heavy nominalizations, passive voice where unnatural, word order mirroring Russian. Give 1–2 plausible meanings when ambiguous, offer safe rewrites.\n\n5. **Rule snippet for every flagged issue** — Rule name + 1–2 sentence explanation + tiny example if helpful.\n\n6. **Produce final rewrite** — \"Suggested patch (clean)\" section with revised lines only, no diff markers, org-mode markup preserved.\n\n## Priority levels\n\n- **High**: grammar error, meaning distortion, clearly non-native\u002Fincorrect collocation, broken org syntax\n- **Medium**: awkward but understandable, wordiness, minor punctuation\n- **Low**: optional polish, alternative phrasing\n\n## Output format\n\n1. Overall assessment — Grammar \u002F Style\u002Fflow \u002F Translation naturalness\n2. Issues list (prioritized High → Medium → Low), each with: Problem → Fix, Why, Rule snippet\n3. Suggested patch (clean) — revised lines, no diff symbols, org-mode markup intact\n4. Optional: 3 learning takeaways (recurring patterns)\n\n## Constraints\n\n- Respond in the user's language for meta-commentary; keep proposed English rewrites in English.\n- Ask max 2 clarification questions, only if meaning is genuinely unclear.\n- Do not introduce new facts or content.\n- Do not remove org-mode markup unless broken; explain any markup changes.\n","# EN Writing & Translation QA (org-mode, git diff)\n\nVERSION: 1.1\n\n## Goal\n\nReview English text edits provided as a unified git diff (source text is org-mode) and help the user:\n\n- fix grammar errors\n- improve style and clarity\n- assess translation quality (RU→EN influence)\n- explain each issue with a short rule-based note\n- propose better rewrites while preserving meaning and org-mode markup\n\n## Input\n\n- git_diff (required): unified diff of an org-mode file — provide inline or ask the user to paste it\n- optional context: audience, tone, register; English variant (American\u002FBritish); strictness (low\u002Fmedium\u002Fhigh)\n\n## Scope\n\n- Review ONLY added\u002Fmodified lines from the diff.\n- Use removed lines only for context.\n- Do not rewrite the whole document.\n- If a change creates a consistency problem with unchanged nearby text, mention briefly.\n\n## Process\n\n1. **Parse the diff** — identify hunks, classify lines (`+` added, `-` removed, ` ` context). Pair removed\u002Fadded blocks when it is clearly a modification.\n\n2. **Grammar & correctness pass** — for each changed line detect mistakes (articles, prepositions, tense, agreement, punctuation, sentence boundaries, word order). Provide: Problem → Fix → Explanation.\n\n3. **Style & clarity pass** — improve naturalness and flow with minimal edits. Prefer concise, idiomatic English. Preserve tone\u002Fvoice unless it harms clarity.\n\n4. **Translation quality check** — detect Russianisms and literal translation patterns: unnatural collocations, incorrect prepositions\u002Farticles, calques\u002Ffalse friends, overly heavy nominalizations, passive voice where unnatural, word order mirroring Russian. Give 1–2 plausible meanings when ambiguous, offer safe rewrites.\n\n5. **Rule snippet for every flagged issue** — Rule name + 1–2 sentence explanation + tiny example if helpful.\n\n6. **Produce final rewrite** — \"Suggested patch (clean)\" section with revised lines only, no diff markers, org-mode markup preserved.\n\n## Priority levels\n\n- **High**: grammar error, meaning distortion, clearly non-native\u002Fincorrect collocation, broken org syntax\n- **Medium**: awkward but understandable, wordiness, minor punctuation\n- **Low**: optional polish, alternative phrasing\n\n## Output format\n\n1. Overall assessment — Grammar \u002F Style\u002Fflow \u002F Translation naturalness\n2. Issues list (prioritized High → Medium → Low), each with: Problem → Fix, Why, Rule snippet\n3. Suggested patch (clean) — revised lines, no diff symbols, org-mode markup intact\n4. Optional: 3 learning takeaways (recurring patterns)\n\n## Constraints\n\n- Respond in the user's language for meta-commentary; keep proposed English rewrites in English.\n- Ask max 2 clarification questions, only if meaning is genuinely unclear.\n- Do not introduce new facts or content.\n- Do not remove org-mode markup unless broken; explain any markup changes.\n",{"name":5,"description":7},"master","cbded6c96796a063405af105d5b3209ab6219407","dotfiles\u002Fdot_agents\u002Fskills\u002Fnote-writer",0,"https:\u002F\u002Fgithub.com\u002FArtawower\u002Fkaizen","https:\u002F\u002Fgithub.com\u002FArtawower","workationmode.com","2026-11-10 19:23:03",{"source":8,"skillName":5,"commands":63,"prompt":73,"zipAvailable":74},[64,67,70],{"tool":65,"command":66},"npx","npx skills add Artawower\u002Fkaizen --skill note-writer",{"tool":68,"command":69},"bunx","bunx skills add Artawower\u002Fkaizen --skill note-writer",{"tool":71,"command":72},"pnpm","pnpm dlx skills add Artawower\u002Fkaizen --skill note-writer","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FArtawower\u002Fkaizen\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_agents\u002Fskills\u002Fnote-writer\u002FSKILL.md",true,[],[77,107,125,149,162,188],{"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":86,"publishedAt":49},"01M71SYJ1B45ZKM8J96AZ3TS0H","yt-analyze","Fetch YouTrack task + comments via MCP, critically analyze relevance and requirements, produce concise summary of what to implement, and build an implementation plan mapped to codebase. Trigger - YouTrack issue ID or request to \"analyze task\", \"plan task\", \"break down YT issue\".","https:\u002F\u002Fgithub.com\u002FArtawower\u002Fkaizen\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_agents\u002Fskills\u002Fyt-analyze\u002FSKILL.md",[83],{"categoryNo":84,"categoryName":85,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发",[87,88,89,90,91,92,93,94,95,96,97,98,99,100,101,102,103,104,105,106],"analyze","yt analyze","yt","fetch","implementation plan","MCP","plan task","plan","request","break","issue","youtrack","down","trigger","produce","break down","comments","requirements","implement","task",{"skillNo":108,"name":109,"nameZh":6,"description":110,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":111,"categories":112,"keywords":113,"publishedAt":49},"01M71SYF7RSTEXKDWPXJ08EVQG","youtrack-task","Analyzes a YouTrack issue, reviews comments and attachments, and proposes or creates actionable subtasks. Use when the user gives a YouTrack issue ID and wants synthesis, decomposition, or follow-up tasks.","https:\u002F\u002Fgithub.com\u002FArtawower\u002Fkaizen\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_agents\u002Fskills\u002Fyoutrack-task\u002FSKILL.md",[],[114,98,106,115,116,117,118,119,120,97,121,41,40,103,122,123,124],"youtrack task","id","reviews","attachments","decomposition","actionable","up","follow-up","tasks","Synthesis","user",{"skillNo":126,"name":127,"nameZh":6,"description":128,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":129,"categories":130,"keywords":131,"publishedAt":49},"01M71SYCE94601T6DA5G2GDKYA","youtrack-search","Searches YouTrack from natural language or native query syntax and returns a concise report with the most relevant issues. Use when the user wants to find issues, triage work, or translate a plain-language query into YouTrack search.","https:\u002F\u002Fgithub.com\u002FArtawower\u002Fkaizen\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_agents\u002Fskills\u002Fyoutrack-search\u002FSKILL.md",[],[132,133,98,134,135,136,137,138,41,40,139,140,141,142,143,144,145,146,147,148],"search","youtrack search","natural language","relevant","translate","issues","plain-language","query","with","work","concise","native","find","report","syntax","triage","plain",{"skillNo":150,"name":151,"nameZh":6,"description":152,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":153,"categories":154,"keywords":157,"publishedAt":49},"01M71SYAXN8EA6DDXEZWVY872S","writing-for-agents","Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.","https:\u002F\u002Fgithub.com\u002FArtawower\u002Fkaizen\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_agents\u002Fskills\u002Fwriting-for-agents\u002FSKILL.md",[155,156],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":24,"categoryName":25,"taxonomyType":26,"taxonomyTypeDesc":27},[158,159,42,160,41,161,40],"writing for agents","for","editing","documents",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":171,"publishedAt":49},"01M71SY8ZKMWPF8ZAENT7MQE28","write-a-prd","Create a PRD through user interview, codebase exploration, and module design, then submit as a GitHub issue. Use when user wants to write a PRD, create a product requirements document, or plan a new feature.","https:\u002F\u002Fgithub.com\u002FArtawower\u002Fkaizen\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_agents\u002Fskills\u002Fwrite-a-prd\u002FSKILL.md",[168],{"categoryNo":169,"categoryName":170,"taxonomyType":26,"taxonomyTypeDesc":27},"01JBSEEDCAT000000000000031","产品经理",[172,173,174,175,176,177,178,179,180,181,182,41,183,40,184,185,104,186,187,94],"write","write a prd","prd","interview","as","exploration","feature","submit","design","module","new","document","user interview","codebase exploration","create","new feature",{"skillNo":189,"name":190,"nameZh":6,"description":191,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":192,"categories":193,"keywords":194,"publishedAt":49},"01M71SY6J9F119TJSMA2YBEP5P","vitest","Plan and write Vitest tests for changed code. Analyses git diff, checks existing tests, produces a concrete test plan using flat test structure (no describe\u002Fit blocks). Use when adding tests for new\u002Fchanged code, improving Vitest coverage, or asking what to test after a change.","https:\u002F\u002Fgithub.com\u002FArtawower\u002Fkaizen\u002Fblob\u002Fmaster\u002Fdotfiles\u002Fdot_agents\u002Fskills\u002Fvitest\u002FSKILL.md",[],[190,195,196,47,159,197,182,41,198,199,40,200,201,202,94,203,204,172,205,206],"coverage","test plan","tests","Existing","adding tests","code","test","structure","change","flat","blocks","git"]