[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NXZ774TAY5VC4RSSJE2FS7":3,"skill-same:01M6NXZ774TAY5VC4RSSJE2FS7":97},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":48,"commitSha":49,"skillDirectory":50,"forksCount":51,"repositoryHtmlUrl":52,"repositoryHomepageUrl":6,"ownerHtmlUrl":53,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":54,"install":55,"resources":68},"01M6NXZ774TAY5VC4RSSJE2FS7","x-twitter-growth",null,"X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","mattonweb\u002Fai-assistant-foundry","mattonweb","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F2309734?v=4","01M6NQYCY846TKYN2ZCRS71WQ7","Matt Johnson","01M6NQYD2NPAQEFVD8TW9W0SVX",1,"MIT","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmarketing-general\u002Falirezarezvani\u002Fmarketing-skill\u002Fx-twitter-growth\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"twitter","x twitter growth","growth","threads","competitive intelligence","grow","mechanics","growth engine","viral","intelligence","social","optimize","write","analyze","competitors","web search","marketing","plan","analyzing","search","2026-11-10 10:12:30",false,"---\nname: \"x-twitter-growth\"\ndescription: \"X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.\"\nlicense: MIT\nmetadata:\n  version: 1.0.0\n  author: Alireza Rezvani\n  category: marketing\n  updated: 2026-03-10\n---\n\n# X\u002FTwitter Growth Engine\n\nX-specific growth skill. For general social media content across platforms, see `social-content`. For social strategy and calendar planning, see `social-media-manager`. This skill goes deep on X.\n\n## When to Use This vs Other Skills\n\n| Need | Use |\n|------|-----|\n| Write a tweet or thread | **This skill** |\n| Plan content across LinkedIn + X + Instagram | social-content |\n| Analyze engagement metrics across platforms | social-media-analyzer |\n| Build overall social strategy | social-media-manager |\n| X-specific growth, algorithm, competitive intel | **This skill** |\n\n---\n\n## Step 1 — Profile Audit\n\nBefore any growth work, audit the current X presence. Run `scripts\u002Fprofile_auditor.py` with the handle, or manually assess:\n\n### Bio Checklist\n- [ ] Clear value proposition in first line (who you help + how)\n- [ ] Specific niche — not \"entrepreneur | thinker | builder\"\n- [ ] Social proof element (followers, title, metric, brand)\n- [ ] CTA or link (newsletter, product, site)\n- [ ] No hashtags in bio (signals amateur)\n\n### Pinned Tweet\n- [ ] Exists and is less than 30 days old\n- [ ] Showcases best work or strongest hook\n- [ ] Has clear CTA (follow, subscribe, read)\n\n### Recent Activity (last 30 posts)\n- [ ] Posting frequency: minimum 1x\u002Fday, ideal 3-5x\u002Fday\n- [ ] Mix of formats: tweets, threads, replies, quotes\n- [ ] Reply ratio: >30% of activity should be replies\n- [ ] Engagement trend: improving, flat, or declining\n\nRun: `python3 scripts\u002Fprofile_auditor.py --handle @username`\n\n---\n\n## Step 2 — Competitive Intelligence\n\nResearch competitors and successful accounts in your niche using web search.\n\n### Process\n1. Search `site:x.com \"topic\" min_faves:100` via Brave to find high-performing content\n2. Identify 5-10 accounts in your niche with strong engagement\n3. For each, analyze: posting frequency, content types, hook patterns, engagement rates\n4. Run: `python3 scripts\u002Fcompetitor_analyzer.py --handles @acc1 @acc2 @acc3`\n\n### What to Extract\n- **Hook patterns** — How do top posts start? Question? Bold claim? Statistic?\n- **Content themes** — What 3-5 topics get the most engagement?\n- **Format mix** — Ratio of tweets vs threads vs replies vs quotes\n- **Posting times** — When do their best posts go out?\n- **Engagement triggers** — What makes people reply vs like vs retweet?\n\n---\n\n## Step 3 — Content Creation\n\n### Tweet Types (ordered by growth impact)\n\n#### 1. Threads (highest reach, highest follow conversion)\n```\nStructure:\n- Tweet 1: Hook — must stop the scroll in \u003C7 words\n- Tweet 2: Context or promise (\"Here's what I learned:\")\n- Tweets 3-N: One idea per tweet, each standalone-worthy\n- Final tweet: Summary + explicit CTA (\"Follow @handle for more\")\n- Reply to tweet 1: Restate hook + \"Follow for more [topic]\"\n\nRules:\n- 5-12 tweets optimal (under 5 feels thin, over 12 loses people)\n- Each tweet should make sense if read alone\n- Use line breaks for readability\n- No tweet should be a wall of text (3-4 lines max)\n- Number the tweets or use \"↓\" in tweet 1\n```\n\n#### 2. Atomic Tweets (breadth, impression farming)\n```\nFormats that work:\n- Observation: \"[Thing] is underrated. Here's why:\"\n- Listicle: \"10 tools I use daily:\\n\\n1. X — for Y\"\n- Contrarian: \"Unpopular opinion: [statement]\"\n- Lesson: \"I [did X] for [time]. Biggest lesson:\"\n- Framework: \"[Concept] explained in 30 seconds:\"\n\nRules:\n- Under 200 characters gets more engagement\n- One idea per tweet\n- No links in tweet body (kills reach — put link in reply)\n- Question tweets drive replies (algorithm loves replies)\n```\n\n#### 3. Quote Tweets (authority building)\n```\nFormula: Original tweet + your unique take\n- Add data the original missed\n- Provide counterpoint or nuance\n- Share personal experience that validates\u002Fcontradicts\n- Never just say \"This\" or \"So true\"\n```\n\n#### 4. Replies (network growth, fastest path to visibility)\n```\nStrategy:\n- Reply to accounts 2-10x your size\n- Add genuine value, not \"great post!\"\n- Be first to reply on accounts with large audiences\n- Your reply IS your content — make it tweet-worthy\n- Controversial\u002Finsightful replies get quote-tweeted (free reach)\n```\n\nRun: `python3 scripts\u002Ftweet_composer.py --type thread --topic \"your topic\" --audience \"your audience\"`\n\n---\n\n## Step 4 — Algorithm Mechanics\n\n### What X rewards (2025-2026)\n| Signal | Weight | Action |\n|--------|--------|--------|\n| Replies received | Very high | Write reply-worthy content (questions, debates) |\n| Time spent reading | High | Threads, longer tweets with line breaks |\n| Profile visits from tweet | High | Curiosity gaps, tease expertise |\n| Bookmarks | High | Tactical, save-worthy content (lists, frameworks) |\n| Retweets\u002FQuotes | Medium | Shareable insights, bold takes |\n| Likes | Low-medium | Easy agreement, relatable content |\n| Link clicks | Low (penalized) | Never put links in tweet body — use reply |\n\n### What kills reach\n- Links in tweet body (put in first reply instead)\n- Editing tweets within 30 min of posting\n- Posting and immediately going offline (no early engagement)\n- More than 2 hashtags\n- Tagging people who don't engage back\n- Threads with inconsistent quality (one weak tweet tanks the whole thread)\n\n### Optimal Posting Cadence\n| Account size | Tweets\u002Fday | Threads\u002Fweek | Replies\u002Fday |\n|-------------|------------|--------------|-------------|\n| \u003C 1K followers | 2-3 | 1-2 | 10-20 |\n| 1K-10K | 3-5 | 2-3 | 5-15 |\n| 10K-50K | 3-7 | 2-4 | 5-10 |\n| 50K+ | 2-5 | 1-3 | 5-10 |\n\n---\n\n## Step 5 — Growth Playbook\n\n### Week 1-2: Foundation\n1. Optimize bio and pinned tweet (Step 1)\n2. Identify 20 accounts in your niche to engage with daily\n3. Reply 10-20 times per day to larger accounts (genuine value only)\n4. Post 2-3 atomic tweets per day testing different formats\n5. Publish 1 thread\n\n### Week 3-4: Pattern Recognition\n1. Review what formats got most engagement\n2. Double down on top 2 content formats\n3. Increase to 3-5 posts per day\n4. Publish 2-3 threads per week\n5. Start quote-tweeting relevant content daily\n\n### Month 2+: Scale\n1. Develop 3-5 recurring content series (e.g., \"Friday Framework\")\n2. Cross-pollinate: repurpose threads as LinkedIn posts, newsletter content\n3. Build reply relationships with 5-10 accounts your size (mutual engagement)\n4. Experiment with spaces\u002Faudio if relevant to niche\n5. Run: `python3 scripts\u002Fgrowth_tracker.py --handle @username --period 30d`\n\n---\n\n## Step 6 — Content Calendar Generation\n\nRun: `python3 scripts\u002Fcontent_planner.py --niche \"your niche\" --frequency 5 --weeks 2`\n\nGenerates a 2-week posting plan with:\n- Daily tweet topics with hook suggestions\n- Thread outlines (2-3 per week)\n- Reply targets (accounts to engage with)\n- Optimal posting times based on niche\n\n---\n\n## Scripts\n\n| Script | Purpose |\n|--------|---------|\n| `scripts\u002Fprofile_auditor.py` | Audit X profile: bio, pinned, activity patterns |\n| `scripts\u002Ftweet_composer.py` | Generate tweets\u002Fthreads with hook patterns |\n| `scripts\u002Fcompetitor_analyzer.py` | Analyze competitor accounts via web search |\n| `scripts\u002Fcontent_planner.py` | Generate weekly\u002Fmonthly content calendars |\n| `scripts\u002Fgrowth_tracker.py` | Track follower growth and engagement trends |\n\n## Common Pitfalls\n\n1. **Posting links directly** — Always put links in the first reply, never in the tweet body\n2. **Thread tweet 1 is weak** — If the hook doesn't stop scrolling, nothing else matters\n3. **Inconsistent posting** — Algorithm rewards daily consistency over occasional bangers\n4. **Only broadcasting** — Replies and engagement are 50%+ of growth, not just posting\n5. **Generic bio** — \"Helping people do things\" tells nobody anything\n6. **Copying formats without adapting** — What works for tech Twitter doesn't work for marketing Twitter\n\n## Related Skills\n\n- `social-content` — Multi-platform content creation\n- `social-media-manager` — Overall social strategy\n- `social-media-analyzer` — Cross-platform analytics\n- `content-production` — Long-form content that feeds X threads\n- `copywriting` — Headline and hook writing techniques\n","# X\u002FTwitter Growth Engine\n\nX-specific growth skill. For general social media content across platforms, see `social-content`. For social strategy and calendar planning, see `social-media-manager`. This skill goes deep on X.\n\n## When to Use This vs Other Skills\n\n| Need | Use |\n|------|-----|\n| Write a tweet or thread | **This skill** |\n| Plan content across LinkedIn + X + Instagram | social-content |\n| Analyze engagement metrics across platforms | social-media-analyzer |\n| Build overall social strategy | social-media-manager |\n| X-specific growth, algorithm, competitive intel | **This skill** |\n\n---\n\n## Step 1 — Profile Audit\n\nBefore any growth work, audit the current X presence. Run `scripts\u002Fprofile_auditor.py` with the handle, or manually assess:\n\n### Bio Checklist\n- [ ] Clear value proposition in first line (who you help + how)\n- [ ] Specific niche — not \"entrepreneur | thinker | builder\"\n- [ ] Social proof element (followers, title, metric, brand)\n- [ ] CTA or link (newsletter, product, site)\n- [ ] No hashtags in bio (signals amateur)\n\n### Pinned Tweet\n- [ ] Exists and is less than 30 days old\n- [ ] Showcases best work or strongest hook\n- [ ] Has clear CTA (follow, subscribe, read)\n\n### Recent Activity (last 30 posts)\n- [ ] Posting frequency: minimum 1x\u002Fday, ideal 3-5x\u002Fday\n- [ ] Mix of formats: tweets, threads, replies, quotes\n- [ ] Reply ratio: >30% of activity should be replies\n- [ ] Engagement trend: improving, flat, or declining\n\nRun: `python3 scripts\u002Fprofile_auditor.py --handle @username`\n\n---\n\n## Step 2 — Competitive Intelligence\n\nResearch competitors and successful accounts in your niche using web search.\n\n### Process\n1. Search `site:x.com \"topic\" min_faves:100` via Brave to find high-performing content\n2. Identify 5-10 accounts in your niche with strong engagement\n3. For each, analyze: posting frequency, content types, hook patterns, engagement rates\n4. Run: `python3 scripts\u002Fcompetitor_analyzer.py --handles @acc1 @acc2 @acc3`\n\n### What to Extract\n- **Hook patterns** — How do top posts start? Question? Bold claim? Statistic?\n- **Content themes** — What 3-5 topics get the most engagement?\n- **Format mix** — Ratio of tweets vs threads vs replies vs quotes\n- **Posting times** — When do their best posts go out?\n- **Engagement triggers** — What makes people reply vs like vs retweet?\n\n---\n\n## Step 3 — Content Creation\n\n### Tweet Types (ordered by growth impact)\n\n#### 1. Threads (highest reach, highest follow conversion)\n```\nStructure:\n- Tweet 1: Hook — must stop the scroll in \u003C7 words\n- Tweet 2: Context or promise (\"Here's what I learned:\")\n- Tweets 3-N: One idea per tweet, each standalone-worthy\n- Final tweet: Summary + explicit CTA (\"Follow @handle for more\")\n- Reply to tweet 1: Restate hook + \"Follow for more [topic]\"\n\nRules:\n- 5-12 tweets optimal (under 5 feels thin, over 12 loses people)\n- Each tweet should make sense if read alone\n- Use line breaks for readability\n- No tweet should be a wall of text (3-4 lines max)\n- Number the tweets or use \"↓\" in tweet 1\n```\n\n#### 2. Atomic Tweets (breadth, impression farming)\n```\nFormats that work:\n- Observation: \"[Thing] is underrated. Here's why:\"\n- Listicle: \"10 tools I use daily:\\n\\n1. X — for Y\"\n- Contrarian: \"Unpopular opinion: [statement]\"\n- Lesson: \"I [did X] for [time]. Biggest lesson:\"\n- Framework: \"[Concept] explained in 30 seconds:\"\n\nRules:\n- Under 200 characters gets more engagement\n- One idea per tweet\n- No links in tweet body (kills reach — put link in reply)\n- Question tweets drive replies (algorithm loves replies)\n```\n\n#### 3. Quote Tweets (authority building)\n```\nFormula: Original tweet + your unique take\n- Add data the original missed\n- Provide counterpoint or nuance\n- Share personal experience that validates\u002Fcontradicts\n- Never just say \"This\" or \"So true\"\n```\n\n#### 4. Replies (network growth, fastest path to visibility)\n```\nStrategy:\n- Reply to accounts 2-10x your size\n- Add genuine value, not \"great post!\"\n- Be first to reply on accounts with large audiences\n- Your reply IS your content — make it tweet-worthy\n- Controversial\u002Finsightful replies get quote-tweeted (free reach)\n```\n\nRun: `python3 scripts\u002Ftweet_composer.py --type thread --topic \"your topic\" --audience \"your audience\"`\n\n---\n\n## Step 4 — Algorithm Mechanics\n\n### What X rewards (2025-2026)\n| Signal | Weight | Action |\n|--------|--------|--------|\n| Replies received | Very high | Write reply-worthy content (questions, debates) |\n| Time spent reading | High | Threads, longer tweets with line breaks |\n| Profile visits from tweet | High | Curiosity gaps, tease expertise |\n| Bookmarks | High | Tactical, save-worthy content (lists, frameworks) |\n| Retweets\u002FQuotes | Medium | Shareable insights, bold takes |\n| Likes | Low-medium | Easy agreement, relatable content |\n| Link clicks | Low (penalized) | Never put links in tweet body — use reply |\n\n### What kills reach\n- Links in tweet body (put in first reply instead)\n- Editing tweets within 30 min of posting\n- Posting and immediately going offline (no early engagement)\n- More than 2 hashtags\n- Tagging people who don't engage back\n- Threads with inconsistent quality (one weak tweet tanks the whole thread)\n\n### Optimal Posting Cadence\n| Account size | Tweets\u002Fday | Threads\u002Fweek | Replies\u002Fday |\n|-------------|------------|--------------|-------------|\n| \u003C 1K followers | 2-3 | 1-2 | 10-20 |\n| 1K-10K | 3-5 | 2-3 | 5-15 |\n| 10K-50K | 3-7 | 2-4 | 5-10 |\n| 50K+ | 2-5 | 1-3 | 5-10 |\n\n---\n\n## Step 5 — Growth Playbook\n\n### Week 1-2: Foundation\n1. Optimize bio and pinned tweet (Step 1)\n2. Identify 20 accounts in your niche to engage with daily\n3. Reply 10-20 times per day to larger accounts (genuine value only)\n4. Post 2-3 atomic tweets per day testing different formats\n5. Publish 1 thread\n\n### Week 3-4: Pattern Recognition\n1. Review what formats got most engagement\n2. Double down on top 2 content formats\n3. Increase to 3-5 posts per day\n4. Publish 2-3 threads per week\n5. Start quote-tweeting relevant content daily\n\n### Month 2+: Scale\n1. Develop 3-5 recurring content series (e.g., \"Friday Framework\")\n2. Cross-pollinate: repurpose threads as LinkedIn posts, newsletter content\n3. Build reply relationships with 5-10 accounts your size (mutual engagement)\n4. Experiment with spaces\u002Faudio if relevant to niche\n5. Run: `python3 scripts\u002Fgrowth_tracker.py --handle @username --period 30d`\n\n---\n\n## Step 6 — Content Calendar Generation\n\nRun: `python3 scripts\u002Fcontent_planner.py --niche \"your niche\" --frequency 5 --weeks 2`\n\nGenerates a 2-week posting plan with:\n- Daily tweet topics with hook suggestions\n- Thread outlines (2-3 per week)\n- Reply targets (accounts to engage with)\n- Optimal posting times based on niche\n\n---\n\n## Scripts\n\n| Script | Purpose |\n|--------|---------|\n| `scripts\u002Fprofile_auditor.py` | Audit X profile: bio, pinned, activity patterns |\n| `scripts\u002Ftweet_composer.py` | Generate tweets\u002Fthreads with hook patterns |\n| `scripts\u002Fcompetitor_analyzer.py` | Analyze competitor accounts via web search |\n| `scripts\u002Fcontent_planner.py` | Generate weekly\u002Fmonthly content calendars |\n| `scripts\u002Fgrowth_tracker.py` | Track follower growth and engagement trends |\n\n## Common Pitfalls\n\n1. **Posting links directly** — Always put links in the first reply, never in the tweet body\n2. **Thread tweet 1 is weak** — If the hook doesn't stop scrolling, nothing else matters\n3. **Inconsistent posting** — Algorithm rewards daily consistency over occasional bangers\n4. **Only broadcasting** — Replies and engagement are 50%+ of growth, not just posting\n5. **Generic bio** — \"Helping people do things\" tells nobody anything\n6. **Copying formats without adapting** — What works for tech Twitter doesn't work for marketing Twitter\n\n## Related Skills\n\n- `social-content` — Multi-platform content creation\n- `social-media-manager` — Overall social strategy\n- `social-media-analyzer` — Cross-platform analytics\n- `content-production` — Long-form content that feeds X threads\n- `copywriting` — Headline and hook writing techniques\n",{"name":5,"license":15,"metadata":44,"description":7},{"author":45,"updated":46,"version":47,"category":35},"Alireza Rezvani",1773100800000,"1.0.0","main","d8518247cb8ab8b2dac57a6be33543ffd23b97c5","marketing-general\u002Falirezarezvani\u002Fmarketing-skill\u002Fx-twitter-growth",0,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry","https:\u002F\u002Fgithub.com\u002Fmattonweb","2026-05-29 08:42:23",{"source":8,"skillName":5,"commands":56,"prompt":66,"zipAvailable":67},[57,60,63],{"tool":58,"command":59},"npx","npx skills add mattonweb\u002Fai-assistant-foundry --skill x-twitter-growth",{"tool":61,"command":62},"bunx","bunx skills add mattonweb\u002Fai-assistant-foundry --skill x-twitter-growth",{"tool":64,"command":65},"pnpm","pnpm dlx skills add mattonweb\u002Fai-assistant-foundry --skill x-twitter-growth","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmarketing-general\u002Falirezarezvani\u002Fmarketing-skill\u002Fx-twitter-growth\u002FSKILL.md",true,[69,75,81,85,89,93],{"path":70,"resourceType":71,"resourceTypeDesc":72,"sizeBytes":73,"sourceHtmlUrl":74},"references\u002Falgorithm-signals.md","REFERENCE","参考文档",2824,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmarketing-general\u002Falirezarezvani\u002Fmarketing-skill\u002Fx-twitter-growth\u002Freferences\u002Falgorithm-signals.md",{"path":76,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":79,"sourceHtmlUrl":80},"scripts\u002Fcompetitor_analyzer.py","SCRIPT","脚本",8321,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmarketing-general\u002Falirezarezvani\u002Fmarketing-skill\u002Fx-twitter-growth\u002Fscripts\u002Fcompetitor_analyzer.py",{"path":82,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":83,"sourceHtmlUrl":84},"scripts\u002Fcontent_planner.py",7374,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmarketing-general\u002Falirezarezvani\u002Fmarketing-skill\u002Fx-twitter-growth\u002Fscripts\u002Fcontent_planner.py",{"path":86,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":87,"sourceHtmlUrl":88},"scripts\u002Fgrowth_tracker.py",9912,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmarketing-general\u002Falirezarezvani\u002Fmarketing-skill\u002Fx-twitter-growth\u002Fscripts\u002Fgrowth_tracker.py",{"path":90,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":91,"sourceHtmlUrl":92},"scripts\u002Fprofile_auditor.py",11521,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmarketing-general\u002Falirezarezvani\u002Fmarketing-skill\u002Fx-twitter-growth\u002Fscripts\u002Fprofile_auditor.py",{"path":94,"resourceType":77,"resourceTypeDesc":78,"sizeBytes":95,"sourceHtmlUrl":96},"scripts\u002Ftweet_composer.py",10449,"https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fmarketing-general\u002Falirezarezvani\u002Fmarketing-skill\u002Fx-twitter-growth\u002Fscripts\u002Ftweet_composer.py",[98,135,149,169,189,215],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":102,"categories":103,"keywords":114,"publishedAt":39},"01M6P02DENRHN6KVGYC55FKASJ","writing-clearly-and-concisely","Use when writing prose humans will read—documentation, commit messages, error messages, explanations, reports, or UI text. Applies Strunk's timeless rules for clearer, stronger, more professional writing.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fwriting-clearly-and-concisely\u002FSKILL.md",[104,109],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},"01JBSEEDCAT000000000000018","写作与文案","SCENARIO","使用场景",{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[115,116,117,118,119,120,121,122,123,124,125,126,127,128,129,130,131,132,133,134],"writing clearly and concisely","writing","concisely","text","for","more","timeless","error","professional","prose","reports","use","read","Rules","commit messages","messages","error messages","ui","documentation","commit",{"skillNo":136,"name":137,"nameZh":6,"description":138,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":139,"categories":140,"keywords":141,"publishedAt":39},"01M6P0286HZ8RWMFCCPC8HF7SC","crafting-effective-readmes","Use when writing or improving README files. Not all READMEs are the same — provides templates and guidance matched to your audience and project type.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsoftaworks\u002Fcrafting-effective-readmes\u002FSKILL.md",[],[142,143,116,144,145,126,146,147,148],"crafting effective readmes","README","templates","type","project","guidance","files",{"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":158,"publishedAt":39},"01M6P025A41BBTPWVTZ3GFQVG6","wiki-architect","You are a documentation architect that produces structured wiki catalogues and onboarding guides from codebases.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Fwiki-architect\u002FSKILL.md",[155],{"categoryNo":156,"categoryName":157,"taxonomyType":112,"taxonomyTypeDesc":113},"01JBSEEDCAT000000000000038","人力资源",[159,160,161,162,163,164,165,166,167,168,133],"wiki","architect","wiki architect","unknown","you","documentation architect","guides","structured","community","onboarding",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":175,"publishedAt":39},"01M6P01NSKPXP77NWB4K0PXRK5","readme","You are an expert technical writer creating comprehensive project documentation. Your goal is to write a README.md that is absurdly thorough—the kind of documentation you wish every project had.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fsickn33\u002Freadme\u002FSKILL.md",[],[143,176,177,178,163,179,180,146,181,182,48,183,31,184,185,186,133,187,188],"project documentation","tree","kind","expert","github","wish","writer","goal","technical writer","technical","https","write a readme","safe",{"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":39},"01M6P01GP0NEN8KT3A3SA6ZFVE","ubiquitous-language","Extract a DDD-style ubiquitous language glossary from the current conversation, flagging ambiguities and proposing canonical terms. Saves to UBIQUITOUS_LANGUAGE.md. Use when user wants to define domain terms, build a glossary, harden terminology, create a ubiquitous language, or mentions \"domain model\" or \"DDD\".","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattpocock\u002Fubiquitous-language\u002FSKILL.md",[],[196,197,126,198,199,200,201,202,203,204,205,206,207,208,209,210,211,212,213,214],"ubiquitous language","language","extract","user","glossary","model","terms","ddd","create","build","true","canonical","style","define","harden","domain model","domain","terminology","conversation",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":223,"publishedAt":39},"01M6P01BJBP9XP4TDRT7QD1ZVA","technical-writing-style","Enforce clear, direct writing in software development documents including OKRs, PRDs, tech specs, architecture decision records (ADRs), git commit messages, PR descriptions, READMEs, changelogs, runbooks, incident postmortems, API docs, and onboarding guides. Trigger whenever a user asks to write, edit, revise, or review any of these document types. Also trigger when the user says writing \"sounds like AI\", \"feels robotic\", \"needs polish\", or asks to \"make it sound more natural\" in the context of technical or professional prose. Do not trigger for fiction, poetry, creative writing, academic papers, or legal documents unless the user explicitly asks for a more natural tone.","https:\u002F\u002Fgithub.com\u002Fmattonweb\u002Fai-assistant-foundry\u002Fblob\u002Fmain\u002Fwrite-technical\u002Fmattnebr\u002Ftechnical-writing-style\u002FSKILL.md",[221,222],{"categoryNo":105,"categoryName":106,"taxonomyType":107,"taxonomyTypeDesc":108},{"categoryNo":110,"categoryName":111,"taxonomyType":112,"taxonomyTypeDesc":113},[224,225,208,185,116,226,123,227,228,229,230,231,232,233,234,130,235,236,134,237],"writing style","technical writing style","technical writing","papers","types","runbooks","software development","incident","Poetry","decision","api","documents","architecture","review"]