[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6NZJ5G7C6VCNPP35W0Q8RZF":3,"skill-same:01M6NZJ5G7C6VCNPP35W0Q8RZF":77},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":35,"commitSha":52,"skillDirectory":53,"forksCount":13,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6NZJ5G7C6VCNPP35W0Q8RZF","competitor-tracking",null,"Systematic competitor analysis for developer tools. Track features, pricing, positioning, content strategy, and community sentiment for direct and indirect competitors.","duc-duy-1612\u002FOnline-Delivery-Systems-Web","duc-duy-1612","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192231384?v=4","01M6NSDKQQDKVTHZ8DZMZ1VYY6","01M6NSDKW8DDVTQHBT1HBDDJPT",0,"MIT","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fcompetitor-tracking\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"competitor","competitor tracking","tracking","wed","track","features","for","tree","critical","systematic","positioning","pricing","main","community","direct","content strategy","competitors","analysis","Tools","developer","2026-11-10 10:12:30",false,"---\nname: competitor-tracking\ndescription: \"Systematic competitor analysis for developer tools. Track features, pricing, positioning, content strategy, and community sentiment for direct and indirect competitors.\"\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Ftree\u002Fmain\u002Fskills\u002Fcompetitor-tracking\nsource_repo: jonathimer\u002Fdevmarketing-skills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Competitor Tracking\n## When to Use\n\nUse this skill when you need systematic competitor analysis for developer tools. Track features, pricing, positioning, content strategy, and community sentiment for direct and indirect competitors. Trigger phrases: \"competitor analysis\", \"track competitors\", \"competitive intelligence\", \"competitor research\", \"what...\n\n\nSystematic framework for tracking competitors in the developer tools space, from identification through ongoing monitoring and battlecard creation.\n\n## Overview\n\nCompetitor tracking for developer tools requires monitoring multiple dimensions: product features, pricing, developer sentiment, content strategy, community growth, and funding\u002Ftrajectory. Unlike consumer products, developer tools compete on technical merit, documentation quality, and community trust.\n\nEffective competitor tracking helps you:\n- Understand your competitive positioning\n- Anticipate competitor moves\n- Arm sales and marketing with accurate battlecards\n- Identify market gaps and opportunities\n- Learn from competitor successes and failures\n\n## Competitor Identification\n\n### Types of Competitors\n\n**Direct Competitors:**\n- Same category, same target developer\n- Solve the same core problem\n- Would appear in the same \"best X tools\" lists\n- Example: If you're a CI\u002FCD tool, other CI\u002FCD tools\n\n**Indirect Competitors:**\n- Adjacent categories that overlap with your use case\n- Might be expanding into your space\n- Developers might use instead of your category\n- Example: GitHub Actions competing with standalone CI tools\n\n**DIY Alternatives:**\n- Open source tools developers self-host\n- Custom scripts and internal tooling\n- \"Just use bash scripts\" or \"build it yourself\"\n- Often your biggest competitor by volume\n\n**Platform Alternatives:**\n- Cloud provider native services (AWS, GCP, Azure equivalents)\n- All-in-one platforms that include your functionality\n- Enterprise suite solutions\n\n### Competitive Landscape Mapping\n\nCreate a competitive landscape document with:\n\n1. **Competitor profiles** - Company, product, target market, positioning\n2. **Feature matrix** - Core features compared across competitors\n3. **Pricing comparison** - Tiers, pricing model, enterprise pricing signals\n4. **Strengths\u002Fweaknesses** - Honest assessment of each competitor\n5. **Trajectory** - Funding, growth signals, strategic direction\n\n## What to Track\n\n### Product and Features\n\n**Track weekly\u002Fmonthly:**\n- Changelog and release notes\n- New feature announcements\n- Pricing changes\n- Integration announcements\n- API changes\n- SDK\u002Flibrary updates\n\n**How to track:**\n- Subscribe to competitor newsletters\n- Follow their GitHub releases\n- Monitor their Twitter\u002Fblog\n- Set up monitoring alerts for \"[competitor] launch\" \"[competitor] announces\"\n\n### Pricing and Packaging\n\n**Key signals:**\n- Pricing page changes (use archive.org to track history)\n- New tier introductions\n- Enterprise\u002Fcustom pricing signals\n- Free tier changes\n- Usage-based vs seat-based shifts\n\n**Competitive pricing intelligence:**\n- What's included in free tier?\n- Where are the upgrade triggers?\n- How do they handle overages?\n- What's the enterprise motion?\n\n### Positioning and Messaging\n\n**Track changes in:**\n- Homepage headline and hero\n- \"Who it's for\" positioning\n- Primary use cases emphasized\n- Comparison pages (how they position against others)\n- Case studies and social proof\n\n**Analyze:**\n- What problem do they lead with?\n- What audience are they targeting?\n- What's their unique angle?\n- How are they different from 6 months ago?\n\n### Content Strategy\n\n**Monitor:**\n- Blog post frequency and topics\n- Documentation quality and coverage\n- Video\u002Ftutorial content\n- Conference talks and sponsorships\n- Developer education initiatives\n\n**Look for:**\n- SEO plays (what keywords are they targeting?)\n- Content gaps you can exploit\n- Successful content formats to learn from\n\n### Community and Traction\n\n**GitHub signals:**\n- Stars\u002Fforks growth rate\n- Issue volume and response time\n- Contributor growth\n- Release frequency\n\n**Community signals:**\n- Discord\u002FSlack member counts\n- Forum activity\n- Stack Overflow tag activity\n- Reddit mention frequency\n\n## Developer Sentiment Monitoring\n\n### Setting Up Competitor Monitoring\n\nUse social listening tools to track developer sentiment toward competitors across platforms. Set up alerts for:\n\n- Competitor brand mentions\n- Negative sentiment toward competitors (opportunity signals)\n- Comparison queries (\"[competitor] vs\")\n\n### Key Sentiment Signals\n\n**Churn signals:**\n- \"Migrating away from [competitor]\"\n- \"Looking for [competitor] alternative\"\n- \"Frustrated with [competitor]\"\n- \"Canceling [competitor]\"\n\n**Praise signals (learn from them):**\n- \"Love [competitor]'s [feature]\"\n- \"[Competitor] just works\"\n- \"Best part of [competitor] is...\"\n\n**Feature gaps:**\n- \"Wish [competitor] had...\"\n- \"[Competitor] doesn't support...\"\n- \"Waiting for [competitor] to add...\"\n\n### Competitive Sentiment Analysis\n\nUse your monitoring tool's analytics for trend analysis:\n\n- Mention volume for competitors over 90 days\n- Sentiment distribution: positive vs negative\n- Co-mentions where competitor and your brand appear together\n\n## Building Competitive Battlecards\n\n### Battlecard Structure\n\nCreate battlecards for sales and marketing teams:\n\n**1. Competitor Overview**\n- Company background\n- Target market\n- Key value proposition\n- Recent news\u002Ftrajectory\n\n**2. When We Win**\n- Scenarios where you have advantage\n- Customer types that prefer you\n- Use cases you excel at\n- Proof points and case studies\n\n**3. When We Lose**\n- Scenarios where competitor has advantage\n- What to watch out for\n- How to mitigate their strengths\n\n**4. Common Objections**\n- \"But [competitor] has [feature]\"\n- \"[Competitor] is cheaper\"\n- \"[Competitor] is more established\"\n- Response frameworks for each\n\n**5. Competitive Differentiation**\n- Key technical differences\n- Pricing comparison\n- Support\u002Fservice differences\n- Community\u002Fecosystem differences\n\n**6. Landmines to Set**\n- Questions to ask that favor you\n- Requirements that highlight your strengths\n- Evaluation criteria that matter\n\n### Keeping Battlecards Fresh\n\n**Update triggers:**\n- Competitor launches major feature\n- Competitor changes pricing\n- You ship something that changes the comparison\n- Sales team reports new objections\n- Win\u002Floss analysis reveals new patterns\n\n**Review cadence:**\n- Major competitors: monthly review\n- Minor competitors: quarterly review\n- Emerging competitors: as needed\n\n## Responding to Competitor Moves\n\n### When to Respond\n\n**Always respond:**\n- Competitor makes false claims about you\n- Competitor targets your specific customers\n- Major market shift that affects positioning\n\n**Consider responding:**\n- Competitor launches feature you have\n- Competitor enters your core market\n- Competitor's crisis creates opportunity\n\n**Usually don't respond:**\n- Minor feature parity announcements\n- Competitor's internal issues (unless affects their customers)\n- Petty competitive shots\n\n### Response Playbooks\n\n**Feature launch response:**\n1. Assess: Do we have parity? Better? Gap?\n2. Internal communication to sales\u002Fsupport\n3. Update battlecards if needed\n4. Consider content response (blog, comparison page update)\n5. Monitor developer conversations for context\n\n**Pricing change response:**\n1. Analyze impact on competitive positioning\n2. Update pricing comparison materials\n3. Brief sales team\n4. Consider if pricing adjustment needed\n5. Monitor churn\u002Facquisition impact\n\n**Crisis opportunity response:**\n1. Don't be sleazy or pile on\n2. Be helpful to affected users if appropriate\n3. Create migration content if there's genuine demand\n4. Let your product speak for itself\n\n## Tools\n\n### Social Listening\n\nUse monitoring tools to set up alerts for these patterns:\n- Competitor sentiment overview (last 30 days, by sentiment)\n- Churn signals: \"alternative OR migrating OR switching\" + competitor name\n- Feature gaps: \"wish OR need OR missing\" + competitor name\n- Comparison mentions: \"[competitor] vs\"\n\n### Other Tools\n\n**GitHub Monitoring:**\n```bash\n# Track competitor repo activity\ngh api repos\u002F[competitor]\u002F[repo] --jq '.stargazers_count, .open_issues_count'\n\n# Search for competitor mentions in issues\ngh search issues \"[competitor]\" --limit 50\n```\n\n**npm\u002FPyPI Monitoring:**\n- Track download trends for competitor packages\n- Monitor version release frequency\n- Watch for new packages in their ecosystem\n\n**Archive.org:**\n- Track historical changes to competitor websites\n- Document pricing changes over time\n- Capture positioning shifts\n\n**LinkedIn\u002FCareers:**\n- Track hiring patterns\n- Identify strategic direction from job postings\n- Monitor team growth signals\n\n## Related Skills\n\n- **developer-listening** - Broader monitoring beyond just competitors\n- **alternatives-pages** - Turn competitive intelligence into content\n- **positioning** - Differentiate based on competitive insights\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# Competitor Tracking\n## When to Use\n\nUse this skill when you need systematic competitor analysis for developer tools. Track features, pricing, positioning, content strategy, and community sentiment for direct and indirect competitors. Trigger phrases: \"competitor analysis\", \"track competitors\", \"competitive intelligence\", \"competitor research\", \"what...\n\n\nSystematic framework for tracking competitors in the developer tools space, from identification through ongoing monitoring and battlecard creation.\n\n## Overview\n\nCompetitor tracking for developer tools requires monitoring multiple dimensions: product features, pricing, developer sentiment, content strategy, community growth, and funding\u002Ftrajectory. Unlike consumer products, developer tools compete on technical merit, documentation quality, and community trust.\n\nEffective competitor tracking helps you:\n- Understand your competitive positioning\n- Anticipate competitor moves\n- Arm sales and marketing with accurate battlecards\n- Identify market gaps and opportunities\n- Learn from competitor successes and failures\n\n## Competitor Identification\n\n### Types of Competitors\n\n**Direct Competitors:**\n- Same category, same target developer\n- Solve the same core problem\n- Would appear in the same \"best X tools\" lists\n- Example: If you're a CI\u002FCD tool, other CI\u002FCD tools\n\n**Indirect Competitors:**\n- Adjacent categories that overlap with your use case\n- Might be expanding into your space\n- Developers might use instead of your category\n- Example: GitHub Actions competing with standalone CI tools\n\n**DIY Alternatives:**\n- Open source tools developers self-host\n- Custom scripts and internal tooling\n- \"Just use bash scripts\" or \"build it yourself\"\n- Often your biggest competitor by volume\n\n**Platform Alternatives:**\n- Cloud provider native services (AWS, GCP, Azure equivalents)\n- All-in-one platforms that include your functionality\n- Enterprise suite solutions\n\n### Competitive Landscape Mapping\n\nCreate a competitive landscape document with:\n\n1. **Competitor profiles** - Company, product, target market, positioning\n2. **Feature matrix** - Core features compared across competitors\n3. **Pricing comparison** - Tiers, pricing model, enterprise pricing signals\n4. **Strengths\u002Fweaknesses** - Honest assessment of each competitor\n5. **Trajectory** - Funding, growth signals, strategic direction\n\n## What to Track\n\n### Product and Features\n\n**Track weekly\u002Fmonthly:**\n- Changelog and release notes\n- New feature announcements\n- Pricing changes\n- Integration announcements\n- API changes\n- SDK\u002Flibrary updates\n\n**How to track:**\n- Subscribe to competitor newsletters\n- Follow their GitHub releases\n- Monitor their Twitter\u002Fblog\n- Set up monitoring alerts for \"[competitor] launch\" \"[competitor] announces\"\n\n### Pricing and Packaging\n\n**Key signals:**\n- Pricing page changes (use archive.org to track history)\n- New tier introductions\n- Enterprise\u002Fcustom pricing signals\n- Free tier changes\n- Usage-based vs seat-based shifts\n\n**Competitive pricing intelligence:**\n- What's included in free tier?\n- Where are the upgrade triggers?\n- How do they handle overages?\n- What's the enterprise motion?\n\n### Positioning and Messaging\n\n**Track changes in:**\n- Homepage headline and hero\n- \"Who it's for\" positioning\n- Primary use cases emphasized\n- Comparison pages (how they position against others)\n- Case studies and social proof\n\n**Analyze:**\n- What problem do they lead with?\n- What audience are they targeting?\n- What's their unique angle?\n- How are they different from 6 months ago?\n\n### Content Strategy\n\n**Monitor:**\n- Blog post frequency and topics\n- Documentation quality and coverage\n- Video\u002Ftutorial content\n- Conference talks and sponsorships\n- Developer education initiatives\n\n**Look for:**\n- SEO plays (what keywords are they targeting?)\n- Content gaps you can exploit\n- Successful content formats to learn from\n\n### Community and Traction\n\n**GitHub signals:**\n- Stars\u002Fforks growth rate\n- Issue volume and response time\n- Contributor growth\n- Release frequency\n\n**Community signals:**\n- Discord\u002FSlack member counts\n- Forum activity\n- Stack Overflow tag activity\n- Reddit mention frequency\n\n## Developer Sentiment Monitoring\n\n### Setting Up Competitor Monitoring\n\nUse social listening tools to track developer sentiment toward competitors across platforms. Set up alerts for:\n\n- Competitor brand mentions\n- Negative sentiment toward competitors (opportunity signals)\n- Comparison queries (\"[competitor] vs\")\n\n### Key Sentiment Signals\n\n**Churn signals:**\n- \"Migrating away from [competitor]\"\n- \"Looking for [competitor] alternative\"\n- \"Frustrated with [competitor]\"\n- \"Canceling [competitor]\"\n\n**Praise signals (learn from them):**\n- \"Love [competitor]'s [feature]\"\n- \"[Competitor] just works\"\n- \"Best part of [competitor] is...\"\n\n**Feature gaps:**\n- \"Wish [competitor] had...\"\n- \"[Competitor] doesn't support...\"\n- \"Waiting for [competitor] to add...\"\n\n### Competitive Sentiment Analysis\n\nUse your monitoring tool's analytics for trend analysis:\n\n- Mention volume for competitors over 90 days\n- Sentiment distribution: positive vs negative\n- Co-mentions where competitor and your brand appear together\n\n## Building Competitive Battlecards\n\n### Battlecard Structure\n\nCreate battlecards for sales and marketing teams:\n\n**1. Competitor Overview**\n- Company background\n- Target market\n- Key value proposition\n- Recent news\u002Ftrajectory\n\n**2. When We Win**\n- Scenarios where you have advantage\n- Customer types that prefer you\n- Use cases you excel at\n- Proof points and case studies\n\n**3. When We Lose**\n- Scenarios where competitor has advantage\n- What to watch out for\n- How to mitigate their strengths\n\n**4. Common Objections**\n- \"But [competitor] has [feature]\"\n- \"[Competitor] is cheaper\"\n- \"[Competitor] is more established\"\n- Response frameworks for each\n\n**5. Competitive Differentiation**\n- Key technical differences\n- Pricing comparison\n- Support\u002Fservice differences\n- Community\u002Fecosystem differences\n\n**6. Landmines to Set**\n- Questions to ask that favor you\n- Requirements that highlight your strengths\n- Evaluation criteria that matter\n\n### Keeping Battlecards Fresh\n\n**Update triggers:**\n- Competitor launches major feature\n- Competitor changes pricing\n- You ship something that changes the comparison\n- Sales team reports new objections\n- Win\u002Floss analysis reveals new patterns\n\n**Review cadence:**\n- Major competitors: monthly review\n- Minor competitors: quarterly review\n- Emerging competitors: as needed\n\n## Responding to Competitor Moves\n\n### When to Respond\n\n**Always respond:**\n- Competitor makes false claims about you\n- Competitor targets your specific customers\n- Major market shift that affects positioning\n\n**Consider responding:**\n- Competitor launches feature you have\n- Competitor enters your core market\n- Competitor's crisis creates opportunity\n\n**Usually don't respond:**\n- Minor feature parity announcements\n- Competitor's internal issues (unless affects their customers)\n- Petty competitive shots\n\n### Response Playbooks\n\n**Feature launch response:**\n1. Assess: Do we have parity? Better? Gap?\n2. Internal communication to sales\u002Fsupport\n3. Update battlecards if needed\n4. Consider content response (blog, comparison page update)\n5. Monitor developer conversations for context\n\n**Pricing change response:**\n1. Analyze impact on competitive positioning\n2. Update pricing comparison materials\n3. Brief sales team\n4. Consider if pricing adjustment needed\n5. Monitor churn\u002Facquisition impact\n\n**Crisis opportunity response:**\n1. Don't be sleazy or pile on\n2. Be helpful to affected users if appropriate\n3. Create migration content if there's genuine demand\n4. Let your product speak for itself\n\n## Tools\n\n### Social Listening\n\nUse monitoring tools to set up alerts for these patterns:\n- Competitor sentiment overview (last 30 days, by sentiment)\n- Churn signals: \"alternative OR migrating OR switching\" + competitor name\n- Feature gaps: \"wish OR need OR missing\" + competitor name\n- Comparison mentions: \"[competitor] vs\"\n\n### Other Tools\n\n**GitHub Monitoring:**\n```bash\n# Track competitor repo activity\ngh api repos\u002F[competitor]\u002F[repo] --jq '.stargazers_count, .open_issues_count'\n\n# Search for competitor mentions in issues\ngh search issues \"[competitor]\" --limit 50\n```\n\n**npm\u002FPyPI Monitoring:**\n- Track download trends for competitor packages\n- Monitor version release frequency\n- Watch for new packages in their ecosystem\n\n**Archive.org:**\n- Track historical changes to competitor websites\n- Document pricing changes over time\n- Capture positioning shifts\n\n**LinkedIn\u002FCareers:**\n- Track hiring patterns\n- Identify strategic direction from job postings\n- Monitor team growth signals\n\n## Related Skills\n\n- **developer-listening** - Broader monitoring beyond just competitors\n- **alternatives-pages** - Turn competitive intelligence into content\n- **positioning** - Differentiate based on competitive insights\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":31,"source":48,"license":14,"date_added":49,"description":7,"source_repo":50,"source_type":36,"license_source":51},"https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Ftree\u002Fmain\u002Fskills\u002Fcompetitor-tracking",1782864000000,"jonathimer\u002Fdevmarketing-skills","https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Fblob\u002Fmain\u002FLICENSE","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Fcompetitor-tracking","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612","2026-10-25 23:50:58",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill competitor-tracking",{"tool":63,"command":64},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill competitor-tracking",{"tool":66,"command":67},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill competitor-tracking","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fcompetitor-tracking\u002FSKILL.md",true,[71],{"path":72,"resourceType":73,"resourceTypeDesc":74,"sizeBytes":75,"sourceHtmlUrl":76},"README.md","REFERENCE","参考文档",1353,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fcompetitor-tracking\u002FREADME.md",[78,106,130,155,179,203],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":89,"publishedAt":43},"01M6Q0FA5FZ410Z33Z3TFQ4DBA","zero-trust","Implement zero-trust network architecture. Configure identity-based access, micro-segmentation, and continuous verification. Use when implementing modern security architectures.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzero-trust\u002FSKILL.md",[84],{"categoryNo":85,"categoryName":86,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[90,91,92,93,94,95,80,96,97,98,99,100,36,35,101,31,102,103,104,105],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","devops-security","access","configure","only","active","scope","scripts","relevant","implementing",{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":43},"01M6Q0F1YZJW3KX5FBKEVZ8CV4","zcode-delegate","Delegate coding tasks to the Z.AI ZCode CLI only when the user explicitly requests it, while the orchestrator retains review and landing responsibility.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzcode-delegate\u002FSKILL.md",[],[113,114,115,116,117,118,119,120,121,122,123,124,125,100,126,36,127,128,31,129],"delegate","zcode","zcode delegate","review","cli","orchestration","tasks","run","Bash","model","node","read","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":43},"01M6Q0ETK41VGNMYEXW0T00AJN","youtube-transcript","Fetch YouTube transcripts through DeepAPI or local fallback tooling and save clean text output.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript\u002FSKILL.md",[],[137,138,139,140,141,142,143,144,145,146,147,148,149,36,35,150,151,152,153,154],"transcript","youtube transcript","youtube","safe","github","codex","research","license","https","text","fetch","tooling","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":156,"name":157,"nameZh":6,"description":158,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":159,"categories":160,"keywords":168,"publishedAt":43},"01M6Q0EPPH2PVMDW40017F8WX0","youtube-transcript-skills","Fetch YouTube video transcripts, search videos\u002Fchannels, browse channels, and extract playlists via the getyoutubetranscript.com API - free tier, no card required.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-transcript-skills\u002FSKILL.md",[161,164,167],{"categoryNo":162,"categoryName":163,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":165,"categoryName":166,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[137,138,139,169,140,170,141,142,144,171,172,173,174,147,175,36,35,176,177,178],"youtube transcript skills","gemini","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":180,"name":181,"nameZh":6,"description":182,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":183,"categories":184,"keywords":189,"publishedAt":43},"01M6Q0EAB96PX83W5PTE8A0R8D","youtube-notetaker","Turn YouTube talks into local study notes with slides, transcripts, editable annotations, and a markdown-backed viewer.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-notetaker\u002FSKILL.md",[185,188],{"categoryNo":186,"categoryName":187,"taxonomyType":87,"taxonomyTypeDesc":88},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":165,"categoryName":166,"taxonomyType":87,"taxonomyTypeDesc":88},[139,190,191,117,140,192,193,194,195,144,173,196,197,198,199,35,200,150,201,202],"youtube notetaker","notetaker","workflow","official","notes","code","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":204,"name":205,"nameZh":6,"description":206,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":207,"categories":208,"keywords":210,"publishedAt":43},"01M6Q0E55F0GW5MX48V8HXS8B5","youtube-full","Fetch YouTube transcripts, search videos, browse channels, and extract playlists via TranscriptAPI — no yt-dlp, no Google API key, works from any cloud server.","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fyoutube-full\u002FSKILL.md",[209],{"categoryNo":162,"categoryName":163,"taxonomyType":87,"taxonomyTypeDesc":88},[211,139,212,213,140,170,171,214,215,172,173,174,147,216,175,36,35,176,217,153],"youtube full","full","google","server","dlp","credits","automatic"]