[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6PBZVZP38WR9GSWK9K5B4Z4":3,"skill-same:01M6PBZVZP38WR9GSWK9K5B4Z4":92},{"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":25,"publishedAt":46,"linkOnly":47,"markdownContent":48,"markdownBody":49,"frontMatter":50,"refName":62,"commitSha":63,"skillDirectory":64,"forksCount":13,"repositoryHtmlUrl":65,"repositoryHomepageUrl":6,"ownerHtmlUrl":66,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":67,"install":68,"resources":81},"01M6PBZVZP38WR9GSWK9K5B4Z4","pre-release-review",null,"Run a read-only pre-release review for deploy readiness, migrations, config, secrets, rollout order, rollback risk, and launch blockers.","duc-duy-1612\u002FOnline-Delivery-Systems-Web","duc-duy-1612","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F192231384?v=4","01M6NSDKQQDKVTHZ8DZMZ1VYY6","01M6NSDKW8DDVTQHBT1HBDDJPT",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fpre-release-review\u002FSKILL.md",[17,22],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",[26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45],"pre release review","release","release review","review","read","for","deploy-readiness","read-only","community","master","only","rollout","secrets","risk","ci-cd","ci","git","run","config","safe","2026-11-10 10:12:30",false,"---\nname: pre-release-review\ndescription: \"Run a read-only pre-release review for deploy readiness, migrations, config, secrets, rollout order, rollback risk, and launch blockers.\"\ncategory: operations\nrisk: safe\nsource: community\nsource_repo: chaunsin\u002Fagent-skills\nsource_type: community\ndate_added: \"2026-06-29\"\nauthor: chaunsin\ntags: [release, deploy-readiness, ci-cd, rollback, production]\ntools: [git, gh, rg]\nlicense: \"Apache-2.0\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002Fchaunsin\u002Fagent-skills\u002Fblob\u002Fmaster\u002FLICENSE\"\n---\n# Pre-release Review\n\nUse this skill to run a read-only production release readiness review. The goal is to reduce\nrelease time and coordination failures by finding missing deploy materials, unsafe ordering,\nconfiguration gaps, data migration gaps, and ambiguous production risks before CI\u002FCD or manual\nrelease steps begin.\n\n## When to Use This Skill\n\n- Use when the user asks for a release audit, pre-release review, go-live review, or deploy readiness check.\n- Use before publishing a tag, deploying production services, or merging a release branch.\n- Use when a PR or git range may include migrations, environment changes, queues, cache behavior, object storage assets, or service contract changes.\n- Use when the user asks whether a change is safe to ship and needs a read-only risk report.\n\n## Non-negotiable rules\n\n- Do not modify source code, configs, migrations, secrets, deployment files, or generated files.\n- Do not execute migrations, clear or warm caches, upload assets, trigger CI\u002FCD, deploy services,\n  publish tags, rotate secrets, or change remote infrastructure.\n- Produce a concise report that lists only confirmed problems and plausible risks needing\n  confirmation. Do not bury the reader in clean checklist items.\n- Sort findings from highest to lowest priority.\n- Include module, finding, evidence, inferred owner, risk, and recommended action for each item.\n- Never reveal private keys, account passwords, tokens, certificates, cookies, or full secret\n  values. Report only file path, line number, variable name, secret type, and a redacted hint.\n- If evidence is incomplete but the risk could block production, list it as a confirmation item.\n\n## Required references\n\n- Read `references\u002Fchecklist.md` before analyzing findings so important release domains are not\n  skipped.\n- Read `references\u002Freport-template.md` before writing the final report so priorities, owner\n  inference, secret redaction, and output shape stay consistent.\n\n## Project guidance discovery\n\nBefore interpreting the release diff, look for project-local guidance files such as `AGENTS.md` and\n`CLAUDE.md` in the repository root and relevant service directories. Read them when present so the\nreview respects the user's project-specific conventions, service boundaries, release rules,\nvalidation expectations, ownership hints, and known operational constraints.\n\n- Treat project guidance as context for how to interpret risks, not as permission to perform\n  mutating release actions.\n- If project guidance conflicts with this skill's non-negotiable safety rules, the read-only,\n  no-secret-disclosure rules in this skill win.\n- If a relevant guidance file cannot be read, note the limitation in \"Unable To Verify\" only when it\n  affects the release review.\n\n## Scope selection\n\nDetermine the review range before judging risk. State the chosen range in the report.\n\n1. If the user provides a pull request URL or PR number, review that PR diff first.\n   - If `gh` is available and authenticated, use read-only commands such as `gh pr view` and\n     `gh pr diff`.\n   - If the PR cannot be fetched due to missing tooling, auth, or network limits, say so and ask\n     for a local branch, patch, or explicit git range. Do not invent the PR contents.\n2. If the user provides an explicit `base..head` range, use it directly.\n3. If the user provides only a head commit, compare the previous usable release tag reachable from\n   that commit to the head commit.\n4. If the user provides no scope, compare the previous usable release tag to `HEAD`.\n5. Choose the previous usable release tag carefully:\n   - Prefer the repository's visible release-tag convention when one is obvious, such as semantic\n     versions, `v*`, or `release-*`. If tag naming is mixed, state the assumption.\n   - If `HEAD` is exactly at one or more tags, treat those as the current release point and compare\n     against the earlier reachable release tag, not `HEAD`'s own tag.\n   - If no usable previous release tag exists, review the latest 5 commits and explicitly warn that\n     this is a fallback: there is no usable previous release tag, so the audit only covers the\n     latest 5 commits; recommend a PR or tag-based range for future reviews.\n\n## Read-only evidence collection\n\nRun only safe inspection commands, adjusted to the repository and current permissions. Useful\ncommands include:\n\n```bash\ngit status --short\ngit rev-parse --show-toplevel\ngit rev-parse --abbrev-ref HEAD\ngit rev-parse HEAD\nrg --files -g 'AGENTS.md' -g 'CLAUDE.md'\ngit tag --merged HEAD --sort=-creatordate\ngit tag --points-at HEAD\ngit for-each-ref --sort=-creatordate --format=\"%(refname:short) %(objectname:short)\" refs\u002Ftags\ngit describe --tags --abbrev=0 HEAD\ngit diff --name-status \u003Cbase>..\u003Chead>\ngit diff --stat \u003Cbase>..\u003Chead>\ngit log --oneline --decorate --no-merges \u003Cbase>..\u003Chead>\ngit diff -U3 \u003Cbase>..\u003Chead> -- \u003Cpath>\ngit blame -L \u003Cstart>,\u003Cend> -- \u003Cpath>\ngit log --format=\"%h %an %s\" -- \u003Cpath>\nrg -n \"\u003Cpattern>\" .\n```\n\nFor PRs, use `gh pr view` and `gh pr diff` only when they are available and allowed. Do not bypass\nnetwork, auth, sandbox, or approval restrictions. If a command cannot run, record the limitation in\nthe report's \"Unable to verify\" section.\n\n## Review workflow\n\n1. Confirm the git repository root, current branch, dirty state, and selected comparison range.\n2. Collect changed file names, file status, diff stats, commit summaries, and touched services.\n3. Inspect relevant diffs rather than relying on filenames alone.\n4. Use the checklist to map changed code to production requirements:\n   - schema changes to migrations, indexes, seeds, and backfills\n   - config reads to env examples, deploy secrets, flags, and runtime config\n   - cache key or TTL changes to invalidation, prewarm, and compatibility work\n   - queue producers\u002Fconsumers to topic setup, DLQ, idempotency, and deploy order\n   - asset references to object storage, CDN, templates, certificates, and permissions\n   - service contract changes to deploy sequence, backward compatibility, and rollback risk\n5. Infer owners with `git blame` on changed lines when possible; otherwise use recent `git log`\n   authors for the file or commit. Label them as inferred owners, and do not include email\n   addresses.\n6. Classify each finding as P0, P1, or P2 using `references\u002Freport-template.md`.\n7. Write the final report in the user's language when practical. Keep conclusion values exactly as\n   `BLOCKED`, `NEEDS_CONFIRMATION`, or `NO_BLOCKER_FOUND`.\n\n## Dirty worktree handling\n\nBy default, review only the selected committed range. Do not silently mix uncommitted or untracked\nchanges into the release diff unless the user explicitly asks to include worktree changes.\n\n- Always report whether the worktree is dirty.\n- If dirty or untracked files touch release-relevant areas such as migrations, deployment config,\n  env examples, CI\u002FCD, secrets, cache, queues, assets, or service contracts, add a P2 confirmation\n  item saying those changes are excluded from the committed-range review and must be committed,\n  discarded, or reviewed separately before release.\n- If the user explicitly asks to include dirty worktree changes, inspect them with read-only\n  commands such as `git diff` and `git diff --name-status`, and clearly label them as uncommitted\n  evidence.\n\n## Evidence expectations\n\nEvery finding should cite concrete evidence:\n\n- file path and line number when available\n- commit hash or PR reference when line evidence is not enough\n- command limitation when evidence could not be collected\n- diff relationship, such as \"schema changed but no migration file changed\"\n\nDo not state that something is safe just because no file matched a pattern. Use \"not verified\" for\nareas that cannot be confirmed from local repository evidence.\n\n## Findings versus verification limits\n\nSeparate release confirmation items from neutral tool limits:\n\n- A release confirmation item is a diff-linked production risk, such as a new env var whose\n  production secret cannot be verified, a schema change with unclear migration status, or a new queue\n  whose infrastructure cannot be confirmed. Classify it as P1 or P2 and set the conclusion to\n  `NEEDS_CONFIRMATION` unless a P0 also exists.\n- An \"Unable To Verify\" entry is a neutral limitation, such as missing remote access or deployment\n  platform credentials when the diff does not introduce a specific release requirement. Neutral\n  limitations do not change the conclusion by themselves.\n- If a limitation blocks confirmation of a release-critical diff change, promote it to a P1\u002FP2\n  finding rather than leaving it only in \"Unable To Verify\".\n- Use `NO_BLOCKER_FOUND` only when no P0-P2 findings or release confirmation items were found from\n  available evidence. The report may still include neutral verification limits.\n\n## Output rules\n\n- Show P0 and P1 findings first, then P2 confirmation items.\n- Do not list clean checklist categories.\n- Include a service deployment order section only when the diff touches multiple services,\n  asynchronous workers, migrations, queues, cache, or public contracts.\n- If no P0 blocker is found but P1\u002FP2 confirmation items remain, use `NEEDS_CONFIRMATION`.\n- If no P0-P2 findings exist, include the reviewed range and any neutral verification limits.\n- Keep the report short enough for a release manager to act on immediately.\n\n## Limitations\n\n- This skill is read-only and does not deploy, tag, publish, run migrations, rotate secrets, or change infrastructure.\n- It can identify release risks from available evidence, but it cannot prove production state without access to the relevant deployment, secrets, database, queue, cache, or observability systems.\n- It should not replace service-owner signoff for high-risk production changes.\n\n## Test prompts\n\nUse these prompts to validate the skill behavior:\n\n- \"Run a pre-release review and tell me if this production deploy has risks.\"\n- \"Review PR #123 before release. Check migrations, configs, and cache work.\"\n- \"This repo has no tags. Use the default strategy and audit release readiness.\"\n- \"Check `v1.2.3..HEAD` for backend go-live blockers.\"\n","# Pre-release Review\n\nUse this skill to run a read-only production release readiness review. The goal is to reduce\nrelease time and coordination failures by finding missing deploy materials, unsafe ordering,\nconfiguration gaps, data migration gaps, and ambiguous production risks before CI\u002FCD or manual\nrelease steps begin.\n\n## When to Use This Skill\n\n- Use when the user asks for a release audit, pre-release review, go-live review, or deploy readiness check.\n- Use before publishing a tag, deploying production services, or merging a release branch.\n- Use when a PR or git range may include migrations, environment changes, queues, cache behavior, object storage assets, or service contract changes.\n- Use when the user asks whether a change is safe to ship and needs a read-only risk report.\n\n## Non-negotiable rules\n\n- Do not modify source code, configs, migrations, secrets, deployment files, or generated files.\n- Do not execute migrations, clear or warm caches, upload assets, trigger CI\u002FCD, deploy services,\n  publish tags, rotate secrets, or change remote infrastructure.\n- Produce a concise report that lists only confirmed problems and plausible risks needing\n  confirmation. Do not bury the reader in clean checklist items.\n- Sort findings from highest to lowest priority.\n- Include module, finding, evidence, inferred owner, risk, and recommended action for each item.\n- Never reveal private keys, account passwords, tokens, certificates, cookies, or full secret\n  values. Report only file path, line number, variable name, secret type, and a redacted hint.\n- If evidence is incomplete but the risk could block production, list it as a confirmation item.\n\n## Required references\n\n- Read `references\u002Fchecklist.md` before analyzing findings so important release domains are not\n  skipped.\n- Read `references\u002Freport-template.md` before writing the final report so priorities, owner\n  inference, secret redaction, and output shape stay consistent.\n\n## Project guidance discovery\n\nBefore interpreting the release diff, look for project-local guidance files such as `AGENTS.md` and\n`CLAUDE.md` in the repository root and relevant service directories. Read them when present so the\nreview respects the user's project-specific conventions, service boundaries, release rules,\nvalidation expectations, ownership hints, and known operational constraints.\n\n- Treat project guidance as context for how to interpret risks, not as permission to perform\n  mutating release actions.\n- If project guidance conflicts with this skill's non-negotiable safety rules, the read-only,\n  no-secret-disclosure rules in this skill win.\n- If a relevant guidance file cannot be read, note the limitation in \"Unable To Verify\" only when it\n  affects the release review.\n\n## Scope selection\n\nDetermine the review range before judging risk. State the chosen range in the report.\n\n1. If the user provides a pull request URL or PR number, review that PR diff first.\n   - If `gh` is available and authenticated, use read-only commands such as `gh pr view` and\n     `gh pr diff`.\n   - If the PR cannot be fetched due to missing tooling, auth, or network limits, say so and ask\n     for a local branch, patch, or explicit git range. Do not invent the PR contents.\n2. If the user provides an explicit `base..head` range, use it directly.\n3. If the user provides only a head commit, compare the previous usable release tag reachable from\n   that commit to the head commit.\n4. If the user provides no scope, compare the previous usable release tag to `HEAD`.\n5. Choose the previous usable release tag carefully:\n   - Prefer the repository's visible release-tag convention when one is obvious, such as semantic\n     versions, `v*`, or `release-*`. If tag naming is mixed, state the assumption.\n   - If `HEAD` is exactly at one or more tags, treat those as the current release point and compare\n     against the earlier reachable release tag, not `HEAD`'s own tag.\n   - If no usable previous release tag exists, review the latest 5 commits and explicitly warn that\n     this is a fallback: there is no usable previous release tag, so the audit only covers the\n     latest 5 commits; recommend a PR or tag-based range for future reviews.\n\n## Read-only evidence collection\n\nRun only safe inspection commands, adjusted to the repository and current permissions. Useful\ncommands include:\n\n```bash\ngit status --short\ngit rev-parse --show-toplevel\ngit rev-parse --abbrev-ref HEAD\ngit rev-parse HEAD\nrg --files -g 'AGENTS.md' -g 'CLAUDE.md'\ngit tag --merged HEAD --sort=-creatordate\ngit tag --points-at HEAD\ngit for-each-ref --sort=-creatordate --format=\"%(refname:short) %(objectname:short)\" refs\u002Ftags\ngit describe --tags --abbrev=0 HEAD\ngit diff --name-status \u003Cbase>..\u003Chead>\ngit diff --stat \u003Cbase>..\u003Chead>\ngit log --oneline --decorate --no-merges \u003Cbase>..\u003Chead>\ngit diff -U3 \u003Cbase>..\u003Chead> -- \u003Cpath>\ngit blame -L \u003Cstart>,\u003Cend> -- \u003Cpath>\ngit log --format=\"%h %an %s\" -- \u003Cpath>\nrg -n \"\u003Cpattern>\" .\n```\n\nFor PRs, use `gh pr view` and `gh pr diff` only when they are available and allowed. Do not bypass\nnetwork, auth, sandbox, or approval restrictions. If a command cannot run, record the limitation in\nthe report's \"Unable to verify\" section.\n\n## Review workflow\n\n1. Confirm the git repository root, current branch, dirty state, and selected comparison range.\n2. Collect changed file names, file status, diff stats, commit summaries, and touched services.\n3. Inspect relevant diffs rather than relying on filenames alone.\n4. Use the checklist to map changed code to production requirements:\n   - schema changes to migrations, indexes, seeds, and backfills\n   - config reads to env examples, deploy secrets, flags, and runtime config\n   - cache key or TTL changes to invalidation, prewarm, and compatibility work\n   - queue producers\u002Fconsumers to topic setup, DLQ, idempotency, and deploy order\n   - asset references to object storage, CDN, templates, certificates, and permissions\n   - service contract changes to deploy sequence, backward compatibility, and rollback risk\n5. Infer owners with `git blame` on changed lines when possible; otherwise use recent `git log`\n   authors for the file or commit. Label them as inferred owners, and do not include email\n   addresses.\n6. Classify each finding as P0, P1, or P2 using `references\u002Freport-template.md`.\n7. Write the final report in the user's language when practical. Keep conclusion values exactly as\n   `BLOCKED`, `NEEDS_CONFIRMATION`, or `NO_BLOCKER_FOUND`.\n\n## Dirty worktree handling\n\nBy default, review only the selected committed range. Do not silently mix uncommitted or untracked\nchanges into the release diff unless the user explicitly asks to include worktree changes.\n\n- Always report whether the worktree is dirty.\n- If dirty or untracked files touch release-relevant areas such as migrations, deployment config,\n  env examples, CI\u002FCD, secrets, cache, queues, assets, or service contracts, add a P2 confirmation\n  item saying those changes are excluded from the committed-range review and must be committed,\n  discarded, or reviewed separately before release.\n- If the user explicitly asks to include dirty worktree changes, inspect them with read-only\n  commands such as `git diff` and `git diff --name-status`, and clearly label them as uncommitted\n  evidence.\n\n## Evidence expectations\n\nEvery finding should cite concrete evidence:\n\n- file path and line number when available\n- commit hash or PR reference when line evidence is not enough\n- command limitation when evidence could not be collected\n- diff relationship, such as \"schema changed but no migration file changed\"\n\nDo not state that something is safe just because no file matched a pattern. Use \"not verified\" for\nareas that cannot be confirmed from local repository evidence.\n\n## Findings versus verification limits\n\nSeparate release confirmation items from neutral tool limits:\n\n- A release confirmation item is a diff-linked production risk, such as a new env var whose\n  production secret cannot be verified, a schema change with unclear migration status, or a new queue\n  whose infrastructure cannot be confirmed. Classify it as P1 or P2 and set the conclusion to\n  `NEEDS_CONFIRMATION` unless a P0 also exists.\n- An \"Unable To Verify\" entry is a neutral limitation, such as missing remote access or deployment\n  platform credentials when the diff does not introduce a specific release requirement. Neutral\n  limitations do not change the conclusion by themselves.\n- If a limitation blocks confirmation of a release-critical diff change, promote it to a P1\u002FP2\n  finding rather than leaving it only in \"Unable To Verify\".\n- Use `NO_BLOCKER_FOUND` only when no P0-P2 findings or release confirmation items were found from\n  available evidence. The report may still include neutral verification limits.\n\n## Output rules\n\n- Show P0 and P1 findings first, then P2 confirmation items.\n- Do not list clean checklist categories.\n- Include a service deployment order section only when the diff touches multiple services,\n  asynchronous workers, migrations, queues, cache, or public contracts.\n- If no P0 blocker is found but P1\u002FP2 confirmation items remain, use `NEEDS_CONFIRMATION`.\n- If no P0-P2 findings exist, include the reviewed range and any neutral verification limits.\n- Keep the report short enough for a release manager to act on immediately.\n\n## Limitations\n\n- This skill is read-only and does not deploy, tag, publish, run migrations, rotate secrets, or change infrastructure.\n- It can identify release risks from available evidence, but it cannot prove production state without access to the relevant deployment, secrets, database, queue, cache, or observability systems.\n- It should not replace service-owner signoff for high-risk production changes.\n\n## Test prompts\n\nUse these prompts to validate the skill behavior:\n\n- \"Run a pre-release review and tell me if this production deploy has risks.\"\n- \"Review PR #123 before release. Check migrations, configs, and cache work.\"\n- \"This repo has no tags. Use the default strategy and audit release readiness.\"\n- \"Check `v1.2.3..HEAD` for backend go-live blockers.\"\n",{"name":5,"risk":45,"tags":51,"tools":54,"author":57,"source":34,"license":14,"category":58,"date_added":59,"description":7,"source_repo":60,"source_type":34,"license_source":61},[27,32,40,52,53],"rollback","production",[42,55,56],"gh","rg","chaunsin","operations","2026-06-29","chaunsin\u002Fagent-skills","https:\u002F\u002Fgithub.com\u002Fchaunsin\u002Fagent-skills\u002Fblob\u002Fmaster\u002FLICENSE","main","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Fpre-release-review","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":69,"prompt":79,"zipAvailable":80},[70,73,76],{"tool":71,"command":72},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill pre-release-review",{"tool":74,"command":75},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill pre-release-review",{"tool":77,"command":78},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill pre-release-review","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fpre-release-review\u002FSKILL.md",true,[82,88],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"references\u002Fchecklist.md","REFERENCE","参考文档",5568,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fpre-release-review\u002Freferences\u002Fchecklist.md",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Freport-template.md",4324,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fpre-release-review\u002Freferences\u002Freport-template.md",[93,118,139,163,191,215],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":98,"categories":99,"keywords":101,"publishedAt":46},"01M6Q0FA5FZ410Z33Z3TFQ4DBA","zero-trust","Implement zero-trust network architecture. Configure identity-based access, micro-segmentation, and continuous verification. Use when implementing modern security architectures.","MIT","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzero-trust\u002FSKILL.md",[100],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[102,103,104,105,106,107,95,108,109,110,111,36,34,62,112,113,114,115,116,117],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","devops-security","access","configure","active","critical","scope","scripts","relevant","implementing",{"skillNo":119,"name":120,"nameZh":6,"description":121,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"publishedAt":46},"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",[],[125,126,127,29,128,129,130,43,131,132,133,30,134,36,135,34,136,137,113,138],"delegate","zcode","zcode delegate","cli","orchestration","tasks","Bash","model","node","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":140,"name":141,"nameZh":6,"description":142,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":143,"categories":144,"keywords":145,"publishedAt":46},"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",[],[146,147,148,45,149,150,151,152,153,154,155,156,157,34,62,158,159,160,161,162],"transcript","youtube transcript","youtube","github","codex","research","license","https","text","fetch","tooling","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":180,"publishedAt":46},"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",[169,172,175],{"categoryNo":170,"categoryName":171,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":173,"categoryName":174,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":176,"categoryName":177,"taxonomyType":178,"taxonomyTypeDesc":179},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[146,147,148,181,45,182,149,150,152,183,184,185,186,155,187,34,62,188,189,190],"youtube transcript skills","gemini","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":192,"name":193,"nameZh":6,"description":194,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":195,"categories":196,"keywords":201,"publishedAt":46},"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",[197,200],{"categoryNo":198,"categoryName":199,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":173,"categoryName":174,"taxonomyType":20,"taxonomyTypeDesc":21},[148,202,203,128,45,204,205,206,207,152,185,208,209,210,211,62,212,158,213,214],"youtube notetaker","notetaker","workflow","official","notes","code","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":216,"name":217,"nameZh":6,"description":218,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":222,"publishedAt":46},"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",[221],{"categoryNo":170,"categoryName":171,"taxonomyType":20,"taxonomyTypeDesc":21},[223,148,224,225,45,182,183,226,227,184,185,186,155,228,187,34,62,188,229,161],"youtube full","full","google","server","dlp","credits","automatic"]