[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7ANDKXEC0P4N0RP8TDQM5DR":3,"skill-same:01M7ANDKXEC0P4N0RP8TDQM5DR":46},{"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":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":6,"ownerHtmlUrl":29,"ownerBlogUrl":6,"ownerDescription":30,"updatedAt":31,"install":32,"resources":45},"01M7ANDKXEC0P4N0RP8TDQM5DR","python-patterns",null,"Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying.","GongYuanCaiJi\u002Fdsh-claude-code-templates","GongYuanCaiJi","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F129952120?v=4","01M7AK39Q4W3VPF7C1K8M58BFX","劉昱廷 Yu-Ting Liu","01M7AK39QPS2RAJKRQY0EPQJPZ",0,"MIT","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Fpython-patterns\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: python-patterns\ndescription: Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying.\nallowed-tools: Read, Write, Edit, Glob, Grep\n---\n\n# Python Patterns\n\n> Python development principles and decision-making for 2025.\n> **Learn to THINK, not memorize patterns.**\n\n---\n\n## ⚠️ How to Use This Skill\n\nThis skill teaches **decision-making principles**, not fixed code to copy.\n\n- ASK user for framework preference when unclear\n- Choose async vs sync based on CONTEXT\n- Don't default to same framework every time\n\n---\n\n## 1. Framework Selection (2025)\n\n### Decision Tree\n\n```\nWhat are you building?\n│\n├── API-first \u002F Microservices\n│   └── FastAPI (async, modern, fast)\n│\n├── Full-stack web \u002F CMS \u002F Admin\n│   └── Django (batteries-included)\n│\n├── Simple \u002F Script \u002F Learning\n│   └── Flask (minimal, flexible)\n│\n├── AI\u002FML API serving\n│   └── FastAPI (Pydantic, async, uvicorn)\n│\n└── Background workers\n    └── Celery + any framework\n```\n\n### Comparison Principles\n\n| Factor | FastAPI | Django | Flask |\n|--------|---------|--------|-------|\n| **Best for** | APIs, microservices | Full-stack, CMS | Simple, learning |\n| **Async** | Native | Django 5.0+ | Via extensions |\n| **Admin** | Manual | Built-in | Via extensions |\n| **ORM** | Choose your own | Django ORM | Choose your own |\n| **Learning curve** | Low | Medium | Low |\n\n### Selection Questions to Ask:\n1. Is this API-only or full-stack?\n2. Need admin interface?\n3. Team familiar with async?\n4. Existing infrastructure?\n\n---\n\n## 2. Async vs Sync Decision\n\n### When to Use Async\n\n```\nasync def is better when:\n├── I\u002FO-bound operations (database, HTTP, file)\n├── Many concurrent connections\n├── Real-time features\n├── Microservices communication\n└── FastAPI\u002FStarlette\u002FDjango ASGI\n\ndef (sync) is better when:\n├── CPU-bound operations\n├── Simple scripts\n├── Legacy codebase\n├── Team unfamiliar with async\n└── Blocking libraries (no async version)\n```\n\n### The Golden Rule\n\n```\nI\u002FO-bound → async (waiting for external)\nCPU-bound → sync + multiprocessing (computing)\n\nDon't:\n├── Mix sync and async carelessly\n├── Use sync libraries in async code\n└── Force async for CPU work\n```\n\n### Async Library Selection\n\n| Need | Async Library |\n|------|---------------|\n| HTTP client | httpx |\n| PostgreSQL | asyncpg |\n| Redis | aioredis \u002F redis-py async |\n| File I\u002FO | aiofiles |\n| Database ORM | SQLAlchemy 2.0 async, Tortoise |\n\n---\n\n## 3. Type Hints Strategy\n\n### When to Type\n\n```\nAlways type:\n├── Function parameters\n├── Return types\n├── Class attributes\n├── Public APIs\n\nCan skip:\n├── Local variables (let inference work)\n├── One-off scripts\n├── Tests (usually)\n```\n\n### Common Type Patterns\n\n```python\n# These are patterns, understand them:\n\n# Optional → might be None\nfrom typing import Optional\ndef find_user(id: int) -> Optional[User]: ...\n\n# Union → one of multiple types\ndef process(data: str | dict) -> None: ...\n\n# Generic collections\ndef get_items() -> list[Item]: ...\ndef get_mapping() -> dict[str, int]: ...\n\n# Callable\nfrom typing import Callable\ndef apply(fn: Callable[[int], str]) -> str: ...\n```\n\n### Pydantic for Validation\n\n```\nWhen to use Pydantic:\n├── API request\u002Fresponse models\n├── Configuration\u002Fsettings\n├── Data validation\n├── Serialization\n\nBenefits:\n├── Runtime validation\n├── Auto-generated JSON schema\n├── Works with FastAPI natively\n└── Clear error messages\n```\n\n---\n\n## 4. Project Structure Principles\n\n### Structure Selection\n\n```\nSmall project \u002F Script:\n├── main.py\n├── utils.py\n└── requirements.txt\n\nMedium API:\n├── app\u002F\n│   ├── __init__.py\n│   ├── main.py\n│   ├── models\u002F\n│   ├── routes\u002F\n│   ├── services\u002F\n│   └── schemas\u002F\n├── tests\u002F\n└── pyproject.toml\n\nLarge application:\n├── src\u002F\n│   └── myapp\u002F\n│       ├── core\u002F\n│       ├── api\u002F\n│       ├── services\u002F\n│       ├── models\u002F\n│       └── ...\n├── tests\u002F\n└── pyproject.toml\n```\n\n### FastAPI Structure Principles\n\n```\nOrganize by feature or layer:\n\nBy layer:\n├── routes\u002F (API endpoints)\n├── services\u002F (business logic)\n├── models\u002F (database models)\n├── schemas\u002F (Pydantic models)\n└── dependencies\u002F (shared deps)\n\nBy feature:\n├── users\u002F\n│   ├── routes.py\n│   ├── service.py\n│   └── schemas.py\n└── products\u002F\n    └── ...\n```\n\n---\n\n## 5. Django Principles (2025)\n\n### Django Async (Django 5.0+)\n\n```\nDjango supports async:\n├── Async views\n├── Async middleware\n├── Async ORM (limited)\n└── ASGI deployment\n\nWhen to use async in Django:\n├── External API calls\n├── WebSocket (Channels)\n├── High-concurrency views\n└── Background task triggering\n```\n\n### Django Best Practices\n\n```\nModel design:\n├── Fat models, thin views\n├── Use managers for common queries\n├── Abstract base classes for shared fields\n\nViews:\n├── Class-based for complex CRUD\n├── Function-based for simple endpoints\n├── Use viewsets with DRF\n\nQueries:\n├── select_related() for FKs\n├── prefetch_related() for M2M\n├── Avoid N+1 queries\n└── Use .only() for specific fields\n```\n\n---\n\n## 6. FastAPI Principles\n\n### async def vs def in FastAPI\n\n```\nUse async def when:\n├── Using async database drivers\n├── Making async HTTP calls\n├── I\u002FO-bound operations\n└── Want to handle concurrency\n\nUse def when:\n├── Blocking operations\n├── Sync database drivers\n├── CPU-bound work\n└── FastAPI runs in threadpool automatically\n```\n\n### Dependency Injection\n\n```\nUse dependencies for:\n├── Database sessions\n├── Current user \u002F Auth\n├── Configuration\n├── Shared resources\n\nBenefits:\n├── Testability (mock dependencies)\n├── Clean separation\n├── Automatic cleanup (yield)\n```\n\n### Pydantic v2 Integration\n\n```python\n# FastAPI + Pydantic are tightly integrated:\n\n# Request validation\n@app.post(\"\u002Fusers\")\nasync def create(user: UserCreate) -> UserResponse:\n    # user is already validated\n    ...\n\n# Response serialization\n# Return type becomes response schema\n```\n\n---\n\n## 7. Background Tasks\n\n### Selection Guide\n\n| Solution | Best For |\n|----------|----------|\n| **BackgroundTasks** | Simple, in-process tasks |\n| **Celery** | Distributed, complex workflows |\n| **ARQ** | Async, Redis-based |\n| **RQ** | Simple Redis queue |\n| **Dramatiq** | Actor-based, simpler than Celery |\n\n### When to Use Each\n\n```\nFastAPI BackgroundTasks:\n├── Quick operations\n├── No persistence needed\n├── Fire-and-forget\n└── Same process\n\nCelery\u002FARQ:\n├── Long-running tasks\n├── Need retry logic\n├── Distributed workers\n├── Persistent queue\n└── Complex workflows\n```\n\n---\n\n## 8. Error Handling Principles\n\n### Exception Strategy\n\n```\nIn FastAPI:\n├── Create custom exception classes\n├── Register exception handlers\n├── Return consistent error format\n└── Log without exposing internals\n\nPattern:\n├── Raise domain exceptions in services\n├── Catch and transform in handlers\n└── Client gets clean error response\n```\n\n### Error Response Philosophy\n\n```\nInclude:\n├── Error code (programmatic)\n├── Message (human readable)\n├── Details (field-level when applicable)\n└── NOT stack traces (security)\n```\n\n---\n\n## 9. Testing Principles\n\n### Testing Strategy\n\n| Type | Purpose | Tools |\n|------|---------|-------|\n| **Unit** | Business logic | pytest |\n| **Integration** | API endpoints | pytest + httpx\u002FTestClient |\n| **E2E** | Full workflows | pytest + DB |\n\n### Async Testing\n\n```python\n# Use pytest-asyncio for async tests\n\nimport pytest\nfrom httpx import AsyncClient\n\n@pytest.mark.asyncio\nasync def test_endpoint():\n    async with AsyncClient(app=app, base_url=\"http:\u002F\u002Ftest\") as client:\n        response = await client.get(\"\u002Fusers\")\n        assert response.status_code == 200\n```\n\n### Fixtures Strategy\n\n```\nCommon fixtures:\n├── db_session → Database connection\n├── client → Test client\n├── authenticated_user → User with token\n└── sample_data → Test data setup\n```\n\n---\n\n## 10. Decision Checklist\n\nBefore implementing:\n\n- [ ] **Asked user about framework preference?**\n- [ ] **Chosen framework for THIS context?** (not just default)\n- [ ] **Decided async vs sync?**\n- [ ] **Planned type hint strategy?**\n- [ ] **Defined project structure?**\n- [ ] **Planned error handling?**\n- [ ] **Considered background tasks?**\n\n---\n\n## 11. Anti-Patterns to Avoid\n\n### ❌ DON'T:\n- Default to Django for simple APIs (FastAPI may be better)\n- Use sync libraries in async code\n- Skip type hints for public APIs\n- Put business logic in routes\u002Fviews\n- Ignore N+1 queries\n- Mix async and sync carelessly\n\n### ✅ DO:\n- Choose framework based on context\n- Ask about async requirements\n- Use Pydantic for validation\n- Separate concerns (routes → services → repos)\n- Test critical paths\n\n---\n\n> **Remember**: Python patterns are about decision-making for YOUR specific context. Don't copy code—think about what serves your application best.\n","# Python Patterns\n\n> Python development principles and decision-making for 2025.\n> **Learn to THINK, not memorize patterns.**\n\n---\n\n## ⚠️ How to Use This Skill\n\nThis skill teaches **decision-making principles**, not fixed code to copy.\n\n- ASK user for framework preference when unclear\n- Choose async vs sync based on CONTEXT\n- Don't default to same framework every time\n\n---\n\n## 1. Framework Selection (2025)\n\n### Decision Tree\n\n```\nWhat are you building?\n│\n├── API-first \u002F Microservices\n│   └── FastAPI (async, modern, fast)\n│\n├── Full-stack web \u002F CMS \u002F Admin\n│   └── Django (batteries-included)\n│\n├── Simple \u002F Script \u002F Learning\n│   └── Flask (minimal, flexible)\n│\n├── AI\u002FML API serving\n│   └── FastAPI (Pydantic, async, uvicorn)\n│\n└── Background workers\n    └── Celery + any framework\n```\n\n### Comparison Principles\n\n| Factor | FastAPI | Django | Flask |\n|--------|---------|--------|-------|\n| **Best for** | APIs, microservices | Full-stack, CMS | Simple, learning |\n| **Async** | Native | Django 5.0+ | Via extensions |\n| **Admin** | Manual | Built-in | Via extensions |\n| **ORM** | Choose your own | Django ORM | Choose your own |\n| **Learning curve** | Low | Medium | Low |\n\n### Selection Questions to Ask:\n1. Is this API-only or full-stack?\n2. Need admin interface?\n3. Team familiar with async?\n4. Existing infrastructure?\n\n---\n\n## 2. Async vs Sync Decision\n\n### When to Use Async\n\n```\nasync def is better when:\n├── I\u002FO-bound operations (database, HTTP, file)\n├── Many concurrent connections\n├── Real-time features\n├── Microservices communication\n└── FastAPI\u002FStarlette\u002FDjango ASGI\n\ndef (sync) is better when:\n├── CPU-bound operations\n├── Simple scripts\n├── Legacy codebase\n├── Team unfamiliar with async\n└── Blocking libraries (no async version)\n```\n\n### The Golden Rule\n\n```\nI\u002FO-bound → async (waiting for external)\nCPU-bound → sync + multiprocessing (computing)\n\nDon't:\n├── Mix sync and async carelessly\n├── Use sync libraries in async code\n└── Force async for CPU work\n```\n\n### Async Library Selection\n\n| Need | Async Library |\n|------|---------------|\n| HTTP client | httpx |\n| PostgreSQL | asyncpg |\n| Redis | aioredis \u002F redis-py async |\n| File I\u002FO | aiofiles |\n| Database ORM | SQLAlchemy 2.0 async, Tortoise |\n\n---\n\n## 3. Type Hints Strategy\n\n### When to Type\n\n```\nAlways type:\n├── Function parameters\n├── Return types\n├── Class attributes\n├── Public APIs\n\nCan skip:\n├── Local variables (let inference work)\n├── One-off scripts\n├── Tests (usually)\n```\n\n### Common Type Patterns\n\n```python\n# These are patterns, understand them:\n\n# Optional → might be None\nfrom typing import Optional\ndef find_user(id: int) -> Optional[User]: ...\n\n# Union → one of multiple types\ndef process(data: str | dict) -> None: ...\n\n# Generic collections\ndef get_items() -> list[Item]: ...\ndef get_mapping() -> dict[str, int]: ...\n\n# Callable\nfrom typing import Callable\ndef apply(fn: Callable[[int], str]) -> str: ...\n```\n\n### Pydantic for Validation\n\n```\nWhen to use Pydantic:\n├── API request\u002Fresponse models\n├── Configuration\u002Fsettings\n├── Data validation\n├── Serialization\n\nBenefits:\n├── Runtime validation\n├── Auto-generated JSON schema\n├── Works with FastAPI natively\n└── Clear error messages\n```\n\n---\n\n## 4. Project Structure Principles\n\n### Structure Selection\n\n```\nSmall project \u002F Script:\n├── main.py\n├── utils.py\n└── requirements.txt\n\nMedium API:\n├── app\u002F\n│   ├── __init__.py\n│   ├── main.py\n│   ├── models\u002F\n│   ├── routes\u002F\n│   ├── services\u002F\n│   └── schemas\u002F\n├── tests\u002F\n└── pyproject.toml\n\nLarge application:\n├── src\u002F\n│   └── myapp\u002F\n│       ├── core\u002F\n│       ├── api\u002F\n│       ├── services\u002F\n│       ├── models\u002F\n│       └── ...\n├── tests\u002F\n└── pyproject.toml\n```\n\n### FastAPI Structure Principles\n\n```\nOrganize by feature or layer:\n\nBy layer:\n├── routes\u002F (API endpoints)\n├── services\u002F (business logic)\n├── models\u002F (database models)\n├── schemas\u002F (Pydantic models)\n└── dependencies\u002F (shared deps)\n\nBy feature:\n├── users\u002F\n│   ├── routes.py\n│   ├── service.py\n│   └── schemas.py\n└── products\u002F\n    └── ...\n```\n\n---\n\n## 5. Django Principles (2025)\n\n### Django Async (Django 5.0+)\n\n```\nDjango supports async:\n├── Async views\n├── Async middleware\n├── Async ORM (limited)\n└── ASGI deployment\n\nWhen to use async in Django:\n├── External API calls\n├── WebSocket (Channels)\n├── High-concurrency views\n└── Background task triggering\n```\n\n### Django Best Practices\n\n```\nModel design:\n├── Fat models, thin views\n├── Use managers for common queries\n├── Abstract base classes for shared fields\n\nViews:\n├── Class-based for complex CRUD\n├── Function-based for simple endpoints\n├── Use viewsets with DRF\n\nQueries:\n├── select_related() for FKs\n├── prefetch_related() for M2M\n├── Avoid N+1 queries\n└── Use .only() for specific fields\n```\n\n---\n\n## 6. FastAPI Principles\n\n### async def vs def in FastAPI\n\n```\nUse async def when:\n├── Using async database drivers\n├── Making async HTTP calls\n├── I\u002FO-bound operations\n└── Want to handle concurrency\n\nUse def when:\n├── Blocking operations\n├── Sync database drivers\n├── CPU-bound work\n└── FastAPI runs in threadpool automatically\n```\n\n### Dependency Injection\n\n```\nUse dependencies for:\n├── Database sessions\n├── Current user \u002F Auth\n├── Configuration\n├── Shared resources\n\nBenefits:\n├── Testability (mock dependencies)\n├── Clean separation\n├── Automatic cleanup (yield)\n```\n\n### Pydantic v2 Integration\n\n```python\n# FastAPI + Pydantic are tightly integrated:\n\n# Request validation\n@app.post(\"\u002Fusers\")\nasync def create(user: UserCreate) -> UserResponse:\n    # user is already validated\n    ...\n\n# Response serialization\n# Return type becomes response schema\n```\n\n---\n\n## 7. Background Tasks\n\n### Selection Guide\n\n| Solution | Best For |\n|----------|----------|\n| **BackgroundTasks** | Simple, in-process tasks |\n| **Celery** | Distributed, complex workflows |\n| **ARQ** | Async, Redis-based |\n| **RQ** | Simple Redis queue |\n| **Dramatiq** | Actor-based, simpler than Celery |\n\n### When to Use Each\n\n```\nFastAPI BackgroundTasks:\n├── Quick operations\n├── No persistence needed\n├── Fire-and-forget\n└── Same process\n\nCelery\u002FARQ:\n├── Long-running tasks\n├── Need retry logic\n├── Distributed workers\n├── Persistent queue\n└── Complex workflows\n```\n\n---\n\n## 8. Error Handling Principles\n\n### Exception Strategy\n\n```\nIn FastAPI:\n├── Create custom exception classes\n├── Register exception handlers\n├── Return consistent error format\n└── Log without exposing internals\n\nPattern:\n├── Raise domain exceptions in services\n├── Catch and transform in handlers\n└── Client gets clean error response\n```\n\n### Error Response Philosophy\n\n```\nInclude:\n├── Error code (programmatic)\n├── Message (human readable)\n├── Details (field-level when applicable)\n└── NOT stack traces (security)\n```\n\n---\n\n## 9. Testing Principles\n\n### Testing Strategy\n\n| Type | Purpose | Tools |\n|------|---------|-------|\n| **Unit** | Business logic | pytest |\n| **Integration** | API endpoints | pytest + httpx\u002FTestClient |\n| **E2E** | Full workflows | pytest + DB |\n\n### Async Testing\n\n```python\n# Use pytest-asyncio for async tests\n\nimport pytest\nfrom httpx import AsyncClient\n\n@pytest.mark.asyncio\nasync def test_endpoint():\n    async with AsyncClient(app=app, base_url=\"http:\u002F\u002Ftest\") as client:\n        response = await client.get(\"\u002Fusers\")\n        assert response.status_code == 200\n```\n\n### Fixtures Strategy\n\n```\nCommon fixtures:\n├── db_session → Database connection\n├── client → Test client\n├── authenticated_user → User with token\n└── sample_data → Test data setup\n```\n\n---\n\n## 10. Decision Checklist\n\nBefore implementing:\n\n- [ ] **Asked user about framework preference?**\n- [ ] **Chosen framework for THIS context?** (not just default)\n- [ ] **Decided async vs sync?**\n- [ ] **Planned type hint strategy?**\n- [ ] **Defined project structure?**\n- [ ] **Planned error handling?**\n- [ ] **Considered background tasks?**\n\n---\n\n## 11. Anti-Patterns to Avoid\n\n### ❌ DON'T:\n- Default to Django for simple APIs (FastAPI may be better)\n- Use sync libraries in async code\n- Skip type hints for public APIs\n- Put business logic in routes\u002Fviews\n- Ignore N+1 queries\n- Mix async and sync carelessly\n\n### ✅ DO:\n- Choose framework based on context\n- Ask about async requirements\n- Use Pydantic for validation\n- Separate concerns (routes → services → repos)\n- Test critical paths\n\n---\n\n> **Remember**: Python patterns are about decision-making for YOUR specific context. Don't copy code—think about what serves your application best.\n",{"name":5,"description":7,"allowed-tools":24},"Read, Write, Edit, Glob, Grep","main","51493f354fd03e3f941d4df7fd64c0b8c7a2632d","skills\u002Fdevelopment\u002Fpython-patterns","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi","漏洞研究、根因分析、黑箱測試｜做 AI agent 工具｜Vulnerability research, root-cause analysis, AI agent tooling","2026-08-16 02:24:07",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill python-patterns",{"tool":38,"command":39},"bunx","bunx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill python-patterns",{"tool":41,"command":42},"pnpm","pnpm dlx skills add GongYuanCaiJi\u002Fdsh-claude-code-templates --skill python-patterns","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fdevelopment\u002Fpython-patterns\u002FSKILL.md",true,[],[47,54,63,70,77,84],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M7ARMYTZ5D4B7N5SKFXV345V","zapier-make-patterns","No-code automation democratizes workflow building. Zapier and Make (formerly Integromat) let non-developers automate business processes without writing code. But no-code doesn't mean no-complexity - these platforms have their own patterns, pitfalls, and breaking points.  This skill covers when to use which platform, how to build reliable automations, and when to graduate to code-based solutions. Key insight: Zapier optimizes for simplicity and integrations (7000+ apps), Make optimizes for power","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fzapier-make-patterns\u002FSKILL.md",[],[],{"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":59,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M7ARMX1BVNEAR98SBANMDF2V","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`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fyeet\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":19},"01M7ARMPR4RQ417MG1HMPGNQHH","workflow-automation","Workflow automation is the infrastructure that makes AI agents reliable. Without durable execution, a network hiccup during a 10-step payment flow means lost money and angry customers. With it, workflows resume exactly where they left off.  This skill covers the platforms (n8n, Temporal, Inngest) and patterns (sequential, parallel, orchestrator-worker) that turn brittle scripts into production-grade automation.  Key insight: The platforms make different tradeoffs. n8n optimizes for accessibility","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fworkflow-automation\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":19},"01M7ARMHBERDMKGDMV7K6MQ6YP","trigger-dev","Trigger.dev expert for background jobs, AI workflows, and reliable async execution with excellent developer experience and TypeScript-first design. Use when: trigger.dev, trigger dev, background task, ai background job, long running task.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Ftrigger-dev\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":19},"01M7ARME0A7KFT330Q2H25HE2B","slack-automation","Automate Slack workspace operations including messaging, search, channel management, and reaction workflows through Composio's Slack toolkit.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fslack-automation\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":19},"01M7ARM8D87V18WDG0GEZS11ZT","planning-with-files","Transforms workflow to use Manus-style persistent markdown files for planning, progress tracking, and knowledge storage. Use when starting complex tasks, multi-step projects, research tasks, or when the user mentions planning, organizing work, tracking progress, or wants structured output.","https:\u002F\u002Fgithub.com\u002FGongYuanCaiJi\u002Fdsh-claude-code-templates\u002Fblob\u002Fmain\u002Fskills\u002Fworkflow-automation\u002Fplanning-with-files\u002FSKILL.md",[],[]]