[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6XC6TCMDFBNP2367EYR21MW":3,"skill-same:01M6XC6TCMDFBNP2367EYR21MW":74},{"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":48,"commitSha":49,"skillDirectory":50,"forksCount":13,"repositoryHtmlUrl":51,"repositoryHomepageUrl":6,"ownerHtmlUrl":52,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":53,"install":54,"resources":67},"01M6XC6TCMDFBNP2367EYR21MW","data-service-circuit-breaker-aware",null,"Create data fetching services with circuit breaker pattern for API resilience. Services handle fetch, cache, retry, and expose typed data to panel components. Includes clear guidance on when to skip the circuit breaker for user-triggered one-shot calls versus background auto-polling services.","UF-gzj\u002Fopenspace-claude-evolution","UF-gzj","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F272393507?v=4","01M6XBCZB755P01VVYGQWPYZY3","01M6XBCZFJA5AREA17WGETA3FW",0,"MIT","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fdata-service-circuit-breaker-aware\u002FSKILL.md",[17],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",[23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42],"data service","data service circuit breaker aware","data","circuit","Circuit Breaker","service","panel","when","data fetching","for","calls","retry","with","components","auto","fetch","api","cache","create","resilience","2026-11-10 10:12:30",false,"---\nname: data-service-circuit-breaker-aware\ndescription: Create data fetching services with circuit breaker pattern for API resilience. Services handle fetch, cache, retry, and expose typed data to panel components. Includes clear guidance on when to skip the circuit breaker for user-triggered one-shot calls versus background auto-polling services.\n---\n\n# Data Service Pattern\n\nEach panel's data comes from a dedicated **service module** in `src\u002Fservices\u002F`. Services handle API calls, caching, error handling with circuit breaker pattern.\n\n## Circuit Breaker\n\nThe circuit breaker prevents cascading failures when an API is down. After N consecutive failures, it enters \"cooldown\" mode and serves cached data instead of hitting the API.\n\nCreate `src\u002Futils\u002Fcircuit-breaker.ts`:\n\n```typescript\ninterface CircuitState {\n  failures: number;\n  cooldownUntil: number;\n}\n\ninterface CacheEntry\u003CT> {\n  data: T;\n  timestamp: number;\n}\n\nexport interface CircuitBreakerOptions {\n  name: string;\n  maxFailures?: number;\n  cooldownMs?: number;\n  cacheTtlMs?: number;\n}\n\nexport class CircuitBreaker\u003CT> {\n  private state: CircuitState = { failures: 0, cooldownUntil: 0 };\n  private cache: CacheEntry\u003CT> | null = null;\n  private name: string;\n  private maxFailures: number;\n  private cooldownMs: number;\n  private cacheTtlMs: number;\n\n  constructor(options: CircuitBreakerOptions) {\n    this.name = options.name;\n    this.maxFailures = options.maxFailures ?? 2;\n    this.cooldownMs = options.cooldownMs ?? 5 * 60 * 1000;  \u002F\u002F 5 minutes\n    this.cacheTtlMs = options.cacheTtlMs ?? 10 * 60 * 1000; \u002F\u002F 10 minutes\n  }\n\n  isOnCooldown(): boolean {\n    if (Date.now() \u003C this.state.cooldownUntil) return true;\n    if (this.state.cooldownUntil > 0) {\n      this.state = { failures: 0, cooldownUntil: 0 };\n    }\n    return false;\n  }\n\n  getCached(): T | null {\n    if (this.cache && Date.now() - this.cache.timestamp \u003C this.cacheTtlMs) {\n      return this.cache.data;\n    }\n    return null;\n  }\n\n  recordSuccess(data: T): void {\n    this.state = { failures: 0, cooldownUntil: 0 };\n    this.cache = { data, timestamp: Date.now() };\n  }\n\n  recordFailure(error?: string): void {\n    this.state.failures++;\n    if (this.state.failures >= this.maxFailures) {\n      this.state.cooldownUntil = Date.now() + this.cooldownMs;\n      console.warn(`[${this.name}] Cooldown for ${this.cooldownMs \u002F 1000}s`);\n    }\n  }\n\n  async execute\u003CR extends T>(fn: () => Promise\u003CR>, defaultValue: R): Promise\u003CR> {\n    if (this.isOnCooldown()) {\n      const cached = this.getCached();\n      return (cached as R) ?? defaultValue;\n    }\n    const cached = this.getCached();\n    if (cached !== null) return cached as R;\n    try {\n      const result = await fn();\n      this.recordSuccess(result);\n      return result;\n    } catch (e) {\n      console.error(`[${this.name}] Failed:`, e);\n      this.recordFailure(String(e));\n      return defaultValue;\n    }\n  }\n}\n\nexport function createCircuitBreaker\u003CT>(options: CircuitBreakerOptions): CircuitBreaker\u003CT> {\n  return new CircuitBreaker\u003CT>(options);\n}\n```\n\n## Service Module Pattern\n\nEach service is a TypeScript module that exports async data-fetching functions:\n\n```typescript\n\u002F\u002F src\u002Fservices\u002Fstock-market.ts\nimport { createCircuitBreaker } from '..\u002Futils\u002Fcircuit-breaker';\n\nexport interface StockQuote {\n  symbol: string;\n  name: string;\n  price: number | null;\n  change: number | null;\n  sparkline?: number[];\n}\n\nconst breaker = createCircuitBreaker\u003CStockQuote[]>({\n  name: 'StockMarket',\n  cacheTtlMs: 60_000, \u002F\u002F 1 minute cache\n});\n\nexport async function fetchStockQuotes(symbols: string[]): Promise\u003CStockQuote[]> {\n  return breaker.execute(async () => {\n    const params = new URLSearchParams({ symbols: symbols.join(',') });\n    const resp = await fetch(`\u002Fapi\u002Fstocks?${params}`);\n    if (!resp.ok) throw new Error(`HTTP ${resp.status}`);\n    return resp.json();\n  }, []);\n}\n```\n\n## Key Patterns\n\n1. **One circuit breaker per API endpoint** — create at module level\n2. **Export typed interfaces** for data shapes\n3. **Wrap fetch calls** in `breaker.execute(fn, defaultValue)`\n4. **Default values** are empty arrays `[]` or empty objects `{}`\n5. **Services are stateless modules** — no class instances, just exported functions\n6. **API proxy**: Frontend calls `\u002Fapi\u002F...` which proxies to external APIs (hides API keys)\n\n## When to Skip the Circuit Breaker\n\nThe circuit breaker is designed to protect **background auto-polling services** from cascading failures. It is **not always appropriate** — applying it blindly adds unnecessary complexity and can actively cause problems for user-driven flows.\n\n### Use the circuit breaker when:\n- The service is **polled automatically** on an interval (e.g., every 30 seconds, every minute)\n- Repeated failures would hammer a degraded API endpoint\n- Serving stale cached data is an acceptable fallback (the user won't notice a brief outage)\n- The data refreshes in the background without explicit user intent\n\n```typescript\n\u002F\u002F ✅ Background polling — circuit breaker appropriate\nconst breaker = createCircuitBreaker\u003CStockQuote[]>({ name: 'StockMarket', cacheTtlMs: 60_000 });\n\nexport async function fetchStockQuotes(symbols: string[]): Promise\u003CStockQuote[]> {\n  return breaker.execute(async () => {\n    const resp = await fetch(`\u002Fapi\u002Fstocks?symbols=${symbols.join(',')}`);\n    if (!resp.ok) throw new Error(`HTTP ${resp.status}`);\n    return resp.json();\n  }, []);\n}\n\n\u002F\u002F Called on a timer — circuit breaker protects against rapid failure storms\nsetInterval(() => fetchStockQuotes(['AAPL', 'MSFT']), 60_000);\n```\n\n### Skip the circuit breaker when:\n- The call is **user-triggered** (button click, explicit refresh, form submit)\n- The operation is **one-shot** and non-repeating (e.g., LLM text generation, send message)\n- Failure should surface immediately to the user as an error — not silently return stale data\n- The user expects a **fresh result**, not a cache hit\n- Retry\u002Ferror handling is managed by the UI layer (e.g., a \"Try again\" button)\n\n```typescript\n\u002F\u002F ✅ User-triggered one-shot LLM call — NO circuit breaker\nexport interface DailyBriefingData {\n  briefing: string;\n  generatedAt: string;\n}\n\nexport async function generateDailyBriefing(context: string): Promise\u003CDailyBriefingData> {\n  \u002F\u002F No circuit breaker: this is explicitly triggered by the user clicking \"Generate\".\n  \u002F\u002F Failures should throw so the UI can show an error and offer a retry button.\n  const resp = await fetch('\u002Fapi\u002Fllm\u002Fgenerate', {\n    method: 'POST',\n    headers: { 'Content-Type': 'application\u002Fjson' },\n    body: JSON.stringify({ prompt: context }),\n  });\n  if (!resp.ok) throw new Error(`LLM generation failed: HTTP ${resp.status}`);\n  const { text } = await resp.json();\n  return { briefing: text, generatedAt: new Date().toISOString() };\n}\n```\n\n### Decision table\n\n| Trigger              | Repeats automatically? | Stale data OK? | Use circuit breaker? |\n|----------------------|------------------------|----------------|----------------------|\n| Timer \u002F interval     | ✅ Yes                 | ✅ Yes         | ✅ Yes               |\n| App startup fetch    | ❌ No                  | ✅ Yes         | Optional             |\n| Button \u002F user action | ❌ No                  | ❌ No          | ❌ No                |\n| LLM generation       | ❌ No                  | ❌ No          | ❌ No                |\n| Explicit refresh     | ❌ No                  | ❌ No          | ❌ No                |\n\n### UI error handling for one-shot calls\n\nWhen skipping the circuit breaker, the calling component is responsible for surfacing errors:\n\n```typescript\n\u002F\u002F In the panel\u002Fcomponent that calls a one-shot service:\nasync generate(): Promise\u003Cvoid> {\n  if (this.isFetching) return;\n  this.isFetching = true;\n  this.showLoading();\n  try {\n    const data = await generateDailyBriefing(this.buildContext());\n    this.render(data);\n  } catch (e) {\n    \u002F\u002F Surface the error directly — no silent cache fallback\n    this.showError('Generation failed. Please try again.', () => this.generate());\n  } finally {\n    this.isFetching = false;\n  }\n}\n```\n\n> **Rule of thumb**: If a human is waiting for the result of a specific action they just took, skip the circuit breaker and let errors propagate to the UI. If a machine is polling in the background, use the circuit breaker.\n\n## API Proxy Pattern\n\nFor APIs requiring keys, create server-side proxy endpoints:\n\n```typescript\n\u002F\u002F api\u002Fstocks.ts (Vercel serverless function)\nexport default async function handler(req, res) {\n  const { symbols } = req.query;\n  const apiKey = process.env.FINNHUB_API_KEY;\n  const data = await fetch(`https:\u002F\u002Ffinnhub.io\u002Fapi\u002Fv1\u002Fquote?symbol=${symbols}&token=${apiKey}`);\n  res.json(await data.json());\n}\n```\n\nThis keeps API keys server-side and provides a single endpoint for the frontend.\n","# Data Service Pattern\n\nEach panel's data comes from a dedicated **service module** in `src\u002Fservices\u002F`. Services handle API calls, caching, error handling with circuit breaker pattern.\n\n## Circuit Breaker\n\nThe circuit breaker prevents cascading failures when an API is down. After N consecutive failures, it enters \"cooldown\" mode and serves cached data instead of hitting the API.\n\nCreate `src\u002Futils\u002Fcircuit-breaker.ts`:\n\n```typescript\ninterface CircuitState {\n  failures: number;\n  cooldownUntil: number;\n}\n\ninterface CacheEntry\u003CT> {\n  data: T;\n  timestamp: number;\n}\n\nexport interface CircuitBreakerOptions {\n  name: string;\n  maxFailures?: number;\n  cooldownMs?: number;\n  cacheTtlMs?: number;\n}\n\nexport class CircuitBreaker\u003CT> {\n  private state: CircuitState = { failures: 0, cooldownUntil: 0 };\n  private cache: CacheEntry\u003CT> | null = null;\n  private name: string;\n  private maxFailures: number;\n  private cooldownMs: number;\n  private cacheTtlMs: number;\n\n  constructor(options: CircuitBreakerOptions) {\n    this.name = options.name;\n    this.maxFailures = options.maxFailures ?? 2;\n    this.cooldownMs = options.cooldownMs ?? 5 * 60 * 1000;  \u002F\u002F 5 minutes\n    this.cacheTtlMs = options.cacheTtlMs ?? 10 * 60 * 1000; \u002F\u002F 10 minutes\n  }\n\n  isOnCooldown(): boolean {\n    if (Date.now() \u003C this.state.cooldownUntil) return true;\n    if (this.state.cooldownUntil > 0) {\n      this.state = { failures: 0, cooldownUntil: 0 };\n    }\n    return false;\n  }\n\n  getCached(): T | null {\n    if (this.cache && Date.now() - this.cache.timestamp \u003C this.cacheTtlMs) {\n      return this.cache.data;\n    }\n    return null;\n  }\n\n  recordSuccess(data: T): void {\n    this.state = { failures: 0, cooldownUntil: 0 };\n    this.cache = { data, timestamp: Date.now() };\n  }\n\n  recordFailure(error?: string): void {\n    this.state.failures++;\n    if (this.state.failures >= this.maxFailures) {\n      this.state.cooldownUntil = Date.now() + this.cooldownMs;\n      console.warn(`[${this.name}] Cooldown for ${this.cooldownMs \u002F 1000}s`);\n    }\n  }\n\n  async execute\u003CR extends T>(fn: () => Promise\u003CR>, defaultValue: R): Promise\u003CR> {\n    if (this.isOnCooldown()) {\n      const cached = this.getCached();\n      return (cached as R) ?? defaultValue;\n    }\n    const cached = this.getCached();\n    if (cached !== null) return cached as R;\n    try {\n      const result = await fn();\n      this.recordSuccess(result);\n      return result;\n    } catch (e) {\n      console.error(`[${this.name}] Failed:`, e);\n      this.recordFailure(String(e));\n      return defaultValue;\n    }\n  }\n}\n\nexport function createCircuitBreaker\u003CT>(options: CircuitBreakerOptions): CircuitBreaker\u003CT> {\n  return new CircuitBreaker\u003CT>(options);\n}\n```\n\n## Service Module Pattern\n\nEach service is a TypeScript module that exports async data-fetching functions:\n\n```typescript\n\u002F\u002F src\u002Fservices\u002Fstock-market.ts\nimport { createCircuitBreaker } from '..\u002Futils\u002Fcircuit-breaker';\n\nexport interface StockQuote {\n  symbol: string;\n  name: string;\n  price: number | null;\n  change: number | null;\n  sparkline?: number[];\n}\n\nconst breaker = createCircuitBreaker\u003CStockQuote[]>({\n  name: 'StockMarket',\n  cacheTtlMs: 60_000, \u002F\u002F 1 minute cache\n});\n\nexport async function fetchStockQuotes(symbols: string[]): Promise\u003CStockQuote[]> {\n  return breaker.execute(async () => {\n    const params = new URLSearchParams({ symbols: symbols.join(',') });\n    const resp = await fetch(`\u002Fapi\u002Fstocks?${params}`);\n    if (!resp.ok) throw new Error(`HTTP ${resp.status}`);\n    return resp.json();\n  }, []);\n}\n```\n\n## Key Patterns\n\n1. **One circuit breaker per API endpoint** — create at module level\n2. **Export typed interfaces** for data shapes\n3. **Wrap fetch calls** in `breaker.execute(fn, defaultValue)`\n4. **Default values** are empty arrays `[]` or empty objects `{}`\n5. **Services are stateless modules** — no class instances, just exported functions\n6. **API proxy**: Frontend calls `\u002Fapi\u002F...` which proxies to external APIs (hides API keys)\n\n## When to Skip the Circuit Breaker\n\nThe circuit breaker is designed to protect **background auto-polling services** from cascading failures. It is **not always appropriate** — applying it blindly adds unnecessary complexity and can actively cause problems for user-driven flows.\n\n### Use the circuit breaker when:\n- The service is **polled automatically** on an interval (e.g., every 30 seconds, every minute)\n- Repeated failures would hammer a degraded API endpoint\n- Serving stale cached data is an acceptable fallback (the user won't notice a brief outage)\n- The data refreshes in the background without explicit user intent\n\n```typescript\n\u002F\u002F ✅ Background polling — circuit breaker appropriate\nconst breaker = createCircuitBreaker\u003CStockQuote[]>({ name: 'StockMarket', cacheTtlMs: 60_000 });\n\nexport async function fetchStockQuotes(symbols: string[]): Promise\u003CStockQuote[]> {\n  return breaker.execute(async () => {\n    const resp = await fetch(`\u002Fapi\u002Fstocks?symbols=${symbols.join(',')}`);\n    if (!resp.ok) throw new Error(`HTTP ${resp.status}`);\n    return resp.json();\n  }, []);\n}\n\n\u002F\u002F Called on a timer — circuit breaker protects against rapid failure storms\nsetInterval(() => fetchStockQuotes(['AAPL', 'MSFT']), 60_000);\n```\n\n### Skip the circuit breaker when:\n- The call is **user-triggered** (button click, explicit refresh, form submit)\n- The operation is **one-shot** and non-repeating (e.g., LLM text generation, send message)\n- Failure should surface immediately to the user as an error — not silently return stale data\n- The user expects a **fresh result**, not a cache hit\n- Retry\u002Ferror handling is managed by the UI layer (e.g., a \"Try again\" button)\n\n```typescript\n\u002F\u002F ✅ User-triggered one-shot LLM call — NO circuit breaker\nexport interface DailyBriefingData {\n  briefing: string;\n  generatedAt: string;\n}\n\nexport async function generateDailyBriefing(context: string): Promise\u003CDailyBriefingData> {\n  \u002F\u002F No circuit breaker: this is explicitly triggered by the user clicking \"Generate\".\n  \u002F\u002F Failures should throw so the UI can show an error and offer a retry button.\n  const resp = await fetch('\u002Fapi\u002Fllm\u002Fgenerate', {\n    method: 'POST',\n    headers: { 'Content-Type': 'application\u002Fjson' },\n    body: JSON.stringify({ prompt: context }),\n  });\n  if (!resp.ok) throw new Error(`LLM generation failed: HTTP ${resp.status}`);\n  const { text } = await resp.json();\n  return { briefing: text, generatedAt: new Date().toISOString() };\n}\n```\n\n### Decision table\n\n| Trigger              | Repeats automatically? | Stale data OK? | Use circuit breaker? |\n|----------------------|------------------------|----------------|----------------------|\n| Timer \u002F interval     | ✅ Yes                 | ✅ Yes         | ✅ Yes               |\n| App startup fetch    | ❌ No                  | ✅ Yes         | Optional             |\n| Button \u002F user action | ❌ No                  | ❌ No          | ❌ No                |\n| LLM generation       | ❌ No                  | ❌ No          | ❌ No                |\n| Explicit refresh     | ❌ No                  | ❌ No          | ❌ No                |\n\n### UI error handling for one-shot calls\n\nWhen skipping the circuit breaker, the calling component is responsible for surfacing errors:\n\n```typescript\n\u002F\u002F In the panel\u002Fcomponent that calls a one-shot service:\nasync generate(): Promise\u003Cvoid> {\n  if (this.isFetching) return;\n  this.isFetching = true;\n  this.showLoading();\n  try {\n    const data = await generateDailyBriefing(this.buildContext());\n    this.render(data);\n  } catch (e) {\n    \u002F\u002F Surface the error directly — no silent cache fallback\n    this.showError('Generation failed. Please try again.', () => this.generate());\n  } finally {\n    this.isFetching = false;\n  }\n}\n```\n\n> **Rule of thumb**: If a human is waiting for the result of a specific action they just took, skip the circuit breaker and let errors propagate to the UI. If a machine is polling in the background, use the circuit breaker.\n\n## API Proxy Pattern\n\nFor APIs requiring keys, create server-side proxy endpoints:\n\n```typescript\n\u002F\u002F api\u002Fstocks.ts (Vercel serverless function)\nexport default async function handler(req, res) {\n  const { symbols } = req.query;\n  const apiKey = process.env.FINNHUB_API_KEY;\n  const data = await fetch(`https:\u002F\u002Ffinnhub.io\u002Fapi\u002Fv1\u002Fquote?symbol=${symbols}&token=${apiKey}`);\n  res.json(await data.json());\n}\n```\n\nThis keeps API keys server-side and provides a single endpoint for the frontend.\n",{"name":5,"description":7},"main","0650921d63895de3997bc81f1ff1d0ac67032072","showcase\u002Fskills\u002Fdata-service-circuit-breaker-aware","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution","https:\u002F\u002Fgithub.com\u002FUF-gzj","2026-04-16 09:31:03",{"source":8,"skillName":5,"commands":55,"prompt":65,"zipAvailable":66},[56,59,62],{"tool":57,"command":58},"npx","npx skills add UF-gzj\u002Fopenspace-claude-evolution --skill data-service-circuit-breaker-aware",{"tool":60,"command":61},"bunx","bunx skills add UF-gzj\u002Fopenspace-claude-evolution --skill data-service-circuit-breaker-aware",{"tool":63,"command":64},"pnpm","pnpm dlx skills add UF-gzj\u002Fopenspace-claude-evolution --skill data-service-circuit-breaker-aware","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fdata-service-circuit-breaker-aware\u002FSKILL.md",true,[68],{"path":69,"resourceType":70,"resourceTypeDesc":71,"sizeBytes":72,"sourceHtmlUrl":73},".skill_id","OTHER","其他",42,"https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fdata-service-circuit-breaker-aware\u002F.skill_id",[75,99,115,124,147,163],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":43},"01M6XCCXD3NCM2YKR3WNGBASPC","write-special-chars-ts-check","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, plus a reliable TypeScript type-checking step that filters output to only the newly-written files to avoid being misled by pre-existing errors.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-ts-check\u002FSKILL.md",[],[82,83,84,85,86,87,88,89,32,90,91,92,93,94,95,96,97,98],"check","write","write special chars ts check","typescript","filters","characters","Existing","type-checking","errors","script","output","type","files","only","template","file","python",{"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":14,"licenseFileUrl":6,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":43},"01M6XCCT7E3J922Q345PBGSHPN","write-special-chars-readback","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) using a Python heredoc script, with mandatory post-write verification via read_file and cleanup of \u002Ftmp helper scripts.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-readback\u002FSKILL.md",[],[106,107,83,97,108,98,109,110,111,112,113,96,114,35,87,32,91],"readback","write special chars readback","helper","post","via","scripts","cleanup","read","verification",{"skillNo":116,"name":117,"nameZh":6,"description":118,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":119,"categories":120,"keywords":121,"publishedAt":43},"01M6XCCMQX1R8B6FECWB3P63T7","write-special-chars-heredoc","Workaround for write_file failures caused by special characters (apostrophes, backticks, template literals) by using a Python heredoc script executed via shell.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fwrite-special-chars-heredoc\u002FSKILL.md",[],[122,83,87,123,91,110,96,97,98,32],"write special chars heredoc","shell",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":131,"publishedAt":43},"01M6XCCG41M994JJEX6VN52PEP","worldmonitor-reference","Curated architecture index of the WorldMonitor open-source dashboard. Reference for extracting patterns — vanilla TypeScript, Panel class hierarchy, service layer, CSS grid, API edge functions, refresh scheduler, and 60+ data source integrations.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fworldmonitor-reference\u002FSKILL.md",[130],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},[132,133,134,135,136,85,137,138,139,140,141,32,142,29,143,144,145,146,39,25],"reference","worldmonitor","worldmonitor reference","architecture","dashboard","css","scheduler","layer","hierarchy","source","extracting","patterns","edge functions","integrations","open",{"skillNo":148,"name":149,"nameZh":6,"description":150,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":151,"categories":152,"keywords":153,"publishedAt":43},"01M6XCCCHWNKG2W4VH9E6A10HF","virtual-list","Implement efficient virtual scrolling for rendering large lists with DOM recycling, chunk-based rendering, and performance optimizations","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fvirtual-list\u002FSKILL.md",[],[154,155,156,157,32,158,35,159,160,161,162],"virtual list","list","virtual","chunk","dom","rendering","recycling","implement","performance",{"skillNo":164,"name":165,"nameZh":6,"description":166,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":167,"categories":168,"keywords":169,"publishedAt":43},"01M6XCC7X8PKMR2DEW91XGHYSV","verify-directory-structure","Diagnose and resolve file access issues by first verifying the directory structure.","https:\u002F\u002Fgithub.com\u002FUF-gzj\u002Fopenspace-claude-evolution\u002Fblob\u002Fmain\u002Fshowcase\u002Fskills\u002Fverify-directory-structure\u002FSKILL.md",[],[170,171,172,173,174,175,97,176,177,178],"directory","verify directory structure","structure","verify","access","first","issues","diagnose","file access"]