[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PBPXTGTYG5YCRWR3VASADH":3,"skill-same:01M6PBPXTGTYG5YCRWR3VASADH":67},{"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":17,"publishedAt":38,"linkOnly":39,"markdownContent":40,"markdownBody":41,"frontMatter":42,"refName":22,"commitSha":48,"skillDirectory":49,"forksCount":13,"repositoryHtmlUrl":50,"repositoryHomepageUrl":6,"ownerHtmlUrl":51,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":52,"install":53,"resources":66},"01M6PBPXTGTYG5YCRWR3VASADH","planning-and-task-breakdown",null,"Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.","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\u002Fplanning-and-task-breakdown\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"task","task breakdown","planning and task breakdown","planning","main","tasks","break","estimate","task-breakdown","tree","you","scope","requirements","license","github","community","agent-skills","use","work","parallel","2026-11-10 10:12:30",false,"---\nname: planning-and-task-breakdown\ndescription: Breaks work into ordered tasks. Use when you have a spec or clear requirements and need to break work into implementable tasks. Use when a task feels too large to start, when you need to estimate scope, or when parallel work is possible.\nrisk: none\nsource: https:\u002F\u002Fgithub.com\u002Faddyosmani\u002Fagent-skills\u002Ftree\u002Fmain\u002Fskills\u002Fplanning-and-task-breakdown\nsource_repo: addyosmani\u002Fagent-skills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Faddyosmani\u002Fagent-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Planning and Task Breakdown\n\n## Overview\n\nDecompose work into small, verifiable tasks with explicit acceptance criteria. Good task breakdown is the difference between an agent that completes work reliably and one that produces a tangled mess. Every task should be small enough to implement, test, and verify in a single focused session.\n\n## When to Use\n\n- You have a spec and need to break it into implementable units\n- A task feels too large or vague to start\n- Work needs to be parallelized across multiple agents or sessions\n- You need to communicate scope to a human\n- The implementation order isn't obvious\n\n**When NOT to use:** Single-file changes with obvious scope, or when the spec already contains well-defined tasks.\n\n## The Planning Process\n\n### Step 1: Enter Plan Mode\n\nBefore writing any code, operate in read-only mode:\n\n- Read the spec and relevant codebase sections\n- Identify existing patterns and conventions\n- Map dependencies between components\n- Note risks and unknowns\n\n**Do NOT write code during planning.** The output is a plan document, not implementation.\n\n### Step 2: Identify the Dependency Graph\n\nMap what depends on what:\n\n```\nDatabase schema\n    │\n    ├── API models\u002Ftypes\n    │       │\n    │       ├── API endpoints\n    │       │       │\n    │       │       └── Frontend API client\n    │       │               │\n    │       │               └── UI components\n    │       │\n    │       └── Validation logic\n    │\n    └── Seed data \u002F migrations\n```\n\nImplementation order follows the dependency graph bottom-up: build foundations first.\n\n### Step 3: Slice Vertically\n\nInstead of building all the database, then all the API, then all the UI — build one complete feature path at a time:\n\n**Bad (horizontal slicing):**\n```\nTask 1: Build entire database schema\nTask 2: Build all API endpoints\nTask 3: Build all UI components\nTask 4: Connect everything\n```\n\n**Good (vertical slicing):**\n```\nTask 1: User can create an account (schema + API + UI for registration)\nTask 2: User can log in (auth schema + API + UI for login)\nTask 3: User can create a task (task schema + API + UI for creation)\nTask 4: User can view task list (query + API + UI for list view)\n```\n\nEach vertical slice delivers working, testable functionality.\n\n### Step 4: Write Tasks\n\nEach task follows this structure:\n\n```markdown\n## Task [N]: [Short descriptive title]\n\n**Description:** One paragraph explaining what this task accomplishes.\n\n**Acceptance criteria:**\n- [ ] [Specific, testable condition]\n- [ ] [Specific, testable condition]\n\n**Verification:**\n- [ ] Tests pass: `npm test -- --grep \"feature-name\"`\n- [ ] Build succeeds: `npm run build`\n- [ ] Manual check: [description of what to verify]\n\n**Dependencies:** [Task numbers this depends on, or \"None\"]\n\n**Files likely touched:**\n- `src\u002Fpath\u002Fto\u002Ffile.ts`\n- `tests\u002Fpath\u002Fto\u002Ftest.ts`\n\n**Estimated scope:** [Small: 1-2 files | Medium: 3-5 files | Large: 5+ files]\n```\n\n### Step 5: Order and Checkpoint\n\nArrange tasks so that:\n\n1. Dependencies are satisfied (build foundation first)\n2. Each task leaves the system in a working state\n3. Verification checkpoints occur after every 2-3 tasks\n4. High-risk tasks are early (fail fast)\n\nAdd explicit checkpoints:\n\n```markdown\n## Checkpoint: After Tasks 1-3\n- [ ] All tests pass\n- [ ] Application builds without errors\n- [ ] Core user flow works end-to-end\n- [ ] Review with human before proceeding\n```\n\n## Task Sizing Guidelines\n\n| Size | Files | Scope | Example |\n|------|-------|-------|---------|\n| **XS** | 1 | Single function or config change | Add a validation rule |\n| **S** | 1-2 | One component or endpoint | Add a new API endpoint |\n| **M** | 3-5 | One feature slice | User registration flow |\n| **L** | 5-8 | Multi-component feature | Search with filtering and pagination |\n| **XL** | 8+ | **Too large — break it down further** | — |\n\nIf a task is L or larger, it should be broken into smaller tasks. An agent performs best on S and M tasks.\n\n**When to break a task down further:**\n- It would take more than one focused session (roughly 2+ hours of agent work)\n- You cannot describe the acceptance criteria in 3 or fewer bullet points\n- It touches two or more independent subsystems (e.g., auth and billing)\n- You find yourself writing \"and\" in the task title (a sign it is two tasks)\n\n## Plan Document Template\n\n```markdown\n# Implementation Plan: [Feature\u002FProject Name]\n\n## Overview\n[One paragraph summary of what we're building]\n\n## Architecture Decisions\n- [Key decision 1 and rationale]\n- [Key decision 2 and rationale]\n\n## Task List\n\n### Phase 1: Foundation\n- [ ] Task 1: ...\n- [ ] Task 2: ...\n\n### Checkpoint: Foundation\n- [ ] Tests pass, builds clean\n\n### Phase 2: Core Features\n- [ ] Task 3: ...\n- [ ] Task 4: ...\n\n### Checkpoint: Core Features\n- [ ] End-to-end flow works\n\n### Phase 3: Polish\n- [ ] Task 5: ...\n- [ ] Task 6: ...\n\n### Checkpoint: Complete\n- [ ] All acceptance criteria met\n- [ ] Ready for review\n\n## Risks and Mitigations\n| Risk | Impact | Mitigation |\n|------|--------|------------|\n| [Risk] | [High\u002FMed\u002FLow] | [Strategy] |\n\n## Open Questions\n- [Question needing human input]\n```\n\n## Parallelization Opportunities\n\nWhen multiple agents or sessions are available:\n\n- **Safe to parallelize:** Independent feature slices, tests for already-implemented features, documentation\n- **Must be sequential:** Database migrations, shared state changes, dependency chains\n- **Needs coordination:** Features that share an API contract (define the contract first, then parallelize)\n\n## Common Rationalizations\n\n| Rationalization | Reality |\n|---|---|\n| \"I'll figure it out as I go\" | That's how you end up with a tangled mess and rework. 10 minutes of planning saves hours. |\n| \"The tasks are obvious\" | Write them down anyway. Explicit tasks surface hidden dependencies and forgotten edge cases. |\n| \"Planning is overhead\" | Planning is the task. Implementation without a plan is just typing. |\n| \"I can hold it all in my head\" | Context windows are finite. Written plans survive session boundaries and compaction. |\n\n## Red Flags\n\n- Starting implementation without a written task list\n- Tasks that say \"implement the feature\" without acceptance criteria\n- No verification steps in the plan\n- All tasks are XL-sized\n- No checkpoints between tasks\n- Dependency order isn't considered\n\n## Verification\n\nBefore starting implementation, confirm:\n\n- [ ] Every task has acceptance criteria\n- [ ] Every task has a verification step\n- [ ] Task dependencies are identified and ordered correctly\n- [ ] No task touches more than ~5 files\n- [ ] Checkpoints exist between major phases\n- [ ] The human has reviewed and approved the plan\n\n## See Also\n\nAcceptance criteria are per-task and answer \"did we build the right thing?\". They sit on top of the project-wide Definition of Done, the standing bar every task clears before it counts as done. See `references\u002Fdefinition-of-done.md`.\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","# Planning and Task Breakdown\n\n## Overview\n\nDecompose work into small, verifiable tasks with explicit acceptance criteria. Good task breakdown is the difference between an agent that completes work reliably and one that produces a tangled mess. Every task should be small enough to implement, test, and verify in a single focused session.\n\n## When to Use\n\n- You have a spec and need to break it into implementable units\n- A task feels too large or vague to start\n- Work needs to be parallelized across multiple agents or sessions\n- You need to communicate scope to a human\n- The implementation order isn't obvious\n\n**When NOT to use:** Single-file changes with obvious scope, or when the spec already contains well-defined tasks.\n\n## The Planning Process\n\n### Step 1: Enter Plan Mode\n\nBefore writing any code, operate in read-only mode:\n\n- Read the spec and relevant codebase sections\n- Identify existing patterns and conventions\n- Map dependencies between components\n- Note risks and unknowns\n\n**Do NOT write code during planning.** The output is a plan document, not implementation.\n\n### Step 2: Identify the Dependency Graph\n\nMap what depends on what:\n\n```\nDatabase schema\n    │\n    ├── API models\u002Ftypes\n    │       │\n    │       ├── API endpoints\n    │       │       │\n    │       │       └── Frontend API client\n    │       │               │\n    │       │               └── UI components\n    │       │\n    │       └── Validation logic\n    │\n    └── Seed data \u002F migrations\n```\n\nImplementation order follows the dependency graph bottom-up: build foundations first.\n\n### Step 3: Slice Vertically\n\nInstead of building all the database, then all the API, then all the UI — build one complete feature path at a time:\n\n**Bad (horizontal slicing):**\n```\nTask 1: Build entire database schema\nTask 2: Build all API endpoints\nTask 3: Build all UI components\nTask 4: Connect everything\n```\n\n**Good (vertical slicing):**\n```\nTask 1: User can create an account (schema + API + UI for registration)\nTask 2: User can log in (auth schema + API + UI for login)\nTask 3: User can create a task (task schema + API + UI for creation)\nTask 4: User can view task list (query + API + UI for list view)\n```\n\nEach vertical slice delivers working, testable functionality.\n\n### Step 4: Write Tasks\n\nEach task follows this structure:\n\n```markdown\n## Task [N]: [Short descriptive title]\n\n**Description:** One paragraph explaining what this task accomplishes.\n\n**Acceptance criteria:**\n- [ ] [Specific, testable condition]\n- [ ] [Specific, testable condition]\n\n**Verification:**\n- [ ] Tests pass: `npm test -- --grep \"feature-name\"`\n- [ ] Build succeeds: `npm run build`\n- [ ] Manual check: [description of what to verify]\n\n**Dependencies:** [Task numbers this depends on, or \"None\"]\n\n**Files likely touched:**\n- `src\u002Fpath\u002Fto\u002Ffile.ts`\n- `tests\u002Fpath\u002Fto\u002Ftest.ts`\n\n**Estimated scope:** [Small: 1-2 files | Medium: 3-5 files | Large: 5+ files]\n```\n\n### Step 5: Order and Checkpoint\n\nArrange tasks so that:\n\n1. Dependencies are satisfied (build foundation first)\n2. Each task leaves the system in a working state\n3. Verification checkpoints occur after every 2-3 tasks\n4. High-risk tasks are early (fail fast)\n\nAdd explicit checkpoints:\n\n```markdown\n## Checkpoint: After Tasks 1-3\n- [ ] All tests pass\n- [ ] Application builds without errors\n- [ ] Core user flow works end-to-end\n- [ ] Review with human before proceeding\n```\n\n## Task Sizing Guidelines\n\n| Size | Files | Scope | Example |\n|------|-------|-------|---------|\n| **XS** | 1 | Single function or config change | Add a validation rule |\n| **S** | 1-2 | One component or endpoint | Add a new API endpoint |\n| **M** | 3-5 | One feature slice | User registration flow |\n| **L** | 5-8 | Multi-component feature | Search with filtering and pagination |\n| **XL** | 8+ | **Too large — break it down further** | — |\n\nIf a task is L or larger, it should be broken into smaller tasks. An agent performs best on S and M tasks.\n\n**When to break a task down further:**\n- It would take more than one focused session (roughly 2+ hours of agent work)\n- You cannot describe the acceptance criteria in 3 or fewer bullet points\n- It touches two or more independent subsystems (e.g., auth and billing)\n- You find yourself writing \"and\" in the task title (a sign it is two tasks)\n\n## Plan Document Template\n\n```markdown\n# Implementation Plan: [Feature\u002FProject Name]\n\n## Overview\n[One paragraph summary of what we're building]\n\n## Architecture Decisions\n- [Key decision 1 and rationale]\n- [Key decision 2 and rationale]\n\n## Task List\n\n### Phase 1: Foundation\n- [ ] Task 1: ...\n- [ ] Task 2: ...\n\n### Checkpoint: Foundation\n- [ ] Tests pass, builds clean\n\n### Phase 2: Core Features\n- [ ] Task 3: ...\n- [ ] Task 4: ...\n\n### Checkpoint: Core Features\n- [ ] End-to-end flow works\n\n### Phase 3: Polish\n- [ ] Task 5: ...\n- [ ] Task 6: ...\n\n### Checkpoint: Complete\n- [ ] All acceptance criteria met\n- [ ] Ready for review\n\n## Risks and Mitigations\n| Risk | Impact | Mitigation |\n|------|--------|------------|\n| [Risk] | [High\u002FMed\u002FLow] | [Strategy] |\n\n## Open Questions\n- [Question needing human input]\n```\n\n## Parallelization Opportunities\n\nWhen multiple agents or sessions are available:\n\n- **Safe to parallelize:** Independent feature slices, tests for already-implemented features, documentation\n- **Must be sequential:** Database migrations, shared state changes, dependency chains\n- **Needs coordination:** Features that share an API contract (define the contract first, then parallelize)\n\n## Common Rationalizations\n\n| Rationalization | Reality |\n|---|---|\n| \"I'll figure it out as I go\" | That's how you end up with a tangled mess and rework. 10 minutes of planning saves hours. |\n| \"The tasks are obvious\" | Write them down anyway. Explicit tasks surface hidden dependencies and forgotten edge cases. |\n| \"Planning is overhead\" | Planning is the task. Implementation without a plan is just typing. |\n| \"I can hold it all in my head\" | Context windows are finite. Written plans survive session boundaries and compaction. |\n\n## Red Flags\n\n- Starting implementation without a written task list\n- Tasks that say \"implement the feature\" without acceptance criteria\n- No verification steps in the plan\n- All tasks are XL-sized\n- No checkpoints between tasks\n- Dependency order isn't considered\n\n## Verification\n\nBefore starting implementation, confirm:\n\n- [ ] Every task has acceptance criteria\n- [ ] Every task has a verification step\n- [ ] Task dependencies are identified and ordered correctly\n- [ ] No task touches more than ~5 files\n- [ ] Checkpoints exist between major phases\n- [ ] The human has reviewed and approved the plan\n\n## See Also\n\nAcceptance criteria are per-task and answer \"did we build the right thing?\". They sit on top of the project-wide Definition of Done, the standing bar every task clears before it counts as done. See `references\u002Fdefinition-of-done.md`.\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":43,"source":44,"license":14,"date_added":45,"description":7,"source_repo":46,"source_type":33,"license_source":47},"none","https:\u002F\u002Fgithub.com\u002Faddyosmani\u002Fagent-skills\u002Ftree\u002Fmain\u002Fskills\u002Fplanning-and-task-breakdown",1782864000000,"addyosmani\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002Faddyosmani\u002Fagent-skills\u002Fblob\u002Fmain\u002FLICENSE","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Fplanning-and-task-breakdown","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":54,"prompt":64,"zipAvailable":65},[55,58,61],{"tool":56,"command":57},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill planning-and-task-breakdown",{"tool":59,"command":60},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill planning-and-task-breakdown",{"tool":62,"command":63},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill planning-and-task-breakdown","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fplanning-and-task-breakdown\u002FSKILL.md",true,[],[68,96,119,142,170,194],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":79,"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",[74],{"categoryNo":75,"categoryName":76,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[80,81,82,83,84,85,70,86,87,88,89,90,33,22,91,92,29,93,94,95],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","devops-security","access","configure","only","active","critical","scripts","relevant","implementing",{"skillNo":97,"name":98,"nameZh":6,"description":99,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":100,"categories":101,"keywords":102,"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",[],[103,104,105,106,107,108,23,109,110,111,112,113,114,90,115,33,116,117,92,118],"delegate","zcode","zcode delegate","review","cli","orchestration","run","Bash","model","node","read","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"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",[],[126,127,128,129,32,130,131,31,132,133,134,135,136,33,22,137,138,139,140,141],"transcript","youtube transcript","youtube","safe","codex","research","https","text","fetch","tooling","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":143,"name":144,"nameZh":6,"description":145,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":146,"categories":147,"keywords":159,"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",[148,151,154],{"categoryNo":149,"categoryName":150,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":152,"categoryName":153,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":155,"categoryName":156,"taxonomyType":157,"taxonomyTypeDesc":158},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[126,127,128,160,129,161,32,130,31,162,163,164,165,134,166,33,22,167,168,169],"youtube transcript skills","gemini","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":171,"name":172,"nameZh":6,"description":173,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":174,"categories":175,"keywords":180,"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",[176,179],{"categoryNo":177,"categoryName":178,"taxonomyType":77,"taxonomyTypeDesc":78},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":152,"categoryName":153,"taxonomyType":77,"taxonomyTypeDesc":78},[128,181,182,107,129,183,184,185,186,31,164,187,188,189,190,22,191,137,192,193],"youtube notetaker","notetaker","workflow","official","notes","code","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":195,"name":196,"nameZh":6,"description":197,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":198,"categories":199,"keywords":201,"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",[200],{"categoryNo":149,"categoryName":150,"taxonomyType":77,"taxonomyTypeDesc":78},[202,128,203,204,129,161,162,205,206,163,164,165,134,207,166,33,22,167,208,140],"youtube full","full","google","server","dlp","credits","automatic"]