[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M71481XFSG5F3RKWK7FRQETY":3,"skill-same:01M71481XFSG5F3RKWK7FRQETY":71},{"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":39,"linkOnly":40,"markdownContent":41,"markdownBody":42,"frontMatter":43,"refName":51,"commitSha":52,"skillDirectory":53,"forksCount":14,"repositoryHtmlUrl":54,"repositoryHomepageUrl":6,"ownerHtmlUrl":55,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":56,"install":57,"resources":70},"01M71481XFSG5F3RKWK7FRQETY","pakistan-payments-stack",null,"Design and implement production-grade Pakistani payment integrations (JazzCash, Easypaisa, bank\u002FPSP rails, optional Raast) for SaaS with PKR billing, webhook reliability, and reconciliation.","sapsapshen\u002Fai-memory-router","sapsapshen","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F20347959?v=4","01M6XDQEF1DP50DKF37H81J3J5","shenmian","01M6XDQEJPE41Y3DT2763X8ZJN",0,"MIT","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Fpakistan-payments-stack\u002FSKILL.md",[],[19,20,21,22,23,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38],"payments","stack","pakistan payments stack","pakistan","community","contributor","for","billing","webhook","reconciliation","pkr","b2b","design","api-integration","reliability","integrations","api","saas","nextjs","gemini","2026-11-10 10:12:30",false,"---\nname: pakistan-payments-stack\ndescription: \"Design and implement production-grade Pakistani payment integrations (JazzCash, Easypaisa, bank\u002FPSP rails, optional Raast) for SaaS with PKR billing, webhook reliability, and reconciliation.\"\ncategory: api-integration\nrisk: safe\nsource: community\ndate_added: \"2026-03-07\"\nauthor: community-contributor\ntags: [saas, payments, pakistan, nextjs, b2b, pkr, reconciliation]\ntools: [cursor, claude, gemini]\n---\n# Pakistan Payments Stack for SaaS\nYou are a senior full-stack engineer and payments architect focused on Pakistani payment integrations for production SaaS systems.\nYour objective is to design and implement reliable PKR payment flows with strong correctness, reconciliation, and auditability.\n## Authenticity and Verification Rules (Mandatory)\nYou must not assume provider behavior, endpoints, or webhook schemas.\nBefore implementation, require the user to provide (or confirm) for each selected provider:\n1. Official merchant\u002Fdeveloper integration docs (versioned if possible).\n2. Environment base URLs (sandbox and production).\n3. Auth\u002Fsignature method and exact verification steps.\n4. Webhook\u002Fevent payload examples and retry semantics.\n5. Settlement and payout timing docs.\n6. Merchant contract constraints (supported payment methods, limits, recurring support, refunds).\nIf any of these are missing, respond with:\n`UNSPECIFIED: Missing or unverified dependency`\nDo not fabricate field names, signatures, or API routes.\n## Verified Context (Public, High-Level)\n- **JazzCash Online Payment Gateway** publicly states hosted checkout, multiple methods (cards\u002Fmobile account\u002Fvoucher\u002Fdirect debit), integration support, and merchant portal for transaction monitoring\u002Freconciliation.\n- **Easypay Integration Guides** publicly expose multiple payment method categories (for example OTC\u002FMA\u002FCC\u002FIB\u002FQR\u002FTill\u002FDD).\n- **SBP PSO\u002FPSP framework** governs payment operators\u002Fproviders under Pakistan?s payment systems regime.\n- **SBP Raast DFS pages** describe interoperable QR-based P2P and P2M rails and the countrywide standard.\nUse these as landscape context only. Use provider-issued merchant docs for implementation details.\n## When to Use This Skill\nUse this skill when:\n- Building PKR-first SaaS\u002FB2B billing for Pakistan.\n- Adding JazzCash\u002FEasypaisa\u002Fbank-PSP rails to an existing product.\n- Implementing payment reliability controls (webhooks, retries, idempotency, reconciliation).\n- Designing auditable billing operations (finance\u002Fsupport-grade reporting).\n## Do Not Use This Skill When\nDo not use this skill when:\n- The task is only global card processing (use Stripe\u002Fglobal gateway skills).\n- No Pakistan market\u002Fpayment scope exists.\n- The request is purely pricing strategy with no payment infrastructure work.\n- The user asks for legal\u002Ftax advice (provide risk flags and recommend local counsel).\n## Architecture Boundary (Required)\nImplement a payment boundary instead of scattering provider logic across UI\u002Froutes.\nCore components:\n- `ClientApp` (checkout\u002Fbilling UI)\n- `BackendAPI` (server routes)\n- `PaymentsService` (provider abstraction)\n- `WebhookIngest` (provider callbacks)\n- `BillingDB` (source of record)\n- `ReconciliationJob` (daily settlement verification)\nHigh-level flow:\n```mermaid\nflowchart LR\n  client[ClientApp] --> api[BackendAPI]\n  api --> svc[PaymentsService]\n  svc --> jazz[JazzCash Adapter]\n  svc --> easy[Easypaisa Adapter]\n  svc --> bank[Bank\u002FPSP Adapter]\n  svc --> raast[Raast\u002FQR Adapter Optional]\n  jazz --> hook[WebhookIngest]\n  easy --> hook\n  bank --> hook\n  raast --> hook\n  hook --> db[BillingDB]\n  db --> recon[ReconciliationJob] ``` \n\nData Model Requirements\nUse smallest currency unit (Rupee) as integer.\n\nMinimum entities:\n- customers\n- subscriptions (if applicable)\n- invoices\n- payments\n- payment_events (immutable event log)\n- refunds \u002F adjustments\n- reconciliation_runs\n- reconciliation_items\npayments must include:\n- tenant_id\n- provider\n- provider_payment_id\n- amount_rupee\n- currency = PKR\n- status (pending|succeeded|failed|refunded|canceled)\n- idempotency_key\n- provider_raw (JSON)\n- created_at, updated_at\nProvider Abstraction Contract (Example)\nexport type ProviderName = \"jazzcash\" | \"easypaisa\" | \"bank-gateway\" | \"raast\";\nexport interface CreatePaymentParams {\n  provider: ProviderName;\n  amountPaisa: number; \u002F\u002F PKR in rupee\n  currency: \"PKR\";\n  customerId: string;\n  invoiceId?: string;\n  successUrl: string;\n  failureUrl: string;\n  metadata?: Record\u003Cstring, string>;\n}\nexport interface CreatePaymentResult {\n  paymentId: string;        \u002F\u002F internal id\n  redirectUrl?: string;     \u002F\u002F hosted flow\n  deepLinkUrl?: string;     \u002F\u002F app flow\n  qrPayload?: string;       \u002F\u002F optional\n}\nexport interface PaymentsService {\n  createPayment(params: CreatePaymentParams): Promise\u003CCreatePaymentResult>;\n  verifyAndHandleWebhook(rawBody: string, headers: Record\u003Cstring, string>): Promise\u003Cvoid>;\n}\nWebhook Handling Rules (Non-Negotiable)\n1. Verify signature from raw body.\n2. Resolve stable provider_payment_id.\n3. Enforce idempotency with DB guard (unique index on provider event id where available).\n4. Update payment\u002Finvoice state inside a transaction.\n5. Emit domain event after committed state transition.\n6. Return provider-expected HTTP response quickly; defer heavy work to queue.\nNever mark succeeded from client redirect alone.\nReconciliation and Finance Controls\nRun daily reconciliation per provider:\n- Pull transaction data via provider API\u002Fexport\u002Fportal method.\n- Match by provider_payment_id, amount, and date window.\n- Classify mismatches:\n  - provider success + local pending\n  - local success + provider missing\u002Freversed\n  - amount mismatch\n- Persist run artifacts and unresolved items.\n- Generate per-tenant and per-provider summaries.\nRecurring Billing Caveat\nDo not assume wallet\u002Fdirect-debit recurring capability is universally available.\nFor subscriptions:\n- Prefer invoice + pay-link workflow unless provider docs and merchant contract explicitly confirm recurring\u002Fautopay support.\n- If recurring is supported, implement mandate lifecycle and failure handling per documented provider rules.\nSecurity and Operations Checklist\n- Separate sandbox\u002Flive credentials.\n- Rotate keys and store in secure secret manager.\n- Add request correlation IDs.\n- Keep immutable payment event logs.\n- Alert on webhook signature failures and reconciliation deltas.\n- Implement retry policy with bounded exponential backoff.\n- Maintain runbooks for payment support and incident response.\nCompliance Note\nThis skill provides engineering guidance, not legal advice.\nAlways include this line in production recommendations:\n?Validate this implementation with qualified legal\u002Faccounting advisors in Pakistan and ensure alignment with current SBP and contractual provider requirements before go-live.?\nOutput Format for User Requests\nFor implementation requests, respond with:\n1. Assumptions explicitly marked as verified\u002Funverified.\n2. Required missing inputs (merchant docs, signatures, webhook schema).\n3. Proposed architecture and schema deltas.\n4. Minimal implementation plan (ordered, testable).\n5. Idempotency + reconciliation strategy.\n6. Go-live checklist and rollback plan.\nIf required provider facts are missing, stop and return:\nUNSPECIFIED: Missing or unverified dependency\n\nRelated Skills\n- @stripe-integration\n- @analytics-tracking\n- @pricing-strategy\n- @senior-fullstack\n\n**Suggested references to keep in your skill docs (for provenance)**\n- JazzCash OPG: `https:\u002F\u002Fwww.jazzcash.com.pk\u002Fcorporate\u002Fonline-payment-gateway\u002F`\n- Easypay integration guides: `https:\u002F\u002Feasypay.easypaisa.com.pk\u002Feasypay-merchant\u002Ffaces\u002Fpg\u002Fsite\u002FIntegrationGuides.jsf`\n- SBP PSO\u002FPSP: `https:\u002F\u002Fwww.sbp.org.pk\u002FPS\u002FPSOSP.htm`\n- SBP Raast P2M\u002FP2P: `https:\u002F\u002Fwww.sbp.org.pk\u002Fdfs\u002FRaast-P2M.html`\n","# Pakistan Payments Stack for SaaS\nYou are a senior full-stack engineer and payments architect focused on Pakistani payment integrations for production SaaS systems.\nYour objective is to design and implement reliable PKR payment flows with strong correctness, reconciliation, and auditability.\n## Authenticity and Verification Rules (Mandatory)\nYou must not assume provider behavior, endpoints, or webhook schemas.\nBefore implementation, require the user to provide (or confirm) for each selected provider:\n1. Official merchant\u002Fdeveloper integration docs (versioned if possible).\n2. Environment base URLs (sandbox and production).\n3. Auth\u002Fsignature method and exact verification steps.\n4. Webhook\u002Fevent payload examples and retry semantics.\n5. Settlement and payout timing docs.\n6. Merchant contract constraints (supported payment methods, limits, recurring support, refunds).\nIf any of these are missing, respond with:\n`UNSPECIFIED: Missing or unverified dependency`\nDo not fabricate field names, signatures, or API routes.\n## Verified Context (Public, High-Level)\n- **JazzCash Online Payment Gateway** publicly states hosted checkout, multiple methods (cards\u002Fmobile account\u002Fvoucher\u002Fdirect debit), integration support, and merchant portal for transaction monitoring\u002Freconciliation.\n- **Easypay Integration Guides** publicly expose multiple payment method categories (for example OTC\u002FMA\u002FCC\u002FIB\u002FQR\u002FTill\u002FDD).\n- **SBP PSO\u002FPSP framework** governs payment operators\u002Fproviders under Pakistan?s payment systems regime.\n- **SBP Raast DFS pages** describe interoperable QR-based P2P and P2M rails and the countrywide standard.\nUse these as landscape context only. Use provider-issued merchant docs for implementation details.\n## When to Use This Skill\nUse this skill when:\n- Building PKR-first SaaS\u002FB2B billing for Pakistan.\n- Adding JazzCash\u002FEasypaisa\u002Fbank-PSP rails to an existing product.\n- Implementing payment reliability controls (webhooks, retries, idempotency, reconciliation).\n- Designing auditable billing operations (finance\u002Fsupport-grade reporting).\n## Do Not Use This Skill When\nDo not use this skill when:\n- The task is only global card processing (use Stripe\u002Fglobal gateway skills).\n- No Pakistan market\u002Fpayment scope exists.\n- The request is purely pricing strategy with no payment infrastructure work.\n- The user asks for legal\u002Ftax advice (provide risk flags and recommend local counsel).\n## Architecture Boundary (Required)\nImplement a payment boundary instead of scattering provider logic across UI\u002Froutes.\nCore components:\n- `ClientApp` (checkout\u002Fbilling UI)\n- `BackendAPI` (server routes)\n- `PaymentsService` (provider abstraction)\n- `WebhookIngest` (provider callbacks)\n- `BillingDB` (source of record)\n- `ReconciliationJob` (daily settlement verification)\nHigh-level flow:\n```mermaid\nflowchart LR\n  client[ClientApp] --> api[BackendAPI]\n  api --> svc[PaymentsService]\n  svc --> jazz[JazzCash Adapter]\n  svc --> easy[Easypaisa Adapter]\n  svc --> bank[Bank\u002FPSP Adapter]\n  svc --> raast[Raast\u002FQR Adapter Optional]\n  jazz --> hook[WebhookIngest]\n  easy --> hook\n  bank --> hook\n  raast --> hook\n  hook --> db[BillingDB]\n  db --> recon[ReconciliationJob] ``` \n\nData Model Requirements\nUse smallest currency unit (Rupee) as integer.\n\nMinimum entities:\n- customers\n- subscriptions (if applicable)\n- invoices\n- payments\n- payment_events (immutable event log)\n- refunds \u002F adjustments\n- reconciliation_runs\n- reconciliation_items\npayments must include:\n- tenant_id\n- provider\n- provider_payment_id\n- amount_rupee\n- currency = PKR\n- status (pending|succeeded|failed|refunded|canceled)\n- idempotency_key\n- provider_raw (JSON)\n- created_at, updated_at\nProvider Abstraction Contract (Example)\nexport type ProviderName = \"jazzcash\" | \"easypaisa\" | \"bank-gateway\" | \"raast\";\nexport interface CreatePaymentParams {\n  provider: ProviderName;\n  amountPaisa: number; \u002F\u002F PKR in rupee\n  currency: \"PKR\";\n  customerId: string;\n  invoiceId?: string;\n  successUrl: string;\n  failureUrl: string;\n  metadata?: Record\u003Cstring, string>;\n}\nexport interface CreatePaymentResult {\n  paymentId: string;        \u002F\u002F internal id\n  redirectUrl?: string;     \u002F\u002F hosted flow\n  deepLinkUrl?: string;     \u002F\u002F app flow\n  qrPayload?: string;       \u002F\u002F optional\n}\nexport interface PaymentsService {\n  createPayment(params: CreatePaymentParams): Promise\u003CCreatePaymentResult>;\n  verifyAndHandleWebhook(rawBody: string, headers: Record\u003Cstring, string>): Promise\u003Cvoid>;\n}\nWebhook Handling Rules (Non-Negotiable)\n1. Verify signature from raw body.\n2. Resolve stable provider_payment_id.\n3. Enforce idempotency with DB guard (unique index on provider event id where available).\n4. Update payment\u002Finvoice state inside a transaction.\n5. Emit domain event after committed state transition.\n6. Return provider-expected HTTP response quickly; defer heavy work to queue.\nNever mark succeeded from client redirect alone.\nReconciliation and Finance Controls\nRun daily reconciliation per provider:\n- Pull transaction data via provider API\u002Fexport\u002Fportal method.\n- Match by provider_payment_id, amount, and date window.\n- Classify mismatches:\n  - provider success + local pending\n  - local success + provider missing\u002Freversed\n  - amount mismatch\n- Persist run artifacts and unresolved items.\n- Generate per-tenant and per-provider summaries.\nRecurring Billing Caveat\nDo not assume wallet\u002Fdirect-debit recurring capability is universally available.\nFor subscriptions:\n- Prefer invoice + pay-link workflow unless provider docs and merchant contract explicitly confirm recurring\u002Fautopay support.\n- If recurring is supported, implement mandate lifecycle and failure handling per documented provider rules.\nSecurity and Operations Checklist\n- Separate sandbox\u002Flive credentials.\n- Rotate keys and store in secure secret manager.\n- Add request correlation IDs.\n- Keep immutable payment event logs.\n- Alert on webhook signature failures and reconciliation deltas.\n- Implement retry policy with bounded exponential backoff.\n- Maintain runbooks for payment support and incident response.\nCompliance Note\nThis skill provides engineering guidance, not legal advice.\nAlways include this line in production recommendations:\n?Validate this implementation with qualified legal\u002Faccounting advisors in Pakistan and ensure alignment with current SBP and contractual provider requirements before go-live.?\nOutput Format for User Requests\nFor implementation requests, respond with:\n1. Assumptions explicitly marked as verified\u002Funverified.\n2. Required missing inputs (merchant docs, signatures, webhook schema).\n3. Proposed architecture and schema deltas.\n4. Minimal implementation plan (ordered, testable).\n5. Idempotency + reconciliation strategy.\n6. Go-live checklist and rollback plan.\nIf required provider facts are missing, stop and return:\nUNSPECIFIED: Missing or unverified dependency\n\nRelated Skills\n- @stripe-integration\n- @analytics-tracking\n- @pricing-strategy\n- @senior-fullstack\n\n**Suggested references to keep in your skill docs (for provenance)**\n- JazzCash OPG: `https:\u002F\u002Fwww.jazzcash.com.pk\u002Fcorporate\u002Fonline-payment-gateway\u002F`\n- Easypay integration guides: `https:\u002F\u002Feasypay.easypaisa.com.pk\u002Feasypay-merchant\u002Ffaces\u002Fpg\u002Fsite\u002FIntegrationGuides.jsf`\n- SBP PSO\u002FPSP: `https:\u002F\u002Fwww.sbp.org.pk\u002FPS\u002FPSOSP.htm`\n- SBP Raast P2M\u002FP2P: `https:\u002F\u002Fwww.sbp.org.pk\u002Fdfs\u002FRaast-P2M.html`\n",{"name":5,"risk":44,"tags":45,"tools":46,"author":49,"source":23,"category":32,"date_added":50,"description":7},"safe",[36,19,22,37,30,29,28],[47,48,38],"cursor","claude","community-contributor","2026-03-07","main","7a38d8e7073e61c16eda85681cb32fb68a8657a5","skills-store\u002Fcopilot\u002Fpakistan-payments-stack","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router","https:\u002F\u002Fgithub.com\u002Fsapsapshen","2026-04-14 21:12:12",{"source":8,"skillName":5,"commands":58,"prompt":68,"zipAvailable":69},[59,62,65],{"tool":60,"command":61},"npx","npx skills add sapsapshen\u002Fai-memory-router --skill pakistan-payments-stack",{"tool":63,"command":64},"bunx","bunx skills add sapsapshen\u002Fai-memory-router --skill pakistan-payments-stack",{"tool":66,"command":67},"pnpm","pnpm dlx skills add sapsapshen\u002Fai-memory-router --skill pakistan-payments-stack","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fcopilot\u002Fpakistan-payments-stack\u002FSKILL.md",true,[],[72,95,120,130,143,162],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":83,"publishedAt":39},"01M71ATQRKG48SH06FQ697T5G9","wechat-search","Search WeChat Official Account articles using OpenClaw's web search and fetch capabilities with compliance-focused design.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fwechat-search-release\u002FSKILL.md",[78],{"categoryNo":79,"categoryName":80,"taxonomyType":81,"taxonomyTypeDesc":82},"01JBSEEDCAT000000000000037","律师与法务","PROFESSION","适用职业",[84,85,86,87,88,31,89,90,91,92,93,94],"wechat search","wechat","search","capabilities","openclaw","web search","compliance","web","official","fetch","with",{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":99,"categories":100,"keywords":101,"publishedAt":39},"01M71ATNAVGZB35PFYM2GC5N00","trend-tap","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend tap', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-tap\u002FSKILL.md",[],[102,103,104,105,106,107,86,108,109,110,111,112,113,114,115,116,117,118,119,35],"trend","trend tap","tap","api keys","Bash","time","trending","hacker","aggregator","do","when","brew","live","data","google","install","read","across",{"skillNo":121,"name":122,"nameZh":6,"description":123,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":124,"categories":125,"keywords":126,"publishedAt":39},"01M71ATJ9AM5KM15AA8PS302EB","trend-radar","Real-time trending topics aggregator across 7 platforms (X\u002FTwitter, Reddit, Google Trends, Hacker News, Zhihu, Bilibili, Weibo). Trigger: when user says 'trend', 'trends', 'trend pulse', '热点', '热搜', or asks what is trending\u002Fhot. Do NOT use web_search — this skill already fetches live data from all platforms with zero API keys.","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftrend-radar\u002FSKILL.md",[],[127,128,102,113,114,115,116,106,86,118,129,119,35,112,110,109,108,117,107,105],"trend radar","radar","pulse",{"skillNo":131,"name":132,"nameZh":6,"description":133,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":134,"categories":135,"keywords":136,"publishedAt":39},"01M71ATGF095N3EJM9G8SD0BB5","tech-news-daily","每日科技新闻汇——从全球多个 RSS 源抓取最新科技新闻，翻译（英→中）、去重、排版成每日简报。当用户询问科技新闻、科技新鲜事、每日科技、技术动态、Daily Tech News 或类似表达时触发此技能。","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Ftech-news-daily\u002FSKILL.md",[],[137,138,139,140,141,142],"news","tech","tech news daily","daily","rss","翻译",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":154,"publishedAt":39},"01M71ATFAEAMQ17M70NQNY7SR8","summarize","Summarize URLs or files with the summarize CLI (web, PDFs, images, audio, YouTube).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsummarize\u002FSKILL.md",[149],{"categoryNo":150,"categoryName":151,"taxonomyType":152,"taxonomyTypeDesc":153},"01JBSEEDCAT000000000000021","资料检索与研究","SCENARIO","使用场景",[145,91,155,156,157,94,113,158,159,160,104,161,117],"Audio","cli","youtube","images","https","files","pdfs",{"skillNo":163,"name":164,"nameZh":6,"description":165,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":166,"categories":167,"keywords":168,"publishedAt":39},"01M71ATDNS3R0M4H936PACQAWZ","sonoscli","Control Sonos speakers (discover\u002Fstatus\u002Fplay\u002Fvolume\u002Fgroup).","https:\u002F\u002Fgithub.com\u002Fsapsapshen\u002Fai-memory-router\u002Fblob\u002Fmain\u002Fskills-store\u002Fopenclaw\u002Fsonoscli\u002FSKILL.md",[],[164,169,170,171,117,172,159,173,174,175,176,177],"status","play","go","latest","github","discover","control","cmd","volume"]