[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6Q09P483NM4FB0XT2AT92HY":3,"skill-same:01M6Q09P483NM4FB0XT2AT92HY":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":30,"commitSha":47,"skillDirectory":48,"forksCount":13,"repositoryHtmlUrl":49,"repositoryHomepageUrl":6,"ownerHtmlUrl":50,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":51,"install":52,"resources":65},"01M6Q09P483NM4FB0XT2AT92HY","wjttc-tester",null,"F1-inspired test EXECUTOR + reporter. Runs a test plan, finds and reproduces bugs, audits suite signal integrity, then files a WJTTC report (Brake\u002FEngine\u002FAero\u002FTyre\u002FPit) with a tier verdict.","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\u002Fwjttc-tester\u002FSKILL.md",[],[18,19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37],"wjttc tester","tester","faf","blob","signal","bugs","tree","with","verdict","executor","critical","github","main","community","files","engine","plan","test plan","license","test","2026-11-10 10:12:30",false,"---\nname: wjttc-tester\ndescription: \"F1-inspired test EXECUTOR + reporter. Runs a test plan, finds and reproduces bugs, audits suite signal integrity, then files a WJTTC report (Brake\u002FEngine\u002FAero\u002FTyre\u002FPit) with a tier verdict.\"\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002FWolfe-Jam\u002Ffaf-skills\u002Ftree\u002Fmain\u002Fskills\u002Fwjttc-tester\nsource_repo: Wolfe-Jam\u002Ffaf-skills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002FWolfe-Jam\u002Ffaf-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# WJTTC Championship Tester\n\n**\"We break things so others never have to know they were broken.\"**\n\nApply F1-inspired standards to software testing. When brakes must work flawlessly at race pace, so must the code in production. This skill **executes** test plans and **files reports** — it is the driver, not the engineer. To plan and generate the suite, use **wjttc-builder**.\n\n## When to use this skill\n\n- Running an existing or just-written test plan and reporting outcomes\n- Reproducing and root-causing a reported bug\n- Edge-case \u002F error-handling \u002F regression validation\n- Auditing whether the suite's CI signal can still be trusted\n- Producing a WJTTC report with a tier verdict\n\n## The WJTTC five tiers\n\nTriage every test by blast radius. The first three set severity; Tyre and Pit cover durability and the release gate.\n\n| Tier | Symbol | Meaning | Examples |\n|------|--------|---------|----------|\n| **Brake** | ? | Life-critical — failure is catastrophic | data loss, auth bypass, payment errors, destructive ops without confirm |\n| **Engine** | ⚡ | Performance-critical — wrong results \u002F poor UX | API accuracy, data transforms, calculations, format compliance, perf |\n| **Aero** | ? | Polish & edge cases — minor inconvenience | UI quirks, rare message formatting, optional-feature edges, docs |\n| **Tyre** | ? | Durability under load — degradation over time | stress\u002Fvolume, concurrency, memory growth, large inputs |\n| **Pit** | ? | Release gate — the stop that lets you go | smoke\u002Fregression suite, CI green, the WJTTC report filed |\n\nTest Brake first. If the brakes don't work, nothing else matters.\n\n## Step 0 — Signal Integrity pre-audit (run BEFORE adding\u002Frunning anything new)\n\n**Red CI is a contract: it must always mean \"stop, look, fix.\"** A suite with high coverage but flaky reds is *less* trustworthy than a smaller suite with zero false alarms — because the team has stopped reading the reds. Fix the signal before you add more tests.\n\n**Method** — classify the last 30 days of CI failures:\n\n| Bucket | Definition | Verdict |\n|--------|-----------|---------|\n| **Real bug** | Red mapped to a real defect; fixed by a code change | ✓ Signal worked |\n| **Flake** | Timing\u002Fnetwork\u002Fconcurrency noise; passed on rerun, no code change | ✗ Test design defect |\n| **Infra** | Missing secret, runner image change, upstream dep — not the code | ✗ Workflow design defect |\n\n**Signal Integrity Score:** `SI = Real bugs \u002F (Real bugs + Flakes + Infra) × 100`\n\n| SI % | Verdict | Action |\n|------|---------|--------|\n| 100% | ✪ | Maintain — exemplary signal |\n| 95–99% | ★ Championship | Annotate any flake immediately |\n| 85–94% | ◇ Acceptable | Schedule the flake-class fix this sprint |\n| 70–84% | ● Eroding | Stop adding tests — fix flakes first |\n| \u003C70% | ○ Dead signal | Block merges until signal restored |\n\n**Eliminate on sight:** hard absolute-time perf asserts on shared runners (`expect(t).toBeLessThan(30)`) → move to a non-gating workflow; network calls in the main suite → mock at the boundary; concurrency tests without explicit ordering; secret-dependent steps that hard-fail when missing → grey-skip.\n\n**The inverse rule:** green CI that passes while something is broken is equally a violation. If a real bug shipped despite green, write the regression test BEFORE the fix lands.\n\n**The conversation is the real gate.** CI is supporting infrastructure for the human + AI audit; flaky CI wastes the audit's bandwidth. Signal Integrity keeps CI worthy of the conversation.\n\n## Execution loop\n\n1. **Scope** — what should it do? happy path, edges, failure modes, perf targets, tier of each.\n2. **Audit signal** (Step 0) before trusting or extending the suite.\n3. **Run** each test: set up, prepare data, execute, observe actual vs expected, record pass\u002Ffail\u002Fblocked, capture evidence on failure.\n4. **Reproduce** every failure deterministically; root-cause it; note the fix.\n5. **Tier coverage check** — confirm every test is tiered:\n   ```bash\n   faf wjttc --path tests          # audit tier coverage (vendor-neutral)\n   faf wjttc --strict --json       # CI gate: non-zero if any test is untiered\n   ```\n6. **Report** — file the WJTTC report (below), then surface the tier verdict.\n\n## WJTTC report format\n\nSave reports to **`.\u002Fwjttc-reports\u002F`** in the project under test (or a path the user specifies). Never write to an absolute\u002Fpersonal path. Name files `YYYY-MM-DD-{project}-{feature}-tests.yaml`.\n\n```yaml\n---\n# WJTTC Test Report\nproject: \"project-name\"\nfeature: \"feature-being-tested\"\ndate: \"2026-06-26\"\ntier: \"Engine\"            # Brake | Engine | Aero | Tyre | Pit\nresult: \"PASS\"            # PASS | FAIL | BLOCKED\nenvironment: \"OS, runtime version, key deps\"\n---\n\n## Summary\nobjective: What was tested\ntotals: { total: 25, passed: 23, failed: 2, blocked: 0, pass_rate: \"92%\" }\n\n## Failures\n- name: \"Long-string handling\"\n  tier: \"Engine ⚡\"\n  status: \"FAIL\"\n  steps: [\"...\", \"...\"]\n  expected: \"Handle gracefully\"\n  actual: \"Crash\"\n  error: \"RangeError: ...\"\n  root_cause: \"Unbounded buffer\"\n  fix: \"Cap input length \u002F stream\"\n\n## Edge cases\n- { case: \"Empty string\", input: \"''\", expected: \"error\", actual: \"error\", status: \"PASS\" }\n- { case: \"Unicode\", input: \"?️\", expected: \"stored\", actual: \"stored\", status: \"PASS\" }\n\n## Performance\n- { op: \"file read\",  target: \"\u003C50ms\", actual: \"18ms\", status: \"PASS\" }\n- { op: \"parse YAML\", target: \"\u003C50ms\", actual: \"12ms\", status: \"PASS\" }\n\n## Bugs found\n- id: 1\n  title: \"...\"\n  severity: \"Brake\"      # tier doubles as severity\n  reproducibility: \"Always\"\n  impact: \"Who is affected, how serious\"\n  fix: \"...\"\n\n## Coverage\ntested:     [\"happy path\", \"edges\", \"error handling\", \"perf\"]\nnot_tested: [\"concurrent access\", \"files >100MB\"]\n\n## Verdict\ntier: \"◆ Silver\"          # from the tier table below\nto_next: [\"Fix 2 failing Engine tests\", \"Add Tyre concurrency tests\"]\n```\n\n## Tier verdict\n\nMap the pass rate (or SI score) to the single canonical FAF tier ladder. No second ladder, no medals.\n\n| Score | Tier | Symbol |\n|-------|------|--------|\n| 100% | Trophy | ✪ |\n| 99% | Gold | ★ |\n| 95% | Silver | ◆ |\n| 85% | Bronze | ◇ |\n| 70% | Green | ● |\n| 55% | Yellow | ● |\n| 1% | Red | ○ |\n| 0% | White | ♡ |\n\nThe FAF score is **deterministic** — same input, same score. A test report should be just as falsifiable: every verdict traces to a reproducible run. **FAF doesn't lie.**\n\n## WJTTC method notes\n\n- **Test with real data**, not just sanitized inputs — anonymized production data, messy inputs, production-like volume.\n- **Document every failure** so it can be reproduced: what failed, how to repro, why it matters, how to fix.\n- **Tier before you test** — severity is the tier, so triage first; `faf wjttc` enforces that nothing ships untiered.\n- **Wire it into CI** with TAF receipts so the report is part of the record, not a one-off:\n  ```bash\n  faf taf setup --write     # create .github\u002Fworkflows\u002Ftaf.yml (test receipts)\n  faf score --json          # deterministic score snapshot for the receipt\n  ```\n\n## Quick checklist (before release)\n\n- [ ] Signal Integrity audited (SI ≥ 85%)\n- [ ] Brake tests pass — zero tolerance\n- [ ] Edges + error handling tested\n- [ ] Tyre: behaves under load \u002F concurrency\n- [ ] `faf wjttc --strict` green — every test tiered\n- [ ] Regression (Pit) suite passes\n- [ ] WJTTC report filed in `.\u002Fwjttc-reports\u002F`\n- [ ] Pass rate ≥ 85% (◇ Bronze, production-ready)\n\n## Resources\n\n- Website: https:\u002F\u002Ffaf.one · Skills Site: https:\u002F\u002Fskills.faf.one\n- faf-cli: https:\u002F\u002Fgithub.com\u002FWolfe-Jam\u002Ffaf-cli\n- Sibling skill: **wjttc-builder** (plan + generate the suite)\n\n---\n\n*Made with ? by wolfejam.dev — \"We break things so others never have to know they were broken.\"*\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","# WJTTC Championship Tester\n\n**\"We break things so others never have to know they were broken.\"**\n\nApply F1-inspired standards to software testing. When brakes must work flawlessly at race pace, so must the code in production. This skill **executes** test plans and **files reports** — it is the driver, not the engineer. To plan and generate the suite, use **wjttc-builder**.\n\n## When to use this skill\n\n- Running an existing or just-written test plan and reporting outcomes\n- Reproducing and root-causing a reported bug\n- Edge-case \u002F error-handling \u002F regression validation\n- Auditing whether the suite's CI signal can still be trusted\n- Producing a WJTTC report with a tier verdict\n\n## The WJTTC five tiers\n\nTriage every test by blast radius. The first three set severity; Tyre and Pit cover durability and the release gate.\n\n| Tier | Symbol | Meaning | Examples |\n|------|--------|---------|----------|\n| **Brake** | ? | Life-critical — failure is catastrophic | data loss, auth bypass, payment errors, destructive ops without confirm |\n| **Engine** | ⚡ | Performance-critical — wrong results \u002F poor UX | API accuracy, data transforms, calculations, format compliance, perf |\n| **Aero** | ? | Polish & edge cases — minor inconvenience | UI quirks, rare message formatting, optional-feature edges, docs |\n| **Tyre** | ? | Durability under load — degradation over time | stress\u002Fvolume, concurrency, memory growth, large inputs |\n| **Pit** | ? | Release gate — the stop that lets you go | smoke\u002Fregression suite, CI green, the WJTTC report filed |\n\nTest Brake first. If the brakes don't work, nothing else matters.\n\n## Step 0 — Signal Integrity pre-audit (run BEFORE adding\u002Frunning anything new)\n\n**Red CI is a contract: it must always mean \"stop, look, fix.\"** A suite with high coverage but flaky reds is *less* trustworthy than a smaller suite with zero false alarms — because the team has stopped reading the reds. Fix the signal before you add more tests.\n\n**Method** — classify the last 30 days of CI failures:\n\n| Bucket | Definition | Verdict |\n|--------|-----------|---------|\n| **Real bug** | Red mapped to a real defect; fixed by a code change | ✓ Signal worked |\n| **Flake** | Timing\u002Fnetwork\u002Fconcurrency noise; passed on rerun, no code change | ✗ Test design defect |\n| **Infra** | Missing secret, runner image change, upstream dep — not the code | ✗ Workflow design defect |\n\n**Signal Integrity Score:** `SI = Real bugs \u002F (Real bugs + Flakes + Infra) × 100`\n\n| SI % | Verdict | Action |\n|------|---------|--------|\n| 100% | ✪ | Maintain — exemplary signal |\n| 95–99% | ★ Championship | Annotate any flake immediately |\n| 85–94% | ◇ Acceptable | Schedule the flake-class fix this sprint |\n| 70–84% | ● Eroding | Stop adding tests — fix flakes first |\n| \u003C70% | ○ Dead signal | Block merges until signal restored |\n\n**Eliminate on sight:** hard absolute-time perf asserts on shared runners (`expect(t).toBeLessThan(30)`) → move to a non-gating workflow; network calls in the main suite → mock at the boundary; concurrency tests without explicit ordering; secret-dependent steps that hard-fail when missing → grey-skip.\n\n**The inverse rule:** green CI that passes while something is broken is equally a violation. If a real bug shipped despite green, write the regression test BEFORE the fix lands.\n\n**The conversation is the real gate.** CI is supporting infrastructure for the human + AI audit; flaky CI wastes the audit's bandwidth. Signal Integrity keeps CI worthy of the conversation.\n\n## Execution loop\n\n1. **Scope** — what should it do? happy path, edges, failure modes, perf targets, tier of each.\n2. **Audit signal** (Step 0) before trusting or extending the suite.\n3. **Run** each test: set up, prepare data, execute, observe actual vs expected, record pass\u002Ffail\u002Fblocked, capture evidence on failure.\n4. **Reproduce** every failure deterministically; root-cause it; note the fix.\n5. **Tier coverage check** — confirm every test is tiered:\n   ```bash\n   faf wjttc --path tests          # audit tier coverage (vendor-neutral)\n   faf wjttc --strict --json       # CI gate: non-zero if any test is untiered\n   ```\n6. **Report** — file the WJTTC report (below), then surface the tier verdict.\n\n## WJTTC report format\n\nSave reports to **`.\u002Fwjttc-reports\u002F`** in the project under test (or a path the user specifies). Never write to an absolute\u002Fpersonal path. Name files `YYYY-MM-DD-{project}-{feature}-tests.yaml`.\n\n```yaml\n---\n# WJTTC Test Report\nproject: \"project-name\"\nfeature: \"feature-being-tested\"\ndate: \"2026-06-26\"\ntier: \"Engine\"            # Brake | Engine | Aero | Tyre | Pit\nresult: \"PASS\"            # PASS | FAIL | BLOCKED\nenvironment: \"OS, runtime version, key deps\"\n---\n\n## Summary\nobjective: What was tested\ntotals: { total: 25, passed: 23, failed: 2, blocked: 0, pass_rate: \"92%\" }\n\n## Failures\n- name: \"Long-string handling\"\n  tier: \"Engine ⚡\"\n  status: \"FAIL\"\n  steps: [\"...\", \"...\"]\n  expected: \"Handle gracefully\"\n  actual: \"Crash\"\n  error: \"RangeError: ...\"\n  root_cause: \"Unbounded buffer\"\n  fix: \"Cap input length \u002F stream\"\n\n## Edge cases\n- { case: \"Empty string\", input: \"''\", expected: \"error\", actual: \"error\", status: \"PASS\" }\n- { case: \"Unicode\", input: \"?️\", expected: \"stored\", actual: \"stored\", status: \"PASS\" }\n\n## Performance\n- { op: \"file read\",  target: \"\u003C50ms\", actual: \"18ms\", status: \"PASS\" }\n- { op: \"parse YAML\", target: \"\u003C50ms\", actual: \"12ms\", status: \"PASS\" }\n\n## Bugs found\n- id: 1\n  title: \"...\"\n  severity: \"Brake\"      # tier doubles as severity\n  reproducibility: \"Always\"\n  impact: \"Who is affected, how serious\"\n  fix: \"...\"\n\n## Coverage\ntested:     [\"happy path\", \"edges\", \"error handling\", \"perf\"]\nnot_tested: [\"concurrent access\", \"files >100MB\"]\n\n## Verdict\ntier: \"◆ Silver\"          # from the tier table below\nto_next: [\"Fix 2 failing Engine tests\", \"Add Tyre concurrency tests\"]\n```\n\n## Tier verdict\n\nMap the pass rate (or SI score) to the single canonical FAF tier ladder. No second ladder, no medals.\n\n| Score | Tier | Symbol |\n|-------|------|--------|\n| 100% | Trophy | ✪ |\n| 99% | Gold | ★ |\n| 95% | Silver | ◆ |\n| 85% | Bronze | ◇ |\n| 70% | Green | ● |\n| 55% | Yellow | ● |\n| 1% | Red | ○ |\n| 0% | White | ♡ |\n\nThe FAF score is **deterministic** — same input, same score. A test report should be just as falsifiable: every verdict traces to a reproducible run. **FAF doesn't lie.**\n\n## WJTTC method notes\n\n- **Test with real data**, not just sanitized inputs — anonymized production data, messy inputs, production-like volume.\n- **Document every failure** so it can be reproduced: what failed, how to repro, why it matters, how to fix.\n- **Tier before you test** — severity is the tier, so triage first; `faf wjttc` enforces that nothing ships untiered.\n- **Wire it into CI** with TAF receipts so the report is part of the record, not a one-off:\n  ```bash\n  faf taf setup --write     # create .github\u002Fworkflows\u002Ftaf.yml (test receipts)\n  faf score --json          # deterministic score snapshot for the receipt\n  ```\n\n## Quick checklist (before release)\n\n- [ ] Signal Integrity audited (SI ≥ 85%)\n- [ ] Brake tests pass — zero tolerance\n- [ ] Edges + error handling tested\n- [ ] Tyre: behaves under load \u002F concurrency\n- [ ] `faf wjttc --strict` green — every test tiered\n- [ ] Regression (Pit) suite passes\n- [ ] WJTTC report filed in `.\u002Fwjttc-reports\u002F`\n- [ ] Pass rate ≥ 85% (◇ Bronze, production-ready)\n\n## Resources\n\n- Website: https:\u002F\u002Ffaf.one · Skills Site: https:\u002F\u002Fskills.faf.one\n- faf-cli: https:\u002F\u002Fgithub.com\u002FWolfe-Jam\u002Ffaf-cli\n- Sibling skill: **wjttc-builder** (plan + generate the suite)\n\n---\n\n*Made with ? by wolfejam.dev — \"We break things so others never have to know they were broken.\"*\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":28,"source":43,"license":14,"date_added":44,"description":7,"source_repo":45,"source_type":31,"license_source":46},"https:\u002F\u002Fgithub.com\u002FWolfe-Jam\u002Ffaf-skills\u002Ftree\u002Fmain\u002Fskills\u002Fwjttc-tester",1782864000000,"Wolfe-Jam\u002Ffaf-skills","https:\u002F\u002Fgithub.com\u002FWolfe-Jam\u002Ffaf-skills\u002Fblob\u002Fmain\u002FLICENSE","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Fwjttc-tester","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 wjttc-tester",{"tool":58,"command":59},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill wjttc-tester",{"tool":61,"command":62},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill wjttc-tester","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fwjttc-tester\u002FSKILL.md",true,[],[67,95,118,140,168,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,31,30,90,28,91,92,93,94],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","devops-security","access","configure","only","active","scope","scripts","relevant","implementing",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"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",[],[102,103,104,105,106,107,108,109,110,111,112,113,114,89,32,31,115,116,28,117],"delegate","zcode","zcode delegate","review","cli","orchestration","tasks","run","Bash","model","node","read","orchestrator","desktop app","app","agent-orchestration",{"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":14,"licenseFileUrl":6,"sourceHtmlUrl":122,"categories":123,"keywords":124,"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",[],[125,126,127,128,29,129,130,36,131,132,133,134,135,31,30,136,137,138,139,21],"transcript","youtube transcript","youtube","safe","codex","research","https","text","fetch","tooling","clean","local","output","deepapi","youtube transcripts",{"skillNo":141,"name":142,"nameZh":6,"description":143,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":144,"categories":145,"keywords":157,"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",[146,149,152],{"categoryNo":147,"categoryName":148,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":150,"categoryName":151,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":153,"categoryName":154,"taxonomyType":155,"taxonomyTypeDesc":156},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[125,126,127,158,128,159,29,129,36,160,161,162,163,133,164,31,30,165,166,167],"youtube transcript skills","gemini","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":169,"name":170,"nameZh":6,"description":171,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":172,"categories":173,"keywords":178,"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",[174,177],{"categoryNo":175,"categoryName":176,"taxonomyType":76,"taxonomyTypeDesc":77},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":150,"categoryName":151,"taxonomyType":76,"taxonomyTypeDesc":77},[127,179,180,106,128,181,182,183,184,36,162,185,186,187,188,30,189,136,190,191],"youtube notetaker","notetaker","workflow","official","notes","code","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":147,"categoryName":148,"taxonomyType":76,"taxonomyTypeDesc":77},[200,127,201,202,128,159,160,203,204,161,162,163,133,205,164,31,30,165,206,139],"youtube full","full","google","server","dlp","credits","automatic"]