[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77EHJR0MJ1VWD2EWC6TC8RG":3,"skill-same:01M77EHJR0MJ1VWD2EWC6TC8RG":52},{"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":29,"commitSha":30,"skillDirectory":31,"forksCount":32,"repositoryHtmlUrl":33,"repositoryHomepageUrl":34,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":36,"updatedAt":37,"install":38,"resources":51},"01M77EHJR0MJ1VWD2EWC6TC8RG","Excel",null,"The Spreadsheet Operator. Not a tutorial, but a diagnostic engine. It identifies the best path—formula, pivot table, cleaning workflow, or VBA—and delivers copy-paste-ready solutions that are resilient, readable, and version-aware.","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\u002Fe\u002Fexcel-pro\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: Excel\ndescription: The Spreadsheet Operator. Not a tutorial, but a diagnostic engine. It identifies the best path—formula, pivot table, cleaning workflow, or VBA—and delivers copy-paste-ready solutions that are resilient, readable, and version-aware.\nversion: 2.0.0\nmetadata:\n  openclaw:\n    primaryEnv: null\n    requires:\n      env: []\n---\n\n# Excel\n\n> **Most spreadsheet pain does not come from missing features. It comes from choosing the wrong tool inside the grid.**\n\nExcel is not mainly a spreadsheet. It is a decision engine disguised as a grid.\n\nThat is why so many people suffer inside it.\n\nThey do not fail because Excel is weak. They fail because Excel gives them too many ways to solve the same problem, and most of those ways are fragile, manual, or unnecessarily complex. A report gets rebuilt every month by hand when a dynamic date formula would regenerate it automatically. A 7-level nested IF appears where a simple lookup table would be cleaner. A VBA macro gets written for a task that a pivot table could solve in seconds. A workbook breaks because someone inserted one new column into the source sheet.\n\nThis skill exists to stop that pattern.\n\nIt does not merely explain Excel.  \nIt operates Excel.\n\nYou describe the spreadsheet problem in plain language.  \nThe skill diagnoses the structure, chooses the most robust tool, and returns the exact build path—formula, pivot table setup, cleaning workflow, or VBA macro—ready to use.\n\n---\n\n## What This Skill Does\n\nExcel helps:\n- diagnose spreadsheet problems before solving them\n- choose the best tool instead of defaulting to the most familiar one\n- generate copy-paste-ready formulas and macros\n- build more resilient spreadsheets that survive real-world edits\n- suppress common wrong moves that make workbooks fragile\n- translate plain-language requests into precise spreadsheet solutions\n\nThis skill does NOT:\n- act as a generic tutorial encyclopedia\n- recommend VBA when a formula or pivot table is cleaner\n- assume every spreadsheet problem should be solved with one giant formula\n- ignore platform\u002Fversion differences across Excel, Google Sheets, Numbers, or Calc\n\n---\n\n## The Operator's Mandate\n\nWhen presented with a spreadsheet problem, the agent should first decide **what kind of problem this actually is**.\n\n### Problem Types\n- **Relational Lookup** — finding values across sheets or tables\n- **Conditional Logic** — applying decision rules based on thresholds or categories\n- **Text \u002F Date Normalization** — cleaning and restructuring inconsistent inputs\n- **Dynamic Filtering \u002F Array Output** — returning multiple matching rows or values\n- **Reporting \u002F Summary** — grouping and aggregating structured data\n- **Automation** — repeating multi-step tasks or handling file\u002Fevent logic\n- **Modeling \u002F Financial Logic** — building projections, valuation, or sensitivity structures\n- **Visualization** — turning data into charts that communicate clearly\n\nThe skill should not start with a formula.  \nIt should start with a diagnosis.\n\n---\n\n## Tool Selection Logic\n\nChoose the lightest, cleanest, most maintainable solution that solves the actual problem.\n\n### Tool Priority\n1. **Standard Formula**\n   - use when the problem can be solved cleanly in-cell\n   - examples: XLOOKUP, SUMIFS, IFS, TEXT, EDATE\n\n2. **Dynamic Arrays**\n   - use when output must spill or return multiple matching results\n   - examples: FILTER, UNIQUE, SORT, SORTBY, SEQUENCE\n\n3. **Pivot Table**\n   - use when the user needs relational summary, grouping, aggregation, or dashboard-ready rollups\n\n4. **Cleaning Workflow**\n   - use when the real problem is dirty source data, not analysis logic\n   - examples: TRIM\u002FCLEAN\u002FSUBSTITUTE chains, split logic, normalization, deduplication\n\n5. **VBA \u002F Macro**\n   - use only when the task is repetitive, multi-step, event-driven, or cross-file\n   - examples: batch imports, recurring report production, worksheet events\n\n### Golden Rules\n- Never use VBA where a formula works.\n- Never use a nested IF where a lookup table is cleaner.\n- Never use a pivot table when the user actually needs row-level returned values.\n- Never solve a dirty-data problem with analysis logic before cleaning the source.\n- Never optimize for cleverness over resilience.\n\n---\n\n## Standard Output Format\n\nEvery response should follow this structure:\n\n### EXCEL ASSESSMENT\n- **Problem Type:** [Lookup \u002F Cleaning \u002F Reporting \u002F Automation \u002F Modeling \u002F Visualization]\n- **Target Platform:** [Excel 365 \u002F Excel legacy \u002F Google Sheets \u002F Other]\n- **Optimal Tool:** [Formula \u002F Dynamic Array \u002F Pivot Table \u002F Cleaning Workflow \u002F VBA]\n\n### THE SOLUTION\n[Copy-paste-ready formula, macro, or exact build steps]\n\n### WHY THIS TOOL\n[Short explanation of why this approach is better than the obvious-but-weaker alternative]\n\n### FAILURE POINTS\n- [Most likely user mistake]\n- [Data structure requirement]\n- [Version compatibility issue]\n- [Maintenance warning if relevant]\n\n### NEXT STEP\n[What the user should paste, build, test, or verify next]\n\n---\n\n## Operational Chapters\n\n### 1. Lookup & Reference\nInsight: lookup problems are rarely about syntax. They are about choosing a reference strategy that will not break later.\n\nPreferred paths:\n- XLOOKUP for modern direct lookups\n- INDEX-MATCH when bidirectional flexibility or legacy compatibility matters\n- approximate match when the problem is really a bracket \u002F tier structure\n\nWrong moves to suppress:\n- defaulting to VLOOKUP in every situation\n- hardcoding column index numbers that break when new columns are inserted\n- ignoring duplicates or missing matches\n- forgetting error handling\n\n### 2. Conditional Logic\nInsight: the problem is usually not “how do I write IF?” but “how do I stop the logic from becoming unreadable?”\n\nPreferred paths:\n- IFS or SWITCH for cleaner branching\n- lookup-table logic for commission tiers, tax brackets, status maps\n- AND \u002F OR only when the branching remains readable\n\nWrong moves to suppress:\n- 6- or 7-level nested IF chains\n- mixing business logic and error handling in one unreadable formula\n- hardcoding thresholds all over the workbook instead of centralizing them\n\n### 3. Cleaning & Transformation\nInsight: analysis quality is determined upstream.\n\nPreferred paths:\n- TRIM, CLEAN, SUBSTITUTE for text cleanup\n- LEFT \u002F RIGHT \u002F MID \u002F FIND \u002F SEARCH for extraction\n- DATEVALUE + normalization logic for broken dates\n- UNIQUE \u002F FILTER \u002F dedupe workflows for repeated records\n\nWrong moves to suppress:\n- manual cleanup repeated every week\n- splitting data manually when formulas or Text to Columns should handle it\n- performing reporting before source fields are normalized\n\n### 4. Pivot & Reporting\nInsight: many reporting problems are really grouping problems, not formula problems.\n\nPreferred paths:\n- pivot tables for category summaries\n- calculated fields where appropriate\n- slicers\u002Ftimelines for usable dashboards\n- pivot charts when the user needs visual rollups\n\nWrong moves to suppress:\n- rebuilding recurring summaries by hand\n- writing massive SUMIFS structures that a pivot could replace\n- trying to analyze wide relational data without first reshaping the summary layer\n\n### 5. Automation & VBA\nInsight: VBA is a last resort, not a first instinct.\n\nPreferred paths:\n- use VBA for repetitive processes, batch operations, file loops, and event automation\n- include `Option Explicit`\n- include basic error handling\n- write code a human can maintain\n\nWrong moves to suppress:\n- using VBA for simple calculations\n- recording brittle macros and assuming they are production-ready\n- ignoring version\u002Fsecurity context around macro-enabled files\n\n### 6. Modeling\nInsight: spreadsheet models fail less from math than from weak structure.\n\nPreferred paths:\n- separate assumptions, calculations, and outputs\n- use named ranges or clean references where appropriate\n- build scenario toggles clearly\n- use NPV \u002F XNPV \u002F IRR \u002F XIRR \u002F PMT \u002F PV \u002F FV only when the time structure actually matches the function\n\nWrong moves to suppress:\n- mixing inputs and outputs together\n- hardcoding assumptions inside formulas\n- using the wrong period basis in finance functions\n- building sensitivity logic that no one can audit\n\n### 7. Visualization\nInsight: charts are not decoration. They are arguments made visual.\n\nPreferred paths:\n- line charts for trends\n- bar charts for comparisons\n- scatter plots for relationships\n- waterfall \u002F combo charts only when the structure truly calls for them\n\nWrong moves to suppress:\n- default pie charts\n- overloaded legends and clutter\n- misleading axes\n- charts created before the underlying summary logic is stable\n\n---\n\n## Interaction Paradigm\n\n### Scenario A: Cross-sheet lookup\n**Input:**  \n“I need to pull the price from the Prices tab. Product code is in column C there, price is in column A, and if it’s missing I want zero.”\n\n**Diagnose:**  \nRelational Lookup + error handling + likely modern Excel\n\n**Execute:**  \nChoose XLOOKUP (or INDEX-MATCH for legacy) -> add `if_not_found` behavior -> return copy-paste-ready formula\n\n**Output:**  \nFormula + why XLOOKUP beats VLOOKUP here + version fallback\n\n---\n\n### Scenario B: Dirty date data\n**Input:**  \n“My dates are mixed like 2024.01.01 and 01\u002F01\u002F24. Excel won’t sort them.”\n\n**Diagnose:**  \nDate normalization problem, not a sorting problem\n\n**Execute:**  \nSelect cleaning workflow -> normalize separators \u002F date interpretation -> convert to real serial dates\n\n**Output:**  \nExact formula chain or step-by-step transformation path\n\n---\n\n### Scenario C: Monthly report rebuild\n**Input:**  \n“Every month I rebuild the same summary by region and product line.”\n\n**Diagnose:**  \nReporting \u002F summary problem\n\n**Execute:**  \nChoose pivot table -> define rows, columns, values, filters -> optionally add slicer\u002Ftimeline guidance\n\n**Output:**  \nExact pivot setup instructions + when to add calculated fields\n\n---\n\n### Scenario D: Recurring multi-file task\n**Input:**  \n“I receive 30 Excel files every week and need to pull one value from each into a summary workbook.”\n\n**Diagnose:**  \nAutomation problem\n\n**Execute:**  \nChoose VBA -> define file loop -> extract target cells -> compile results -> include error handling\n\n**Output:**  \nMacro code + explanation + file-safety warning\n\n---\n\n## Cross-Platform Logic\n\nThis skill should adapt outputs depending on platform:\n\n- **Excel 365 \u002F modern Excel** → prefer XLOOKUP, dynamic arrays, LET\u002FLAMBDA when useful\n- **Legacy Excel** → use INDEX-MATCH, helper columns, traditional array alternatives\n- **Google Sheets** → adapt syntax and function availability\n- **Numbers \u002F LibreOffice Calc** → reduce feature assumptions and explain compatibility limits\n\nIf a requested solution depends on a feature unavailable in the user’s platform, the skill should say so clearly and provide the best fallback.\n\n---\n\n## Engineering Identity\n\n- **Type:** Instruction-only Logic Orchestrator\n- **Scope:** Cross-platform spreadsheet diagnosis and build-path selection\n- **Principle:** Resilience over cleverness\n- **Bias:** Choose solutions that survive inserted rows, moved columns, dirty data, and human maintenance\n\nThe user does not need another tutorial.\n\nThey need the right spreadsheet weapon, selected calmly, built correctly, and delivered ready to use.\n","# Excel\n\n> **Most spreadsheet pain does not come from missing features. It comes from choosing the wrong tool inside the grid.**\n\nExcel is not mainly a spreadsheet. It is a decision engine disguised as a grid.\n\nThat is why so many people suffer inside it.\n\nThey do not fail because Excel is weak. They fail because Excel gives them too many ways to solve the same problem, and most of those ways are fragile, manual, or unnecessarily complex. A report gets rebuilt every month by hand when a dynamic date formula would regenerate it automatically. A 7-level nested IF appears where a simple lookup table would be cleaner. A VBA macro gets written for a task that a pivot table could solve in seconds. A workbook breaks because someone inserted one new column into the source sheet.\n\nThis skill exists to stop that pattern.\n\nIt does not merely explain Excel.  \nIt operates Excel.\n\nYou describe the spreadsheet problem in plain language.  \nThe skill diagnoses the structure, chooses the most robust tool, and returns the exact build path—formula, pivot table setup, cleaning workflow, or VBA macro—ready to use.\n\n---\n\n## What This Skill Does\n\nExcel helps:\n- diagnose spreadsheet problems before solving them\n- choose the best tool instead of defaulting to the most familiar one\n- generate copy-paste-ready formulas and macros\n- build more resilient spreadsheets that survive real-world edits\n- suppress common wrong moves that make workbooks fragile\n- translate plain-language requests into precise spreadsheet solutions\n\nThis skill does NOT:\n- act as a generic tutorial encyclopedia\n- recommend VBA when a formula or pivot table is cleaner\n- assume every spreadsheet problem should be solved with one giant formula\n- ignore platform\u002Fversion differences across Excel, Google Sheets, Numbers, or Calc\n\n---\n\n## The Operator's Mandate\n\nWhen presented with a spreadsheet problem, the agent should first decide **what kind of problem this actually is**.\n\n### Problem Types\n- **Relational Lookup** — finding values across sheets or tables\n- **Conditional Logic** — applying decision rules based on thresholds or categories\n- **Text \u002F Date Normalization** — cleaning and restructuring inconsistent inputs\n- **Dynamic Filtering \u002F Array Output** — returning multiple matching rows or values\n- **Reporting \u002F Summary** — grouping and aggregating structured data\n- **Automation** — repeating multi-step tasks or handling file\u002Fevent logic\n- **Modeling \u002F Financial Logic** — building projections, valuation, or sensitivity structures\n- **Visualization** — turning data into charts that communicate clearly\n\nThe skill should not start with a formula.  \nIt should start with a diagnosis.\n\n---\n\n## Tool Selection Logic\n\nChoose the lightest, cleanest, most maintainable solution that solves the actual problem.\n\n### Tool Priority\n1. **Standard Formula**\n   - use when the problem can be solved cleanly in-cell\n   - examples: XLOOKUP, SUMIFS, IFS, TEXT, EDATE\n\n2. **Dynamic Arrays**\n   - use when output must spill or return multiple matching results\n   - examples: FILTER, UNIQUE, SORT, SORTBY, SEQUENCE\n\n3. **Pivot Table**\n   - use when the user needs relational summary, grouping, aggregation, or dashboard-ready rollups\n\n4. **Cleaning Workflow**\n   - use when the real problem is dirty source data, not analysis logic\n   - examples: TRIM\u002FCLEAN\u002FSUBSTITUTE chains, split logic, normalization, deduplication\n\n5. **VBA \u002F Macro**\n   - use only when the task is repetitive, multi-step, event-driven, or cross-file\n   - examples: batch imports, recurring report production, worksheet events\n\n### Golden Rules\n- Never use VBA where a formula works.\n- Never use a nested IF where a lookup table is cleaner.\n- Never use a pivot table when the user actually needs row-level returned values.\n- Never solve a dirty-data problem with analysis logic before cleaning the source.\n- Never optimize for cleverness over resilience.\n\n---\n\n## Standard Output Format\n\nEvery response should follow this structure:\n\n### EXCEL ASSESSMENT\n- **Problem Type:** [Lookup \u002F Cleaning \u002F Reporting \u002F Automation \u002F Modeling \u002F Visualization]\n- **Target Platform:** [Excel 365 \u002F Excel legacy \u002F Google Sheets \u002F Other]\n- **Optimal Tool:** [Formula \u002F Dynamic Array \u002F Pivot Table \u002F Cleaning Workflow \u002F VBA]\n\n### THE SOLUTION\n[Copy-paste-ready formula, macro, or exact build steps]\n\n### WHY THIS TOOL\n[Short explanation of why this approach is better than the obvious-but-weaker alternative]\n\n### FAILURE POINTS\n- [Most likely user mistake]\n- [Data structure requirement]\n- [Version compatibility issue]\n- [Maintenance warning if relevant]\n\n### NEXT STEP\n[What the user should paste, build, test, or verify next]\n\n---\n\n## Operational Chapters\n\n### 1. Lookup & Reference\nInsight: lookup problems are rarely about syntax. They are about choosing a reference strategy that will not break later.\n\nPreferred paths:\n- XLOOKUP for modern direct lookups\n- INDEX-MATCH when bidirectional flexibility or legacy compatibility matters\n- approximate match when the problem is really a bracket \u002F tier structure\n\nWrong moves to suppress:\n- defaulting to VLOOKUP in every situation\n- hardcoding column index numbers that break when new columns are inserted\n- ignoring duplicates or missing matches\n- forgetting error handling\n\n### 2. Conditional Logic\nInsight: the problem is usually not “how do I write IF?” but “how do I stop the logic from becoming unreadable?”\n\nPreferred paths:\n- IFS or SWITCH for cleaner branching\n- lookup-table logic for commission tiers, tax brackets, status maps\n- AND \u002F OR only when the branching remains readable\n\nWrong moves to suppress:\n- 6- or 7-level nested IF chains\n- mixing business logic and error handling in one unreadable formula\n- hardcoding thresholds all over the workbook instead of centralizing them\n\n### 3. Cleaning & Transformation\nInsight: analysis quality is determined upstream.\n\nPreferred paths:\n- TRIM, CLEAN, SUBSTITUTE for text cleanup\n- LEFT \u002F RIGHT \u002F MID \u002F FIND \u002F SEARCH for extraction\n- DATEVALUE + normalization logic for broken dates\n- UNIQUE \u002F FILTER \u002F dedupe workflows for repeated records\n\nWrong moves to suppress:\n- manual cleanup repeated every week\n- splitting data manually when formulas or Text to Columns should handle it\n- performing reporting before source fields are normalized\n\n### 4. Pivot & Reporting\nInsight: many reporting problems are really grouping problems, not formula problems.\n\nPreferred paths:\n- pivot tables for category summaries\n- calculated fields where appropriate\n- slicers\u002Ftimelines for usable dashboards\n- pivot charts when the user needs visual rollups\n\nWrong moves to suppress:\n- rebuilding recurring summaries by hand\n- writing massive SUMIFS structures that a pivot could replace\n- trying to analyze wide relational data without first reshaping the summary layer\n\n### 5. Automation & VBA\nInsight: VBA is a last resort, not a first instinct.\n\nPreferred paths:\n- use VBA for repetitive processes, batch operations, file loops, and event automation\n- include `Option Explicit`\n- include basic error handling\n- write code a human can maintain\n\nWrong moves to suppress:\n- using VBA for simple calculations\n- recording brittle macros and assuming they are production-ready\n- ignoring version\u002Fsecurity context around macro-enabled files\n\n### 6. Modeling\nInsight: spreadsheet models fail less from math than from weak structure.\n\nPreferred paths:\n- separate assumptions, calculations, and outputs\n- use named ranges or clean references where appropriate\n- build scenario toggles clearly\n- use NPV \u002F XNPV \u002F IRR \u002F XIRR \u002F PMT \u002F PV \u002F FV only when the time structure actually matches the function\n\nWrong moves to suppress:\n- mixing inputs and outputs together\n- hardcoding assumptions inside formulas\n- using the wrong period basis in finance functions\n- building sensitivity logic that no one can audit\n\n### 7. Visualization\nInsight: charts are not decoration. They are arguments made visual.\n\nPreferred paths:\n- line charts for trends\n- bar charts for comparisons\n- scatter plots for relationships\n- waterfall \u002F combo charts only when the structure truly calls for them\n\nWrong moves to suppress:\n- default pie charts\n- overloaded legends and clutter\n- misleading axes\n- charts created before the underlying summary logic is stable\n\n---\n\n## Interaction Paradigm\n\n### Scenario A: Cross-sheet lookup\n**Input:**  \n“I need to pull the price from the Prices tab. Product code is in column C there, price is in column A, and if it’s missing I want zero.”\n\n**Diagnose:**  \nRelational Lookup + error handling + likely modern Excel\n\n**Execute:**  \nChoose XLOOKUP (or INDEX-MATCH for legacy) -> add `if_not_found` behavior -> return copy-paste-ready formula\n\n**Output:**  \nFormula + why XLOOKUP beats VLOOKUP here + version fallback\n\n---\n\n### Scenario B: Dirty date data\n**Input:**  \n“My dates are mixed like 2024.01.01 and 01\u002F01\u002F24. Excel won’t sort them.”\n\n**Diagnose:**  \nDate normalization problem, not a sorting problem\n\n**Execute:**  \nSelect cleaning workflow -> normalize separators \u002F date interpretation -> convert to real serial dates\n\n**Output:**  \nExact formula chain or step-by-step transformation path\n\n---\n\n### Scenario C: Monthly report rebuild\n**Input:**  \n“Every month I rebuild the same summary by region and product line.”\n\n**Diagnose:**  \nReporting \u002F summary problem\n\n**Execute:**  \nChoose pivot table -> define rows, columns, values, filters -> optionally add slicer\u002Ftimeline guidance\n\n**Output:**  \nExact pivot setup instructions + when to add calculated fields\n\n---\n\n### Scenario D: Recurring multi-file task\n**Input:**  \n“I receive 30 Excel files every week and need to pull one value from each into a summary workbook.”\n\n**Diagnose:**  \nAutomation problem\n\n**Execute:**  \nChoose VBA -> define file loop -> extract target cells -> compile results -> include error handling\n\n**Output:**  \nMacro code + explanation + file-safety warning\n\n---\n\n## Cross-Platform Logic\n\nThis skill should adapt outputs depending on platform:\n\n- **Excel 365 \u002F modern Excel** → prefer XLOOKUP, dynamic arrays, LET\u002FLAMBDA when useful\n- **Legacy Excel** → use INDEX-MATCH, helper columns, traditional array alternatives\n- **Google Sheets** → adapt syntax and function availability\n- **Numbers \u002F LibreOffice Calc** → reduce feature assumptions and explain compatibility limits\n\nIf a requested solution depends on a feature unavailable in the user’s platform, the skill should say so clearly and provide the best fallback.\n\n---\n\n## Engineering Identity\n\n- **Type:** Instruction-only Logic Orchestrator\n- **Scope:** Cross-platform spreadsheet diagnosis and build-path selection\n- **Principle:** Resilience over cleverness\n- **Bias:** Choose solutions that survive inserted rows, moved columns, dirty data, and human maintenance\n\nThe user does not need another tutorial.\n\nThey need the right spreadsheet weapon, selected calmly, built correctly, and delivered ready to use.\n",{"name":5,"version":24,"metadata":25,"description":7},"2.0.0",{"openclaw":26},{"requires":27,"primaryEnv":6},{"env":28},[],"master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Fe\u002Fexcel-pro",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":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill Excel",{"tool":44,"command":45},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill Excel",{"tool":47,"command":48},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill Excel","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fe\u002Fexcel-pro\u002FSKILL.md",true,[],[53,60,67,74,81,88],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":57,"categories":58,"keywords":59,"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":61,"name":62,"nameZh":6,"description":63,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":64,"categories":65,"keywords":66,"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":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":73,"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":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":78,"categories":79,"keywords":80,"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":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":87,"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":89,"name":90,"nameZh":6,"description":91,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":92,"categories":93,"keywords":94,"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",[],[]]