[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7BRBNNWK2JC6BW5ZGSQZNHS":3,"skill-same:01M7BRBNNWK2JC6BW5ZGSQZNHS":66},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":19,"publishedAt":20,"linkOnly":21,"markdownContent":22,"markdownBody":23,"frontMatter":24,"refName":25,"commitSha":26,"skillDirectory":5,"forksCount":14,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7BRBNNWK2JC6BW5ZGSQZNHS","netlify-functions",null,"Guide for writing Netlify serverless functions. Use when creating API endpoints, background processing, scheduled tasks, or any server-side logic using Netlify Functions. Covers modern syntax (default export + Config), TypeScript, path routing, background functions, scheduled functions, streaming, and method routing.","hikmet4434\u002Fclaude-skills","hikmet4434","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F301146035?v=4","01M7BNXPE7A92JBFSZV3GXVQA4","hikmet tanriverdi","01M7BNXPEXW1JAJ271VVPSK87C",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhikmet4434\u002Fclaude-skills\u002Fblob\u002Fmaster\u002Fnetlify-functions\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fhikmet4434\u002Fclaude-skills\u002Fblob\u002Fmaster\u002Fnetlify-functions\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: netlify-functions\ndescription: Guide for writing Netlify serverless functions. Use when creating API endpoints, background processing, scheduled tasks, or any server-side logic using Netlify Functions. Covers modern syntax (default export + Config), TypeScript, path routing, background functions, scheduled functions, streaming, and method routing.\n---\n\n# Netlify Functions\n\n## Modern Syntax\n\nAlways use the modern default export + Config pattern. Never use the legacy `exports.handler` or named `handler` export.\n\n```typescript\nimport type { Context, Config } from \"@netlify\u002Ffunctions\";\n\nexport default async (req: Request, context: Context) => {\n  return new Response(\"Hello, world!\");\n};\n\nexport const config: Config = {\n  path: \"\u002Fapi\u002Fhello\",\n};\n```\n\nThe handler receives a standard Web API `Request` and returns a `Response`. The second argument is a Netlify `Context` object.\n\n## File Structure\n\nPlace functions in `netlify\u002Ffunctions\u002F`:\n\n```\nnetlify\u002Ffunctions\u002F\n  _shared\u002F           # Non-function shared code (underscore prefix)\n    auth.ts\n    db.ts\n  items.ts           # -> \u002F.netlify\u002Ffunctions\u002Fitems (or custom path via config)\n  users\u002Findex.ts     # -> \u002F.netlify\u002Ffunctions\u002Fusers\n```\n\nUse `.ts` or `.mts` extensions. If both `.ts` and `.js` exist with the same name, the `.js` file takes precedence.\n\n## Path Routing\n\nDefine custom paths via the `config` export:\n\n```typescript\nexport const config: Config = {\n  path: \"\u002Fapi\u002Fitems\",                    \u002F\u002F Static path\n  \u002F\u002F path: \"\u002Fapi\u002Fitems\u002F:id\",            \u002F\u002F Path parameter\n  \u002F\u002F path: [\"\u002Fapi\u002Fitems\", \"\u002Fapi\u002Fitems\u002F:id\"], \u002F\u002F Multiple paths\n  \u002F\u002F excludedPath: \"\u002Fapi\u002Fitems\u002Fspecial\", \u002F\u002F Excluded paths\n  \u002F\u002F preferStatic: true,                \u002F\u002F Don't override static files\n};\n```\n\nWithout a `path` config, functions are available at `\u002F.netlify\u002Ffunctions\u002F{name}`. Setting a `path` makes the function available **only** at that path.\n\nAccess path parameters via `context.params`:\n\n```typescript\n\u002F\u002F config: { path: \"\u002Fapi\u002Fitems\u002F:id\" }\nexport default async (req: Request, context: Context) => {\n  const { id } = context.params;\n  \u002F\u002F ...\n};\n```\n\n## Method Routing\n\n```typescript\nexport default async (req: Request, context: Context) => {\n  switch (req.method) {\n    case \"GET\":    return handleGet(context.params.id);\n    case \"POST\":   return handlePost(await req.json());\n    case \"DELETE\": return handleDelete(context.params.id);\n    default:       return new Response(\"Method not allowed\", { status: 405 });\n  }\n};\n\nexport const config: Config = {\n  path: \"\u002Fapi\u002Fitems\u002F:id\",\n  method: [\"GET\", \"POST\", \"DELETE\"],\n};\n```\n\n## Background Functions\n\nFor long-running tasks (up to 15 minutes). The client receives an immediate `202` response; return values are ignored.\n\nName the file with a `-background` suffix:\n\n```\nnetlify\u002Ffunctions\u002Fprocess-background.ts\n```\n\nStore results externally (Netlify Blobs, database) for later retrieval.\n\n## Scheduled Functions\n\nRun on a cron schedule (UTC timezone):\n\n```typescript\nexport default async (req: Request) => {\n  const { next_run } = await req.json();\n  console.log(\"Next invocation at:\", next_run);\n};\n\nexport const config: Config = {\n  schedule: \"@hourly\", \u002F\u002F or cron: \"0 * * * *\"\n};\n```\n\nShortcuts: `@yearly`, `@monthly`, `@weekly`, `@daily`, `@hourly`. Scheduled functions have a **30-second timeout** and only run on published deploys.\n\n## Streaming Responses\n\nReturn a `ReadableStream` body for streamed responses (up to 20 MB):\n\n```typescript\nexport default async (req: Request) => {\n  const stream = new ReadableStream({ \u002F* ... *\u002F });\n  return new Response(stream, {\n    headers: { \"Content-Type\": \"text\u002Fevent-stream\" },\n  });\n};\n```\n\n## Context Object\n\n| Property | Description |\n|---|---|\n| `context.params` | Path parameters from config |\n| `context.geo` | `{ city, country: {code, name}, latitude, longitude, subdivision, timezone, postalCode }` |\n| `context.ip` | Client IP address |\n| `context.cookies` | `.get()`, `.set()`, `.delete()` |\n| `context.deploy` | `{ context, id, published }` |\n| `context.site` | `{ id, name, url }` |\n| `context.account.id` | Team account ID |\n| `context.requestId` | Unique request ID |\n| `context.waitUntil(promise)` | Extend execution after response is sent |\n\n## Environment Variables\n\nUse `Netlify.env` (not `process.env`) inside functions:\n\n```typescript\nconst apiKey = Netlify.env.get(\"API_KEY\");\n```\n\n## Resource Limits\n\n| Resource | Limit |\n|---|---|\n| Synchronous timeout | 60 seconds |\n| Background timeout | 15 minutes |\n| Scheduled timeout | 30 seconds |\n| Memory | 1024 MB |\n| Buffered payload | 6 MB |\n| Streamed payload | 20 MB |\n\n## Framework Considerations\n\nFrameworks with server-side capabilities (Astro, Next.js, Nuxt, SvelteKit, TanStack Start) typically generate their own serverless functions via adapters. You usually do not write raw Netlify Functions in these projects — the framework adapter handles server-side rendering and API routes. Write Netlify Functions directly when:\n\n- Using a client-side-only framework (Vite + React SPA, vanilla JS)\n- Adding background or scheduled tasks to any project\n- Building standalone API endpoints outside the framework's routing\n\nSee the **netlify-frameworks** skill for adapter setup.\n","# Netlify Functions\n\n## Modern Syntax\n\nAlways use the modern default export + Config pattern. Never use the legacy `exports.handler` or named `handler` export.\n\n```typescript\nimport type { Context, Config } from \"@netlify\u002Ffunctions\";\n\nexport default async (req: Request, context: Context) => {\n  return new Response(\"Hello, world!\");\n};\n\nexport const config: Config = {\n  path: \"\u002Fapi\u002Fhello\",\n};\n```\n\nThe handler receives a standard Web API `Request` and returns a `Response`. The second argument is a Netlify `Context` object.\n\n## File Structure\n\nPlace functions in `netlify\u002Ffunctions\u002F`:\n\n```\nnetlify\u002Ffunctions\u002F\n  _shared\u002F           # Non-function shared code (underscore prefix)\n    auth.ts\n    db.ts\n  items.ts           # -> \u002F.netlify\u002Ffunctions\u002Fitems (or custom path via config)\n  users\u002Findex.ts     # -> \u002F.netlify\u002Ffunctions\u002Fusers\n```\n\nUse `.ts` or `.mts` extensions. If both `.ts` and `.js` exist with the same name, the `.js` file takes precedence.\n\n## Path Routing\n\nDefine custom paths via the `config` export:\n\n```typescript\nexport const config: Config = {\n  path: \"\u002Fapi\u002Fitems\",                    \u002F\u002F Static path\n  \u002F\u002F path: \"\u002Fapi\u002Fitems\u002F:id\",            \u002F\u002F Path parameter\n  \u002F\u002F path: [\"\u002Fapi\u002Fitems\", \"\u002Fapi\u002Fitems\u002F:id\"], \u002F\u002F Multiple paths\n  \u002F\u002F excludedPath: \"\u002Fapi\u002Fitems\u002Fspecial\", \u002F\u002F Excluded paths\n  \u002F\u002F preferStatic: true,                \u002F\u002F Don't override static files\n};\n```\n\nWithout a `path` config, functions are available at `\u002F.netlify\u002Ffunctions\u002F{name}`. Setting a `path` makes the function available **only** at that path.\n\nAccess path parameters via `context.params`:\n\n```typescript\n\u002F\u002F config: { path: \"\u002Fapi\u002Fitems\u002F:id\" }\nexport default async (req: Request, context: Context) => {\n  const { id } = context.params;\n  \u002F\u002F ...\n};\n```\n\n## Method Routing\n\n```typescript\nexport default async (req: Request, context: Context) => {\n  switch (req.method) {\n    case \"GET\":    return handleGet(context.params.id);\n    case \"POST\":   return handlePost(await req.json());\n    case \"DELETE\": return handleDelete(context.params.id);\n    default:       return new Response(\"Method not allowed\", { status: 405 });\n  }\n};\n\nexport const config: Config = {\n  path: \"\u002Fapi\u002Fitems\u002F:id\",\n  method: [\"GET\", \"POST\", \"DELETE\"],\n};\n```\n\n## Background Functions\n\nFor long-running tasks (up to 15 minutes). The client receives an immediate `202` response; return values are ignored.\n\nName the file with a `-background` suffix:\n\n```\nnetlify\u002Ffunctions\u002Fprocess-background.ts\n```\n\nStore results externally (Netlify Blobs, database) for later retrieval.\n\n## Scheduled Functions\n\nRun on a cron schedule (UTC timezone):\n\n```typescript\nexport default async (req: Request) => {\n  const { next_run } = await req.json();\n  console.log(\"Next invocation at:\", next_run);\n};\n\nexport const config: Config = {\n  schedule: \"@hourly\", \u002F\u002F or cron: \"0 * * * *\"\n};\n```\n\nShortcuts: `@yearly`, `@monthly`, `@weekly`, `@daily`, `@hourly`. Scheduled functions have a **30-second timeout** and only run on published deploys.\n\n## Streaming Responses\n\nReturn a `ReadableStream` body for streamed responses (up to 20 MB):\n\n```typescript\nexport default async (req: Request) => {\n  const stream = new ReadableStream({ \u002F* ... *\u002F });\n  return new Response(stream, {\n    headers: { \"Content-Type\": \"text\u002Fevent-stream\" },\n  });\n};\n```\n\n## Context Object\n\n| Property | Description |\n|---|---|\n| `context.params` | Path parameters from config |\n| `context.geo` | `{ city, country: {code, name}, latitude, longitude, subdivision, timezone, postalCode }` |\n| `context.ip` | Client IP address |\n| `context.cookies` | `.get()`, `.set()`, `.delete()` |\n| `context.deploy` | `{ context, id, published }` |\n| `context.site` | `{ id, name, url }` |\n| `context.account.id` | Team account ID |\n| `context.requestId` | Unique request ID |\n| `context.waitUntil(promise)` | Extend execution after response is sent |\n\n## Environment Variables\n\nUse `Netlify.env` (not `process.env`) inside functions:\n\n```typescript\nconst apiKey = Netlify.env.get(\"API_KEY\");\n```\n\n## Resource Limits\n\n| Resource | Limit |\n|---|---|\n| Synchronous timeout | 60 seconds |\n| Background timeout | 15 minutes |\n| Scheduled timeout | 30 seconds |\n| Memory | 1024 MB |\n| Buffered payload | 6 MB |\n| Streamed payload | 20 MB |\n\n## Framework Considerations\n\nFrameworks with server-side capabilities (Astro, Next.js, Nuxt, SvelteKit, TanStack Start) typically generate their own serverless functions via adapters. You usually do not write raw Netlify Functions in these projects — the framework adapter handles server-side rendering and API routes. Write Netlify Functions directly when:\n\n- Using a client-side-only framework (Vite + React SPA, vanilla JS)\n- Adding background or scheduled tasks to any project\n- Building standalone API endpoints outside the framework's routing\n\nSee the **netlify-frameworks** skill for adapter setup.\n",{"name":5,"description":7},"master","8f65f9c8da48757c0ec3e7d6483545ecc0167ee1","https:\u002F\u002Fgithub.com\u002Fhikmet4434\u002Fclaude-skills","https:\u002F\u002Fgithub.com\u002Fhikmet4434","thirdhand.com.tr","2026-11-01 23:11:46",{"source":8,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add hikmet4434\u002Fclaude-skills --skill netlify-functions",{"tool":37,"command":38},"bunx","bunx skills add hikmet4434\u002Fclaude-skills --skill netlify-functions",{"tool":40,"command":41},"pnpm","pnpm dlx skills add hikmet4434\u002Fclaude-skills --skill netlify-functions","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhikmet4434\u002Fclaude-skills\u002Fblob\u002Fmaster\u002Fnetlify-functions\u002FSKILL.md",true,[45,51,57,61],{"path":46,"resourceType":47,"resourceTypeDesc":48,"sizeBytes":49,"sourceHtmlUrl":50},"agents\u002Fopenai.yaml","REFERENCE","参考文档",352,"https:\u002F\u002Fgithub.com\u002Fhikmet4434\u002Fclaude-skills\u002Fblob\u002Fmaster\u002Fnetlify-functions\u002Fagents\u002Fopenai.yaml",{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"assets\u002Fnetlify-small.svg","ASSET","资产文件",1291,"https:\u002F\u002Fgithub.com\u002Fhikmet4434\u002Fclaude-skills\u002Fblob\u002Fmaster\u002Fnetlify-functions\u002Fassets\u002Fnetlify-small.svg",{"path":58,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":59,"sourceHtmlUrl":60},"assets\u002Fnetlify.png",2686,"https:\u002F\u002Fgithub.com\u002Fhikmet4434\u002Fclaude-skills\u002Fblob\u002Fmaster\u002Fnetlify-functions\u002Fassets\u002Fnetlify.png",{"path":62,"resourceType":63,"resourceTypeDesc":64,"sizeBytes":65,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",10776,[67,75,83,90,98,106],{"skillNo":68,"name":69,"nameZh":6,"description":70,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":71,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":20},"01M7BTGA12ETGPJZV002TR0YDS","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","https:\u002F\u002Fgithub.com\u002Fhikmet4434\u002Fclaude-skills\u002Fblob\u002Fmaster\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fhikmet4434\u002Fclaude-skills\u002Fblob\u002Fmaster\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":20},"01M7BTG43MC8DG3395QZ9V8628","yayin-seo-geo-yasal-denetim","Bir web uygulaması canlıya çıkmadan veya iş teslimi biterken resmî\u002Fkurumsal sayfaları, SEO, GEO, indeksleme ve canlı çıktıyı denetler; eksikleri kodda tamamlar ve üretimde kanıtlar. Uygulama bitti, canlıya hazır mı, yayına al, launch checklist, release readiness, SEO audit, GEO audit, legal pages, privacy policy, terms, cookies, KVKK, robots, sitemap, canonical, hreflang, JSON-LD, llms.txt ifadelerinde kullan. Yeni veya önemli ölçüde değişmiş halka açık web uygulamasının son teslim aşamasında kullanıcı ayrıca istemese de uygula. Güvenlik sızma testi için güvenlik skillini ayrıca kullan.","MIT","https:\u002F\u002Fgithub.com\u002Fhikmet4434\u002Fclaude-skills\u002Fblob\u002Fmaster\u002Fyayin-seo-geo-yasal-denetim\u002FSKILL.md",[],[],{"skillNo":84,"name":85,"nameZh":6,"description":86,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":87,"categories":88,"keywords":89,"publishedAt":20},"01M7BTG0P2JC1MW62J36K8GTXE","xurl","X\u002FTwitter via xurl CLI: post, search, DM, media, v2 API.","https:\u002F\u002Fgithub.com\u002Fhikmet4434\u002Fclaude-skills\u002Fblob\u002Fmaster\u002Fxurl\u002FSKILL.md",[],[],{"skillNo":91,"name":92,"nameZh":6,"description":93,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":94,"sourceHtmlUrl":95,"categories":96,"keywords":97,"publishedAt":20},"01M7BTF744QWNY97F5SQJZ7WQ1","wrangler","Cloudflare Workers CLI for deploying, developing, and managing Workers, KV, R2, D1, Vectorize, Hyperdrive, Workers AI, Containers, Queues, Workflows, Pipelines, and Secrets Store. Load before running wrangler commands to ensure correct syntax and best practices. Biases towards retrieval from Cloudflare docs over pre-trained knowledge.","https:\u002F\u002Fgithub.com\u002Fhikmet4434\u002Fclaude-skills\u002Fblob\u002Fmaster\u002Fwrangler\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fhikmet4434\u002Fclaude-skills\u002Fblob\u002Fmaster\u002Fwrangler\u002FSKILL.md",[],[],{"skillNo":99,"name":100,"nameZh":6,"description":101,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":102,"sourceHtmlUrl":103,"categories":104,"keywords":105,"publishedAt":20},"01M7BTD1RVAZTYZ3J6JT97W2XJ","winui-app","Bootstrap, develop, and design modern WinUI 3 desktop applications with C# and the Windows App SDK using official Microsoft guidance, WinUI Gallery patterns, Windows App SDK samples, and CommunityToolkit components. Use when creating a brand new app, preparing a machine for WinUI, reviewing, refactoring, planning, troubleshooting, environment-checking, or setting up WinUI 3 XAML, controls, navigation, windowing, theming, accessibility, responsiveness, performance, deployment, or related Windows app design and development work.","https:\u002F\u002Fgithub.com\u002Fhikmet4434\u002Fclaude-skills\u002Fblob\u002Fmaster\u002Fwinui-app\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fhikmet4434\u002Fclaude-skills\u002Fblob\u002Fmaster\u002Fwinui-app\u002FSKILL.md",[],[],{"skillNo":107,"name":108,"nameZh":6,"description":109,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":79,"licenseFileUrl":6,"sourceHtmlUrl":110,"categories":111,"keywords":112,"publishedAt":20},"01M7BTCJJ3F3G3VASJYEAWXDQ1","whisper","OpenAI's general-purpose speech recognition model. Supports 99 languages, transcription, translation to English, and language identification. Six model sizes from tiny (39M params) to large (1550M params). Use for speech-to-text, podcast transcription, or multilingual audio processing. Best for robust, multilingual ASR.","https:\u002F\u002Fgithub.com\u002Fhikmet4434\u002Fclaude-skills\u002Fblob\u002Fmaster\u002Fwhisper\u002FSKILL.md",[],[]]