[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M76V4J65TEPJ4K9NJRYEWVM4":3,"skill-same:01M76V4J65TEPJ4K9NJRYEWVM4":75},{"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":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":35,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M76V4J65TEPJ4K9NJRYEWVM4","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.","lukemcqueen\u002Fsteadfaste-fleet","lukemcqueen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F405240?v=4","01M757MHPAGRXTJAT46SKZP98R","Luke McQueen","01M757MHPZ573KP8DT9GB8SBQ7",4,"MIT","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: x-twitter-growth\nversion: 1.0.0\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.\"\ntriggers:\n  - \"twitter growth\"\n  - \"x growth\"\n  - \"twitter strategy\"\n  - \"x audience growth\"\n---\n\n## When to Use\n\nUse when growing an audience on X\u002FTwitter: writing tweets and threads, optimizing a profile, researching competitors, planning cadence, or analyzing engagement. For multi-platform social content generally, use social-content; this skill adds X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization.\n\n## Workflow\n\n1. **Optimize the profile before any posting.** Four elements, in order:\n   - **Bio:** who you are + who you help + proof, under 160 chars. \"I turn B2B analytics into decisions. Ex-Gartner. Writing the weekly Numbers That Matter.\" beats \"Digital marketing professional.\"\n   - **Pinned post:** one high-performing piece stating your thesis — the first thing visitors read. Refresh when outperformed.\n   - **Header:** reinforces the promise (position, product, or one-line value prop).\n   - **Name & handle:** searchable, matching where the audience looks.\n\n2. **Define 3–5 content pillars.** Each is a recurring topic you can produce indefinitely, tied to the audience's job. Examples: (1) lessons from shipping, (2) decision frameworks, (3) data pulls others won't do, (4) behind-the-scenes. Every post maps to a pillar; none fits = noise.\n\n3. **Write threads with a proven structure:**\n   - **Hook tweet (tweet 1):** a specific, defensible claim or concrete observation — no \"unpopular opinion\" clichés, no vague motivation.\n   - **Insight tweets (middle):** one idea per tweet, one screenshot-able unit. Build step by step; end each with a forward pull (\"the next part is where it gets counterintuitive\").\n   - **Expansion\u002FCTA (final tweet):** summarize the takeaway, invite replies with a specific question, or link the long-form piece it expands.\n   - Keep tweets under 240 characters — room for quote-post commentary.\n\n4. **Set posting cadence.** A sustainable base: 1–3 native posts a day plus 1–2 threads a week. Replies count as posting. Batch-write threads ahead; keep native posts daily between big pieces.\n\n5. **Engage with a reply-first strategy.** Spend as much time replying as posting: answer niche conversations within the first hour (early replies shape a thread's engagement). Quote-post with added value (\"This misses X — here's the version with numbers\"). Replies are how the algorithm finds you; posts are how they stay.\n\n6. **Measure what matters.** Weekly:\n   - **Impressions:** the reach proxy; healthy accounts grow steadily.\n   - **Engagement rate:** (likes + replies + reposts + follows) ÷ impressions. 1–3% is normal; under 1% means weak hooks or a mismatched audience.\n   - **Profile visits → follows:** high visits, low follows = the profile (bio\u002Fpinned) is the leak.\n   - **Reply rate on threads:** the best quality signal — threads that get replies are working.\n\n7. **Choose tactics that age well.** Durable: consistent value, reply-first engagement, teaching threads, real data, niche depth. Penalized or dead: follow-for-follow, engagement pods, bought followers, hashtag stuffing, verbatim copies, substance-free bait. Recommend durable tactics; explain why the cheap ones backfire.\n\n## Pitfalls\n\n- Profile last: posting before bio\u002Fpinned\u002Fheader are set wastes impressions.\n- Threads written as one long paragraph split by ellipses — every tweet must stand alone.\n- Chasing impressions with bait; engagement rate and follows are the real scoreboard.\n- Replying only to big accounts; niche conversations are where an audience actually forms.\n- Copying what worked for others without the context that made it work (authority, timing, audience).\n\n## Scripts\n\nFive no-API helpers under `scripts\u002F` — pure content scaffolding, they emit text\nand never post on your behalf:\n\n- `scripts\u002Fprofile_auditor.py` — audit a profile for growth readiness (bio, pinned post, posting pattern)\n- `scripts\u002Ftweet_composer.py` — compose tweets\u002Fthreads with hook patterns, character counting and thread formatting\n- `scripts\u002Fcontent_planner.py` — build a weekly posting calendar with topic and format mix\n- `scripts\u002Fcompetitor_analyzer.py` — analyse competitor profiles for content strategy and gaps\n- `scripts\u002Fgrowth_tracker.py` — store metric snapshots and calculate growth trends\n\nEach is runnable directly: `python3 scripts\u002Ftweet_composer.py --validate \"\u003Ctext>\"`.\n\n## Verification\n\n- Can a stranger tell what you do, who you help, and why to follow — from bio and pinned post alone?\n- Does every post map to a pillar? Does every thread have hook \u002F insight units \u002F CTA?\n- Are impressions, engagement rate, and follow-through named with a data source (X Analytics or the user's tool)?\n- Could the account survive 2 weeks on scheduled content alone? If not, cadence is too aggressive.\n","## When to Use\n\nUse when growing an audience on X\u002FTwitter: writing tweets and threads, optimizing a profile, researching competitors, planning cadence, or analyzing engagement. For multi-platform social content generally, use social-content; this skill adds X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization.\n\n## Workflow\n\n1. **Optimize the profile before any posting.** Four elements, in order:\n   - **Bio:** who you are + who you help + proof, under 160 chars. \"I turn B2B analytics into decisions. Ex-Gartner. Writing the weekly Numbers That Matter.\" beats \"Digital marketing professional.\"\n   - **Pinned post:** one high-performing piece stating your thesis — the first thing visitors read. Refresh when outperformed.\n   - **Header:** reinforces the promise (position, product, or one-line value prop).\n   - **Name & handle:** searchable, matching where the audience looks.\n\n2. **Define 3–5 content pillars.** Each is a recurring topic you can produce indefinitely, tied to the audience's job. Examples: (1) lessons from shipping, (2) decision frameworks, (3) data pulls others won't do, (4) behind-the-scenes. Every post maps to a pillar; none fits = noise.\n\n3. **Write threads with a proven structure:**\n   - **Hook tweet (tweet 1):** a specific, defensible claim or concrete observation — no \"unpopular opinion\" clichés, no vague motivation.\n   - **Insight tweets (middle):** one idea per tweet, one screenshot-able unit. Build step by step; end each with a forward pull (\"the next part is where it gets counterintuitive\").\n   - **Expansion\u002FCTA (final tweet):** summarize the takeaway, invite replies with a specific question, or link the long-form piece it expands.\n   - Keep tweets under 240 characters — room for quote-post commentary.\n\n4. **Set posting cadence.** A sustainable base: 1–3 native posts a day plus 1–2 threads a week. Replies count as posting. Batch-write threads ahead; keep native posts daily between big pieces.\n\n5. **Engage with a reply-first strategy.** Spend as much time replying as posting: answer niche conversations within the first hour (early replies shape a thread's engagement). Quote-post with added value (\"This misses X — here's the version with numbers\"). Replies are how the algorithm finds you; posts are how they stay.\n\n6. **Measure what matters.** Weekly:\n   - **Impressions:** the reach proxy; healthy accounts grow steadily.\n   - **Engagement rate:** (likes + replies + reposts + follows) ÷ impressions. 1–3% is normal; under 1% means weak hooks or a mismatched audience.\n   - **Profile visits → follows:** high visits, low follows = the profile (bio\u002Fpinned) is the leak.\n   - **Reply rate on threads:** the best quality signal — threads that get replies are working.\n\n7. **Choose tactics that age well.** Durable: consistent value, reply-first engagement, teaching threads, real data, niche depth. Penalized or dead: follow-for-follow, engagement pods, bought followers, hashtag stuffing, verbatim copies, substance-free bait. Recommend durable tactics; explain why the cheap ones backfire.\n\n## Pitfalls\n\n- Profile last: posting before bio\u002Fpinned\u002Fheader are set wastes impressions.\n- Threads written as one long paragraph split by ellipses — every tweet must stand alone.\n- Chasing impressions with bait; engagement rate and follows are the real scoreboard.\n- Replying only to big accounts; niche conversations are where an audience actually forms.\n- Copying what worked for others without the context that made it work (authority, timing, audience).\n\n## Scripts\n\nFive no-API helpers under `scripts\u002F` — pure content scaffolding, they emit text\nand never post on your behalf:\n\n- `scripts\u002Fprofile_auditor.py` — audit a profile for growth readiness (bio, pinned post, posting pattern)\n- `scripts\u002Ftweet_composer.py` — compose tweets\u002Fthreads with hook patterns, character counting and thread formatting\n- `scripts\u002Fcontent_planner.py` — build a weekly posting calendar with topic and format mix\n- `scripts\u002Fcompetitor_analyzer.py` — analyse competitor profiles for content strategy and gaps\n- `scripts\u002Fgrowth_tracker.py` — store metric snapshots and calculate growth trends\n\nEach is runnable directly: `python3 scripts\u002Ftweet_composer.py --validate \"\u003Ctext>\"`.\n\n## Verification\n\n- Can a stranger tell what you do, who you help, and why to follow — from bio and pinned post alone?\n- Does every post map to a pillar? Does every thread have hook \u002F insight units \u002F CTA?\n- Are impressions, engagement rate, and follow-through named with a data source (X Analytics or the user's tool)?\n- Could the account survive 2 weeks on scheduled content alone? If not, cadence is too aggressive.\n",{"name":5,"version":24,"triggers":25,"description":7},"1.0.0",[26,27,28,29],"twitter growth","x growth","twitter strategy","x audience growth","main","6509c2742680f6f230c89044437ab43c0e29d530","skills\u002Fx-twitter-growth",1,"https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet","steadfaste.com","https:\u002F\u002Fgithub.com\u002Flukemcqueen","AI Architect | Building Hermes Cortex: governed multi-agent AI for autonomous software engineering | Enterprise Tech Consultant","2026-11-14 22:33:34",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add lukemcqueen\u002Fsteadfaste-fleet --skill x-twitter-growth",{"tool":45,"command":46},"bunx","bunx skills add lukemcqueen\u002Fsteadfaste-fleet --skill x-twitter-growth",{"tool":48,"command":49},"pnpm","pnpm dlx skills add lukemcqueen\u002Fsteadfaste-fleet --skill x-twitter-growth","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",true,[53,59,63,67,71],{"path":54,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":57,"sourceHtmlUrl":58},"scripts\u002Fcompetitor_analyzer.py","SCRIPT","脚本",8571,"https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002Fscripts\u002Fcompetitor_analyzer.py",{"path":60,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":61,"sourceHtmlUrl":62},"scripts\u002Fcontent_planner.py",7624,"https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002Fscripts\u002Fcontent_planner.py",{"path":64,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":65,"sourceHtmlUrl":66},"scripts\u002Fgrowth_tracker.py",10162,"https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002Fscripts\u002Fgrowth_tracker.py",{"path":68,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":69,"sourceHtmlUrl":70},"scripts\u002Fprofile_auditor.py",11771,"https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002Fscripts\u002Fprofile_auditor.py",{"path":72,"resourceType":55,"resourceTypeDesc":56,"sizeBytes":73,"sourceHtmlUrl":74},"scripts\u002Ftweet_composer.py",10699,"https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002Fscripts\u002Ftweet_composer.py",[76,84,91,98,105,112],{"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":83},"01M7DXY4G8NSVB59K8B6S2AQNP","macbook-linux-maintenance","Legacy MacBook Linux fixes: GPU wedge, reboot hang, thermal.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fmacbook-linux-maintenance\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":83},"01M7DXXYJCXFJ3TGB84ZQ8KFE6","governance-regression-triage","Triage a host's governance issues: what changed.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fgovernance-regression-triage\u002FSKILL.md",[],[],{"skillNo":92,"name":93,"nameZh":6,"description":94,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":83},"01M7DXXSAP1G8FDRJAMXQGBBMK","enforcement-immutability","Use when enforcement files lose their immutable flag.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fenforcement-immutability\u002FSKILL.md",[],[],{"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":104,"publishedAt":83},"01M78SSDQVRYX64Y16X32TC0NS","steadfaste-fleet-repo-deploy","Use when committing to the steadfaste-fleet repo.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fsteadfaste-fleet-repo-deploy\u002FSKILL.md",[],[],{"skillNo":106,"name":107,"nameZh":6,"description":108,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":83},"01M78SS928F3R2RJAYVW4E30CE","steadfaste-fleet-maintenance","Maintain an installed Steadfaste Fleet instance — update both the upstream Hermes Agent and the fleet repo layer, merge diverged histories, sync skills safely, and troubleshoot common issues. Covers the dual-update workflow (hermes update + fleet-update.sh), encrypted brain data backup, mycortex import, and recovery techniques.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Fsteadfaste-fleet-maintenance\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":83},"01M78SP1CHW0T0BWE5ZT6JBPX8","fleet-preflight","DEPRECATED alias — merged into survey-before-action (2026-08-20). Load survey-before-action instead; its \"Repo-Specific Pre-Flight\" section covers git search, Hermes boundary, and deployment verification.","https:\u002F\u002Fgithub.com\u002Flukemcqueen\u002Fsteadfaste-fleet\u002Fblob\u002Fmain\u002Fskills\u002Fdevops\u002Ffleet-preflight\u002FSKILL.md",[],[]]