[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6P9TYP4BCGYY6KJA85BEMJE":3,"skill-same:01M6P9TYP4BCGYY6KJA85BEMJE":71},{"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":33,"commitSha":52,"skillDirectory":53,"forksCount":13,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M6P9TYP4BCGYY6KJA85BEMJE","monte-carlo-asset-health",null,"Curated upstream guidance for Monte Carlo Asset Health; use when the workflow matches the user goal.","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\u002Fmonte-carlo-asset-health\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"monte carlo asset health","asset","health","community","for","tree","mc","critical","monte-carlo","upstream","main","github","guidance","goal","use","data","https","license","toolkit","workflow","2026-11-10 10:12:30",false,"---\ndescription: Curated upstream guidance for Monte Carlo Asset Health; use when the workflow matches the user goal.\nname: monte-carlo-asset-health\nrisk: critical\nsource: https:\u002F\u002Fgithub.com\u002Fmonte-carlo-data\u002Fmc-agent-toolkit\u002Ftree\u002Fmain\u002Fskills\u002Fasset-health\nsource_repo: monte-carlo-data\u002Fmc-agent-toolkit\nsource_type: community\ndate_added: 2026-07-01\nlicense: Apache-2.0\nlicense_source: https:\u002F\u002Fgithub.com\u002Fmonte-carlo-data\u002Fmc-agent-toolkit\u002Fblob\u002Fmain\u002FLICENSE\n---\n## When to Use\n\n- Use when the user goal matches this upstream workflow.\n\n# Monte Carlo Asset Health Skill\n\nThis skill checks the health of a data asset using Monte Carlo's observability\nplatform. It produces a structured health report covering freshness, alerts,\nmonitoring coverage, importance, and upstream dependency health.\n\n> **Monte Carlo tool routing (required):** Always call Monte Carlo MCP tools through this plugin's\n> bundled server, whose fully-qualified tool names are\n> `mcp__plugin_mc-agent-toolkit_monte-carlo-mcp__\u003Ctool>` (e.g.\n> `mcp__plugin_mc-agent-toolkit_monte-carlo-mcp__get_alerts`). Bare tool names used in this skill\n> (`get_alerts`, `search`, `get_table`, …) refer to that bundled server. If the session also has a\n> separately-configured `monte-carlo-mcp` server, do **not** route to it — it may point at a\n> different endpoint or credentials.\n\n## REQUIRED: Read reference files before executing\n\n**You MUST read both reference files using the Read tool before making any MCP\ntool calls.** These files are the source of truth for tool calls, parameters,\nand response interpretation. This file only defines when to activate and how to\nformat the output.\n\n1. `references\u002Fworkflows.md` (relative to this file) — exact tool calls, phases, and execution order\n2. `references\u002Fparameters.md` (relative to this file) — parameter conventions and field details\n\n**Do NOT make any MCP tool calls until you have read both files.**\n\n## When to activate this skill\n\nActivate when the user:\n\n- Asks about health: \"how is table X doing?\", \"check health of X\", \"is X healthy?\"\n- Asks about status: \"what's the status of X?\", \"status of orders table\"\n- Asks to check on a table: \"check on X table\", \"check on X\"\n- Asks about reliability, freshness, or quality of a specific asset\n- References a table in context of incident triage or change planning\n\n## When NOT to activate this skill\n\n- **Profiling or exploring table data** (row counts, column stats, distributions) → use `explore-table`\n- **Creating or suggesting monitors** → use `monitoring-advisor`\n- **Active incident triage** (investigating root cause of a firing alert) → use prevent skill Workflow 3\n\n## Health report format\n\n**CRITICAL: Only report data returned by the tools defined in `references\u002Fworkflows.md`.\nDo NOT call additional tools, do NOT infer or fabricate metrics. Each row below\nspecifies exactly which tool provides its value.**\n\n**All sections (Active Alerts, Monitors, Upstream Issues, Recommendations) must\nalways appear with their heading.** Never omit a section — if there is no data,\nshow the empty-state text defined below.\n\n**Never use emoji shortcodes** (like `:warning:` or `:arrow_up:`). Use Unicode\nemoji characters directly (like ⚠️) or plain text. Shortcodes render as raw text\nin the terminal.\n\n**Always display URLs as bare URLs**, never as markdown links (e.g., `[text](https:\u002F\u002Fgithub.com\u002Fmonte-carlo-data\u002Fmc-agent-toolkit\u002Ftree\u002Fmain\u002Fskills\u002Fasset-health\u002Furl)`).\n\n**`{MC_WEBAPP_URL}` appears throughout this template.** Every occurrence must be\nreplaced with the actual value returned by calling `get_mc_webapp_url()`. Never\nhardcode or guess this URL — it varies by environment.\n\nPresent results in this structure:\n\n```\n## Health Check: \u003Ctable_name>\n\n**Tags:** `tag1:value1`, `tag2:value2` (or \"None\" if no tags)\n**Link:** {MC_WEBAPP_URL}\u002Fassets\u002F{mcon}\n**Warehouse:** snowflake-prod (Snowflake)\n**Status: ? Healthy \u002F ? Degraded \u002F ? Unhealthy** | **Importance:** 0.85 (key asset ⭐️)\n**Avg Reads\u002FDay:** ~538 | **Avg Writes\u002FDay:** ~12\n\n| Metric        | Value                          | Signal |\n|---------------|--------------------------------|--------|\n| Last Activity | Apr 6, 2025                    | ? Recent    |\n| Alerts        | 2 active                       | ? Has alerts |\n| Monitoring    | 3 active monitors              | ? Monitored  |\n| Upstream      | 1\u002F3 sources unhealthy          | ? Issues     |\n\n### Active Alerts\n\n| Date  | Type           | Priority | Status           | Link                                                    |\n|-------|----------------|----------|------------------|---------------------------------------------------------|\n| Apr 8 | Metric anomaly | P3       | Not acknowledged | {MC_WEBAPP_URL}\u002Falerts\u002F{alert_uuid} |\n| Apr 7 | Freshness      | P2       | Acknowledged     | {MC_WEBAPP_URL}\u002Falerts\u002F{alert_uuid} |\n\nIf there are more than 5 active alerts, display only 5. Do NOT put the overflow\nmessage inside the table as a row. Instead, put it as plain text on the line\nimmediately after the table:\n\nThere are N more alerts not shown for brevity\n\nIf there are zero active alerts, show:\nNo active alerts in the last 7 days.\n\n### Monitors\n\n| Type        | Name                                    | Incidents (7d) | Status              |\n|-------------|-----------------------------------------|----------------|---------------------|\n| TABLE       | Orders freshness and schema             | 3              | Running hourly      |\n| METRIC      | Revenue row count                       | 0              | Never executed      |\n| BULK_METRIC | Warehouse volume check                  | 21             | ⚠️ 1 table has errors |\n\nIf there are zero monitors, show:\nNo monitors configured for this table.\n\n### Upstream Issues\n- raw_orders — FRESHNESS alert: not updated in 8h\n- raw_payments — healthy\n- dim_customers — healthy\n\n> Want me to check further upstream for **raw_orders**?\n\nIf there are no upstream dependencies, show:\nNo upstream dependencies found.\n\n### Diagnosis\n\n1-2 sentences summarizing what is causing the table to be unhealthy, or\nconfirming it is healthy. This should naturally lead into the recommendations.\n\nExample (unhealthy):\nUpstream table raw_orders has not been updated in 8 hours, which is likely\ncausing staleness in this table. There are also 2 unacknowledged alerts.\n\nExample (healthy):\nTable is healthy — no active alerts, monitored, and all upstream sources\nare in good shape.\n\n### Recommendations\n- Investigate upstream raw_orders freshness — likely root cause of this table's staleness\n- Acknowledge or investigate the 2 active alerts\n\nIf there are no recommendations, show:\nNo recommendations — table looks healthy.\n\n```\n\n### Metric definitions — exact data sources\n\nEach metric row MUST use only the specified data source. Do not add, infer, or\nembellish values beyond what the tool returns.\n\n| Metric | Data source | What to show | Signal |\n|--------|------------|-------------|--------|\n| **Last Activity** | `get_table` → `last_activity` | Date of last activity (e.g., \"Apr 6, 2025\") | ? Recent (within 7 days) \u002F ? Stale (older than 7 days) |\n| **Alerts** | `get_alerts` → count | \"N active\" or \"No active alerts\" | ? Has alerts \u002F ? No alerts |\n| **Monitoring** | `get_monitors` → count where `is_paused` is false | \"N active monitors\" or \"0 active monitors (M paused)\". Include relevant details from monitor fields (incident counts, error counts, types). | ? Monitored (≥1 active) \u002F ? Unmonitored (0 active) |\n| **Upstream** | `get_asset_lineage` (upstream) + Phase 3 checks | \"N\u002FM sources unhealthy\" or \"All N sources healthy\" | ? Issues (any unhealthy) \u002F ? Healthy (all healthy) |\n\n**Importance** is shown next to the Status line (not in the metrics table). Source:\n`get_table` → `importance_score` + `is_important`. Show \"X.XX (key asset ⭐️)\" if\nkey asset or importance > 0.8, otherwise just \"X.XX\".\n\n**Avg Reads\u002FDay** and **Avg Writes\u002FDay** are shown below the Status line. Source:\n`get_table` → `table_stats.avg_reads_per_active_day` and `table_stats.avg_writes_per_active_day`.\n\n**Do NOT include downstream data.** This skill only queries upstream lineage.\n\n### Status determination\n\n- **? Unhealthy:** Any active alerts on the asset (from `get_alerts` with statuses `[\"NOT_ACKNOWLEDGED\", \"ACKNOWLEDGED\", \"WORK_IN_PROGRESS\"]` — see `parameters.md`)\n- **? Degraded:** No active alerts, but 0 active monitors on a high-importance\n  asset (importance > 0.8 or key asset)\n- **? Healthy:** No active alerts and has at least 1 active monitor\n\n### Tags\n\nDisplay tags from the `search` tool's `properties` field. Show as inline badges:\n`key:value`. If no tags exist, show \"None\". Always include the Tags line.\n\n### Warehouse\n\nDisplay the warehouse name and type from the `search` result. Always include this line.\n\n### Recommendations\n\nOnly include recommendations derivable from collected data:\n- Upstream health issues that may be root causes\n- Active alerts that need acknowledgment or investigation\n- Do NOT recommend specific monitor types — that is outside this skill's scope\n\n\n## Examples\n\n```text\nUser: Apply this skill to my current task.\nAssistant: Follow the workflow in this skill, cite limitations, and ask before risky steps.\n```\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","## When to Use\n\n- Use when the user goal matches this upstream workflow.\n\n# Monte Carlo Asset Health Skill\n\nThis skill checks the health of a data asset using Monte Carlo's observability\nplatform. It produces a structured health report covering freshness, alerts,\nmonitoring coverage, importance, and upstream dependency health.\n\n> **Monte Carlo tool routing (required):** Always call Monte Carlo MCP tools through this plugin's\n> bundled server, whose fully-qualified tool names are\n> `mcp__plugin_mc-agent-toolkit_monte-carlo-mcp__\u003Ctool>` (e.g.\n> `mcp__plugin_mc-agent-toolkit_monte-carlo-mcp__get_alerts`). Bare tool names used in this skill\n> (`get_alerts`, `search`, `get_table`, …) refer to that bundled server. If the session also has a\n> separately-configured `monte-carlo-mcp` server, do **not** route to it — it may point at a\n> different endpoint or credentials.\n\n## REQUIRED: Read reference files before executing\n\n**You MUST read both reference files using the Read tool before making any MCP\ntool calls.** These files are the source of truth for tool calls, parameters,\nand response interpretation. This file only defines when to activate and how to\nformat the output.\n\n1. `references\u002Fworkflows.md` (relative to this file) — exact tool calls, phases, and execution order\n2. `references\u002Fparameters.md` (relative to this file) — parameter conventions and field details\n\n**Do NOT make any MCP tool calls until you have read both files.**\n\n## When to activate this skill\n\nActivate when the user:\n\n- Asks about health: \"how is table X doing?\", \"check health of X\", \"is X healthy?\"\n- Asks about status: \"what's the status of X?\", \"status of orders table\"\n- Asks to check on a table: \"check on X table\", \"check on X\"\n- Asks about reliability, freshness, or quality of a specific asset\n- References a table in context of incident triage or change planning\n\n## When NOT to activate this skill\n\n- **Profiling or exploring table data** (row counts, column stats, distributions) → use `explore-table`\n- **Creating or suggesting monitors** → use `monitoring-advisor`\n- **Active incident triage** (investigating root cause of a firing alert) → use prevent skill Workflow 3\n\n## Health report format\n\n**CRITICAL: Only report data returned by the tools defined in `references\u002Fworkflows.md`.\nDo NOT call additional tools, do NOT infer or fabricate metrics. Each row below\nspecifies exactly which tool provides its value.**\n\n**All sections (Active Alerts, Monitors, Upstream Issues, Recommendations) must\nalways appear with their heading.** Never omit a section — if there is no data,\nshow the empty-state text defined below.\n\n**Never use emoji shortcodes** (like `:warning:` or `:arrow_up:`). Use Unicode\nemoji characters directly (like ⚠️) or plain text. Shortcodes render as raw text\nin the terminal.\n\n**Always display URLs as bare URLs**, never as markdown links (e.g., `[text](https:\u002F\u002Fgithub.com\u002Fmonte-carlo-data\u002Fmc-agent-toolkit\u002Ftree\u002Fmain\u002Fskills\u002Fasset-health\u002Furl)`).\n\n**`{MC_WEBAPP_URL}` appears throughout this template.** Every occurrence must be\nreplaced with the actual value returned by calling `get_mc_webapp_url()`. Never\nhardcode or guess this URL — it varies by environment.\n\nPresent results in this structure:\n\n```\n## Health Check: \u003Ctable_name>\n\n**Tags:** `tag1:value1`, `tag2:value2` (or \"None\" if no tags)\n**Link:** {MC_WEBAPP_URL}\u002Fassets\u002F{mcon}\n**Warehouse:** snowflake-prod (Snowflake)\n**Status: ? Healthy \u002F ? Degraded \u002F ? Unhealthy** | **Importance:** 0.85 (key asset ⭐️)\n**Avg Reads\u002FDay:** ~538 | **Avg Writes\u002FDay:** ~12\n\n| Metric        | Value                          | Signal |\n|---------------|--------------------------------|--------|\n| Last Activity | Apr 6, 2025                    | ? Recent    |\n| Alerts        | 2 active                       | ? Has alerts |\n| Monitoring    | 3 active monitors              | ? Monitored  |\n| Upstream      | 1\u002F3 sources unhealthy          | ? Issues     |\n\n### Active Alerts\n\n| Date  | Type           | Priority | Status           | Link                                                    |\n|-------|----------------|----------|------------------|---------------------------------------------------------|\n| Apr 8 | Metric anomaly | P3       | Not acknowledged | {MC_WEBAPP_URL}\u002Falerts\u002F{alert_uuid} |\n| Apr 7 | Freshness      | P2       | Acknowledged     | {MC_WEBAPP_URL}\u002Falerts\u002F{alert_uuid} |\n\nIf there are more than 5 active alerts, display only 5. Do NOT put the overflow\nmessage inside the table as a row. Instead, put it as plain text on the line\nimmediately after the table:\n\nThere are N more alerts not shown for brevity\n\nIf there are zero active alerts, show:\nNo active alerts in the last 7 days.\n\n### Monitors\n\n| Type        | Name                                    | Incidents (7d) | Status              |\n|-------------|-----------------------------------------|----------------|---------------------|\n| TABLE       | Orders freshness and schema             | 3              | Running hourly      |\n| METRIC      | Revenue row count                       | 0              | Never executed      |\n| BULK_METRIC | Warehouse volume check                  | 21             | ⚠️ 1 table has errors |\n\nIf there are zero monitors, show:\nNo monitors configured for this table.\n\n### Upstream Issues\n- raw_orders — FRESHNESS alert: not updated in 8h\n- raw_payments — healthy\n- dim_customers — healthy\n\n> Want me to check further upstream for **raw_orders**?\n\nIf there are no upstream dependencies, show:\nNo upstream dependencies found.\n\n### Diagnosis\n\n1-2 sentences summarizing what is causing the table to be unhealthy, or\nconfirming it is healthy. This should naturally lead into the recommendations.\n\nExample (unhealthy):\nUpstream table raw_orders has not been updated in 8 hours, which is likely\ncausing staleness in this table. There are also 2 unacknowledged alerts.\n\nExample (healthy):\nTable is healthy — no active alerts, monitored, and all upstream sources\nare in good shape.\n\n### Recommendations\n- Investigate upstream raw_orders freshness — likely root cause of this table's staleness\n- Acknowledge or investigate the 2 active alerts\n\nIf there are no recommendations, show:\nNo recommendations — table looks healthy.\n\n```\n\n### Metric definitions — exact data sources\n\nEach metric row MUST use only the specified data source. Do not add, infer, or\nembellish values beyond what the tool returns.\n\n| Metric | Data source | What to show | Signal |\n|--------|------------|-------------|--------|\n| **Last Activity** | `get_table` → `last_activity` | Date of last activity (e.g., \"Apr 6, 2025\") | ? Recent (within 7 days) \u002F ? Stale (older than 7 days) |\n| **Alerts** | `get_alerts` → count | \"N active\" or \"No active alerts\" | ? Has alerts \u002F ? No alerts |\n| **Monitoring** | `get_monitors` → count where `is_paused` is false | \"N active monitors\" or \"0 active monitors (M paused)\". Include relevant details from monitor fields (incident counts, error counts, types). | ? Monitored (≥1 active) \u002F ? Unmonitored (0 active) |\n| **Upstream** | `get_asset_lineage` (upstream) + Phase 3 checks | \"N\u002FM sources unhealthy\" or \"All N sources healthy\" | ? Issues (any unhealthy) \u002F ? Healthy (all healthy) |\n\n**Importance** is shown next to the Status line (not in the metrics table). Source:\n`get_table` → `importance_score` + `is_important`. Show \"X.XX (key asset ⭐️)\" if\nkey asset or importance > 0.8, otherwise just \"X.XX\".\n\n**Avg Reads\u002FDay** and **Avg Writes\u002FDay** are shown below the Status line. Source:\n`get_table` → `table_stats.avg_reads_per_active_day` and `table_stats.avg_writes_per_active_day`.\n\n**Do NOT include downstream data.** This skill only queries upstream lineage.\n\n### Status determination\n\n- **? Unhealthy:** Any active alerts on the asset (from `get_alerts` with statuses `[\"NOT_ACKNOWLEDGED\", \"ACKNOWLEDGED\", \"WORK_IN_PROGRESS\"]` — see `parameters.md`)\n- **? Degraded:** No active alerts, but 0 active monitors on a high-importance\n  asset (importance > 0.8 or key asset)\n- **? Healthy:** No active alerts and has at least 1 active monitor\n\n### Tags\n\nDisplay tags from the `search` tool's `properties` field. Show as inline badges:\n`key:value`. If no tags exist, show \"None\". Always include the Tags line.\n\n### Warehouse\n\nDisplay the warehouse name and type from the `search` result. Always include this line.\n\n### Recommendations\n\nOnly include recommendations derivable from collected data:\n- Upstream health issues that may be root causes\n- Active alerts that need acknowledgment or investigation\n- Do NOT recommend specific monitor types — that is outside this skill's scope\n\n\n## Examples\n\n```text\nUser: Apply this skill to my current task.\nAssistant: Follow the workflow in this skill, cite limitations, and ask before risky steps.\n```\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":30,"source":48,"license":14,"date_added":49,"description":7,"source_repo":50,"source_type":26,"license_source":51},"https:\u002F\u002Fgithub.com\u002Fmonte-carlo-data\u002Fmc-agent-toolkit\u002Ftree\u002Fmain\u002Fskills\u002Fasset-health",1782864000000,"monte-carlo-data\u002Fmc-agent-toolkit","https:\u002F\u002Fgithub.com\u002Fmonte-carlo-data\u002Fmc-agent-toolkit\u002Fblob\u002Fmain\u002FLICENSE","f3312ba749561b6159f477dbfc9313c875d40a56",".agents\u002Fskills_archive\u002Fmonte-carlo-asset-health","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":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill monte-carlo-asset-health",{"tool":63,"command":64},"bunx","bunx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill monte-carlo-asset-health",{"tool":66,"command":67},"pnpm","pnpm dlx skills add duc-duy-1612\u002FOnline-Delivery-Systems-Web --skill monte-carlo-asset-health","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fmonte-carlo-asset-health\u002FSKILL.md",true,[],[72,99,123,145,173,196],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":82,"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.","MIT","https:\u002F\u002Fgithub.com\u002Fduc-duy-1612\u002FOnline-Delivery-Systems-Web\u002Fblob\u002Fmain\u002F.agents\u002Fskills_archive\u002Fzero-trust\u002FSKILL.md",[79],{"categoryNo":80,"categoryName":81,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000011","运维与部署",[83,84,85,86,87,88,74,89,90,91,92,93,26,33,94,30,95,96,97,98],"ZeRO","trust","zero trust","architecture","assessment","verification","segmentation","devops-security","access","configure","only","active","scope","scripts","relevant","implementing",{"skillNo":100,"name":101,"nameZh":6,"description":102,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"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",[],[106,107,108,109,110,111,112,113,114,115,116,117,118,93,119,26,120,121,30,122],"delegate","zcode","zcode delegate","review","cli","orchestration","tasks","run","Bash","model","node","read","orchestrator","files","desktop app","app","agent-orchestration",{"skillNo":124,"name":125,"nameZh":6,"description":126,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":127,"categories":128,"keywords":129,"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",[],[130,131,132,133,34,134,135,40,39,136,137,138,139,26,33,140,141,142,143,144],"transcript","youtube transcript","youtube","safe","codex","research","text","fetch","tooling","clean","local","output","deepapi","youtube transcripts","blob",{"skillNo":146,"name":147,"nameZh":6,"description":148,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":149,"categories":150,"keywords":162,"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",[151,154,157],{"categoryNo":152,"categoryName":153,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000010","后端与接口",{"categoryNo":155,"categoryName":156,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000016","图像与多媒体",{"categoryNo":158,"categoryName":159,"taxonomyType":160,"taxonomyTypeDesc":161},"01JBSEEDCAT000000000000030","开发工程师","PROFESSION","适用职业",[130,131,132,163,133,164,34,134,40,165,166,167,168,137,169,26,33,170,171,172],"youtube transcript skills","gemini","search","api","Video","browse","api-integration","free","card","channels",{"skillNo":174,"name":175,"nameZh":6,"description":176,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":177,"categories":178,"keywords":183,"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",[179,182],{"categoryNo":180,"categoryName":181,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000003","演示文稿",{"categoryNo":155,"categoryName":156,"taxonomyType":20,"taxonomyTypeDesc":21},[132,184,185,110,133,42,186,187,188,40,167,189,190,191,192,33,193,140,194,195],"youtube notetaker","notetaker","official","notes","code","markdown","slides","annotations","README","study","dair-academy","viewer",{"skillNo":197,"name":198,"nameZh":6,"description":199,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":76,"licenseFileUrl":6,"sourceHtmlUrl":200,"categories":201,"keywords":203,"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",[202],{"categoryNo":152,"categoryName":153,"taxonomyType":20,"taxonomyTypeDesc":21},[204,132,205,206,133,164,165,207,208,166,167,168,137,209,169,26,33,170,210,143],"youtube full","full","google","server","dlp","credits","automatic"]