[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6H7QPFXV46V73MGBCQM2RMR":3,"skill-same:01M6H7QPFXV46V73MGBCQM2RMR":80},{"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":53,"commitSha":54,"skillDirectory":55,"forksCount":56,"repositoryHtmlUrl":57,"repositoryHomepageUrl":6,"ownerHtmlUrl":58,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":59,"install":60,"resources":73},"01M6H7QPFXV46V73MGBCQM2RMR","linear-data-handling",null,"Data synchronization, backup, and consistency patterns for Linear.\nUse when implementing data sync, creating backups,\nor ensuring data consistency across systems.\nTrigger with phrases like \"linear data sync\", \"backup linear\",\n\"linear data consistency\", \"sync linear issues\", \"linear data export\".","micsapp\u002Fmicstec-skills","micsapp","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F82411001?v=4","01M6GWCFQ6D3PV8EHNY62NN5VW","01M6GWCFVE1PA5HG0DKC7AMFJ3",4,"MIT","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Flinear-pack\u002Fskills\u002Flinear-data-handling\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],"linear","data","linear data handling","use","for","implementing","consistency","with","trigger","io","across","data sync","codex","write","read","synchronization","Bash","backup","issues","code","2026-11-10 10:12:30",false,"---\nname: linear-data-handling\ndescription: |\n  Data synchronization, backup, and consistency patterns for Linear.\n  Use when implementing data sync, creating backups,\n  or ensuring data consistency across systems.\n  Trigger with phrases like \"linear data sync\", \"backup linear\",\n  \"linear data consistency\", \"sync linear issues\", \"linear data export\".\nallowed-tools: Read, Write, Edit, Grep, Bash(node:*)\nversion: 1.0.0\nlicense: MIT\nauthor: Jeremy Longshore \u003Cjeremy@intentsolutions.io>\ncompatible-with: claude-code, codex, openclaw\n---\n# Linear Data Handling\n\n## Contents\n- [Overview](#overview)\n- [Prerequisites](#prerequisites)\n- [Instructions](#instructions)\n- [Output](#output)\n- [Error Handling](#error-handling)\n- [Examples](#examples)\n- [Resources](#resources)\n\n## Overview\nImplement reliable data synchronization, backup, and consistency for Linear integrations using full sync, incremental webhooks, export\u002Fbackup, consistency checks, and conflict resolution.\n\n## Prerequisites\n- Linear API access\n- Database for local storage (Drizzle ORM recommended)\n- Understanding of eventual consistency\n\n## Instructions\n\n### Step 1: Data Model Mapping\nDefine Zod schemas for core Linear entities (`LinearIssueSchema`, `LinearProjectSchema`) covering all fields: id, identifier, title, description, priority, estimate, stateId\u002FstateName, teamId\u002FteamKey, assigneeId, projectId, cycleId, timestamps. Use `z.infer` for type exports.\n\n### Step 2: Full Sync Implementation\nBuild `fullSync()` that paginates through all issues (100 per page), maps each to the local schema (resolving state\u002Fteam relations), then runs a database transaction to upsert new\u002Fupdated issues and soft-delete removed ones. Track stats: total, created, updated, deleted, errors.\n\n### Step 3: Incremental Sync with Webhooks\nCreate `processWebhookSync()` that handles Linear webhook events (create\u002Fupdate\u002Fremove) for Issue entities, performing the corresponding database insert, update, or soft-delete with a `syncedAt` timestamp.\n\n### Step 4: Data Export\u002FBackup\nBuild `createBackup()` that exports teams, projects, cycles, and all issues (with optional comments) via paginated API calls, writing to JSON or CSV format. Include metadata (exportedAt, version).\n\n### Step 5: Data Consistency Checks\nImplement `checkConsistency()` that samples remote issues and compares against local state, detecting missing, stale, and orphaned records. Schedule via daily cron; auto-trigger full sync when thresholds are exceeded.\n\n### Step 6: Conflict Resolution\nCreate `resolveConflict()` supporting four strategies: remote-wins, local-wins, merge (field-level), and manual (throws `ConflictError`). Allow configurable merge fields.\n\nSee [detailed implementation](${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md) for complete Zod schemas, full sync with pagination, webhook handler, backup exporter, consistency checker, and conflict resolution code.\n\n## Output\n- Zod-validated data model schemas\n- Full sync with pagination and transactions\n- Incremental webhook sync handler\n- Data export\u002Fbackup utility\n- Consistency check with scheduled monitoring\n- Configurable conflict resolution\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Sync timeout | Too many records | Use smaller batches |\n| Conflict detected | Concurrent edits | Apply conflict resolution strategy |\n| Stale data | Missed webhooks | Trigger full sync |\n| Export failed | API rate limit | Add delays between requests |\n\n## Examples\n\n\n**Basic usage**: Apply linear data handling to a standard project setup with default configuration options.\n\n**Advanced scenario**: Customize linear data handling for production environments with multiple constraints and team-specific requirements.\n\n## Resources\n- [Linear GraphQL API](https:\u002F\u002Fdevelopers.linear.app\u002Fdocs\u002Fgraphql\u002Fworking-with-the-graphql-api)\n- [Data Sync Patterns](https:\u002F\u002Fmartinfowler.com\u002Farticles\u002Fpatterns-of-distributed-systems\u002F)\n- [Eventual Consistency](https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FEventual_consistency)\n\n## Next Steps\nImplement enterprise RBAC with `linear-enterprise-rbac`.","# Linear Data Handling\n\n## Contents\n- [Overview](#overview)\n- [Prerequisites](#prerequisites)\n- [Instructions](#instructions)\n- [Output](#output)\n- [Error Handling](#error-handling)\n- [Examples](#examples)\n- [Resources](#resources)\n\n## Overview\nImplement reliable data synchronization, backup, and consistency for Linear integrations using full sync, incremental webhooks, export\u002Fbackup, consistency checks, and conflict resolution.\n\n## Prerequisites\n- Linear API access\n- Database for local storage (Drizzle ORM recommended)\n- Understanding of eventual consistency\n\n## Instructions\n\n### Step 1: Data Model Mapping\nDefine Zod schemas for core Linear entities (`LinearIssueSchema`, `LinearProjectSchema`) covering all fields: id, identifier, title, description, priority, estimate, stateId\u002FstateName, teamId\u002FteamKey, assigneeId, projectId, cycleId, timestamps. Use `z.infer` for type exports.\n\n### Step 2: Full Sync Implementation\nBuild `fullSync()` that paginates through all issues (100 per page), maps each to the local schema (resolving state\u002Fteam relations), then runs a database transaction to upsert new\u002Fupdated issues and soft-delete removed ones. Track stats: total, created, updated, deleted, errors.\n\n### Step 3: Incremental Sync with Webhooks\nCreate `processWebhookSync()` that handles Linear webhook events (create\u002Fupdate\u002Fremove) for Issue entities, performing the corresponding database insert, update, or soft-delete with a `syncedAt` timestamp.\n\n### Step 4: Data Export\u002FBackup\nBuild `createBackup()` that exports teams, projects, cycles, and all issues (with optional comments) via paginated API calls, writing to JSON or CSV format. Include metadata (exportedAt, version).\n\n### Step 5: Data Consistency Checks\nImplement `checkConsistency()` that samples remote issues and compares against local state, detecting missing, stale, and orphaned records. Schedule via daily cron; auto-trigger full sync when thresholds are exceeded.\n\n### Step 6: Conflict Resolution\nCreate `resolveConflict()` supporting four strategies: remote-wins, local-wins, merge (field-level), and manual (throws `ConflictError`). Allow configurable merge fields.\n\nSee [detailed implementation](${CLAUDE_SKILL_DIR}\u002Freferences\u002Fimplementation.md) for complete Zod schemas, full sync with pagination, webhook handler, backup exporter, consistency checker, and conflict resolution code.\n\n## Output\n- Zod-validated data model schemas\n- Full sync with pagination and transactions\n- Incremental webhook sync handler\n- Data export\u002Fbackup utility\n- Consistency check with scheduled monitoring\n- Configurable conflict resolution\n\n## Error Handling\n\n| Issue | Cause | Solution |\n|-------|-------|----------|\n| Sync timeout | Too many records | Use smaller batches |\n| Conflict detected | Concurrent edits | Apply conflict resolution strategy |\n| Stale data | Missed webhooks | Trigger full sync |\n| Export failed | API rate limit | Add delays between requests |\n\n## Examples\n\n\n**Basic usage**: Apply linear data handling to a standard project setup with default configuration options.\n\n**Advanced scenario**: Customize linear data handling for production environments with multiple constraints and team-specific requirements.\n\n## Resources\n- [Linear GraphQL API](https:\u002F\u002Fdevelopers.linear.app\u002Fdocs\u002Fgraphql\u002Fworking-with-the-graphql-api)\n- [Data Sync Patterns](https:\u002F\u002Fmartinfowler.com\u002Farticles\u002Fpatterns-of-distributed-systems\u002F)\n- [Eventual Consistency](https:\u002F\u002Fen.wikipedia.org\u002Fwiki\u002FEventual_consistency)\n\n## Next Steps\nImplement enterprise RBAC with `linear-enterprise-rbac`.",{"name":5,"author":48,"license":14,"version":49,"description":50,"allowed-tools":51,"compatible-with":52},"Jeremy Longshore \u003Cjeremy@intentsolutions.io>","1.0.0","Data synchronization, backup, and consistency patterns for Linear.\nUse when implementing data sync, creating backups,\nor ensuring data consistency across systems.\nTrigger with phrases like \"linear data sync\", \"backup linear\",\n\"linear data consistency\", \"sync linear issues\", \"linear data export\".\n","Read, Write, Edit, Grep, Bash(node:*)","claude-code, codex, openclaw","master","3f5d983eb4ef375b749adcd6b07ec03bd82ae8a8","claude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Flinear-pack\u002Fskills\u002Flinear-data-handling",0,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills","https:\u002F\u002Fgithub.com\u002Fmicsapp","2026-03-20 11:24:18",{"source":8,"skillName":5,"commands":61,"prompt":71,"zipAvailable":72},[62,65,68],{"tool":63,"command":64},"npx","npx skills add micsapp\u002Fmicstec-skills --skill linear-data-handling",{"tool":66,"command":67},"bunx","bunx skills add micsapp\u002Fmicstec-skills --skill linear-data-handling",{"tool":69,"command":70},"pnpm","pnpm dlx skills add micsapp\u002Fmicstec-skills --skill linear-data-handling","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Flinear-pack\u002Fskills\u002Flinear-data-handling\u002FSKILL.md",true,[74],{"path":75,"resourceType":76,"resourceTypeDesc":77,"sizeBytes":78,"sourceHtmlUrl":79},"references\u002Fimplementation.md","REFERENCE","参考文档",8812,"https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fclaude-code\u002Fplugins-plus-skills\u002Fplugins\u002Fsaas-packs\u002Flinear-pack\u002Fskills\u002Flinear-data-handling\u002Freferences\u002Fimplementation.md",[81,115,143,163,183,207],{"skillNo":82,"name":83,"nameZh":6,"description":84,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":85,"categories":86,"keywords":95,"publishedAt":43},"01M6HBTJ02FXBFG9NYEHHYAP52","azure-apim-architecture","Analyzes and explains Azure API Management architecture decisions for enterprise API marketplace implementations using VNet Internal mode, Front Door, hybrid authentication, and multi-environment strategies. Use when discussing APIM component selection, network topology, cost optimization, or comparing alternatives like workspaces vs instances, VNet Internal vs External mode, or Front Door vs Application Gateway.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fazure-apim-architecture\u002FSKILL.md",[87,92],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000010","后端与接口","SCENARIO","使用场景",{"categoryNo":93,"categoryName":94,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000030","开发工程师",[96,97,98,99,100,101,102,103,104,105,106,107,108,109,110,111,112,113,114,27],"architecture","azure","azure apim architecture","component","authentication","gateway","topology","Optimization","network","api","team","environment","multi-environment","workspaces","instances","selection","strategies","azure api management","mode",{"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":129,"publishedAt":43},"01M6HBT7J4H082JEEA670B3EQ9","apiops-deployment","Guides deployment of Azure API Management infrastructure using Infrastructure as Code (Bicep\u002FTerraform), CI\u002FCD pipelines (GitHub Actions\u002FAzure DevOps), and APIOps workflows. Use when deploying APIM, creating pipelines, or implementing dev→test→prod promotion strategies.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapiops-deployment\u002FSKILL.md",[121,122,125,128],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},{"categoryNo":123,"categoryName":124,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000011","运维与部署",{"categoryNo":126,"categoryName":127,"taxonomyType":90,"taxonomyTypeDesc":91},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":93,"categoryName":94,"taxonomyType":20,"taxonomyTypeDesc":21},[130,131,132,133,97,134,42,135,136,137,138,139,105,106,112,140,141,113,142,28],"deployment","apiops deployment","workflows","azure devops","infrastructure","infrastructure as code","actions","ci","github actions","github-actions","as","guides","CI\u002FCD",{"skillNo":144,"name":145,"nameZh":6,"description":146,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":147,"categories":148,"keywords":150,"publishedAt":43},"01M6HBT2HEA23THNE9E00GYQBE","apim-policy-authoring","Creates production-ready Azure API Management policy XML for authentication (OAuth 2.0, JWT validation, subscription keys), rate limiting, CORS configuration, error handling, and API transformations. Use when implementing API security, access control, or request\u002Fresponse processing logic.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapim-policy-authoring\u002FSKILL.md",[149],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},[151,152,153,154,97,100,105,106,155,26,156,157,158,159,160,113,161,162,28,27],"policy","authoring","apim policy authoring","security","access","ready","api security","Access Control","error","processing","cors configuration","production-ready",{"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":171,"publishedAt":43},"01M6HBSY65SB29J9WE9KYD0K6T","api-security-review","Reviews Azure API Management configurations for security vulnerabilities, OWASP API Security Top 10 compliance, VNet Internal mode validation, Private Link verification, and Azure Security Benchmark alignment. Use when performing security audits, pre-deployment validation, or compliance reviews.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fcopilot-agent-skills\u002F.github\u002Fskills\u002Fapi-security-review\u002FSKILL.md",[169,170],{"categoryNo":88,"categoryName":89,"taxonomyType":90,"taxonomyTypeDesc":91},{"categoryNo":93,"categoryName":94,"taxonomyType":20,"taxonomyTypeDesc":21},[172,154,173,105,157,174,97,130,175,176,177,178,106,179,113,180,181,182,114,27],"review","security review","api security review","benchmark","verification","owasp","owasp-api","alignment","azure security","reviews","top",{"skillNo":184,"name":185,"nameZh":6,"description":186,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":187,"categories":188,"keywords":189,"publishedAt":43},"01M6HBSRW4PDFE6K4F8JYPZQ05","jira-cli","Interact with Jira from the command line to create, list, view, edit, and transition issues, manage sprints and epics, and perform common Jira workflows. Use when the user asks about Jira tasks, tickets, issues, sprints, or needs to manage project work items.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fjira-cli\u002FSKILL.md",[],[190,191,192,132,193,194,195,41,105,196,197,198,199,200,201,202,203,204,205,206],"cli","jira","jira cli","init","tasks","create","common","work","command","edit","list","view","project","project work","token","line","sprints",{"skillNo":208,"name":209,"nameZh":6,"description":210,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":211,"categories":212,"keywords":213,"publishedAt":43},"01M6HBSNS3JHMW603G47TWE31H","calculator","Performs arbitrary-precision arithmetic calculations including addition, subtraction, multiplication, division, and exponents. Use when the user asks to calculate, compute, or evaluate math expressions, or when precise decimal arithmetic is needed to avoid floating-point errors.","https:\u002F\u002Fgithub.com\u002Fmicsapp\u002Fmicstec-skills\u002Fblob\u002Fmaster\u002Fcopilot-cli\u002Fawesome-copilot-agents\u002Fskills\u002Fcalculator\u002FSKILL.md",[],[209,214,215,216,217,218,219,26,220,221],"npm","js","calculate","node","math","user","compute","errors"]