[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75FT8NFAS258AW7QWQJKJTB":3,"skill-same:01M75FT8NFAS258AW7QWQJKJTB":47},{"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":24,"commitSha":25,"skillDirectory":26,"forksCount":27,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":30,"ownerDescription":31,"updatedAt":32,"install":33,"resources":46},"01M75FT8NFAS258AW7QWQJKJTB","swift-architecture-skill",null,"Agent Skill for Swift architecture design and implementation patterns, with architecture-specific playbooks and review checklists. Use when designing new features, refactoring existing modules, reviewing pull requests, or debugging maintainability issues in SwiftUI\u002FUIKit projects and you need concrete guidance for MVVM, MVI, TCA, Clean Architecture, VIPER, or Reactive patterns.","javimosch\u002Fopen-claw-skills","javimosch","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F12900508?v=4","01M6D3F2AS6PV75ET9PZ1QGP8J","Javier Leandro Arancibia","01M75B8NCTAJG9WH5YNZH7C3D8",0,"MIT","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fefremidze\u002Fswift-architecture-skill\u002FSKILL.md",[],[],"2026-11-12 13:55:43",false,"---\nname: swift-architecture-skill\ndescription: Agent Skill for Swift architecture design and implementation patterns, with architecture-specific playbooks and review checklists. Use when designing new features, refactoring existing modules, reviewing pull requests, or debugging maintainability issues in SwiftUI\u002FUIKit projects and you need concrete guidance for MVVM, MVI, TCA, Clean Architecture, VIPER, or Reactive patterns.\n---\n\n# Swift Architecture Skill\n\n## Overview\n\nUse this skill to pick the best Swift architecture playbook for SwiftUI\u002FUIKit codebases and apply it to the user’s task.\n\n## Workflow\n\n### Step 1: Analyze the Request Context\n\nBefore selecting an architecture, capture:\n- task type (new feature, refactor, PR review, debugging)\n- UI stack (SwiftUI, UIKit, or mixed)\n- scope (single screen, multi-screen, app-wide)\n- existing conventions to preserve\n\n### Step 2: Select the Architecture\n\nIf the user explicitly names an architecture, treat it as the initial candidate and run a fit check before committing:\n- validate against UI stack fit (SwiftUI\u002FUIKit\u002Fmixed), state complexity, effect orchestration needs, team familiarity, and existing codebase conventions\n- if it fits, proceed with the requested architecture\n- if it mismatches key constraints, explicitly explain the mismatch and recommend the closest-fit alternative from `references\u002Fselection-guide.md`\n- if the user still insists on a mismatched architecture, proceed with a risk-mitigated plan and state the risks up front\n\nWhen no architecture is named, load `references\u002Fselection-guide.md` and infer the best fit from stated constraints (state complexity, team familiarity, testing goals, effect orchestration needs, and framework preferences). Explain the recommendation briefly.\n\nArchitecture reference mapping:\n- MVVM → `references\u002Fmvvm.md`\n- MVI → `references\u002Fmvi.md`\n- TCA → `references\u002Ftca.md`\n- Clean Architecture → `references\u002Fclean-architecture.md`\n- VIPER → `references\u002Fviper.md`\n- Reactive → `references\u002Freactive.md`\n\n### Step 3: Analyze Existing Codebase (When Applicable)\n\nWhen code already exists:\n- detect current architecture and DI style\n- note concurrency model (async\u002Fawait, Combine, GCD, mixed)\n- align recommendations to local conventions\n\n### Step 4: Produce Concrete Deliverables\n\nRead the selected architecture reference and convert its guidance into deliverables tailored to the user's request:\n\n- **File and module structure**: directory layout with file names specific to the feature\n- **State and dependency boundaries**: concrete types, protocols, and injection points\n- **Async strategy**: cancellation, actor isolation, and error paths\n- **Testing strategy**: what to test, how to stub dependencies, and example test structure\n- **Migration path** (for refactors): incremental steps to move from current to target architecture\n- **UI stack adaptation**: where SwiftUI and UIKit guidance should differ for the chosen architecture\n\n### Step 5: Validate with Checklist\n\nEnd with the architecture-specific PR review checklist from the reference file, adapted to the user's feature.\n\n## Output Requirements\n\n- Keep recommendations scoped to the requested feature or review task.\n- Prefer protocol-based dependency injection and explicit state modeling.\n- Flag anti-patterns found in existing code and provide direct fixes.\n- Include cancellation and error handling in all async flows.\n- For explicit architecture requests, include a short fit result (`fit` or `mismatch`) with 1-2 reasons.\n- For mismatch cases, include one closest-fit alternative and why it better matches the stated constraints.\n- When writing code, include only the patterns relevant to the task — do not dump entire playbooks.\n- Treat reference snippets as illustrative by default; add full compile scaffolding only if the user asks for runnable code.\n- Ask only minimum blocking questions; otherwise proceed with explicit assumptions stated up front.\n- When reviewing PRs, use the architecture-specific checklist and call out specific violations with line-level fixes.\n","# Swift Architecture Skill\n\n## Overview\n\nUse this skill to pick the best Swift architecture playbook for SwiftUI\u002FUIKit codebases and apply it to the user’s task.\n\n## Workflow\n\n### Step 1: Analyze the Request Context\n\nBefore selecting an architecture, capture:\n- task type (new feature, refactor, PR review, debugging)\n- UI stack (SwiftUI, UIKit, or mixed)\n- scope (single screen, multi-screen, app-wide)\n- existing conventions to preserve\n\n### Step 2: Select the Architecture\n\nIf the user explicitly names an architecture, treat it as the initial candidate and run a fit check before committing:\n- validate against UI stack fit (SwiftUI\u002FUIKit\u002Fmixed), state complexity, effect orchestration needs, team familiarity, and existing codebase conventions\n- if it fits, proceed with the requested architecture\n- if it mismatches key constraints, explicitly explain the mismatch and recommend the closest-fit alternative from `references\u002Fselection-guide.md`\n- if the user still insists on a mismatched architecture, proceed with a risk-mitigated plan and state the risks up front\n\nWhen no architecture is named, load `references\u002Fselection-guide.md` and infer the best fit from stated constraints (state complexity, team familiarity, testing goals, effect orchestration needs, and framework preferences). Explain the recommendation briefly.\n\nArchitecture reference mapping:\n- MVVM → `references\u002Fmvvm.md`\n- MVI → `references\u002Fmvi.md`\n- TCA → `references\u002Ftca.md`\n- Clean Architecture → `references\u002Fclean-architecture.md`\n- VIPER → `references\u002Fviper.md`\n- Reactive → `references\u002Freactive.md`\n\n### Step 3: Analyze Existing Codebase (When Applicable)\n\nWhen code already exists:\n- detect current architecture and DI style\n- note concurrency model (async\u002Fawait, Combine, GCD, mixed)\n- align recommendations to local conventions\n\n### Step 4: Produce Concrete Deliverables\n\nRead the selected architecture reference and convert its guidance into deliverables tailored to the user's request:\n\n- **File and module structure**: directory layout with file names specific to the feature\n- **State and dependency boundaries**: concrete types, protocols, and injection points\n- **Async strategy**: cancellation, actor isolation, and error paths\n- **Testing strategy**: what to test, how to stub dependencies, and example test structure\n- **Migration path** (for refactors): incremental steps to move from current to target architecture\n- **UI stack adaptation**: where SwiftUI and UIKit guidance should differ for the chosen architecture\n\n### Step 5: Validate with Checklist\n\nEnd with the architecture-specific PR review checklist from the reference file, adapted to the user's feature.\n\n## Output Requirements\n\n- Keep recommendations scoped to the requested feature or review task.\n- Prefer protocol-based dependency injection and explicit state modeling.\n- Flag anti-patterns found in existing code and provide direct fixes.\n- Include cancellation and error handling in all async flows.\n- For explicit architecture requests, include a short fit result (`fit` or `mismatch`) with 1-2 reasons.\n- For mismatch cases, include one closest-fit alternative and why it better matches the stated constraints.\n- When writing code, include only the patterns relevant to the task — do not dump entire playbooks.\n- Treat reference snippets as illustrative by default; add full compile scaffolding only if the user asks for runnable code.\n- Ask only minimum blocking questions; otherwise proceed with explicit assumptions stated up front.\n- When reviewing PRs, use the architecture-specific checklist and call out specific violations with line-level fixes.\n",{"name":5,"description":7},"main","f9d3fe7cf9ac8f1ea63a0d96e98e1f510a3814db","skills\u002Fefremidze\u002Fswift-architecture-skill",1,"https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills","https:\u002F\u002Fgithub.com\u002Fjavimosch","intrane.fr","Building robust, open-source infrastructure for the commons. AI-leveraged, self-hosted, built to last.","2026-06-07 03:34:58",{"source":8,"skillName":5,"commands":34,"prompt":44,"zipAvailable":45},[35,38,41],{"tool":36,"command":37},"npx","npx skills add javimosch\u002Fopen-claw-skills --skill swift-architecture-skill",{"tool":39,"command":40},"bunx","bunx skills add javimosch\u002Fopen-claw-skills --skill swift-architecture-skill",{"tool":42,"command":43},"pnpm","pnpm dlx skills add javimosch\u002Fopen-claw-skills --skill swift-architecture-skill","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fefremidze\u002Fswift-architecture-skill\u002FSKILL.md",true,[],[48,56,63,70,77,84],{"skillNo":49,"name":50,"nameZh":6,"description":51,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":52,"categories":53,"keywords":54,"publishedAt":55},"01M778GGXG2VQ0YF31W2MKGMQZ","crowd-prompting","A marketplace where AI agents improve prompts, system instructions, tool descriptions, and other text-based content with domain expertise from real-world operations — and earn tokens for valuable contributions.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzzadrian\u002Fcrowd-prompting\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":55},"01M778G7BH8SBJ9FJ6C3G7CB1K","ceaser","Interact with the Ceaser privacy protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- shield, unshield, note management, and protocol queries. All ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). Ceaser is a privacy-preserving ETH wrapper using Noir\u002FUltraHonk zero-knowledge proofs on Base L2 (chain ID 8453).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":55},"01M778FYCJQZWFKKX5FYMK3S47","ceaser-send","Fully automated private ETH transfer via Ceaser Protocol on Base L2 using the ceaser-mcp MCP tools. This skill uses the ceaser-mcp npm package for ALL operations -- all ceaser tool calls use CLI subcommands (npx -y ceaser-mcp \u003Csubcommand>). WARNING -- creates observable on-chain links between user wallet and hot wallet (see Privacy Warning). Generates an ephemeral hot wallet with BIP-39 mnemonic recovery, user funds it, agent signs and broadcasts the Shield TX automatically. Exactly one manual step required (funding the hot wallet with ETH). Uses Noir\u002FUltraHonk zero-knowledge proofs.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyra-v21\u002Fceaser-send\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":55},"01M778FQQNSEYA3HJKZBPQ4M9Z","dilemm-ai","Compete in DilemmAI, the prisoner's dilemma AI arena at dilemm.ai. Use when an OpenClaw agent wants to create an account, design and submit strategy prompts for their bot, enter matchmaking, analyze historical matches and leaderboards, and iterate on bot strategy. Requires headless browser automation (no API available yet).","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyori\u002Fdilemm-ai\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":55},"01M778FGVZX7QA2TF9BFMM37FY","moldium","Post and manage content on the Moldium blog platform. Triggered by \"post to Moldium\", \"write a blog post\", \"publish an article\", etc.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzyom45\u002Fmoldium\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":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":55},"01M778F88D8PQ9MQ0KNW2TJ8ZH","arxiv-paper-reviews","Interact with arXiv Crawler API to fetch papers, read reviews, submit comments, search papers, and import papers. Use when working with arXiv papers, fetching paper lists by date\u002Fcategory\u002Finterest, viewing paper details with comments, submitting paper reviews, searching papers by title, or importing papers from arXiv URLs via API at http:\u002F\u002Fweakaccept.top:8000\u002F.","https:\u002F\u002Fgithub.com\u002Fjavimosch\u002Fopen-claw-skills\u002Fblob\u002Fmain\u002Fskills\u002Fzxrys\u002Farxiv-paper-reviews\u002FSKILL.md",[],[]]