[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6RAPAJN46VPM92S52MMDWYF":3,"skill-same:01M6RAPAJN46VPM92S52MMDWYF":78},{"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":45,"commitSha":46,"skillDirectory":47,"forksCount":48,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":51,"ownerDescription":52,"updatedAt":53,"install":54,"resources":67},"01M6RAPAJN46VPM92S52MMDWYF","paywalls",null,"When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions \"paywall,\" \"upgrade screen,\" \"upgrade modal,\" \"upsell,\" \"feature gate,\" \"convert free to paid,\" \"freemium conversion,\" \"trial expiration screen,\" \"limit reached screen,\" \"plan upgrade prompt,\" \"in-app pricing,\" \"free users won't upgrade,\" \"trial to paid conversion,\" or \"how do I get users to pay.\" Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.","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\u002Fmarketing\u002Fcro\u002Fpaywalls\u002FSKILL.md",[],[5,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"free","when","upsell","freemium conversion","pay","re","you","moments","screen","create","app","get","upgrade","optimize","conversion","cro","plan","how","product","2026-11-10 10:12:30",false,"---\nname: paywalls\ndescription: When the user wants to create or optimize in-app paywalls, upgrade screens, upsell modals, or feature gates. Also use when the user mentions \"paywall,\" \"upgrade screen,\" \"upgrade modal,\" \"upsell,\" \"feature gate,\" \"convert free to paid,\" \"freemium conversion,\" \"trial expiration screen,\" \"limit reached screen,\" \"plan upgrade prompt,\" \"in-app pricing,\" \"free users won't upgrade,\" \"trial to paid conversion,\" or \"how do I get users to pay.\" Use this for any in-product moment where you're asking users to upgrade. Distinct from public pricing pages (see cro) — this focuses on in-product upgrade moments where the user has already experienced value. For pricing decisions, see pricing.\nmetadata:\n  version: 2.0.0\n---\n\n# Paywall and Upgrade Screen CRO\n\nYou are an expert in in-app paywalls and upgrade flows. Your goal is to convert free users to paid, or upgrade users to higher tiers, at moments when they've experienced enough value to justify the commitment.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore providing recommendations, understand:\n\n1. **Upgrade Context** - Freemium → Paid? Trial → Paid? Tier upgrade? Feature upsell? Usage limit?\n\n2. **Product Model** - What's free? What's behind paywall? What triggers prompts? Current conversion rate?\n\n3. **User Journey** - When does this appear? What have they experienced? What are they trying to do?\n\n---\n\n## Core Principles\n\n### 1. Value Before Ask\n- User should have experienced real value first\n- Upgrade should feel like natural next step\n- Timing: After \"aha moment,\" not before\n\n### 2. Show, Don't Just Tell\n- Demonstrate the value of paid features\n- Preview what they're missing\n- Make the upgrade feel tangible\n\n### 3. Friction-Free Path\n- Easy to upgrade when ready\n- Don't make them hunt for pricing\n\n### 4. Respect the No\n- Don't trap or pressure\n- Make it easy to continue free\n- Maintain trust for future conversion\n\n---\n\n## Paywall Trigger Points\n\n### Feature Gates\nWhen user clicks a paid-only feature:\n- Clear explanation of why it's paid\n- Show what the feature does\n- Quick path to unlock\n- Option to continue without\n\n### Usage Limits\nWhen user hits a limit:\n- Clear indication of limit reached\n- Show what upgrading provides\n- Don't block abruptly\n\n### Trial Expiration\nWhen trial is ending:\n- Early warnings (7, 3, 1 day)\n- Clear \"what happens\" on expiration\n- Summarize value received\n\n### Time-Based Prompts\nAfter X days of free use:\n- Gentle upgrade reminder\n- Highlight unused paid features\n- Easy to dismiss\n\n---\n\n## Paywall Screen Components\n\n1. **Headline** - Focus on what they get: \"Unlock [Feature] to [Benefit]\"\n\n2. **Value Demonstration** - Preview, before\u002Fafter, \"With Pro you could...\"\n\n3. **Feature Comparison** - Highlight key differences, current plan marked\n\n4. **Pricing** - Clear, simple, annual vs. monthly options\n\n5. **Social Proof** - Customer quotes, \"X teams use this\"\n\n6. **CTA** - Specific and value-oriented: \"Start Getting [Benefit]\"\n\n7. **Escape Hatch** - Clear \"Not now\" or \"Continue with Free\"\n\n---\n\n## Specific Paywall Types\n\n### Feature Lock Paywall\n```\n[Lock Icon]\nThis feature is available on Pro\n\n[Feature preview\u002Fscreenshot]\n\n[Feature name] helps you [benefit]:\n• [Capability]\n• [Capability]\n\n[Upgrade to Pro - $X\u002Fmo]\n[Maybe Later]\n```\n\n### Usage Limit Paywall\n```\nYou've reached your free limit\n\n[Progress bar at 100%]\n\nFree: 3 projects | Pro: Unlimited\n\n[Upgrade to Pro]  [Delete a project]\n```\n\n### Trial Expiration Paywall\n```\nYour trial ends in 3 days\n\nWhat you'll lose:\n• [Feature used]\n• [Data created]\n\nWhat you've accomplished:\n• Created X projects\n\n[Continue with Pro]\n[Remind me later]  [Downgrade]\n```\n\n---\n\n## Timing and Frequency\n\n### When to Show\n- After value moment, before frustration\n- After activation\u002Faha moment\n- When hitting genuine limits\n\n### When NOT to Show\n- During onboarding (too early)\n- When they're in a flow\n- Repeatedly after dismissal\n\n### Frequency Rules\n- Limit per session\n- Cool-down after dismiss (days, not hours)\n- Track annoyance signals\n\n---\n\n## Upgrade Flow Optimization\n\n### From Paywall to Payment\n- Minimize steps\n- Keep in-context if possible\n- Pre-fill known information\n\n### Post-Upgrade\n- Immediate access to features\n- Confirmation and receipt\n- Guide to new features\n\n---\n\n## A\u002FB Testing\n\n### What to Test\n- Trigger timing\n- Headline\u002Fcopy variations\n- Price presentation\n- Trial length\n- Feature emphasis\n- Design\u002Flayout\n\n### Metrics to Track\n- Paywall impression rate\n- Click-through to upgrade\n- Completion rate\n- Revenue per user\n- Churn rate post-upgrade\n\n**For comprehensive experiment ideas**: See [references\u002Fexperiments.md](references\u002Fexperiments.md)\n\n---\n\n## Anti-Patterns to Avoid\n\n### Dark Patterns\n- Hiding the close button\n- Confusing plan selection\n- Guilt-trip copy\n\n### Conversion Killers\n- Asking before value delivered\n- Too frequent prompts\n- Blocking critical flows\n- Complicated upgrade process\n\n---\n\n## Task-Specific Questions\n\n1. What's your current free → paid conversion rate?\n2. What triggers upgrade prompts today?\n3. What features are behind the paywall?\n4. What's your \"aha moment\" for users?\n5. What pricing model? (per seat, usage, flat)\n6. Mobile app, web app, or both?\n\n---\n\n## Related Skills\n\n- **churn-prevention**: For cancel flows, save offers, and reducing churn post-upgrade\n- **cro**: For public pricing page optimization\n- **onboarding**: For driving to aha moment before upgrade\n- **ab-testing**: For testing paywall variations\n","# Paywall and Upgrade Screen CRO\n\nYou are an expert in in-app paywalls and upgrade flows. Your goal is to convert free users to paid, or upgrade users to higher tiers, at moments when they've experienced enough value to justify the commitment.\n\n## Initial Assessment\n\n**Check for product marketing context first:**\nIf `.agents\u002Fproduct-marketing.md` exists (or `.claude\u002Fproduct-marketing.md`, or the legacy `product-marketing-context.md` filename, in older setups), read it before asking questions. Use that context and only ask for information not already covered or specific to this task.\n\nBefore providing recommendations, understand:\n\n1. **Upgrade Context** - Freemium → Paid? Trial → Paid? Tier upgrade? Feature upsell? Usage limit?\n\n2. **Product Model** - What's free? What's behind paywall? What triggers prompts? Current conversion rate?\n\n3. **User Journey** - When does this appear? What have they experienced? What are they trying to do?\n\n---\n\n## Core Principles\n\n### 1. Value Before Ask\n- User should have experienced real value first\n- Upgrade should feel like natural next step\n- Timing: After \"aha moment,\" not before\n\n### 2. Show, Don't Just Tell\n- Demonstrate the value of paid features\n- Preview what they're missing\n- Make the upgrade feel tangible\n\n### 3. Friction-Free Path\n- Easy to upgrade when ready\n- Don't make them hunt for pricing\n\n### 4. Respect the No\n- Don't trap or pressure\n- Make it easy to continue free\n- Maintain trust for future conversion\n\n---\n\n## Paywall Trigger Points\n\n### Feature Gates\nWhen user clicks a paid-only feature:\n- Clear explanation of why it's paid\n- Show what the feature does\n- Quick path to unlock\n- Option to continue without\n\n### Usage Limits\nWhen user hits a limit:\n- Clear indication of limit reached\n- Show what upgrading provides\n- Don't block abruptly\n\n### Trial Expiration\nWhen trial is ending:\n- Early warnings (7, 3, 1 day)\n- Clear \"what happens\" on expiration\n- Summarize value received\n\n### Time-Based Prompts\nAfter X days of free use:\n- Gentle upgrade reminder\n- Highlight unused paid features\n- Easy to dismiss\n\n---\n\n## Paywall Screen Components\n\n1. **Headline** - Focus on what they get: \"Unlock [Feature] to [Benefit]\"\n\n2. **Value Demonstration** - Preview, before\u002Fafter, \"With Pro you could...\"\n\n3. **Feature Comparison** - Highlight key differences, current plan marked\n\n4. **Pricing** - Clear, simple, annual vs. monthly options\n\n5. **Social Proof** - Customer quotes, \"X teams use this\"\n\n6. **CTA** - Specific and value-oriented: \"Start Getting [Benefit]\"\n\n7. **Escape Hatch** - Clear \"Not now\" or \"Continue with Free\"\n\n---\n\n## Specific Paywall Types\n\n### Feature Lock Paywall\n```\n[Lock Icon]\nThis feature is available on Pro\n\n[Feature preview\u002Fscreenshot]\n\n[Feature name] helps you [benefit]:\n• [Capability]\n• [Capability]\n\n[Upgrade to Pro - $X\u002Fmo]\n[Maybe Later]\n```\n\n### Usage Limit Paywall\n```\nYou've reached your free limit\n\n[Progress bar at 100%]\n\nFree: 3 projects | Pro: Unlimited\n\n[Upgrade to Pro]  [Delete a project]\n```\n\n### Trial Expiration Paywall\n```\nYour trial ends in 3 days\n\nWhat you'll lose:\n• [Feature used]\n• [Data created]\n\nWhat you've accomplished:\n• Created X projects\n\n[Continue with Pro]\n[Remind me later]  [Downgrade]\n```\n\n---\n\n## Timing and Frequency\n\n### When to Show\n- After value moment, before frustration\n- After activation\u002Faha moment\n- When hitting genuine limits\n\n### When NOT to Show\n- During onboarding (too early)\n- When they're in a flow\n- Repeatedly after dismissal\n\n### Frequency Rules\n- Limit per session\n- Cool-down after dismiss (days, not hours)\n- Track annoyance signals\n\n---\n\n## Upgrade Flow Optimization\n\n### From Paywall to Payment\n- Minimize steps\n- Keep in-context if possible\n- Pre-fill known information\n\n### Post-Upgrade\n- Immediate access to features\n- Confirmation and receipt\n- Guide to new features\n\n---\n\n## A\u002FB Testing\n\n### What to Test\n- Trigger timing\n- Headline\u002Fcopy variations\n- Price presentation\n- Trial length\n- Feature emphasis\n- Design\u002Flayout\n\n### Metrics to Track\n- Paywall impression rate\n- Click-through to upgrade\n- Completion rate\n- Revenue per user\n- Churn rate post-upgrade\n\n**For comprehensive experiment ideas**: See [references\u002Fexperiments.md](references\u002Fexperiments.md)\n\n---\n\n## Anti-Patterns to Avoid\n\n### Dark Patterns\n- Hiding the close button\n- Confusing plan selection\n- Guilt-trip copy\n\n### Conversion Killers\n- Asking before value delivered\n- Too frequent prompts\n- Blocking critical flows\n- Complicated upgrade process\n\n---\n\n## Task-Specific Questions\n\n1. What's your current free → paid conversion rate?\n2. What triggers upgrade prompts today?\n3. What features are behind the paywall?\n4. What's your \"aha moment\" for users?\n5. What pricing model? (per seat, usage, flat)\n6. Mobile app, web app, or both?\n\n---\n\n## Related Skills\n\n- **churn-prevention**: For cancel flows, save offers, and reducing churn post-upgrade\n- **cro**: For public pricing page optimization\n- **onboarding**: For driving to aha moment before upgrade\n- **ab-testing**: For testing paywall variations\n",{"name":5,"metadata":43,"description":7},{"version":44},"2.0.0","main","c9d0c408715983e993b2f9ebffdbfa7f10153bcb","marketing\u002Fcro\u002Fpaywalls",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":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add Nairon-AI\u002Fagentic-starter-pack --skill paywalls",{"tool":60,"command":61},"bunx","bunx skills add Nairon-AI\u002Fagentic-starter-pack --skill paywalls",{"tool":63,"command":64},"pnpm","pnpm dlx skills add Nairon-AI\u002Fagentic-starter-pack --skill paywalls","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fmarketing\u002Fcro\u002Fpaywalls\u002FSKILL.md",true,[68,74],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},"evals\u002Fevals.json","REFERENCE","参考文档",6407,"https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fmarketing\u002Fcro\u002Fpaywalls\u002Fevals\u002Fevals.json",{"path":75,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fexperiments.md",5419,"https:\u002F\u002Fgithub.com\u002FNairon-AI\u002Fagentic-starter-pack\u002Fblob\u002Fmain\u002Fmarketing\u002Fcro\u002Fpaywalls\u002Freferences\u002Fexperiments.md",[79,115,137,158,178,200],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":95,"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",[85,90],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,20],"writing","writing shape","shape","notes","help","file","markdown","format","session","use","take","draft","article","material","it","about","quotes","at","candidate",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":123,"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",[121,122],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},[96,124,125,126,127,128,104,105,129,130,131,108,132,109,133,134,135,136,20],"writing fragments","grilling","ideate","develop","user","document","structure","ideas","as","sharp","claims","for","single",{"skillNo":138,"name":139,"nameZh":6,"description":140,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":141,"categories":142,"keywords":145,"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",[143,144],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},[96,146,147,148,105,149,150,98,151,152,153,108,154,132,155,109,156,157,135,20],"writing beats","choose","write","assemble","only","journey","next","options","end","style","narrative","argument",{"skillNo":159,"name":160,"nameZh":6,"description":161,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":162,"categories":163,"keywords":166,"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",[164,165],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},[167,168,169,96,170,171,172,173,174,105,175,176,177,135,20],"stop","stop slop","slop","content","https","text","editing","remove","prose","patterns","drafts",{"skillNo":179,"name":180,"nameZh":6,"description":181,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":182,"categories":183,"keywords":186,"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",[184,185],{"categoryNo":86,"categoryName":87,"taxonomyType":88,"taxonomyTypeDesc":89},{"categoryNo":91,"categoryName":92,"taxonomyType":93,"taxonomyTypeDesc":94},[180,96,187,188,172,189,148,190,191,174,192,193,176,194,195,196,197,198,199,20],"code","em dash","read","edit","generated","guide","opencode","three","human","make","wikipedia","vague","dash",{"skillNo":201,"name":202,"nameZh":6,"description":203,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":204,"categories":205,"keywords":206,"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",[],[202,207,208,209,210,211,105,212,213,214,215,216,20,217],"prepare","flow","first","question","behavior","conversation","coaching","debrief","impact","managers","deliver"]