[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P3PKNYRQRDABCWJTHBTFQZ":3,"skill-same:01M6P3PKNYRQRDABCWJTHBTFQZ":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":22,"publishedAt":43,"linkOnly":44,"markdownContent":45,"markdownBody":46,"frontMatter":47,"refName":30,"commitSha":63,"skillDirectory":64,"forksCount":13,"repositoryHtmlUrl":65,"repositoryHomepageUrl":6,"ownerHtmlUrl":66,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":67,"install":68,"resources":81},"01M6P3PKNYRQRDABCWJTHBTFQZ","fsi-compliance-checker",null,"Maps code, architecture, and infrastructure changes to specific control IDs in PCI-DSS v4.0 and MAS TRM (Singapore financial regulator), producing an audit-traceable findings report with per-control remediation.","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\u002Ffsi-compliance-checker\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"checker","fsi compliance checker","compliance checker","fsi","compliance","ids","pci","main","community","maps","security-review","review","remediation","audit","code","infrastructure","architecture","security","gemini","safe","2026-11-10 10:12:30",false,"---\nname: fsi-compliance-checker\ndescription: \"Maps code, architecture, and infrastructure changes to specific control IDs in PCI-DSS v4.0 and MAS TRM (Singapore financial regulator), producing an audit-traceable findings report with per-control remediation.\"\ncategory: security\nrisk: safe\nsource: community\nsource_repo: timwukp\u002Fagent-skills-best-practice\nsource_type: community\ndate_added: \"2026-06-12\"\nauthor: timwukp\ntags: [compliance, pci-dss, mas-trm, fintech, banking, security-review, audit, financial-services]\ntools: [claude, cursor, gemini, codex, antigravity]\nlicense: \"MIT\"\nlicense_source: \"https:\u002F\u002Fgithub.com\u002Ftimwukp\u002Fagent-skills-best-practice\u002Fblob\u002Fmain\u002FLICENSE\"\n---\n\n# FSI Compliance Checker\n\n## Overview\n\nMaps a concrete change (code diff, architecture design, IaC, pipeline config) to the specific controls it touches in financial services compliance frameworks — PCI-DSS v4.0 for payment card data and MAS TRM for Singapore-regulated institutions — and reports gaps with actionable remediation. This is engineering-level compliance triage: it helps teams catch violations before audit, but it does not replace a qualified assessor (QSA) or the institution's compliance function. Say so in every report.\n\n## When to Use This Skill\n\n- Use when a change touches payment card data (PAN, CVV, track data) and needs a PCI-DSS check\n- Use when reviewing changes at a Singapore-regulated financial institution against MAS TRM expectations\n- Use when someone asks \"is this compliant\", \"does logging this violate PCI\", or requests a banking-regulation review of a diff, design, or Terraform change\n- Do NOT use for generic security review (no framework involved), GDPR\u002FSOC2\u002FHIPAA (out of bundled scope), or legal advice\n\n## How It Works\n\n### Step 1: Select the framework\n\nLoad only the reference file(s) the engagement needs:\n\n| Situation | Load |\n|-----------|------|\n| Payment card data is stored, processed, or transmitted | [pci-dss.md](pci-dss.md) |\n| Singapore-regulated financial institution (bank, insurer, capital markets, major payment institution) | [mas-trm.md](mas-trm.md) |\n| Both apply (e.g. Singapore bank handling cards) | Both files |\n| Other jurisdictions\u002Fframeworks (SOX, GDPR, HKMA, APRA) | State they are out of scope; offer general secure-engineering review instead |\n\nIf the user hasn't said which applies, ask one question: what data does the change touch, and is the institution Singapore-regulated?\n\n### Step 2: Scope the change\n\nIdentify what the diff\u002Fdesign actually touches: data elements (card data? customer PII? credentials?), trust boundaries, environments (production? DR?), and third parties.\n\n### Step 3: Assess applicable controls\n\nSelect the applicable controls from the loaded reference file(s) — typically 5-15 controls, not the whole framework. List what you ruled out and why (one line each) so the scoping is auditable. Assess each as `Compliant` \u002F `Gap` \u002F `Needs evidence` (can't tell from the artifact — name the evidence required).\n\n### Step 4: Report\n\nEvery Gap gets: the control ID, what's wrong in this specific change, concrete remediation, and severity (Critical = violation involving live regulated data; High = control absent; Medium = control partial\u002Fundocumented).\n\n```markdown\n# Compliance Review: [change title]\n**Frameworks:** [PCI-DSS v4.0 \u002F MAS TRM 2021] · **Date:** [YYYY-MM-DD]\n**Scope:** [what was reviewed: files, design doc, pipeline]\n> Engineering triage only — not a substitute for QSA assessment or the compliance function.\n\n## Data & Boundary Analysis\n- Data elements touched: [e.g. PAN (masked), customer NRIC, none]\n- Environments\u002Fboundaries: [e.g. CDE-adjacent service, public API]\n\n## Findings\n| # | Control | Status | Severity | Finding | Remediation |\n|---|---------|--------|----------|---------|-------------|\n| 1 | [PCI 3.5.1] | Gap | Critical | [specific issue in this change] | [specific fix] |\n\n## Ruled Out (not applicable)\n- [Control area] — [one-line reason]\n\n## Evidence Needed\n- [Control]: [what artifact would demonstrate compliance]\n```\n\n### Step 5: Offer story conversion\n\nOffer to turn findings into backlog items with the control ID in each story for traceability.\n\n## Examples\n\n### Example 1: Logging review\n\n**User**: \"Is this PCI-DSS compliant: we log the full request body of card authorization calls for debugging?\"\n\n**Skill**: Loads pci-dss.md → Critical findings against 3.3.1 (CVV must never be stored post-authorization — logs are storage), 3.4.1 (PAN display masking), 3.5.1 (PAN unreadable at rest); remediation: remove the log line or apply a field-allowlist redaction filter; flags downstream log-pipeline scoping (10.3.x); QSA disclaimer included.\n\n### Example 2: Cloud migration\n\n**User**: \"Our Singapore bank is moving the customer notification service to a cloud region in another country. MAS TRM implications?\"\n\n**Skill**: Loads mas-trm.md → reviews against §11.5 (cloud: due diligence, data residency, exit strategy), flags the MAS Outsourcing Guidelines as a related instrument, asks what customer data the service touches before rating severity.\n\n## Common FSI Engineering Triggers\n\nChanges that almost always have compliance impact — check proactively when they appear in a diff:\n\n- Logging statements near payment or authentication flows (PAN\u002FCVV must never be logged; MAS TRM requires security event logging — both directions matter)\n- New data stores or caches receiving customer or card data (encryption at rest, retention, residency)\n- Authentication\u002Fsession changes (MFA requirements, session timeout, credential storage)\n- New third-party SDKs or API integrations (outsourcing\u002Fvendor controls, data flows leaving the boundary)\n- Infrastructure changes touching network segmentation, security groups, or public exposure\n- CI\u002FCD changes that alter who\u002Fwhat can deploy to production (change management, segregation of duties)\n\n## Guardrails\n\n- Cite control IDs precisely (e.g. \"PCI-DSS 8.3.6\", \"MAS TRM 9.1.1\") so findings are traceable in audit tooling; the bundled reference files carry the ID schemes.\n- Severity discipline: don't inflate. A missing comment is not a Critical; unencrypted PAN at rest is.\n- When the change is compliant, say so affirmatively per control — \"no findings\" plus the checked-control list is a useful audit artifact.\n- Never output real card numbers, even as examples; use the standard test PANs (e.g. 4111 1111 1111 1111) when illustrating.\n- Read-only: this skill reviews and reports; it never modifies code, infrastructure, or configuration.\n\n## Limitations\n\n- Covers only the bundled PCI-DSS v4.0 and MAS TRM engineering summaries; other frameworks or local policy overlays need separate review.\n- Provides engineering triage, not legal advice, QSA assessment, or formal compliance sign-off.\n- Requires concrete evidence such as diffs, designs, IaC, logs, or control artifacts; incomplete evidence should be marked `Needs evidence`.\n- The bundled references are concise control maps, not substitutes for reading the official standards.\n\n## Credits\n\nAdapted from [timwukp\u002Fagent-skills-best-practice](https:\u002F\u002Fgithub.com\u002Ftimwukp\u002Fagent-skills-best-practice) (MIT), where the skill ships with evals and a documented 4-layer test methodology (see the repo's TESTING.md).\n","# FSI Compliance Checker\n\n## Overview\n\nMaps a concrete change (code diff, architecture design, IaC, pipeline config) to the specific controls it touches in financial services compliance frameworks — PCI-DSS v4.0 for payment card data and MAS TRM for Singapore-regulated institutions — and reports gaps with actionable remediation. This is engineering-level compliance triage: it helps teams catch violations before audit, but it does not replace a qualified assessor (QSA) or the institution's compliance function. Say so in every report.\n\n## When to Use This Skill\n\n- Use when a change touches payment card data (PAN, CVV, track data) and needs a PCI-DSS check\n- Use when reviewing changes at a Singapore-regulated financial institution against MAS TRM expectations\n- Use when someone asks \"is this compliant\", \"does logging this violate PCI\", or requests a banking-regulation review of a diff, design, or Terraform change\n- Do NOT use for generic security review (no framework involved), GDPR\u002FSOC2\u002FHIPAA (out of bundled scope), or legal advice\n\n## How It Works\n\n### Step 1: Select the framework\n\nLoad only the reference file(s) the engagement needs:\n\n| Situation | Load |\n|-----------|------|\n| Payment card data is stored, processed, or transmitted | [pci-dss.md](pci-dss.md) |\n| Singapore-regulated financial institution (bank, insurer, capital markets, major payment institution) | [mas-trm.md](mas-trm.md) |\n| Both apply (e.g. Singapore bank handling cards) | Both files |\n| Other jurisdictions\u002Fframeworks (SOX, GDPR, HKMA, APRA) | State they are out of scope; offer general secure-engineering review instead |\n\nIf the user hasn't said which applies, ask one question: what data does the change touch, and is the institution Singapore-regulated?\n\n### Step 2: Scope the change\n\nIdentify what the diff\u002Fdesign actually touches: data elements (card data? customer PII? credentials?), trust boundaries, environments (production? DR?), and third parties.\n\n### Step 3: Assess applicable controls\n\nSelect the applicable controls from the loaded reference file(s) — typically 5-15 controls, not the whole framework. List what you ruled out and why (one line each) so the scoping is auditable. Assess each as `Compliant` \u002F `Gap` \u002F `Needs evidence` (can't tell from the artifact — name the evidence required).\n\n### Step 4: Report\n\nEvery Gap gets: the control ID, what's wrong in this specific change, concrete remediation, and severity (Critical = violation involving live regulated data; High = control absent; Medium = control partial\u002Fundocumented).\n\n```markdown\n# Compliance Review: [change title]\n**Frameworks:** [PCI-DSS v4.0 \u002F MAS TRM 2021] · **Date:** [YYYY-MM-DD]\n**Scope:** [what was reviewed: files, design doc, pipeline]\n> Engineering triage only — not a substitute for QSA assessment or the compliance function.\n\n## Data & Boundary Analysis\n- Data elements touched: [e.g. PAN (masked), customer NRIC, none]\n- Environments\u002Fboundaries: [e.g. CDE-adjacent service, public API]\n\n## Findings\n| # | Control | Status | Severity | Finding | Remediation |\n|---|---------|--------|----------|---------|-------------|\n| 1 | [PCI 3.5.1] | Gap | Critical | [specific issue in this change] | [specific fix] |\n\n## Ruled Out (not applicable)\n- [Control area] — [one-line reason]\n\n## Evidence Needed\n- [Control]: [what artifact would demonstrate compliance]\n```\n\n### Step 5: Offer story conversion\n\nOffer to turn findings into backlog items with the control ID in each story for traceability.\n\n## Examples\n\n### Example 1: Logging review\n\n**User**: \"Is this PCI-DSS compliant: we log the full request body of card authorization calls for debugging?\"\n\n**Skill**: Loads pci-dss.md → Critical findings against 3.3.1 (CVV must never be stored post-authorization — logs are storage), 3.4.1 (PAN display masking), 3.5.1 (PAN unreadable at rest); remediation: remove the log line or apply a field-allowlist redaction filter; flags downstream log-pipeline scoping (10.3.x); QSA disclaimer included.\n\n### Example 2: Cloud migration\n\n**User**: \"Our Singapore bank is moving the customer notification service to a cloud region in another country. MAS TRM implications?\"\n\n**Skill**: Loads mas-trm.md → reviews against §11.5 (cloud: due diligence, data residency, exit strategy), flags the MAS Outsourcing Guidelines as a related instrument, asks what customer data the service touches before rating severity.\n\n## Common FSI Engineering Triggers\n\nChanges that almost always have compliance impact — check proactively when they appear in a diff:\n\n- Logging statements near payment or authentication flows (PAN\u002FCVV must never be logged; MAS TRM requires security event logging — both directions matter)\n- New data stores or caches receiving customer or card data (encryption at rest, retention, residency)\n- Authentication\u002Fsession changes (MFA requirements, session timeout, credential storage)\n- New third-party SDKs or API integrations (outsourcing\u002Fvendor controls, data flows leaving the boundary)\n- Infrastructure changes touching network segmentation, security groups, or public exposure\n- CI\u002FCD changes that alter who\u002Fwhat can deploy to production (change management, segregation of duties)\n\n## Guardrails\n\n- Cite control IDs precisely (e.g. \"PCI-DSS 8.3.6\", \"MAS TRM 9.1.1\") so findings are traceable in audit tooling; the bundled reference files carry the ID schemes.\n- Severity discipline: don't inflate. A missing comment is not a Critical; unencrypted PAN at rest is.\n- When the change is compliant, say so affirmatively per control — \"no findings\" plus the checked-control list is a useful audit artifact.\n- Never output real card numbers, even as examples; use the standard test PANs (e.g. 4111 1111 1111 1111) when illustrating.\n- Read-only: this skill reviews and reports; it never modifies code, infrastructure, or configuration.\n\n## Limitations\n\n- Covers only the bundled PCI-DSS v4.0 and MAS TRM engineering summaries; other frameworks or local policy overlays need separate review.\n- Provides engineering triage, not legal advice, QSA assessment, or formal compliance sign-off.\n- Requires concrete evidence such as diffs, designs, IaC, logs, or control artifacts; incomplete evidence should be marked `Needs evidence`.\n- The bundled references are concise control maps, not substitutes for reading the official standards.\n\n## Credits\n\nAdapted from [timwukp\u002Fagent-skills-best-practice](https:\u002F\u002Fgithub.com\u002Ftimwukp\u002Fagent-skills-best-practice) (MIT), where the skill ships with evals and a documented 4-layer test methodology (see the repo's TESTING.md).\n",{"name":5,"risk":42,"tags":48,"tools":54,"author":59,"source":31,"license":14,"category":40,"date_added":60,"description":7,"source_repo":61,"source_type":31,"license_source":62},[27,49,50,51,52,33,36,53],"pci-dss","mas-trm","fintech","banking","financial-services",[55,56,41,57,58],"claude","cursor","codex","antigravity","timwukp","2026-06-12","timwukp\u002Fagent-skills-best-practice","https:\u002F\u002Fgithub.com\u002Ftimwukp\u002Fagent-skills-best-practice\u002Fblob\u002Fmain\u002FLICENSE","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Ffsi-compliance-checker","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 fsi-compliance-checker",{"tool":74,"command":75},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill fsi-compliance-checker",{"tool":77,"command":78},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill fsi-compliance-checker","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Ffsi-compliance-checker\u002FSKILL.md",true,[82,88],{"path":83,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":86,"sourceHtmlUrl":87},"mas-trm.md","REFERENCE","参考文档",8125,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Ffsi-compliance-checker\u002Fmas-trm.md",{"path":89,"resourceType":84,"resourceTypeDesc":85,"sizeBytes":90,"sourceHtmlUrl":91},"pci-dss.md",6577,"https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Ffsi-compliance-checker\u002Fpci-dss.md",[93,121,144,167,192,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":14,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":104,"publishedAt":43},"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",[99],{"categoryNo":100,"categoryName":101,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000011","运维与部署","SCENARIO","使用场景",[105,106,107,39,108,109,95,110,111,112,113,114,31,30,115,116,117,118,119,120],"ZeRO","trust","zero trust","assessment","verification","segmentation","devops-security","access","configure","only","active","critical","scope","scripts","relevant","implementing",{"skillNo":122,"name":123,"nameZh":6,"description":124,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":125,"categories":126,"keywords":127,"publishedAt":43},"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",[],[128,129,130,34,131,132,133,134,135,136,137,138,139,114,140,31,141,142,116,143],"delegate","zcode","zcode delegate","cli","orchestration","tasks","run","Bash","model","node","read","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":145,"name":146,"nameZh":6,"description":147,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":148,"categories":149,"keywords":150,"publishedAt":43},"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",[],[151,152,153,42,154,57,155,156,157,158,159,160,161,31,30,162,163,164,165,166],"transcript","youtube transcript","youtube","github","research","license","https","text","fetch","tooling","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":168,"name":169,"nameZh":6,"description":170,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":171,"categories":172,"keywords":182,"publishedAt":43},"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",[173,176,179],{"categoryNo":174,"categoryName":175,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":177,"categoryName":178,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":180,"categoryName":181,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000030","开发工程师",[151,152,153,183,42,41,154,57,156,184,185,186,187,159,188,31,30,189,190,191],"youtube transcript skills","search","api","Video","browse","api-integration","free","card","channels",{"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":202,"publishedAt":43},"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",[198,201],{"categoryNo":199,"categoryName":200,"taxonomyType":102,"taxonomyTypeDesc":103},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":177,"categoryName":178,"taxonomyType":102,"taxonomyTypeDesc":103},[153,203,204,131,42,205,206,207,37,156,186,208,209,210,211,30,212,162,213,214],"youtube notetaker","notetaker","workflow","official","notes","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":14,"licenseFileUrl":6,"sourceHtmlUrl":219,"categories":220,"keywords":222,"publishedAt":43},"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":174,"categoryName":175,"taxonomyType":102,"taxonomyTypeDesc":103},[223,153,224,225,42,41,184,226,227,185,186,187,159,228,188,31,30,189,229,165],"youtube full","full","google","server","dlp","credits","automatic"]