[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6RA4EM2YX9VWCFSM7BYXQ3Q":3,"skill-same:01M6RA4EM2YX9VWCFSM7BYXQ3Q":68},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":46,"commitSha":47,"skillDirectory":48,"forksCount":49,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":52,"ownerDescription":53,"updatedAt":54,"install":55,"resources":67},"01M6RA4EM2YX9VWCFSM7BYXQ3Q","animate",null,"Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive.","Nairon-AI\u002Fagentic-starter-pack","Nairon-AI","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F260662138?v=4","01M6R8PZ1Y8CSQGFN61VACZGTH","Nairon AI","01M6R8PZ6184VR3BA88YZFBC3N",4,"MIT","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Ffrontend\u002Fspecialists\u002Fanimate\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"motion","when","animations","effects","true","more","with","feature","transitions","motion design","design","enhance","usability","use","improve","Animation","micro","hover","review","2026-11-10 10:12:30",false,"---\nname: animate\ndescription: Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight. Use when the user mentions adding animation, transitions, micro-interactions, motion design, hover effects, or making the UI feel more alive.\nversion: 2.1.1\nuser-invocable: true\nargument-hint: \"[target]\"\n---\n\nAnalyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight.\n\n## MANDATORY PREPARATION\n\nInvoke \u002Fimpeccable — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run \u002Fimpeccable teach first. Additionally gather: performance constraints.\n\n---\n\n## Assess Animation Opportunities\n\nAnalyze where motion would improve the experience:\n\n1. **Identify static areas**:\n   - **Missing feedback**: Actions without visual acknowledgment (button clicks, form submission, etc.)\n   - **Jarring transitions**: Instant state changes that feel abrupt (show\u002Fhide, page loads, route changes)\n   - **Unclear relationships**: Spatial or hierarchical relationships that aren't obvious\n   - **Lack of delight**: Functional but joyless interactions\n   - **Missed guidance**: Opportunities to direct attention or explain behavior\n\n2. **Understand the context**:\n   - What's the personality? (Playful vs serious, energetic vs calm)\n   - What's the performance budget? (Mobile-first? Complex page?)\n   - Who's the audience? (Motion-sensitive users? Power users who want speed?)\n   - What matters most? (One hero animation vs many micro-interactions?)\n\nIf any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer.\n\n**CRITICAL**: Respect `prefers-reduced-motion`. Always provide non-animated alternatives for users who need them.\n\n## Plan Animation Strategy\n\nCreate a purposeful animation plan:\n\n- **Hero moment**: What's the ONE signature animation? (Page load? Hero section? Key interaction?)\n- **Feedback layer**: Which interactions need acknowledgment?\n- **Transition layer**: Which state changes need smoothing?\n- **Delight layer**: Where can we surprise and delight?\n\n**IMPORTANT**: One well-orchestrated experience beats scattered animations everywhere. Focus on high-impact moments.\n\n## Implement Animations\n\nAdd motion systematically across these categories:\n\n### Entrance Animations\n- **Page load choreography**: Stagger element reveals (100-150ms delays), fade + slide combinations\n- **Hero section**: Dramatic entrance for primary content (scale, parallax, or creative effects)\n- **Content reveals**: Scroll-triggered animations using intersection observer\n- **Modal\u002Fdrawer entry**: Smooth slide + fade, backdrop fade, focus management\n\n### Micro-interactions\n- **Button feedback**:\n  - Hover: Subtle scale (1.02-1.05), color shift, shadow increase\n  - Click: Quick scale down then up (0.95 → 1), ripple effect\n  - Loading: Spinner or pulse state\n- **Form interactions**:\n  - Input focus: Border color transition, slight scale or glow\n  - Validation: Shake on error, check mark on success, smooth color transitions\n- **Toggle switches**: Smooth slide + color transition (200-300ms)\n- **Checkboxes\u002Fradio**: Check mark animation, ripple effect\n- **Like\u002Ffavorite**: Scale + rotation, particle effects, color transition\n\n### State Transitions\n- **Show\u002Fhide**: Fade + slide (not instant), appropriate timing (200-300ms)\n- **Expand\u002Fcollapse**: Height transition with overflow handling, icon rotation\n- **Loading states**: Skeleton screen fades, spinner animations, progress bars\n- **Success\u002Ferror**: Color transitions, icon animations, gentle scale pulse\n- **Enable\u002Fdisable**: Opacity transitions, cursor changes\n\n### Navigation & Flow\n- **Page transitions**: Crossfade between routes, shared element transitions\n- **Tab switching**: Slide indicator, content fade\u002Fslide\n- **Carousel\u002Fslider**: Smooth transforms, snap points, momentum\n- **Scroll effects**: Parallax layers, sticky headers with state changes, scroll progress indicators\n\n### Feedback & Guidance\n- **Hover hints**: Tooltip fade-ins, cursor changes, element highlights\n- **Drag & drop**: Lift effect (shadow + scale), drop zone highlights, smooth repositioning\n- **Copy\u002Fpaste**: Brief highlight flash on paste, \"copied\" confirmation\n- **Focus flow**: Highlight path through form or workflow\n\n### Delight Moments\n- **Empty states**: Subtle floating animations on illustrations\n- **Completed actions**: Confetti, check mark flourish, success celebrations\n- **Easter eggs**: Hidden interactions for discovery\n- **Contextual animation**: Weather effects, time-of-day themes, seasonal touches\n\n## Technical Implementation\n\nUse appropriate techniques for each animation:\n\n### Timing & Easing\n\n**Durations by purpose:**\n- **100-150ms**: Instant feedback (button press, toggle)\n- **200-300ms**: State changes (hover, menu open)\n- **300-500ms**: Layout changes (accordion, modal)\n- **500-800ms**: Entrance animations (page load)\n\n**Easing curves (use these, not CSS defaults):**\n```css\n\u002F* Recommended - natural deceleration *\u002F\n--ease-out-quart: cubic-bezier(0.25, 1, 0.5, 1);    \u002F* Smooth, refined *\u002F\n--ease-out-quint: cubic-bezier(0.22, 1, 0.36, 1);   \u002F* Slightly snappier *\u002F\n--ease-out-expo: cubic-bezier(0.16, 1, 0.3, 1);     \u002F* Confident, decisive *\u002F\n\n\u002F* AVOID - feel dated and tacky *\u002F\n\u002F* bounce: cubic-bezier(0.34, 1.56, 0.64, 1); *\u002F\n\u002F* elastic: cubic-bezier(0.68, -0.6, 0.32, 1.6); *\u002F\n```\n\n**Exit animations are faster than entrances.** Use ~75% of enter duration.\n\n### CSS Animations\n```css\n\u002F* Prefer for simple, declarative animations *\u002F\n- transitions for state changes\n- @keyframes for complex sequences\n- transform + opacity only (GPU-accelerated)\n```\n\n### JavaScript Animation\n```javascript\n\u002F* Use for complex, interactive animations *\u002F\n- Web Animations API for programmatic control\n- Framer Motion for React\n- GSAP for complex sequences\n```\n\n### Performance\n- **GPU acceleration**: Use `transform` and `opacity`, avoid layout properties\n- **will-change**: Add sparingly for known expensive animations\n- **Reduce paint**: Minimize repaints, use `contain` where appropriate\n- **Monitor FPS**: Ensure 60fps on target devices\n\n### Accessibility\n```css\n@media (prefers-reduced-motion: reduce) {\n  * {\n    animation-duration: 0.01ms !important;\n    animation-iteration-count: 1 !important;\n    transition-duration: 0.01ms !important;\n  }\n}\n```\n\n**NEVER**:\n- Use bounce or elastic easing curves—they feel dated and draw attention to the animation itself\n- Animate layout properties (width, height, top, left)—use transform instead\n- Use durations over 500ms for feedback—it feels laggy\n- Animate without purpose—every animation needs a reason\n- Ignore `prefers-reduced-motion`—this is an accessibility violation\n- Animate everything—animation fatigue makes interfaces feel exhausting\n- Block interaction during animations unless intentional\n\n## Verify Quality\n\nTest animations thoroughly:\n\n- **Smooth at 60fps**: No jank on target devices\n- **Feels natural**: Easing curves feel organic, not robotic\n- **Appropriate timing**: Not too fast (jarring) or too slow (laggy)\n- **Reduced motion works**: Animations disabled or simplified appropriately\n- **Doesn't block**: Users can interact during\u002Fafter animations\n- **Adds value**: Makes interface clearer or more delightful\n\nRemember: Motion should enhance understanding and provide feedback, not just add decoration. Animate with purpose, respect performance constraints, and always consider accessibility. Great animation is invisible - it just makes everything feel right.","Analyze a feature and strategically add animations and micro-interactions that enhance understanding, provide feedback, and create delight.\n\n## MANDATORY PREPARATION\n\nInvoke \u002Fimpeccable — it contains design principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no design context exists yet, you MUST run \u002Fimpeccable teach first. Additionally gather: performance constraints.\n\n---\n\n## Assess Animation Opportunities\n\nAnalyze where motion would improve the experience:\n\n1. **Identify static areas**:\n   - **Missing feedback**: Actions without visual acknowledgment (button clicks, form submission, etc.)\n   - **Jarring transitions**: Instant state changes that feel abrupt (show\u002Fhide, page loads, route changes)\n   - **Unclear relationships**: Spatial or hierarchical relationships that aren't obvious\n   - **Lack of delight**: Functional but joyless interactions\n   - **Missed guidance**: Opportunities to direct attention or explain behavior\n\n2. **Understand the context**:\n   - What's the personality? (Playful vs serious, energetic vs calm)\n   - What's the performance budget? (Mobile-first? Complex page?)\n   - Who's the audience? (Motion-sensitive users? Power users who want speed?)\n   - What matters most? (One hero animation vs many micro-interactions?)\n\nIf any of these are unclear from the codebase, ask the user directly to clarify what you cannot infer.\n\n**CRITICAL**: Respect `prefers-reduced-motion`. Always provide non-animated alternatives for users who need them.\n\n## Plan Animation Strategy\n\nCreate a purposeful animation plan:\n\n- **Hero moment**: What's the ONE signature animation? (Page load? Hero section? Key interaction?)\n- **Feedback layer**: Which interactions need acknowledgment?\n- **Transition layer**: Which state changes need smoothing?\n- **Delight layer**: Where can we surprise and delight?\n\n**IMPORTANT**: One well-orchestrated experience beats scattered animations everywhere. Focus on high-impact moments.\n\n## Implement Animations\n\nAdd motion systematically across these categories:\n\n### Entrance Animations\n- **Page load choreography**: Stagger element reveals (100-150ms delays), fade + slide combinations\n- **Hero section**: Dramatic entrance for primary content (scale, parallax, or creative effects)\n- **Content reveals**: Scroll-triggered animations using intersection observer\n- **Modal\u002Fdrawer entry**: Smooth slide + fade, backdrop fade, focus management\n\n### Micro-interactions\n- **Button feedback**:\n  - Hover: Subtle scale (1.02-1.05), color shift, shadow increase\n  - Click: Quick scale down then up (0.95 → 1), ripple effect\n  - Loading: Spinner or pulse state\n- **Form interactions**:\n  - Input focus: Border color transition, slight scale or glow\n  - Validation: Shake on error, check mark on success, smooth color transitions\n- **Toggle switches**: Smooth slide + color transition (200-300ms)\n- **Checkboxes\u002Fradio**: Check mark animation, ripple effect\n- **Like\u002Ffavorite**: Scale + rotation, particle effects, color transition\n\n### State Transitions\n- **Show\u002Fhide**: Fade + slide (not instant), appropriate timing (200-300ms)\n- **Expand\u002Fcollapse**: Height transition with overflow handling, icon rotation\n- **Loading states**: Skeleton screen fades, spinner animations, progress bars\n- **Success\u002Ferror**: Color transitions, icon animations, gentle scale pulse\n- **Enable\u002Fdisable**: Opacity transitions, cursor changes\n\n### Navigation & Flow\n- **Page transitions**: Crossfade between routes, shared element transitions\n- **Tab switching**: Slide indicator, content fade\u002Fslide\n- **Carousel\u002Fslider**: Smooth transforms, snap points, momentum\n- **Scroll effects**: Parallax layers, sticky headers with state changes, scroll progress indicators\n\n### Feedback & Guidance\n- **Hover hints**: Tooltip fade-ins, cursor changes, element highlights\n- **Drag & drop**: Lift effect (shadow + scale), drop zone highlights, smooth repositioning\n- **Copy\u002Fpaste**: Brief highlight flash on paste, \"copied\" confirmation\n- **Focus flow**: Highlight path through form or workflow\n\n### Delight Moments\n- **Empty states**: Subtle floating animations on illustrations\n- **Completed actions**: Confetti, check mark flourish, success celebrations\n- **Easter eggs**: Hidden interactions for discovery\n- **Contextual animation**: Weather effects, time-of-day themes, seasonal touches\n\n## Technical Implementation\n\nUse appropriate techniques for each animation:\n\n### Timing & Easing\n\n**Durations by purpose:**\n- **100-150ms**: Instant feedback (button press, toggle)\n- **200-300ms**: State changes (hover, menu open)\n- **300-500ms**: Layout changes (accordion, modal)\n- **500-800ms**: Entrance animations (page load)\n\n**Easing curves (use these, not CSS defaults):**\n```css\n\u002F* Recommended - natural deceleration *\u002F\n--ease-out-quart: cubic-bezier(0.25, 1, 0.5, 1);    \u002F* Smooth, refined *\u002F\n--ease-out-quint: cubic-bezier(0.22, 1, 0.36, 1);   \u002F* Slightly snappier *\u002F\n--ease-out-expo: cubic-bezier(0.16, 1, 0.3, 1);     \u002F* Confident, decisive *\u002F\n\n\u002F* AVOID - feel dated and tacky *\u002F\n\u002F* bounce: cubic-bezier(0.34, 1.56, 0.64, 1); *\u002F\n\u002F* elastic: cubic-bezier(0.68, -0.6, 0.32, 1.6); *\u002F\n```\n\n**Exit animations are faster than entrances.** Use ~75% of enter duration.\n\n### CSS Animations\n```css\n\u002F* Prefer for simple, declarative animations *\u002F\n- transitions for state changes\n- @keyframes for complex sequences\n- transform + opacity only (GPU-accelerated)\n```\n\n### JavaScript Animation\n```javascript\n\u002F* Use for complex, interactive animations *\u002F\n- Web Animations API for programmatic control\n- Framer Motion for React\n- GSAP for complex sequences\n```\n\n### Performance\n- **GPU acceleration**: Use `transform` and `opacity`, avoid layout properties\n- **will-change**: Add sparingly for known expensive animations\n- **Reduce paint**: Minimize repaints, use `contain` where appropriate\n- **Monitor FPS**: Ensure 60fps on target devices\n\n### Accessibility\n```css\n@media (prefers-reduced-motion: reduce) {\n  * {\n    animation-duration: 0.01ms !important;\n    animation-iteration-count: 1 !important;\n    transition-duration: 0.01ms !important;\n  }\n}\n```\n\n**NEVER**:\n- Use bounce or elastic easing curves—they feel dated and draw attention to the animation itself\n- Animate layout properties (width, height, top, left)—use transform instead\n- Use durations over 500ms for feedback—it feels laggy\n- Animate without purpose—every animation needs a reason\n- Ignore `prefers-reduced-motion`—this is an accessibility violation\n- Animate everything—animation fatigue makes interfaces feel exhausting\n- Block interaction during animations unless intentional\n\n## Verify Quality\n\nTest animations thoroughly:\n\n- **Smooth at 60fps**: No jank on target devices\n- **Feels natural**: Easing curves feel organic, not robotic\n- **Appropriate timing**: Not too fast (jarring) or too slow (laggy)\n- **Reduced motion works**: Animations disabled or simplified appropriately\n- **Doesn't block**: Users can interact during\u002Fafter animations\n- **Adds value**: Makes interface clearer or more delightful\n\nRemember: Motion should enhance understanding and provide feedback, not just add decoration. Animate with purpose, respect performance constraints, and always consider accessibility. Great animation is invisible - it just makes everything feel right.",{"name":5,"version":43,"description":7,"argument-hint":44,"user-invocable":45},"2.1.1","[target]",true,"main","c9d0c408715983e993b2f9ebffdbfa7f10153bcb","frontend\u002Fspecialists\u002Fanimate",0,"https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack","https:\u002F\u002Fgithub.com\u002FNairon-AI","https:\u002F\u002Fwww.naironai.com\u002F","Building the future of Work","2026-09-20 17:40:05",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":45},[57,60,63],{"tool":58,"command":59},"npx","npx skills add Nairon-AI\u002Fagentic-starter-pack --skill animate",{"tool":61,"command":62},"bunx","bunx skills add Nairon-AI\u002Fagentic-starter-pack --skill animate",{"tool":64,"command":65},"pnpm","pnpm dlx skills add Nairon-AI\u002Fagentic-starter-pack --skill animate","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Ffrontend\u002Fspecialists\u002Fanimate\u002FSKILL.md",[],[69,104,126,147,167,189],{"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":85,"publishedAt":38},"01M6RBCG630Y8X99XWR9Q4GYNY","writing-shape","Take a markdown file of raw material and shape it into an article through a conversational session — drafting candidate openings, growing the piece paragraph by paragraph, arguing about format (lists, tables, callouts, quotes) at each step. Use when the user has a pile of notes, fragments, or a rough draft and wants help turning it into something publishable.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fwriting-shape\u002FSKILL.md",[75,80],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[86,87,88,89,90,91,92,93,94,32,95,96,97,98,99,100,101,102,103,20],"writing","writing shape","shape","notes","help","file","markdown","format","session","take","draft","article","material","it","about","quotes","at","candidate",{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":108,"categories":109,"keywords":112,"publishedAt":38},"01M6RBCCCB1KMF01P5SYGFWBSW","writing-fragments","Grilling session that mines the user for fragments — heterogeneous nuggets of writing (claims, vignettes, sharp sentences, half-thoughts) — and appends them to a single document as raw material for a future article. Use when the user wants to develop ideas before imposing structure, or mentions \"fragments\", \"ideate\", or \"raw material\" for writing.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fwriting-fragments\u002FSKILL.md",[110,111],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},[86,113,114,115,116,117,94,32,118,119,120,97,121,98,122,123,124,125,20],"writing fragments","grilling","ideate","develop","user","document","structure","ideas","as","sharp","claims","for","single",{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":134,"publishedAt":38},"01M6RBC8V7NHHKMTAZB4BPXVYQ","writing-beats","Shape an article as a journey of beats, choose-your-own-adventure style. The user picks a starting beat from the raw material, you write only that beat, then offer options for where to pivot next, beat by beat, until the article reaches a natural end. Use when the user has raw material and wants to assemble it as a narrative rather than an argument.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fwriting-beats\u002FSKILL.md",[132,133],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},[86,135,136,137,32,138,139,88,140,141,142,97,143,121,144,98,145,146,124,20],"writing beats","choose","write","assemble","only","journey","next","options","end","style","narrative","argument",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":155,"publishedAt":38},"01M6RBC58SG5Y5SC4ZV4ZNEFHC","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fstop-slop\u002FSKILL.md",[153,154],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},[156,157,158,86,159,160,161,162,163,32,164,165,166,124,20],"stop","stop slop","slop","content","https","text","editing","remove","prose","patterns","drafts",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":175,"publishedAt":38},"01M6RBBJTTCJ7KZCP16G9JDFZH","humanizer","Remove signs of AI-generated writing from text. Use when editing or reviewing\ntext to make it sound more natural and human-written. Based on Wikipedia's\ncomprehensive \"Signs of AI writing\" guide. Detects and fixes patterns including:\ninflated symbolism, promotional language, superficial -ing analyses, vague\nattributions, em dash overuse, rule of three, AI vocabulary words, passive\nvoice, negative parallelisms, and filler phrases.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Fhumanizer\u002FSKILL.md",[173,174],{"categoryNo":76,"categoryName":77,"taxonomyType":78,"taxonomyTypeDesc":79},{"categoryNo":81,"categoryName":82,"taxonomyType":83,"taxonomyTypeDesc":84},[169,86,176,177,161,178,137,179,180,163,181,182,165,183,184,185,186,187,188,20],"code","em dash","read","edit","generated","guide","opencode","three","human","make","wikipedia","vague","dash",{"skillNo":190,"name":191,"nameZh":6,"description":192,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":193,"categories":194,"keywords":195,"publishedAt":38},"01M6RBBEQKJ5HRH8AV9J85QB1T","feedback","Prepare, deliver, and debrief timely interpersonal feedback using a question-first coaching flow, observable behavior, owned experience, and concrete impact. Use when drafting feedback, coaching managers, rehearsing a feedback conversation, praising specific behavior, or reviewing whether feedback landed.","https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fwriting\u002Ffeedback\u002FSKILL.md",[],[191,196,197,198,199,200,32,201,202,203,204,205,20,206],"prepare","flow","first","question","behavior","conversation","coaching","debrief","impact","managers","deliver"]