[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P1EVFKX7A0TYWK22T0P2SE":3,"skill-same:01M6P1EVFKX7A0TYWK22T0P2SE":80},{"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":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":34,"commitSha":47,"skillDirectory":48,"forksCount":13,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M6P1EVFKX7A0TYWK22T0P2SE","developer-audience-context",null,"When the user wants to establish or update their developer audience context. Also use when starting any other developer marketing skill to ensure foundational context is loaded.","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\u002Fdeveloper-audience-context\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],"developer","context","developer audience context","github","update","license","https","marketing","user","use","community","main","wed","critical","tree","2026-11-10 10:12:30",false,"---\nname: developer-audience-context\ndescription: \"When the user wants to establish or update their developer audience context. Also use when starting any other developer marketing skill to ensure foundational context is loaded.\"\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Ftree\u002Fmain\u002Fskills\u002Fdeveloper-audience-context\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# Developer Audience Context\n## When to Use\n\nUse this skill when you need when the user wants to establish or update their developer audience context. Also use when starting any other developer marketing skill to ensure foundational context is loaded. Trigger phrases include \"developer persona,\" \"target developers,\" \"who are our developers,\" \"developer...\n\n\nThis skill helps you create and maintain `.agents\u002Fdeveloper-audience-context.md` — a foundational document that captures everything about your target developers. All other developer marketing skills reference this document first, so you only define your audience once.\n\n---\n\n## Before You Start\n\nCheck if `.agents\u002Fdeveloper-audience-context.md` exists:\n\n- **If it exists**: Read it and offer to update specific sections\n- **If it doesn't exist**: Create the directory and file, then walk through each section\n\n---\n\n## Two Ways to Build Context\n\n### Option 1: Auto-Draft from Codebase (Recommended)\n\nAnalyze existing materials to draft an initial version:\n\n1. **README.md** — Product description, features, getting started\n2. **Documentation** — `\u002Fdocs`, API reference, tutorials\n3. **Landing pages** — `index.html`, marketing copy\n4. **package.json \u002F pyproject.toml** — Dependencies reveal ecosystem\n5. **GitHub Issues** — Common questions, frustrations, use cases\n6. **Existing blog posts** — Technical content, tutorials\n\nAfter drafting, walk through each section to validate and fill gaps.\n\n### Option 2: Start from Scratch\n\nAsk questions section-by-section. Don't advance until the current section is complete.\n\n---\n\n## The 10 Sections to Capture\n\n### 1. Product Overview\n\n| Field | What to capture |\n|-------|-----------------|\n| Product name | Official name and any aliases |\n| One-liner | \"We help [developers] do [X] without [Y]\" |\n| Category | API, SDK, CLI, SaaS, open source library, infrastructure |\n| Core technology | Languages, frameworks, platforms supported |\n| Pricing model | Free\u002Fopen source, freemium, usage-based, seat-based |\n\n### 2. Developer Persona\n\nNot \"developers\" generically — get specific:\n\n| Field | What to capture |\n|-------|-----------------|\n| Primary role | Backend, frontend, full-stack, DevOps, data, ML, mobile |\n| Seniority | Junior, mid, senior, staff, lead, architect |\n| Company size | Solo, startup, scale-up, enterprise |\n| Industry verticals | Fintech, healthtech, e-commerce, gaming, B2B SaaS |\n| Tech stack | Languages, frameworks, cloud providers they use |\n| Decision authority | Individual contributor, team lead, buyer, influencer |\n\n**Ask**: \"Describe the developer who gets the most value from your product in one paragraph. What's their day-to-day like?\"\n\n### 3. Where They Hang Out\n\nDevelopers research before they buy. Know where:\n\n| Channel | Specifics to capture |\n|---------|---------------------|\n| Communities | Specific subreddits, Discord servers, Slack groups |\n| Social | Twitter\u002FX hashtags, LinkedIn groups |\n| Content | Blogs they read, newsletters they subscribe to, podcasts |\n| Events | Conferences, meetups, hackathons |\n| Code | GitHub topics, Stack Overflow tags |\n\n**Pro tip**: Use social listening tools to monitor conversations across Hacker News, Reddit, Stack Overflow, GitHub, and Twitter. See where discussions about your problem space happen organically.\n\n### 4. Problems & Pain Points\n\nCapture the actual problems, not your solution's features:\n\n| Level | What to capture |\n|-------|-----------------|\n| Functional | \"I can't do X\" \u002F \"X takes too long\" \u002F \"X is error-prone\" |\n| Emotional | Frustration, anxiety, embarrassment, fear |\n| Situational | When does the pain occur? What triggers the search? |\n\n**Ask**: \"What's the #1 frustration that brings developers to you?\"\n\n**Research**: Search Reddit, Hacker News, and Stack Overflow for complaints about your problem space. Capture verbatim quotes.\n\n### 5. Current Alternatives\n\nWhat are developers using today instead of you?\n\n| Alternative type | Examples |\n|-----------------|----------|\n| Direct competitors | Tools that solve the same problem |\n| DIY \u002F build it yourself | Custom scripts, internal tools |\n| Indirect solutions | Workarounds, manual processes |\n| Do nothing | Live with the pain |\n\nFor each alternative, capture:\n- Why developers choose it\n- What's frustrating about it\n- What would make them switch\n\n### 6. Key Differentiators\n\nWhat makes you different — in developer terms:\n\n| Differentiator type | Example |\n|--------------------|---------|\n| Technical | \"10x faster,\" \"No dependencies,\" \"Type-safe\" |\n| DX (Developer Experience) | \"5-minute setup,\" \"Great docs,\" \"First-class CLI\" |\n| Ecosystem | \"Works with X,\" \"Built for Y framework\" |\n| Philosophy | \"Open source,\" \"Privacy-first,\" \"Local-first\" |\n\n**Warning**: Avoid marketing fluff. Developers see through \"best-in-class\" and \"enterprise-grade.\" Use specific, provable claims.\n\n### 7. Verbatim Developer Language\n\nCapture exact phrases developers use — not polished marketing copy:\n\n| Category | Examples |\n|----------|----------|\n| Describing the problem | \"This is such a pain,\" \"I wish I could just...\" |\n| Describing your product | How they explain it to others |\n| Objections | \"But what about...\", \"I'm worried that...\" |\n| Praise | Testimonials, tweets, GitHub comments |\n\n**Sources**: GitHub issues, Twitter mentions, Hacker News comments, support tickets, sales calls, community Slack\u002FDiscord.\n\n### 8. Technical Trust Signals\n\nWhat proof points matter to developers:\n\n| Signal type | Examples |\n|-------------|----------|\n| Adoption | GitHub stars, npm downloads, Docker pulls |\n| Quality | Test coverage, security audits, uptime SLA |\n| Community | Contributors, Discord members, forum activity |\n| Credibility | Backed by X, used by Y, created by Z |\n| Transparency | Open source, public roadmap, changelog |\n\n### 9. Conversion Actions\n\nWhat does success look like at each stage?\n\n| Stage | Primary action | Secondary actions |\n|-------|---------------|-------------------|\n| Awareness | Star repo, follow on Twitter | Read blog post, share content |\n| Consideration | Clone repo, read docs | Watch demo, join Discord |\n| Trial | Sign up, install SDK | Complete quickstart, make first API call |\n| Activation | Reach \"Hello World\" moment | Integrate into real project |\n| Conversion | Upgrade to paid | Add team members, expand usage |\n\n### 10. Voice & Tone\n\nHow should you sound when talking to these developers?\n\n| Dimension | Spectrum |\n|-----------|----------|\n| Formality | Casual ← → Professional |\n| Technicality | Accessible ← → Deep technical |\n| Personality | Neutral ← → Opinionated |\n| Humor | Serious ← → Playful |\n\n**Examples**:\n- Stripe → Professional, precise, clean\n- Vercel → Modern, confident, developer-first\n- Supabase → Friendly, accessible, community-driven\n- Tailwind → Opinionated, direct, practical\n\n---\n\n## Output Format\n\nSave to `.agents\u002Fdeveloper-audience-context.md` with this structure:\n\n```markdown\n# Developer Audience Context\n\nLast updated: [DATE]\n\n## Product Overview\n[Section content]\n\n## Developer Persona\n[Section content]\n\n## Where They Hang Out\n[Section content]\n\n## Problems & Pain Points\n[Section content]\n\n## Current Alternatives\n[Section content]\n\n## Key Differentiators\n[Section content]\n\n## Verbatim Developer Language\n[Section content]\n\n## Technical Trust Signals\n[Section content]\n\n## Conversion Actions\n[Section content]\n\n## Voice & Tone\n[Section content]\n```\n\n---\n\n## Maintenance\n\nUpdate this document when:\n\n- You learn something new from user research\n- You find great verbatim quotes\n- Your positioning or differentiation changes\n- You expand to new developer segments\n\n---\n\n## Tools\n\n| Tool | Use case |\n|------|----------|\n| **[Octolens](https:\u002F\u002Foctolens.com)** | Monitor developer conversations across GitHub, Hacker News, Reddit, Stack Overflow, Twitter. Essential for capturing verbatim language, finding pain points, and understanding where your developers hang out. |\n| **GitHub Search** | Find how developers describe problems in issues |\n| **Twitter Advanced Search** | Find discussions about your space |\n| **Google Alerts** | Track mentions of competitors and problem keywords |\n\n---\n\n## Related Skills\n\nAfter establishing context, these skills will reference it:\n\n- `devrel-content` — Writing content that resonates\n- `hacker-news-strategy` — Engaging on HN authentically\n- `developer-onboarding` — Optimizing time-to-value\n- `developer-seo` — Targeting the right technical queries\n- `competitor-tracking` — Understanding your competitive landscape\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","# Developer Audience Context\n## When to Use\n\nUse this skill when you need when the user wants to establish or update their developer audience context. Also use when starting any other developer marketing skill to ensure foundational context is loaded. Trigger phrases include \"developer persona,\" \"target developers,\" \"who are our developers,\" \"developer...\n\n\nThis skill helps you create and maintain `.agents\u002Fdeveloper-audience-context.md` — a foundational document that captures everything about your target developers. All other developer marketing skills reference this document first, so you only define your audience once.\n\n---\n\n## Before You Start\n\nCheck if `.agents\u002Fdeveloper-audience-context.md` exists:\n\n- **If it exists**: Read it and offer to update specific sections\n- **If it doesn't exist**: Create the directory and file, then walk through each section\n\n---\n\n## Two Ways to Build Context\n\n### Option 1: Auto-Draft from Codebase (Recommended)\n\nAnalyze existing materials to draft an initial version:\n\n1. **README.md** — Product description, features, getting started\n2. **Documentation** — `\u002Fdocs`, API reference, tutorials\n3. **Landing pages** — `index.html`, marketing copy\n4. **package.json \u002F pyproject.toml** — Dependencies reveal ecosystem\n5. **GitHub Issues** — Common questions, frustrations, use cases\n6. **Existing blog posts** — Technical content, tutorials\n\nAfter drafting, walk through each section to validate and fill gaps.\n\n### Option 2: Start from Scratch\n\nAsk questions section-by-section. Don't advance until the current section is complete.\n\n---\n\n## The 10 Sections to Capture\n\n### 1. Product Overview\n\n| Field | What to capture |\n|-------|-----------------|\n| Product name | Official name and any aliases |\n| One-liner | \"We help [developers] do [X] without [Y]\" |\n| Category | API, SDK, CLI, SaaS, open source library, infrastructure |\n| Core technology | Languages, frameworks, platforms supported |\n| Pricing model | Free\u002Fopen source, freemium, usage-based, seat-based |\n\n### 2. Developer Persona\n\nNot \"developers\" generically — get specific:\n\n| Field | What to capture |\n|-------|-----------------|\n| Primary role | Backend, frontend, full-stack, DevOps, data, ML, mobile |\n| Seniority | Junior, mid, senior, staff, lead, architect |\n| Company size | Solo, startup, scale-up, enterprise |\n| Industry verticals | Fintech, healthtech, e-commerce, gaming, B2B SaaS |\n| Tech stack | Languages, frameworks, cloud providers they use |\n| Decision authority | Individual contributor, team lead, buyer, influencer |\n\n**Ask**: \"Describe the developer who gets the most value from your product in one paragraph. What's their day-to-day like?\"\n\n### 3. Where They Hang Out\n\nDevelopers research before they buy. Know where:\n\n| Channel | Specifics to capture |\n|---------|---------------------|\n| Communities | Specific subreddits, Discord servers, Slack groups |\n| Social | Twitter\u002FX hashtags, LinkedIn groups |\n| Content | Blogs they read, newsletters they subscribe to, podcasts |\n| Events | Conferences, meetups, hackathons |\n| Code | GitHub topics, Stack Overflow tags |\n\n**Pro tip**: Use social listening tools to monitor conversations across Hacker News, Reddit, Stack Overflow, GitHub, and Twitter. See where discussions about your problem space happen organically.\n\n### 4. Problems & Pain Points\n\nCapture the actual problems, not your solution's features:\n\n| Level | What to capture |\n|-------|-----------------|\n| Functional | \"I can't do X\" \u002F \"X takes too long\" \u002F \"X is error-prone\" |\n| Emotional | Frustration, anxiety, embarrassment, fear |\n| Situational | When does the pain occur? What triggers the search? |\n\n**Ask**: \"What's the #1 frustration that brings developers to you?\"\n\n**Research**: Search Reddit, Hacker News, and Stack Overflow for complaints about your problem space. Capture verbatim quotes.\n\n### 5. Current Alternatives\n\nWhat are developers using today instead of you?\n\n| Alternative type | Examples |\n|-----------------|----------|\n| Direct competitors | Tools that solve the same problem |\n| DIY \u002F build it yourself | Custom scripts, internal tools |\n| Indirect solutions | Workarounds, manual processes |\n| Do nothing | Live with the pain |\n\nFor each alternative, capture:\n- Why developers choose it\n- What's frustrating about it\n- What would make them switch\n\n### 6. Key Differentiators\n\nWhat makes you different — in developer terms:\n\n| Differentiator type | Example |\n|--------------------|---------|\n| Technical | \"10x faster,\" \"No dependencies,\" \"Type-safe\" |\n| DX (Developer Experience) | \"5-minute setup,\" \"Great docs,\" \"First-class CLI\" |\n| Ecosystem | \"Works with X,\" \"Built for Y framework\" |\n| Philosophy | \"Open source,\" \"Privacy-first,\" \"Local-first\" |\n\n**Warning**: Avoid marketing fluff. Developers see through \"best-in-class\" and \"enterprise-grade.\" Use specific, provable claims.\n\n### 7. Verbatim Developer Language\n\nCapture exact phrases developers use — not polished marketing copy:\n\n| Category | Examples |\n|----------|----------|\n| Describing the problem | \"This is such a pain,\" \"I wish I could just...\" |\n| Describing your product | How they explain it to others |\n| Objections | \"But what about...\", \"I'm worried that...\" |\n| Praise | Testimonials, tweets, GitHub comments |\n\n**Sources**: GitHub issues, Twitter mentions, Hacker News comments, support tickets, sales calls, community Slack\u002FDiscord.\n\n### 8. Technical Trust Signals\n\nWhat proof points matter to developers:\n\n| Signal type | Examples |\n|-------------|----------|\n| Adoption | GitHub stars, npm downloads, Docker pulls |\n| Quality | Test coverage, security audits, uptime SLA |\n| Community | Contributors, Discord members, forum activity |\n| Credibility | Backed by X, used by Y, created by Z |\n| Transparency | Open source, public roadmap, changelog |\n\n### 9. Conversion Actions\n\nWhat does success look like at each stage?\n\n| Stage | Primary action | Secondary actions |\n|-------|---------------|-------------------|\n| Awareness | Star repo, follow on Twitter | Read blog post, share content |\n| Consideration | Clone repo, read docs | Watch demo, join Discord |\n| Trial | Sign up, install SDK | Complete quickstart, make first API call |\n| Activation | Reach \"Hello World\" moment | Integrate into real project |\n| Conversion | Upgrade to paid | Add team members, expand usage |\n\n### 10. Voice & Tone\n\nHow should you sound when talking to these developers?\n\n| Dimension | Spectrum |\n|-----------|----------|\n| Formality | Casual ← → Professional |\n| Technicality | Accessible ← → Deep technical |\n| Personality | Neutral ← → Opinionated |\n| Humor | Serious ← → Playful |\n\n**Examples**:\n- Stripe → Professional, precise, clean\n- Vercel → Modern, confident, developer-first\n- Supabase → Friendly, accessible, community-driven\n- Tailwind → Opinionated, direct, practical\n\n---\n\n## Output Format\n\nSave to `.agents\u002Fdeveloper-audience-context.md` with this structure:\n\n```markdown\n# Developer Audience Context\n\nLast updated: [DATE]\n\n## Product Overview\n[Section content]\n\n## Developer Persona\n[Section content]\n\n## Where They Hang Out\n[Section content]\n\n## Problems & Pain Points\n[Section content]\n\n## Current Alternatives\n[Section content]\n\n## Key Differentiators\n[Section content]\n\n## Verbatim Developer Language\n[Section content]\n\n## Technical Trust Signals\n[Section content]\n\n## Conversion Actions\n[Section content]\n\n## Voice & Tone\n[Section content]\n```\n\n---\n\n## Maintenance\n\nUpdate this document when:\n\n- You learn something new from user research\n- You find great verbatim quotes\n- Your positioning or differentiation changes\n- You expand to new developer segments\n\n---\n\n## Tools\n\n| Tool | Use case |\n|------|----------|\n| **[Octolens](https:\u002F\u002Foctolens.com)** | Monitor developer conversations across GitHub, Hacker News, Reddit, Stack Overflow, Twitter. Essential for capturing verbatim language, finding pain points, and understanding where your developers hang out. |\n| **GitHub Search** | Find how developers describe problems in issues |\n| **Twitter Advanced Search** | Find discussions about your space |\n| **Google Alerts** | Track mentions of competitors and problem keywords |\n\n---\n\n## Related Skills\n\nAfter establishing context, these skills will reference it:\n\n- `devrel-content` — Writing content that resonates\n- `hacker-news-strategy` — Engaging on HN authentically\n- `developer-onboarding` — Optimizing time-to-value\n- `developer-seo` — Targeting the right technical queries\n- `competitor-tracking` — Understanding your competitive landscape\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":36,"source":43,"license":14,"date_added":44,"description":7,"source_repo":45,"source_type":33,"license_source":46},"https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Ftree\u002Fmain\u002Fskills\u002Fdeveloper-audience-context",1782864000000,"jonathimer\u002Fdevmarketing-skills","https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Fblob\u002Fmain\u002FLICENSE","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Fdeveloper-audience-context","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":53,"prompt":63,"zipAvailable":64},[54,57,60],{"tool":55,"command":56},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill developer-audience-context",{"tool":58,"command":59},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill developer-audience-context",{"tool":61,"command":62},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill developer-audience-context","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fdeveloper-audience-context\u002FSKILL.md",true,[66,72,76],{"path":67,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":70,"sourceHtmlUrl":71},"README.md","REFERENCE","参考文档",2183,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fdeveloper-audience-context\u002FREADME.md",{"path":73,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":74,"sourceHtmlUrl":75},"references\u002Fexample-apitest.md",7009,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fdeveloper-audience-context\u002Freferences\u002Fexample-apitest.md",{"path":77,"resourceType":68,"resourceTypeDesc":69,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Ftemplate.md",2954,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fdeveloper-audience-context\u002Freferences\u002Ftemplate.md",[81,109,133,155,179,203],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":92,"publishedAt":38},"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",[87],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[93,94,95,96,97,98,83,99,100,101,102,103,33,34,104,36,105,106,107,108],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","devops-security","access","configure","only","active","scope","scripts","relevant","implementing",{"skillNo":110,"name":111,"nameZh":6,"description":112,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":38},"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",[],[116,117,118,119,120,121,122,123,124,125,126,127,128,103,129,33,130,131,36,132],"delegate","zcode","zcode delegate","review","cli","orchestration","tasks","run","Bash","model","node","read","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":38},"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",[],[140,141,142,143,26,144,145,28,29,146,147,148,149,33,34,150,151,152,153,154],"transcript","youtube transcript","youtube","safe","codex","research","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":38},"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":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":165,"categoryName":166,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[140,141,142,169,143,170,26,144,28,171,172,173,174,147,175,33,34,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":38},"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":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":165,"categoryName":166,"taxonomyType":90,"taxonomyTypeDesc":91},[142,190,191,120,143,192,193,194,195,28,173,196,197,198,199,34,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":38},"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":90,"taxonomyTypeDesc":91},[211,142,212,213,143,170,171,214,215,172,173,174,147,216,175,33,34,176,217,153],"youtube full","full","google","server","dlp","credits","automatic"]