[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77KQRWS12AY2C7TDC4GY9NP":3,"skill-same:01M77KQRWS12AY2C7TDC4GY9NP":48},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":28,"repositoryHtmlUrl":29,"repositoryHomepageUrl":30,"ownerHtmlUrl":31,"ownerBlogUrl":6,"ownerDescription":32,"updatedAt":33,"install":34,"resources":47},"01M77KQRWS12AY2C7TDC4GY9NP","Lead",null,"Qualify, prioritize, and advance sales prospects into the next best action. Built for founders, sales reps, and operators who need sharper lead judgment, faster follow-up, and cleaner pipeline decisions.","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\u002Flead\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: Lead\ndescription: Qualify, prioritize, and advance sales prospects into the next best action. Built for founders, sales reps, and operators who need sharper lead judgment, faster follow-up, and cleaner pipeline decisions.\nversion: 2.1.0\n---\n\n# Lead\n\n> ⚠️ **Scope Notice**  \n> This skill is for **sales lead qualification** only.  \n> It is not for music, medicine, journalism, recruiting, or generic team-role uses of the word \"lead\".\n\nLead is a decision skill for handling commercial prospects with speed, clarity, and discipline.\n\nUse this skill when you need to:\n- evaluate whether a sales lead is worth active pursuit\n- identify what information is still missing\n- determine the next best action\n- write follow-up that moves the conversation forward\n- prevent good leads from dying due to weak process\n\n## Lead vs Prospect\n\nUse **Prospect** before contact.  \nUse **Lead** after engagement begins.\n\n| | Prospect | Lead |\n|---|---|---|\n| **Stage** | Before contact | After engagement |\n| **Question** | \"Is this target worth reaching out to?\" | \"Should I keep pursuing this person?\" |\n| **Input** | Names, profiles, company data, signals | Conversation history, replies, behavior |\n| **Output** | Priority tier + route | Qualification score + next action |\n\nIf there has been no reply, no meeting, and no active interaction yet, the contact may still be better handled by **Prospect**.\n\n## What this skill does\n\nLead helps transform raw prospect information into clear action.\n\nIt can:\n- assess lead quality based on fit, intent, urgency, and authority\n- distinguish real opportunities from vague interest\n- identify blockers, risks, and missing qualification data\n- recommend the next best action for each lead\n- draft follow-up messages that have a reason to exist\n- separate active pursuit, nurture, and deprioritize decisions\n\n## Best use cases\n\n- inbound lead triage\n- outbound reply handling\n- founder-led sales\n- SDR qualification\n- stalled lead diagnosis\n- re-engagement planning\n- next-step planning after discovery calls\n\n## What to provide\n\nUseful input includes:\n- who the lead is\n- company and role\n- source of the lead\n- what they asked for or responded to\n- current pain point\n- timeline, budget, or buying signals\n- last interaction and current status\n\n## What this skill should return\n\nA strong response should usually include:\n\n1. Lead assessment  \n   - hot \u002F warm \u002F cold  \n   - strong fit \u002F unclear fit \u002F weak fit\n\n2. Missing information  \n   - what must be clarified before investing more time\n\n3. Risks or friction  \n   - weak authority\n   - weak urgency\n   - weak problem clarity\n   - weak timing\n   - weak follow-through\n\n4. Next best action  \n   - pursue now\n   - qualify further\n   - nurture\n   - deprioritize\n\n5. Optional follow-up draft  \n   - short\n   - relevant\n   - specific\n   - non-annoying\n\n## Decision principles\n\n- Do not confuse activity with opportunity.\n- Do not treat every lead as pipeline.\n- Do not push unclear leads into active pursuit too early.\n- Preserve momentum when signal is strong.\n- Reduce wasted effort when fit or timing is weak.\n- Always prefer a clear next step over vague optimism.\n\n## Execution Protocol (for AI agents)\n\nWhen user provides lead information, follow this sequence.\n\n### Step 1: Extract context\nParse input for:\n- prospect identity\n- company and role\n- source\n- pain signal\n- engagement level\n- buying context\n- timeline, budget, authority, or competitors if mentioned\n\n### Step 2: Score only from visible evidence\nAssign 0-10 for each dimension using only evidence present in the input.\n\n**Fit Score**\n- ICP match\n- problem-product alignment\n- role relevance\n\n**Intent Score**\n- explicit ask vs passive interest\n- specificity of questions\n- effort already shown\n\n**Urgency Score**\n- timeline mentioned\n- pain severity\n- trigger event or active problem\n\n**Authority Score**\n- decision-maker vs influencer\n- budget control\n- internal champion strength\n\nIf evidence is missing, do not guess. Score conservatively.\n\n### Step 3: Identify gaps\nList unknowns that block sound judgment, such as:\n- budget not confirmed\n- authority unclear\n- timeline unknown\n- current solution unknown\n- success criteria unclear\n\n### Step 4: Recommend action\nUse the score as guidance, not certainty.\n\n- 32-40: Hot → pursue now\n- 24-31: Warm → qualify further\n- 16-23: Nurture → stay in touch without active pursuit\n- 0-15: Deprioritize → do not invest heavily\n\n### Step 5: Draft follow-up if needed\nIf pursue now or qualify further is recommended:\n- reference something specific they said or did\n- provide new value\n- include one clear next step\n- keep it concise\n- never use empty phrases like \"just checking in\" or \"touching base\"\n\n## Upstream Check (for AI agents)\n\nIf user provides only:\n- names\n- companies\n- roles\n- static firmographic information\n- broad target signals\n\nand there is no sign of reply, meeting, active conversation, or engagement, then respond:\n\n\"This may still be a prospect rather than an active lead. Use `\u002Fprospect` when the goal is to filter and prioritize targets before outreach. Use Lead only once engagement has begun.\"\n\n## Activation Rules (for AI agents)\n\n### Use this skill when the user is asking about:\n- evaluating a sales lead\n- qualifying a prospect after engagement\n- deciding whether to pursue a business opportunity already in motion\n- handling a stalled commercial conversation\n- writing follow-up for a potential customer\n\n### Do NOT use this skill for:\n- music contexts\n- medical or toxicology contexts\n- journalism contexts\n- job-hunting contexts\n- generic project lead or team lead contexts unless clearly about sales\n\n### If context is ambiguous\nAsk:\n\"Are you asking about evaluating a sales lead or commercial prospect?\"\n\n## When NOT to use Lead\n\nDo not use this skill when:\n- full CRM architecture design is needed\n- detailed financial forecasting is needed\n- legal review is needed\n- broad sales theory is needed instead of lead-level judgment\n\n## Works Well With\n\n- `\u002Fprospect` for filtering and prioritizing targets before outreach\n- `\u002Fpipeline` for reviewing the health of the whole active opportunity system\n\n## Output style\n\nResponses should be:\n- concise\n- commercial\n- diagnostic\n- actionable\n- honest about uncertainty\n\nNever inflate lead quality without evidence.  \nNever recommend aggressive follow-up without a reason.  \nNever fabricate authority, urgency, budget, or buying intent.\n","# Lead\n\n> ⚠️ **Scope Notice**  \n> This skill is for **sales lead qualification** only.  \n> It is not for music, medicine, journalism, recruiting, or generic team-role uses of the word \"lead\".\n\nLead is a decision skill for handling commercial prospects with speed, clarity, and discipline.\n\nUse this skill when you need to:\n- evaluate whether a sales lead is worth active pursuit\n- identify what information is still missing\n- determine the next best action\n- write follow-up that moves the conversation forward\n- prevent good leads from dying due to weak process\n\n## Lead vs Prospect\n\nUse **Prospect** before contact.  \nUse **Lead** after engagement begins.\n\n| | Prospect | Lead |\n|---|---|---|\n| **Stage** | Before contact | After engagement |\n| **Question** | \"Is this target worth reaching out to?\" | \"Should I keep pursuing this person?\" |\n| **Input** | Names, profiles, company data, signals | Conversation history, replies, behavior |\n| **Output** | Priority tier + route | Qualification score + next action |\n\nIf there has been no reply, no meeting, and no active interaction yet, the contact may still be better handled by **Prospect**.\n\n## What this skill does\n\nLead helps transform raw prospect information into clear action.\n\nIt can:\n- assess lead quality based on fit, intent, urgency, and authority\n- distinguish real opportunities from vague interest\n- identify blockers, risks, and missing qualification data\n- recommend the next best action for each lead\n- draft follow-up messages that have a reason to exist\n- separate active pursuit, nurture, and deprioritize decisions\n\n## Best use cases\n\n- inbound lead triage\n- outbound reply handling\n- founder-led sales\n- SDR qualification\n- stalled lead diagnosis\n- re-engagement planning\n- next-step planning after discovery calls\n\n## What to provide\n\nUseful input includes:\n- who the lead is\n- company and role\n- source of the lead\n- what they asked for or responded to\n- current pain point\n- timeline, budget, or buying signals\n- last interaction and current status\n\n## What this skill should return\n\nA strong response should usually include:\n\n1. Lead assessment  \n   - hot \u002F warm \u002F cold  \n   - strong fit \u002F unclear fit \u002F weak fit\n\n2. Missing information  \n   - what must be clarified before investing more time\n\n3. Risks or friction  \n   - weak authority\n   - weak urgency\n   - weak problem clarity\n   - weak timing\n   - weak follow-through\n\n4. Next best action  \n   - pursue now\n   - qualify further\n   - nurture\n   - deprioritize\n\n5. Optional follow-up draft  \n   - short\n   - relevant\n   - specific\n   - non-annoying\n\n## Decision principles\n\n- Do not confuse activity with opportunity.\n- Do not treat every lead as pipeline.\n- Do not push unclear leads into active pursuit too early.\n- Preserve momentum when signal is strong.\n- Reduce wasted effort when fit or timing is weak.\n- Always prefer a clear next step over vague optimism.\n\n## Execution Protocol (for AI agents)\n\nWhen user provides lead information, follow this sequence.\n\n### Step 1: Extract context\nParse input for:\n- prospect identity\n- company and role\n- source\n- pain signal\n- engagement level\n- buying context\n- timeline, budget, authority, or competitors if mentioned\n\n### Step 2: Score only from visible evidence\nAssign 0-10 for each dimension using only evidence present in the input.\n\n**Fit Score**\n- ICP match\n- problem-product alignment\n- role relevance\n\n**Intent Score**\n- explicit ask vs passive interest\n- specificity of questions\n- effort already shown\n\n**Urgency Score**\n- timeline mentioned\n- pain severity\n- trigger event or active problem\n\n**Authority Score**\n- decision-maker vs influencer\n- budget control\n- internal champion strength\n\nIf evidence is missing, do not guess. Score conservatively.\n\n### Step 3: Identify gaps\nList unknowns that block sound judgment, such as:\n- budget not confirmed\n- authority unclear\n- timeline unknown\n- current solution unknown\n- success criteria unclear\n\n### Step 4: Recommend action\nUse the score as guidance, not certainty.\n\n- 32-40: Hot → pursue now\n- 24-31: Warm → qualify further\n- 16-23: Nurture → stay in touch without active pursuit\n- 0-15: Deprioritize → do not invest heavily\n\n### Step 5: Draft follow-up if needed\nIf pursue now or qualify further is recommended:\n- reference something specific they said or did\n- provide new value\n- include one clear next step\n- keep it concise\n- never use empty phrases like \"just checking in\" or \"touching base\"\n\n## Upstream Check (for AI agents)\n\nIf user provides only:\n- names\n- companies\n- roles\n- static firmographic information\n- broad target signals\n\nand there is no sign of reply, meeting, active conversation, or engagement, then respond:\n\n\"This may still be a prospect rather than an active lead. Use `\u002Fprospect` when the goal is to filter and prioritize targets before outreach. Use Lead only once engagement has begun.\"\n\n## Activation Rules (for AI agents)\n\n### Use this skill when the user is asking about:\n- evaluating a sales lead\n- qualifying a prospect after engagement\n- deciding whether to pursue a business opportunity already in motion\n- handling a stalled commercial conversation\n- writing follow-up for a potential customer\n\n### Do NOT use this skill for:\n- music contexts\n- medical or toxicology contexts\n- journalism contexts\n- job-hunting contexts\n- generic project lead or team lead contexts unless clearly about sales\n\n### If context is ambiguous\nAsk:\n\"Are you asking about evaluating a sales lead or commercial prospect?\"\n\n## When NOT to use Lead\n\nDo not use this skill when:\n- full CRM architecture design is needed\n- detailed financial forecasting is needed\n- legal review is needed\n- broad sales theory is needed instead of lead-level judgment\n\n## Works Well With\n\n- `\u002Fprospect` for filtering and prioritizing targets before outreach\n- `\u002Fpipeline` for reviewing the health of the whole active opportunity system\n\n## Output style\n\nResponses should be:\n- concise\n- commercial\n- diagnostic\n- actionable\n- honest about uncertainty\n\nNever inflate lead quality without evidence.  \nNever recommend aggressive follow-up without a reason.  \nNever fabricate authority, urgency, budget, or buying intent.\n",{"name":5,"version":24,"description":7},"2.1.0","master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Fl\u002Flead",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":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill Lead",{"tool":40,"command":41},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill Lead",{"tool":43,"command":44},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill Lead","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fl\u002Flead\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"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":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"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":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"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":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"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":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"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":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":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",[],[]]