[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M77T7GD9GK84PR3T6E28B8TZ":3,"skill-same:01M77T7GD9GK84PR3T6E28B8TZ":62},{"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":39,"commitSha":40,"skillDirectory":41,"forksCount":42,"repositoryHtmlUrl":43,"repositoryHomepageUrl":44,"ownerHtmlUrl":45,"ownerBlogUrl":6,"ownerDescription":46,"updatedAt":47,"install":48,"resources":61},"01M77T7GD9GK84PR3T6E28B8TZ","Content Pipeline",null,"4-stage content pipeline orchestrator: Research -> Ideate -> Write -> Queue.\nGive it a topic, it researches existing discussions, generates hook angles,\nwrites a draft, and queues it for review. Inspired by @shannholmberg's\n4-Agent content system (Research -> Ideate -> Write -> Orchestrate).\nDesigned for creators who build in public and want systematic content production.","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\u002Fr\u002Frunesleo-content-pipeline\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: Content Pipeline\nversion: 1.0.0\ndescription: |\n  4-stage content pipeline orchestrator: Research -> Ideate -> Write -> Queue.\n  Give it a topic, it researches existing discussions, generates hook angles,\n  writes a draft, and queues it for review. Inspired by @shannholmberg's\n  4-Agent content system (Research -> Ideate -> Write -> Orchestrate).\n  Designed for creators who build in public and want systematic content production.\nwhen_to_use: when creating original content that needs research, angle selection, and drafting from scratch\ntrigger: \u002Fpipeline\nlanguages: all\nattribution: Inspired by @shannholmberg's 4-Agent content system. Pipeline architecture is original.\nallowed-tools:\n  - Read\n  - Write\n  - Edit\n  - Bash\n  - Grep\n  - Glob\n  - Agent\n  - AskUserQuestion\n---\n\n# Content Pipeline Orchestrator\n\n> **One command, from topic to review-ready draft.**\n> Research -> Ideate -> Write -> Queue\n\n## When to use vs. not\n\n**Use pipeline** (original content that needs research):\n- Writing from scratch on a topic you haven't deeply explored\n- Need to survey existing discussion, find data, pick an angle\n- Example: \"write about the impact of MoE on local inference\" \u002F \"year-end market review\"\n\n**Don't use pipeline** (already have material):\n- Quoting someone else's post -> just write directly\n- Replying\u002Fcommenting -> just write directly\n- Polishing an existing draft -> just edit directly\n- These scenarios waste 4-5x tokens through the pipeline with zero benefit\n\n## File locations\n\nConfigure these paths for your project:\n\n| File | Purpose |\n|------|---------|\n| `.\u002Fcontent-queue.json` | Idea lifecycle state |\n| `.\u002Fresearch\u002F` | Research results (by date + slug) |\n\n## Commands\n\nParse user input, match first hit:\n\n| Input | Command | Action |\n|-------|---------|--------|\n| `\u002Fpipeline \u003Ctopic>` | **run** | Full pipeline: research -> ideate -> write -> queue |\n| `\u002Fpipeline url \u003Curl>` | **url** | Extract from URL -> ideate -> write -> queue |\n| `\u002Fpipeline seed \u003Cidea>` | **seed** | Add raw idea to queue as seed |\n| `\u002Fpipeline status` | **status** | Show queue grouped by status |\n| `\u002Fpipeline review \u003Cid>` | **review** | Show a draft for review |\n| `\u002Fpipeline approve \u003Cid>` | **approve** | Mark as approved |\n| `\u002Fpipeline adapt \u003Cid> \u003Cplatform>` | **adapt** | Generate platform variant |\n| `\u002Fpipeline publish \u003Cid>` | **publish** | Mark as published + timestamp |\n| `\u002Fpipeline clean` | **clean** | Archive items published 30+ days ago |\n\n---\n\n## Queue data model\n\n**File**: `.\u002Fcontent-queue.json`\n\n```json\n{\n  \"ideas\": [\n    {\n      \"id\": 1,\n      \"topic\": \"AI Agent end-to-end automation\",\n      \"status\": \"drafted\",\n      \"platform\": \"twitter\",\n      \"created\": \"2026-03-03T15:00:00Z\",\n      \"updated\": \"2026-03-03T15:05:00Z\",\n      \"research_file\": \"research\u002F20260303-ai-agent-automation.md\",\n      \"hook_angle\": \"Builder perspective: Writing is easy, Research is the bottleneck\",\n      \"draft\": \"This person built a full...\",\n      \"variants\": {},\n      \"source_url\": null,\n      \"feedback\": [],\n      \"published\": null\n    }\n  ],\n  \"next_id\": 2\n}\n```\n\n**Status flow**: `seed -> researched -> drafted -> approved -> published -> archived`\n\n### Queue read\u002Fwrite rules\n\n1. **Read**: Read `.\u002Fcontent-queue.json`\n2. **Write**: Write back complete JSON (single-user, no concurrency issue)\n3. **ID assignment**: Use `next_id`, increment after write\n4. **Timestamps**: ISO 8601 with timezone\n\n---\n\n## Command details\n\n### \u002Fpipeline \u003Ctopic> -- Full Pipeline\n\n**Input**: topic (keywords or short phrase)\n\n#### Stage 1: Research\n\n1. Search for existing discussion on the topic using available search tools:\n   - Twitter\u002FX search for relevant posts and threads\n   - Web search for articles and data\n   - Any domain-specific sources you have access to\n2. Compile findings into a research file:\n   ```\n   .\u002Fresearch\u002FYYYYMMDD-{slug}.md\n   ```\n   slug = topic keywords, lowercase with hyphens, max 30 chars\n\n**Research file format**:\n```markdown\n# Research: {topic}\n**Date**: YYYY-MM-DD\n**Sources**: [list search methods used]\n\n## Key findings\n- [Finding 1 + source attribution]\n- [Finding 2 + data\u002Fnumbers]\n- [Finding 3 + opposing viewpoint]\n\n## Notable posts\u002Farticles\n1. @user1 (N likes): \"Core point summary\"\n2. @user2 (N likes): \"Core point summary\"\n\n## Data points\n- [Specific numbers, comparisons, statistics]\n\n## Opposing viewpoints\n- [Contrarian takes, if any]\n\n## Source links\n- [List of original URLs]\n```\n\n#### Stage 2: Ideate\n\n1. Read the research file\n2. Generate 3 hook angles based on the research:\n\n**Angle generation prompt** (adapt for your LLM of choice):\n```\nYou are a content strategist. Based on the following research, generate 3 hook angles for a post.\n\nResearch:\n{research file content}\n\nRequirements:\n1. Each angle includes:\n   - Hook type (contrast \u002F counterintuitive \u002F data-driven \u002F story \u002F question)\n   - Core thesis (one sentence)\n   - Key supporting points (2-3)\n   - Estimated virality score (1-5)\n2. Match the creator's voice and domain expertise\n3. Avoid: AI cliches, marketing speak, listicle format\n\nOutput as JSON array:\n[{\"type\": \"contrast\", \"thesis\": \"...\", \"supports\": [\"...\", \"...\"], \"score\": 4}, ...]\n```\n\n3. Select the highest-scored angle\n4. If multiple angles tie, present options for user to choose\n\n#### Stage 3: Write\n\n1. Write the draft using the selected hook angle + research data points\n2. **Content format routing**:\n   - Content \u003C= 280 chars -> short post (tweet)\n   - 280-2000 chars -> long post (thread)\n   - > 2000 chars -> article\n3. Apply your preferred writing style\u002Fvoice (integrate with a style skill if you have one)\n4. Verify all claims have source attribution from the research\n\n#### Stage 4: Queue\n\n1. Read content-queue.json\n2. Create new entry:\n   - `status`: \"drafted\"\n   - `platform`: target platform\n   - `research_file`: relative path\n   - `hook_angle`: selected angle description\n   - `draft`: written text\n3. Write back content-queue.json\n4. Output confirmation:\n   ```\n   Pipeline complete -- queued #\u003Cid>\n   Topic: \u003Ctopic>\n   Hook: \u003Cangle summary>\n   Draft: \u003Cfirst 80 chars>...\n   Format: short \u002F long \u002F article\n   Use \u002Fpipeline review \u003Cid> to see full content\n   ```\n\n---\n\n### \u002Fpipeline url \u003Curl> -- From URL input\n\n1. Fetch the URL content using available tools\n2. Extract core arguments and data points\n3. Skip Stage 1 (use extracted content as research)\n4. Continue to Stage 2 (ideate) -> Stage 3 (write) -> Stage 4 (queue)\n5. Record `source_url` in the entry\n\n---\n\n### \u002Fpipeline seed \u003Cidea> -- Add raw seed\n\n1. Create queue entry:\n   - `status`: \"seed\"\n   - `topic`: the idea text\n   - `draft`: null (seeds have no draft yet)\n2. Output: `Seed added to queue #\u003Cid>`\n\nSeeds are raw ideas waiting to be developed. Run `\u002Fpipeline \u003Ctopic>` later to expand a seed through the full pipeline.\n\n---\n\n### \u002Fpipeline status -- Queue status\n\nRead content-queue.json, output grouped by status:\n\n```\nContent Pipeline Status\n\nSeed (N):\n  #3 \"Multi-agent orchestration\" -- 3\u002F3 15:00\n\nDrafted (N):\n  #1 \"AI Agent automation\" -- 3\u002F3 15:05\n  #2 \"Market arbitrage math\" -- 3\u002F3 16:20\n\nApproved (N):\n  #5 \"MCP practical experience\" -- 3\u002F2 20:00\n\nPublished (N):\n  #4 \"Three-layer scraping approach\" -- 3\u002F1\n\nTotal: N items | Pending: seed(N) + drafted(N)\n```\n\nShow only non-archived items. If over 20 items, show most recent 20 + total count.\n\n---\n\n### \u002Fpipeline review \u003Cid> -- Review\n\n1. Find the entry in queue\n2. Display full info:\n\n```\nReview #\u003Cid>\n\nTopic: \u003Ctopic>\nStatus: \u003Cstatus>\nHook: \u003Chook_angle>\nCreated: \u003Ccreated>\n\n--- Draft ---\n\u003Cfull draft text>\n\n--- Variants ---\n[list any platform variants]\n\n--- Research ---\nFile: \u003Cresearch_file>\n[first 5 key findings if research file exists]\n\nActions:\n  \u002Fpipeline approve \u003Cid> -- approve for publishing\n  \u002Fpipeline adapt \u003Cid> \u003Cplatform> -- generate platform variant\n```\n\n---\n\n### \u002Fpipeline approve \u003Cid> -- Approve\n\n1. Change status to \"approved\"\n2. Update `updated` timestamp\n3. Output: `#\u003Cid> approved -- ready to publish`\n\n---\n\n### \u002Fpipeline adapt \u003Cid> \u003Cplatform> -- Multi-platform adaptation\n\nAdapt the draft for a different platform:\n\n1. Read the entry's draft\n2. Rewrite for the target platform's conventions:\n   - Different character limits\n   - Different audience expectations\n   - Different formatting norms\n3. Store in `variants.\u003Cplatform>` field\n4. Output: `\u003Cplatform> variant generated -- \u002Fpipeline review \u003Cid> to see`\n\n---\n\n### \u002Fpipeline publish \u003Cid> -- Publish marker\n\n1. Change status to \"published\"\n2. Record `published` timestamp\n3. Output: `#\u003Cid> marked as published`\n\n---\n\n### \u002Fpipeline clean -- Archive cleanup\n\n1. Scan all `published` entries\n2. Archive entries older than 30 days\n3. Output: `Archived N old entries`\n\n---\n\n## Design principles\n\n- Research and Ideate stages are **platform-agnostic** -- only the Write stage adapts for platform\n- One research effort can produce content for multiple platforms (\"one fish, many meals\")\n- Drafts should be **source-verified** before entering the queue -- no unsourced claims\n- Seeds are cheap to capture, expensive to develop -- capture freely, develop selectively\n- The pipeline is a framework, not a straitjacket -- skip stages when you already have what you need\n","# Content Pipeline Orchestrator\n\n> **One command, from topic to review-ready draft.**\n> Research -> Ideate -> Write -> Queue\n\n## When to use vs. not\n\n**Use pipeline** (original content that needs research):\n- Writing from scratch on a topic you haven't deeply explored\n- Need to survey existing discussion, find data, pick an angle\n- Example: \"write about the impact of MoE on local inference\" \u002F \"year-end market review\"\n\n**Don't use pipeline** (already have material):\n- Quoting someone else's post -> just write directly\n- Replying\u002Fcommenting -> just write directly\n- Polishing an existing draft -> just edit directly\n- These scenarios waste 4-5x tokens through the pipeline with zero benefit\n\n## File locations\n\nConfigure these paths for your project:\n\n| File | Purpose |\n|------|---------|\n| `.\u002Fcontent-queue.json` | Idea lifecycle state |\n| `.\u002Fresearch\u002F` | Research results (by date + slug) |\n\n## Commands\n\nParse user input, match first hit:\n\n| Input | Command | Action |\n|-------|---------|--------|\n| `\u002Fpipeline \u003Ctopic>` | **run** | Full pipeline: research -> ideate -> write -> queue |\n| `\u002Fpipeline url \u003Curl>` | **url** | Extract from URL -> ideate -> write -> queue |\n| `\u002Fpipeline seed \u003Cidea>` | **seed** | Add raw idea to queue as seed |\n| `\u002Fpipeline status` | **status** | Show queue grouped by status |\n| `\u002Fpipeline review \u003Cid>` | **review** | Show a draft for review |\n| `\u002Fpipeline approve \u003Cid>` | **approve** | Mark as approved |\n| `\u002Fpipeline adapt \u003Cid> \u003Cplatform>` | **adapt** | Generate platform variant |\n| `\u002Fpipeline publish \u003Cid>` | **publish** | Mark as published + timestamp |\n| `\u002Fpipeline clean` | **clean** | Archive items published 30+ days ago |\n\n---\n\n## Queue data model\n\n**File**: `.\u002Fcontent-queue.json`\n\n```json\n{\n  \"ideas\": [\n    {\n      \"id\": 1,\n      \"topic\": \"AI Agent end-to-end automation\",\n      \"status\": \"drafted\",\n      \"platform\": \"twitter\",\n      \"created\": \"2026-03-03T15:00:00Z\",\n      \"updated\": \"2026-03-03T15:05:00Z\",\n      \"research_file\": \"research\u002F20260303-ai-agent-automation.md\",\n      \"hook_angle\": \"Builder perspective: Writing is easy, Research is the bottleneck\",\n      \"draft\": \"This person built a full...\",\n      \"variants\": {},\n      \"source_url\": null,\n      \"feedback\": [],\n      \"published\": null\n    }\n  ],\n  \"next_id\": 2\n}\n```\n\n**Status flow**: `seed -> researched -> drafted -> approved -> published -> archived`\n\n### Queue read\u002Fwrite rules\n\n1. **Read**: Read `.\u002Fcontent-queue.json`\n2. **Write**: Write back complete JSON (single-user, no concurrency issue)\n3. **ID assignment**: Use `next_id`, increment after write\n4. **Timestamps**: ISO 8601 with timezone\n\n---\n\n## Command details\n\n### \u002Fpipeline \u003Ctopic> -- Full Pipeline\n\n**Input**: topic (keywords or short phrase)\n\n#### Stage 1: Research\n\n1. Search for existing discussion on the topic using available search tools:\n   - Twitter\u002FX search for relevant posts and threads\n   - Web search for articles and data\n   - Any domain-specific sources you have access to\n2. Compile findings into a research file:\n   ```\n   .\u002Fresearch\u002FYYYYMMDD-{slug}.md\n   ```\n   slug = topic keywords, lowercase with hyphens, max 30 chars\n\n**Research file format**:\n```markdown\n# Research: {topic}\n**Date**: YYYY-MM-DD\n**Sources**: [list search methods used]\n\n## Key findings\n- [Finding 1 + source attribution]\n- [Finding 2 + data\u002Fnumbers]\n- [Finding 3 + opposing viewpoint]\n\n## Notable posts\u002Farticles\n1. @user1 (N likes): \"Core point summary\"\n2. @user2 (N likes): \"Core point summary\"\n\n## Data points\n- [Specific numbers, comparisons, statistics]\n\n## Opposing viewpoints\n- [Contrarian takes, if any]\n\n## Source links\n- [List of original URLs]\n```\n\n#### Stage 2: Ideate\n\n1. Read the research file\n2. Generate 3 hook angles based on the research:\n\n**Angle generation prompt** (adapt for your LLM of choice):\n```\nYou are a content strategist. Based on the following research, generate 3 hook angles for a post.\n\nResearch:\n{research file content}\n\nRequirements:\n1. Each angle includes:\n   - Hook type (contrast \u002F counterintuitive \u002F data-driven \u002F story \u002F question)\n   - Core thesis (one sentence)\n   - Key supporting points (2-3)\n   - Estimated virality score (1-5)\n2. Match the creator's voice and domain expertise\n3. Avoid: AI cliches, marketing speak, listicle format\n\nOutput as JSON array:\n[{\"type\": \"contrast\", \"thesis\": \"...\", \"supports\": [\"...\", \"...\"], \"score\": 4}, ...]\n```\n\n3. Select the highest-scored angle\n4. If multiple angles tie, present options for user to choose\n\n#### Stage 3: Write\n\n1. Write the draft using the selected hook angle + research data points\n2. **Content format routing**:\n   - Content \u003C= 280 chars -> short post (tweet)\n   - 280-2000 chars -> long post (thread)\n   - > 2000 chars -> article\n3. Apply your preferred writing style\u002Fvoice (integrate with a style skill if you have one)\n4. Verify all claims have source attribution from the research\n\n#### Stage 4: Queue\n\n1. Read content-queue.json\n2. Create new entry:\n   - `status`: \"drafted\"\n   - `platform`: target platform\n   - `research_file`: relative path\n   - `hook_angle`: selected angle description\n   - `draft`: written text\n3. Write back content-queue.json\n4. Output confirmation:\n   ```\n   Pipeline complete -- queued #\u003Cid>\n   Topic: \u003Ctopic>\n   Hook: \u003Cangle summary>\n   Draft: \u003Cfirst 80 chars>...\n   Format: short \u002F long \u002F article\n   Use \u002Fpipeline review \u003Cid> to see full content\n   ```\n\n---\n\n### \u002Fpipeline url \u003Curl> -- From URL input\n\n1. Fetch the URL content using available tools\n2. Extract core arguments and data points\n3. Skip Stage 1 (use extracted content as research)\n4. Continue to Stage 2 (ideate) -> Stage 3 (write) -> Stage 4 (queue)\n5. Record `source_url` in the entry\n\n---\n\n### \u002Fpipeline seed \u003Cidea> -- Add raw seed\n\n1. Create queue entry:\n   - `status`: \"seed\"\n   - `topic`: the idea text\n   - `draft`: null (seeds have no draft yet)\n2. Output: `Seed added to queue #\u003Cid>`\n\nSeeds are raw ideas waiting to be developed. Run `\u002Fpipeline \u003Ctopic>` later to expand a seed through the full pipeline.\n\n---\n\n### \u002Fpipeline status -- Queue status\n\nRead content-queue.json, output grouped by status:\n\n```\nContent Pipeline Status\n\nSeed (N):\n  #3 \"Multi-agent orchestration\" -- 3\u002F3 15:00\n\nDrafted (N):\n  #1 \"AI Agent automation\" -- 3\u002F3 15:05\n  #2 \"Market arbitrage math\" -- 3\u002F3 16:20\n\nApproved (N):\n  #5 \"MCP practical experience\" -- 3\u002F2 20:00\n\nPublished (N):\n  #4 \"Three-layer scraping approach\" -- 3\u002F1\n\nTotal: N items | Pending: seed(N) + drafted(N)\n```\n\nShow only non-archived items. If over 20 items, show most recent 20 + total count.\n\n---\n\n### \u002Fpipeline review \u003Cid> -- Review\n\n1. Find the entry in queue\n2. Display full info:\n\n```\nReview #\u003Cid>\n\nTopic: \u003Ctopic>\nStatus: \u003Cstatus>\nHook: \u003Chook_angle>\nCreated: \u003Ccreated>\n\n--- Draft ---\n\u003Cfull draft text>\n\n--- Variants ---\n[list any platform variants]\n\n--- Research ---\nFile: \u003Cresearch_file>\n[first 5 key findings if research file exists]\n\nActions:\n  \u002Fpipeline approve \u003Cid> -- approve for publishing\n  \u002Fpipeline adapt \u003Cid> \u003Cplatform> -- generate platform variant\n```\n\n---\n\n### \u002Fpipeline approve \u003Cid> -- Approve\n\n1. Change status to \"approved\"\n2. Update `updated` timestamp\n3. Output: `#\u003Cid> approved -- ready to publish`\n\n---\n\n### \u002Fpipeline adapt \u003Cid> \u003Cplatform> -- Multi-platform adaptation\n\nAdapt the draft for a different platform:\n\n1. Read the entry's draft\n2. Rewrite for the target platform's conventions:\n   - Different character limits\n   - Different audience expectations\n   - Different formatting norms\n3. Store in `variants.\u003Cplatform>` field\n4. Output: `\u003Cplatform> variant generated -- \u002Fpipeline review \u003Cid> to see`\n\n---\n\n### \u002Fpipeline publish \u003Cid> -- Publish marker\n\n1. Change status to \"published\"\n2. Record `published` timestamp\n3. Output: `#\u003Cid> marked as published`\n\n---\n\n### \u002Fpipeline clean -- Archive cleanup\n\n1. Scan all `published` entries\n2. Archive entries older than 30 days\n3. Output: `Archived N old entries`\n\n---\n\n## Design principles\n\n- Research and Ideate stages are **platform-agnostic** -- only the Write stage adapts for platform\n- One research effort can produce content for multiple platforms (\"one fish, many meals\")\n- Drafts should be **source-verified** before entering the queue -- no unsourced claims\n- Seeds are cheap to capture, expensive to develop -- capture freely, develop selectively\n- The pipeline is a framework, not a straitjacket -- skip stages when you already have what you need\n",{"name":5,"trigger":24,"version":25,"languages":26,"attribution":27,"description":28,"when_to_use":29,"allowed-tools":30},"\u002Fpipeline","1.0.0","all","Inspired by @shannholmberg's 4-Agent content system. Pipeline architecture is original.","4-stage content pipeline orchestrator: Research -> Ideate -> Write -> Queue.\nGive it a topic, it researches existing discussions, generates hook angles,\nwrites a draft, and queues it for review. Inspired by @shannholmberg's\n4-Agent content system (Research -> Ideate -> Write -> Orchestrate).\nDesigned for creators who build in public and want systematic content production.\n","when creating original content that needs research, angle selection, and drafting from scratch",[31,32,33,34,35,36,37,38],"Read","Write","Edit","Bash","Grep","Glob","Agent","AskUserQuestion","master","4aa004da461d820f4ea5499e58eb8d196cf99016","community\u002Fclawhub\u002Fr\u002Frunesleo-content-pipeline",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":49,"prompt":59,"zipAvailable":60},[50,53,56],{"tool":51,"command":52},"npx","npx skills add Lord1Egypt\u002Fawesome-skill-forge --skill \"Content Pipeline\"",{"tool":54,"command":55},"bunx","bunx skills add Lord1Egypt\u002Fawesome-skill-forge --skill \"Content Pipeline\"",{"tool":57,"command":58},"pnpm","pnpm dlx skills add Lord1Egypt\u002Fawesome-skill-forge --skill \"Content Pipeline\"","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FLord1Egypt\u002Fawesome-skill-forge\u002Fblob\u002Fmaster\u002Fcommunity\u002Fclawhub\u002Fr\u002Frunesleo-content-pipeline\u002FSKILL.md",true,[],[63,70,77,84,91,98],{"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},"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":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},"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":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},"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":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},"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":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":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":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":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",[],[]]