[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7A6V5W74790WK8VDZX2P3JB":3,"skill-same:01M7A6V5W74790WK8VDZX2P3JB":53},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":36,"ownerDescription":37,"updatedAt":38,"install":39,"resources":52},"01M7A6V5W74790WK8VDZX2P3JB","monte-carlo-asset-health",null,"Check the health of a data table\u002Fasset using Monte Carlo. Activates on \"how is table X\", \"check health of X\", \"is X healthy\", \"status of X\", \"check on X table\", or any health\u002Fstatus question about a data asset.","MHassan0000\u002FSkills","MHassan0000","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F224296448?v=4","01M7A14DTC1EZCRN04582533RD","Muhammad Hassan Yousaf","01M7A14DV10KTW8NHQTJPD08X0",1,"Apache-2.0","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fmonte-carlo-asset-health\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: monte-carlo-asset-health\ndescription: Check the health of a data table\u002Fasset using Monte Carlo. Activates on \"how is table X\", \"check health of X\", \"is X healthy\", \"status of X\", \"check on X table\", or any health\u002Fstatus question about a data asset.\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\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## 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","# 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## 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":24,"source":25,"license":15,"date_added":26,"description":7,"source_repo":27,"source_type":28,"license_source":29},"critical","https:\u002F\u002Fgithub.com\u002Fmonte-carlo-data\u002Fmc-agent-toolkit\u002Ftree\u002Fmain\u002Fskills\u002Fasset-health",1782864000000,"monte-carlo-data\u002Fmc-agent-toolkit","community","https:\u002F\u002Fgithub.com\u002Fmonte-carlo-data\u002Fmc-agent-toolkit\u002Fblob\u002Fmain\u002FLICENSE","main","a4404a75dc81d6b7e58c5906b6aaffbcb5e84747","Claude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fmonte-carlo-asset-health",0,"https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills","https:\u002F\u002Fgithub.com\u002FMHassan0000","https:\u002F\u002Fhassanyousaf.vercel.app","Full Stack Developer building web apps, SaaS, AI systems, and automations. Passionate about clean code, UI\u002FUX, backend systems, and turning ideas into products.","2026-08-07 20:42:05",{"source":8,"skillName":5,"commands":40,"prompt":50,"zipAvailable":51},[41,44,47],{"tool":42,"command":43},"npx","npx skills add MHassan0000\u002FSkills --skill monte-carlo-asset-health",{"tool":45,"command":46},"bunx","bunx skills add MHassan0000\u002FSkills --skill monte-carlo-asset-health",{"tool":48,"command":49},"pnpm","pnpm dlx skills add MHassan0000\u002FSkills --skill monte-carlo-asset-health","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fantigravity skills\u002Fagentic-awesome-skills\u002Fskills\u002Fmonte-carlo-asset-health\u002FSKILL.md",true,[],[54,62,69,76,84,92],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":58,"licenseFileUrl":6,"sourceHtmlUrl":59,"categories":60,"keywords":61,"publishedAt":19},"01M7AGBX58S04DX8DKKME8N311","vercel-react-best-practices","React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React\u002FNext.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.","MIT","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fvercel-react-best-practices\u002FSKILL.md",[],[],{"skillNo":63,"name":64,"nameZh":6,"description":65,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":58,"licenseFileUrl":6,"sourceHtmlUrl":66,"categories":67,"keywords":68,"publishedAt":19},"01M7AGBREE890608Z7YDMAKH27","stop-slop","Remove AI writing patterns from prose. Use when drafting, editing, or reviewing text to eliminate predictable AI tells and produce more human-like writing.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fstop-slop\u002FSKILL.md",[],[],{"skillNo":70,"name":71,"nameZh":6,"description":72,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":58,"licenseFileUrl":6,"sourceHtmlUrl":73,"categories":74,"keywords":75,"publishedAt":19},"01M7AGAS972A2AN7Q5EW8HEAXK","ogilvy-copywriting","Apply David Ogilvy's advertising principles when writing or reviewing copy, headlines, product descriptions, landing pages, ads, emails, or any persuasive text. Use when the goal is copy that sells, not copy that wins awards. Covers positioning, headlines, promises, brand voice, long-form copy, and visual logic. Source: How to Create Advertising That Sells (1972) + Ogilvy on Advertising.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Fogilvy\u002FSKILL.md",[],[],{"skillNo":77,"name":78,"nameZh":6,"description":79,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":80,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M7AGAF12803G5JPVMK79AYJB","frontend-design","Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML\u002FCSS layouts, or when styling\u002Fbeautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fskills boraztunc github\u002Ffrontend-design\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M7AG88WWVWCGJY9WA9CH7EY4","webapp-testing","Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fwebapp-testing\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7AG7ZTNV7XQCWDQ9674FBYB","web-artifacts-builder","Suite of tools for creating elaborate, multi-component claude.ai HTML artifacts using modern frontend web technologies (React, Tailwind CSS, shadcn\u002Fui). Use for complex artifacts requiring state management, routing, or shadcn\u002Fui components - not for simple single-file HTML\u002FJSX artifacts.","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FMHassan0000\u002FSkills\u002Fblob\u002Fmain\u002FClaude\u002Fobra superpower skills\u002Fweb-artifacts-builder\u002FSKILL.md",[],[]]