[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77KXEWMDP9G090DHBQCHWTH":3,"skill-same:01M77KXEWMDP9G090DHBQCHWTH":47},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M77KXEWMDP9G090DHBQCHWTH","linkedin-post-generator",null,"Generate high-quality LinkedIn posts locally from a short prompt, topic, or outline. Use when the user asks to draft, rewrite, or improve a LinkedIn post, headline, or caption, including adding hooks, CTAs, or tailoring tone and length.","Lord1Egypt\u002Fawesome-skill-forge","Lord1Egypt","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F99746359?v=4","01M7592YDNT0XK9WJ0T2MQVPDN","Mohamed Mounir Ali AL Keshita","01M75GRFNHC8VZNWEB8DKDE433",3,"MIT","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fl\u002Flinkedin-post-generator-nivas\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: linkedin-post-generator\ndescription: Generate high-quality LinkedIn posts locally from a short prompt, topic, or outline. Use when the user asks to draft, rewrite, or improve a LinkedIn post, headline, or caption, including adding hooks, CTAs, or tailoring tone and length.\n---\n\n# LinkedIn Post Generator\n\nThis skill helps generate and refine LinkedIn posts **locally on this machine**, without calling the LinkedIn API. The user will copy-paste the final post into LinkedIn manually.\n\n## When to use this skill\n\nUse this skill whenever the user asks for help with:\n\n- Writing a new LinkedIn post from a topic, idea, or outline\n- Rewriting or improving an existing LinkedIn post\n- Adjusting tone (professional, casual, storytelling, technical, etc.)\n- Changing length (short, medium, long \u002F thread-style)\n- Adding hooks, CTAs, or hashtags suitable for LinkedIn\n\nExamples of triggering requests:\n\n- \"Draft a LinkedIn post about my new project in AI\"\n- \"Rewrite this LinkedIn post to be more engaging\"\n- \"Make this post more professional and concise for LinkedIn\"\n- \"Give me 3 hook options for this LinkedIn update\"\n\n## Srinivas-specific optimization\n\nWhen the user is **Kusumanchi Srinivas** (headline mentions SRKR CSE ’25 \u002F Associate ML Engineer @Yanthraa \u002F Research Associate @Li2 Edu):\n\n- Optimize posts for:\n - Growing **reach, followers, likes, comments, and impressions** on a professional audience.\n - Attracting **engineers, founders, recruiters, tech leaders, and ambitious students** across software and AI.\n- Emphasize themes that fit his profile and past posts, without locking into a tiny niche:\n - Software engineering and backend\u002Fsystem design.\n - AI\u002FML and data-driven products.\n - Cloud and modern infrastructure when relevant.\n - Career growth, mindset, and lessons from internships, research, and real projects.\n - Tech leadership, teamwork, and how to think about building products.\n- Avoid:\n - Over-focusing on old “B.Tech student” identity (keep it light if used at all).\n - Internal project names, sprint labels, file names, or code snippets unless explicitly requested.\n\n## Inputs to collect\n\nWhen the user asks for a LinkedIn post, try to clarify these (only ask follow-ups if not obvious):\n\n1. **Goal** of the post (choose or infer):\n - announce (launch, promotion, new role, milestone)\n - share learning (lesson, story, failure, insight)\n - ask (help, feedback, hiring, referrals)\n - promote (product, service, content)\n\n2. **Audience** (e.g. recruiters, engineers, designers, founders, managers, students).\n\n3. **Tone** (default: \"professional but friendly\"):\n - options: professional, friendly, casual, storytelling, technical, inspirational.\n\n4. **Length**:\n - `short` (1–3 paragraphs)\n - `medium` (3–6 paragraphs)\n - `long` (story\u002Fessay-style)\n\n5. **Language** (default: English unless user text suggests another).\n\n6. **Input content**:\n - either a topic\u002Foutline, or an existing draft to improve.\n\nIf the user is being very casual (\"just write something\"), use sensible defaults and do not over-question.\n\n## Workflow\n\nFollow this workflow:\n\n1. **Parse the request**\n - Identify if the user provided: topic only, topic + key points, or a full draft.\n - Infer goal, audience, tone, and length when obvious.\n\n2. **Clarify if needed**\n - Ask at most 1–3 short follow-up questions when critical details are missing.\n - Skip questions if the request is clear enough to produce something useful.\n\n3. **Generate a first draft**\n - Use the `scripts\u002Fgenerate_post.py` helper when available.\n - If script output is missing or script is unavailable, generate directly in the model.\n\n4. **Polish for LinkedIn conventions**\n Ensure the post generally follows these patterns (adapt when user asks otherwise):\n\n - Strong first line (hook) that makes people stop scrolling.\n - Short paragraphs (1–3 lines) and some line breaks for readability.\n - Clear structure: hook → context\u002Fstory → insight\u002Fvalue → CTA (optional).\n - Avoid heavy emoji spam; 0–3 emojis max unless user wants more.\n - Optional light hashtags at the end (2–6), relevant and non-spammy.\n\n5. **Offer variants when helpful**\n - By default, provide **1 main post**.\n - Optionally add:\n - 2–3 alternative hooks, or\n - a shorter \u002F more concise variant,\n when that seems useful or the user asks for \"options\".\n\n6. **Respect user constraints**\n - If the user gives a word\u002Fcharacter limit, target within ~10–15%.\n - Keep or adapt any mandatory phrases, links, or hashtags they specify.\n\n## Helper script: scripts\u002Fgenerate_post.py\n\nIf this repository includes `scripts\u002Fgenerate_post.py`, prefer calling it for deterministic formatting.\n\nExpected behavior (conceptual):\n\n- Input (arguments or stdin JSON):\n - topic \u002F prompt\n - optional: audience, tone, length, language, and any raw draft text\n- Output: a single LinkedIn-ready post on stdout (no extra explanations).\n\nIf the script is missing or fails, fall back to generating the post directly in this agent.\n\n## Style guidelines\n\nWhen generating LinkedIn posts, always optimize for **reach and engagement on a professional audience**, not internal team context.\n\n- **Audience-first**: Assume the reader does *not* know the project, sprint names, or internal file names. Explain in plain language.\n- **Voice**: Clear, confident, and human. Avoid corporate buzzword soup.\n- **Jargon**: Use domain terms only when audience would understand them.\n- **Specifics over vagueness**: Prefer concrete, relatable examples and outcomes (\"faster app, smoother experience\") over internal details (\"Sprint 2, PHASE3_RUNTIME_INTERACTION.md\").\n- **Brevity**: Say what matters in as few words as needed; avoid filler.\n- **Authenticity**: When user shares personal story, preserve their voice and details.\n- **No raw code or private data**: Never paste code, logs, or internal data into the post unless the user explicitly says it’s a code-focused audience.\n- **Hook for attention**: Prioritize strong first lines that make professionals stop scrolling.\n\n## Safety & compliance\n\n- Do **not** fabricate employment history, degrees, or certifications unless explicitly requested as a fictional\u002Fsample post.\n- Avoid discriminatory, harassing, or misleading content.\n- If the user asks for unethical growth-hacking (spammy DMs, fake testimonials, deceptive claims), gently refuse and suggest ethical alternatives.\n\n## Example usages\n\n1. **New post from topic**\n\n> User: \"Write a LinkedIn post announcing I joined ACME as a Senior Data Engineer in Bangalore, excited about building real-time pipelines. Keep it professional and a bit warm.\"\n\nAction:\n- Infer goal: announce new role\n- Audience: professional network, recruiters, colleagues\n- Tone: professional but warm\n- Length: short\u002Fmedium\n- Generate a post with a clear hook and a brief CTA (e.g. \"If you work in data infra, would love to connect\").\n\n2. **Rewrite a draft**\n\n> User: \"Make this more engaging for LinkedIn while keeping the main points: [user draft]\"\n\nAction:\n- Keep all factual claims.\n- Improve hook, structure, and flow.\n- Preserve any required links or hashtags.\n\n3. **Multiple hooks**\n\n> User: \"Give me 5 hook ideas for a LinkedIn post about switching careers from mechanical engineering to data science.\"\n\nAction:\n- Produce 5 strong first-line hook options tailored to LinkedIn.\n","# LinkedIn Post Generator\n\nThis skill helps generate and refine LinkedIn posts **locally on this machine**, without calling the LinkedIn API. The user will copy-paste the final post into LinkedIn manually.\n\n## When to use this skill\n\nUse this skill whenever the user asks for help with:\n\n- Writing a new LinkedIn post from a topic, idea, or outline\n- Rewriting or improving an existing LinkedIn post\n- Adjusting tone (professional, casual, storytelling, technical, etc.)\n- Changing length (short, medium, long \u002F thread-style)\n- Adding hooks, CTAs, or hashtags suitable for LinkedIn\n\nExamples of triggering requests:\n\n- \"Draft a LinkedIn post about my new project in AI\"\n- \"Rewrite this LinkedIn post to be more engaging\"\n- \"Make this post more professional and concise for LinkedIn\"\n- \"Give me 3 hook options for this LinkedIn update\"\n\n## Srinivas-specific optimization\n\nWhen the user is **Kusumanchi Srinivas** (headline mentions SRKR CSE ’25 \u002F Associate ML Engineer @Yanthraa \u002F Research Associate @Li2 Edu):\n\n- Optimize posts for:\n - Growing **reach, followers, likes, comments, and impressions** on a professional audience.\n - Attracting **engineers, founders, recruiters, tech leaders, and ambitious students** across software and AI.\n- Emphasize themes that fit his profile and past posts, without locking into a tiny niche:\n - Software engineering and backend\u002Fsystem design.\n - AI\u002FML and data-driven products.\n - Cloud and modern infrastructure when relevant.\n - Career growth, mindset, and lessons from internships, research, and real projects.\n - Tech leadership, teamwork, and how to think about building products.\n- Avoid:\n - Over-focusing on old “B.Tech student” identity (keep it light if used at all).\n - Internal project names, sprint labels, file names, or code snippets unless explicitly requested.\n\n## Inputs to collect\n\nWhen the user asks for a LinkedIn post, try to clarify these (only ask follow-ups if not obvious):\n\n1. **Goal** of the post (choose or infer):\n - announce (launch, promotion, new role, milestone)\n - share learning (lesson, story, failure, insight)\n - ask (help, feedback, hiring, referrals)\n - promote (product, service, content)\n\n2. **Audience** (e.g. recruiters, engineers, designers, founders, managers, students).\n\n3. **Tone** (default: \"professional but friendly\"):\n - options: professional, friendly, casual, storytelling, technical, inspirational.\n\n4. **Length**:\n - `short` (1–3 paragraphs)\n - `medium` (3–6 paragraphs)\n - `long` (story\u002Fessay-style)\n\n5. **Language** (default: English unless user text suggests another).\n\n6. **Input content**:\n - either a topic\u002Foutline, or an existing draft to improve.\n\nIf the user is being very casual (\"just write something\"), use sensible defaults and do not over-question.\n\n## Workflow\n\nFollow this workflow:\n\n1. **Parse the request**\n - Identify if the user provided: topic only, topic + key points, or a full draft.\n - Infer goal, audience, tone, and length when obvious.\n\n2. **Clarify if needed**\n - Ask at most 1–3 short follow-up questions when critical details are missing.\n - Skip questions if the request is clear enough to produce something useful.\n\n3. **Generate a first draft**\n - Use the `scripts\u002Fgenerate_post.py` helper when available.\n - If script output is missing or script is unavailable, generate directly in the model.\n\n4. **Polish for LinkedIn conventions**\n Ensure the post generally follows these patterns (adapt when user asks otherwise):\n\n - Strong first line (hook) that makes people stop scrolling.\n - Short paragraphs (1–3 lines) and some line breaks for readability.\n - Clear structure: hook → context\u002Fstory → insight\u002Fvalue → CTA (optional).\n - Avoid heavy emoji spam; 0–3 emojis max unless user wants more.\n - Optional light hashtags at the end (2–6), relevant and non-spammy.\n\n5. **Offer variants when helpful**\n - By default, provide **1 main post**.\n - Optionally add:\n - 2–3 alternative hooks, or\n - a shorter \u002F more concise variant,\n when that seems useful or the user asks for \"options\".\n\n6. **Respect user constraints**\n - If the user gives a word\u002Fcharacter limit, target within ~10–15%.\n - Keep or adapt any mandatory phrases, links, or hashtags they specify.\n\n## Helper script: scripts\u002Fgenerate_post.py\n\nIf this repository includes `scripts\u002Fgenerate_post.py`, prefer calling it for deterministic formatting.\n\nExpected behavior (conceptual):\n\n- Input (arguments or stdin JSON):\n - topic \u002F prompt\n - optional: audience, tone, length, language, and any raw draft text\n- Output: a single LinkedIn-ready post on stdout (no extra explanations).\n\nIf the script is missing or fails, fall back to generating the post directly in this agent.\n\n## Style guidelines\n\nWhen generating LinkedIn posts, always optimize for **reach and engagement on a professional audience**, not internal team context.\n\n- **Audience-first**: Assume the reader does *not* know the project, sprint names, or internal file names. Explain in plain language.\n- **Voice**: Clear, confident, and human. Avoid corporate buzzword soup.\n- **Jargon**: Use domain terms only when audience would understand them.\n- **Specifics over vagueness**: Prefer concrete, relatable examples and outcomes (\"faster app, smoother experience\") over internal details (\"Sprint 2, PHASE3_RUNTIME_INTERACTION.md\").\n- **Brevity**: Say what matters in as few words as needed; avoid filler.\n- **Authenticity**: When user shares personal story, preserve their voice and details.\n- **No raw code or private data**: Never paste code, logs, or internal data into the post unless the user explicitly says it’s a code-focused audience.\n- **Hook for attention**: Prioritize strong first lines that make professionals stop scrolling.\n\n## Safety & compliance\n\n- Do **not** fabricate employment history, degrees, or certifications unless explicitly requested as a fictional\u002Fsample post.\n- Avoid discriminatory, harassing, or misleading content.\n- If the user asks for unethical growth-hacking (spammy DMs, fake testimonials, deceptive claims), gently refuse and suggest ethical alternatives.\n\n## Example usages\n\n1. **New post from topic**\n\n> User: \"Write a LinkedIn post announcing I joined ACME as a Senior Data Engineer in Bangalore, excited about building real-time pipelines. Keep it professional and a bit warm.\"\n\nAction:\n- Infer goal: announce new role\n- Audience: professional network, recruiters, colleagues\n- Tone: professional but warm\n- Length: short\u002Fmedium\n- Generate a post with a clear hook and a brief CTA (e.g. \"If you work in data infra, would love to connect\").\n\n2. **Rewrite a draft**\n\n> User: \"Make this more engaging for LinkedIn while keeping the main points: [user draft]\"\n\nAction:\n- Keep all factual claims.\n- Improve hook, structure, and flow.\n- Preserve any required links or hashtags.\n\n3. **Multiple hooks**\n\n> User: \"Give me 5 hook ideas for a LinkedIn post about switching careers from mechanical engineering to data science.\"\n\nAction:\n- Produce 5 strong first-line hook options tailored to LinkedIn.\n",{"name":5,"description":7},"master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Fl\u002Flinkedin-post-generator-nivas",0,"https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge","https:\u002F\u002Fskill-explorer-rho.vercel.app","https:\u002F\u002Fgithub.com\u002FLord1Egypt","Unbreakable. Unstoppable. Unmatched⚡.\r\n Speaker of machine tongues 🤖  | World-builder of decentralized dreams 🌐 | Defender of the digital realm🛡️.","2026-06-10 08:21:01",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill linkedin-post-generator",{"tool":39,"command":40},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill linkedin-post-generator",{"tool":42,"command":43},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill linkedin-post-generator","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fl\u002Flinkedin-post-generator-nivas\u002FSKILL.md",true,[],[48,55,62,69,76,83],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":19},"01M785WKJB99G3STR1NF9NRTJW","youtube-content","YouTube transcripts to summaries, threads, blogs.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fyoutube-content\u002FSKILL.md",[],[],{"skillNo":56,"name":57,"nameZh":6,"description":58,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M785WEFHB0G2S9YA6EPR3H0E","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M785W98EDN4EFJXJPMQEHCRC","touchdesigner-mcp","Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftouchdesigner-mcp\u002FSKILL.md",[],[],{"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":75,"publishedAt":19},"01M785W5S9FP3QBH2V191E025P","test-driven-development","TDD: enforce RED-GREEN-REFACTOR, tests before code.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Ftest-driven-development\u002FSKILL.md",[],[],{"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":19},"01M785W2AS08NSSH9YATCV6FJB","teams-meeting-pipeline","Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fteams-meeting-pipeline\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":19},"01M785VXKW4T34BTP1SCHW1R7F","systematic-debugging","4-phase root cause debugging: understand bugs before fixing.","https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fskills\u002Fsystematic-debugging\u002FSKILL.md",[],[]]