[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PCV6MBS14NH4QX1JS6H8EV":3,"skill-same:01M6PCV6MBS14NH4QX1JS6H8EV":66},{"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":47,"skillDirectory":48,"forksCount":13,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M6PCV6MBS14NH4QX1JS6H8EV","review-and-simplify-changes",null,"Review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes.","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\u002Freview-and-simplify-changes\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"changes","simplify","review and simplify changes","review","main","apply","fixes","for","tree","reuse","scope","critical","community","standards","diff","file","license","issues","code","code quality","2026-11-10 10:12:30",false,"---\nname: review-and-simplify-changes\ndescription: \"Review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes.\"\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002FDimillian\u002FSkills\u002Ftree\u002Fmain\u002Freview-and-simplify-changes\nsource_repo: Dimillian\u002FSkills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002FDimillian\u002FSkills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# Review and Simplify Changes\n## When to Use\n\nUse this skill when you need review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes. Use when the user asks to \"simplify code\", \"review changed code\", \"check for code reuse\", \"review code quality\", \"review...\n\n\nReview changed code for reuse, quality, efficiency, and clarity issues. Use Codex sub-agents to review in parallel, but keep those sub-agents read-only: they should only inspect code and send findings back to the main agent. Only the main agent may apply high-confidence, behavior-preserving fixes.\n\n## Modes\n\nChoose the mode from the user's request:\n\n- `review-only`: user asks to review, audit, or check the changes\n- `safe-fixes`: user asks to simplify, clean up, or refactor the changes\n- `fix-and-validate`: same as `safe-fixes`, but also run the smallest relevant validation after edits\n\nIf the user does not specify, default to:\n\n- `review-only` for \"review\", \"audit\", or \"check\"\n- `safe-fixes` for \"simplify\", \"clean up\", or \"refactor\"\n\n## Step 1: Determine the Scope and Diff Command\n\nPrefer this scope order:\n\n1. Files or paths explicitly named by the user\n2. Current git changes\n3. Files edited earlier in the current Codex turn\n4. Most recently modified tracked files, only if the user asked for a review but there is no diff\n\nIf there is no clear scope, stop and say so briefly.\n\nWhen using git changes, determine the smallest correct diff command based on the repo state:\n\n- unstaged work: `git diff`\n- staged work: `git diff --cached`\n- branch or commit comparison explicitly requested by the user: use that exact diff target\n- mixed staged and unstaged work: review both\n\nDo not assume `git diff HEAD` is the right default when a smaller diff is available.\n\nBefore reviewing standards or applying fixes, read the repo's local instruction files and relevant project docs for the touched area. Prefer the closest applicable guidance, such as:\n\n- `AGENTS.md`\n- repo workflow docs\n- architecture or style docs for the touched module\n\nUse those instructions to distinguish real issues from intentional local patterns.\n\n## Step 2: Launch Four Read-Only Review Sub-Agents in Parallel\n\nUse Codex sub-agents when the scope is large enough for parallel review to help. For a tiny diff or one very small file, it is acceptable to review locally instead.\n\nWhen spawning sub-agents:\n\n- give each sub-agent the same scope\n- tell each sub-agent to inspect only its assigned review role\n- tell each sub-agent it is operating in a read-only review pass\n- do not let sub-agents edit files, run `apply_patch`, stage changes, commit, or perform other state-mutating actions\n- ask for concise, structured findings only\n- ask each sub-agent to report file, line or symbol, problem, recommended fix, and confidence\n- ask each sub-agent to return findings to the main agent only; they must not implement fixes themselves\n\nUse four review roles.\n\n### Sub-Agent 1: Code Reuse Review\n\nReview the changes for reuse opportunities:\n\n1. Search for existing helpers, utilities, or shared abstractions that already solve the same problem.\n2. Flag duplicated functions or near-duplicate logic introduced in the change.\n3. Flag inline logic that should call an existing helper instead of re-implementing it.\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `explorer` for broad codebase lookup, or `reviewer` if a stronger review pass is more useful than wide search.\n\n### Sub-Agent 2: Code Quality Review\n\nReview the same changes for code quality issues:\n\n1. Redundant state, cached values, or derived values stored unnecessarily\n2. Parameter sprawl caused by threading new arguments through existing call chains\n3. Copy-paste with slight variation that should become a shared abstraction\n4. Leaky abstractions or ownership violations across module boundaries\n5. Stringly-typed values where existing typed contracts, enums, or constants already exist\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `reviewer`\n\n### Sub-Agent 3: Efficiency Review\n\nReview the same changes for efficiency issues:\n\n1. Repeated work, duplicate reads, duplicate API calls, or unnecessary recomputation\n2. Sequential work that could safely run concurrently\n3. New work added to startup, render, request, or other hot paths without clear need\n4. Pre-checks for existence when the operation itself can be attempted directly and errors handled\n5. Memory growth, missing cleanup, or listener\u002Fsubscription leaks\n6. Overly broad reads or scans when the code only needs a subset\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `reviewer`\n\n### Sub-Agent 4: Clarity and Standards Review\n\nReview the same changes for clarity, local standards, and balance:\n\n1. Violations of local project conventions or module patterns\n2. Unnecessary complexity, deep nesting, weak names, or redundant comments\n3. Overly compact or clever code that reduces readability\n4. Over-simplification that collapses separate concerns into one unclear unit\n5. Dead code, dead abstractions, or indirection without value\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `reviewer`\n\nOnly report issues that materially improve maintainability, correctness, or cost. Do not churn code just to make it look different.\n\n## Step 3: Aggregate Findings\n\nWait for all review sub-agents to complete, then merge their findings.\n\nThe main agent owns this step. Treat sub-agent output as review input only, not as permission to delegate code changes back out.\n\nNormalize findings into this shape:\n\n1. File and line or nearest symbol\n2. Category: reuse, quality, efficiency, or clarity\n3. Why it is a problem\n4. Recommended fix\n5. Confidence: high, medium, or low\n\nDiscard weak, duplicative, or instruction-conflicting findings before editing.\n\n## Step 4: Fix Issues Carefully\n\nIn `review-only` mode, stop after reporting findings.\n\nIn `safe-fixes` or `fix-and-validate` mode:\n\n- Only the main agent applies fixes for this skill\n- Apply only high-confidence, behavior-preserving fixes\n- Skip subjective refactors that need product or architectural judgment\n- Preserve local patterns when they are intentional or instruction-backed\n- Keep edits scoped to the reviewed files unless a small adjacent change is required to complete the fix correctly\n\nPrefer fixes like:\n\n- replacing duplicated code with an existing helper\n- removing redundant state or dead code\n- simplifying control flow without changing behavior\n- narrowing overly broad operations\n- renaming unclear locals when the scope is contained\n\nDo not stage, commit, or push changes as part of this skill.\n\n## Step 5: Validate When Required\n\nIn `fix-and-validate` mode, after the main agent finishes edits, run the smallest relevant validation for the touched scope.\n\nExamples:\n\n- targeted tests for the touched module\n- typecheck or compile for the touched target\n- formatter or lint check if that is the project's real safety gate\n\nPrefer fast, scoped validation over full-suite runs unless the change breadth justifies more.\n\nIf validation is skipped because the user asked not to run it, say so explicitly.\n\n## Step 6: Summarize Outcome\n\nClose with a brief result:\n\n- what was reviewed\n- what was fixed, if anything\n- what was intentionally left alone\n- whether validation ran\n\nIf the code is already clean for this rubric, say that directly instead of manufacturing edits.\n\n## Example\n\n**User request:**\n\n> Review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes.\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","# Review and Simplify Changes\n## When to Use\n\nUse this skill when you need review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes. Use when the user asks to \"simplify code\", \"review changed code\", \"check for code reuse\", \"review code quality\", \"review...\n\n\nReview changed code for reuse, quality, efficiency, and clarity issues. Use Codex sub-agents to review in parallel, but keep those sub-agents read-only: they should only inspect code and send findings back to the main agent. Only the main agent may apply high-confidence, behavior-preserving fixes.\n\n## Modes\n\nChoose the mode from the user's request:\n\n- `review-only`: user asks to review, audit, or check the changes\n- `safe-fixes`: user asks to simplify, clean up, or refactor the changes\n- `fix-and-validate`: same as `safe-fixes`, but also run the smallest relevant validation after edits\n\nIf the user does not specify, default to:\n\n- `review-only` for \"review\", \"audit\", or \"check\"\n- `safe-fixes` for \"simplify\", \"clean up\", or \"refactor\"\n\n## Step 1: Determine the Scope and Diff Command\n\nPrefer this scope order:\n\n1. Files or paths explicitly named by the user\n2. Current git changes\n3. Files edited earlier in the current Codex turn\n4. Most recently modified tracked files, only if the user asked for a review but there is no diff\n\nIf there is no clear scope, stop and say so briefly.\n\nWhen using git changes, determine the smallest correct diff command based on the repo state:\n\n- unstaged work: `git diff`\n- staged work: `git diff --cached`\n- branch or commit comparison explicitly requested by the user: use that exact diff target\n- mixed staged and unstaged work: review both\n\nDo not assume `git diff HEAD` is the right default when a smaller diff is available.\n\nBefore reviewing standards or applying fixes, read the repo's local instruction files and relevant project docs for the touched area. Prefer the closest applicable guidance, such as:\n\n- `AGENTS.md`\n- repo workflow docs\n- architecture or style docs for the touched module\n\nUse those instructions to distinguish real issues from intentional local patterns.\n\n## Step 2: Launch Four Read-Only Review Sub-Agents in Parallel\n\nUse Codex sub-agents when the scope is large enough for parallel review to help. For a tiny diff or one very small file, it is acceptable to review locally instead.\n\nWhen spawning sub-agents:\n\n- give each sub-agent the same scope\n- tell each sub-agent to inspect only its assigned review role\n- tell each sub-agent it is operating in a read-only review pass\n- do not let sub-agents edit files, run `apply_patch`, stage changes, commit, or perform other state-mutating actions\n- ask for concise, structured findings only\n- ask each sub-agent to report file, line or symbol, problem, recommended fix, and confidence\n- ask each sub-agent to return findings to the main agent only; they must not implement fixes themselves\n\nUse four review roles.\n\n### Sub-Agent 1: Code Reuse Review\n\nReview the changes for reuse opportunities:\n\n1. Search for existing helpers, utilities, or shared abstractions that already solve the same problem.\n2. Flag duplicated functions or near-duplicate logic introduced in the change.\n3. Flag inline logic that should call an existing helper instead of re-implementing it.\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `explorer` for broad codebase lookup, or `reviewer` if a stronger review pass is more useful than wide search.\n\n### Sub-Agent 2: Code Quality Review\n\nReview the same changes for code quality issues:\n\n1. Redundant state, cached values, or derived values stored unnecessarily\n2. Parameter sprawl caused by threading new arguments through existing call chains\n3. Copy-paste with slight variation that should become a shared abstraction\n4. Leaky abstractions or ownership violations across module boundaries\n5. Stringly-typed values where existing typed contracts, enums, or constants already exist\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `reviewer`\n\n### Sub-Agent 3: Efficiency Review\n\nReview the same changes for efficiency issues:\n\n1. Repeated work, duplicate reads, duplicate API calls, or unnecessary recomputation\n2. Sequential work that could safely run concurrently\n3. New work added to startup, render, request, or other hot paths without clear need\n4. Pre-checks for existence when the operation itself can be attempted directly and errors handled\n5. Memory growth, missing cleanup, or listener\u002Fsubscription leaks\n6. Overly broad reads or scans when the code only needs a subset\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `reviewer`\n\n### Sub-Agent 4: Clarity and Standards Review\n\nReview the same changes for clarity, local standards, and balance:\n\n1. Violations of local project conventions or module patterns\n2. Unnecessary complexity, deep nesting, weak names, or redundant comments\n3. Overly compact or clever code that reduces readability\n4. Over-simplification that collapses separate concerns into one unclear unit\n5. Dead code, dead abstractions, or indirection without value\n\nThis sub-agent is read-only. It must not edit files, apply patches, or make any other workspace changes.\n\nRecommended sub-agent role: `reviewer`\n\nOnly report issues that materially improve maintainability, correctness, or cost. Do not churn code just to make it look different.\n\n## Step 3: Aggregate Findings\n\nWait for all review sub-agents to complete, then merge their findings.\n\nThe main agent owns this step. Treat sub-agent output as review input only, not as permission to delegate code changes back out.\n\nNormalize findings into this shape:\n\n1. File and line or nearest symbol\n2. Category: reuse, quality, efficiency, or clarity\n3. Why it is a problem\n4. Recommended fix\n5. Confidence: high, medium, or low\n\nDiscard weak, duplicative, or instruction-conflicting findings before editing.\n\n## Step 4: Fix Issues Carefully\n\nIn `review-only` mode, stop after reporting findings.\n\nIn `safe-fixes` or `fix-and-validate` mode:\n\n- Only the main agent applies fixes for this skill\n- Apply only high-confidence, behavior-preserving fixes\n- Skip subjective refactors that need product or architectural judgment\n- Preserve local patterns when they are intentional or instruction-backed\n- Keep edits scoped to the reviewed files unless a small adjacent change is required to complete the fix correctly\n\nPrefer fixes like:\n\n- replacing duplicated code with an existing helper\n- removing redundant state or dead code\n- simplifying control flow without changing behavior\n- narrowing overly broad operations\n- renaming unclear locals when the scope is contained\n\nDo not stage, commit, or push changes as part of this skill.\n\n## Step 5: Validate When Required\n\nIn `fix-and-validate` mode, after the main agent finishes edits, run the smallest relevant validation for the touched scope.\n\nExamples:\n\n- targeted tests for the touched module\n- typecheck or compile for the touched target\n- formatter or lint check if that is the project's real safety gate\n\nPrefer fast, scoped validation over full-suite runs unless the change breadth justifies more.\n\nIf validation is skipped because the user asked not to run it, say so explicitly.\n\n## Step 6: Summarize Outcome\n\nClose with a brief result:\n\n- what was reviewed\n- what was fixed, if anything\n- what was intentionally left alone\n- whether validation ran\n\nIf the code is already clean for this rubric, say that directly instead of manufacturing edits.\n\n## Example\n\n**User request:**\n\n> Review a git diff or explicit file scope for reuse, code quality, efficiency, clarity, and standards issues, then optionally apply safe Codex-driven fixes.\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":29,"source":43,"license":14,"date_added":44,"description":7,"source_repo":45,"source_type":30,"license_source":46},"https:\u002F\u002Fgithub.com\u002FDimillian\u002FSkills\u002Ftree\u002Fmain\u002Freview-and-simplify-changes",1782864000000,"Dimillian\u002FSkills","https:\u002F\u002Fgithub.com\u002FDimillian\u002FSkills\u002Fblob\u002Fmain\u002FLICENSE","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Freview-and-simplify-changes","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 review-and-simplify-changes",{"tool":58,"command":59},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill review-and-simplify-changes",{"tool":61,"command":62},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill review-and-simplify-changes","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Freview-and-simplify-changes\u002FSKILL.md",true,[],[67,94,117,141,169,192],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":71,"categories":72,"keywords":78,"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",[73],{"categoryNo":74,"categoryName":75,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[79,80,81,82,83,84,69,85,86,87,88,89,30,22,90,29,28,91,92,93],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","devops-security","access","configure","only","active","scripts","relevant","implementing",{"skillNo":95,"name":96,"nameZh":6,"description":97,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":100,"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",[],[101,102,103,21,104,105,106,107,108,109,110,111,112,89,113,30,114,115,29,116],"delegate","zcode","zcode delegate","cli","orchestration","tasks","run","Bash","model","node","read","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":118,"name":119,"nameZh":6,"description":120,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":121,"categories":122,"keywords":123,"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",[],[124,125,126,127,128,129,130,34,131,132,133,134,135,30,22,136,137,138,139,140],"transcript","youtube transcript","youtube","safe","github","codex","research","https","text","fetch","tooling","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":142,"name":143,"nameZh":6,"description":144,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":145,"categories":146,"keywords":158,"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",[147,150,153],{"categoryNo":148,"categoryName":149,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":151,"categoryName":152,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":154,"categoryName":155,"taxonomyType":156,"taxonomyTypeDesc":157},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[124,125,126,159,127,160,128,129,34,161,162,163,164,133,165,30,22,166,167,168],"youtube transcript skills","gemini","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":170,"name":171,"nameZh":6,"description":172,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":173,"categories":174,"keywords":179,"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",[175,178],{"categoryNo":176,"categoryName":177,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":151,"categoryName":152,"taxonomyType":76,"taxonomyTypeDesc":77},[126,180,181,104,127,182,183,184,36,34,163,185,186,187,188,22,189,136,190,191],"youtube notetaker","notetaker","workflow","official","notes","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":193,"name":194,"nameZh":6,"description":195,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":196,"categories":197,"keywords":199,"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",[198],{"categoryNo":148,"categoryName":149,"taxonomyType":76,"taxonomyTypeDesc":77},[200,126,201,202,127,160,161,203,204,162,163,164,133,205,165,30,22,166,206,139],"youtube full","full","google","server","dlp","credits","automatic"]