[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EST88F7Q17A99F2814STS2":3,"skill-same:01M7EST88F7Q17A99F2814STS2":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EST88F7Q17A99F2814STS2","ams-linear-api-automation",null,"TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-linear-api-automation\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: linear-api-automation\ndescription: Automate Linear via its native GraphQL API: issues, projects, cycles, and integrations without middleware. Use when scripting Linear workflows or syncing it with other tools.\ncategory: workflow-automation\n---\n\n# Linear API Automation\n\n## Overview\n\nLinear's GraphQL API exposes issues, projects, cycles, teams, users, and comments — everything the UI does, scriptable.\n\nUse cases: bulk issue management, custom triage, syncing with GitHub\u002FSentry\u002FCRMs, reporting beyond Linear's views, and enforcing conventions.\n\nThis skill uses Linear's native GraphQL API directly — scripts you control, no middleware required.\n\n## When to use\n\n- Bulk creating, updating, or triaging Linear issues\n- Custom reports and exports from Linear data\n- Syncing Linear with GitHub, Sentry, or other tools\n- Enforcing labeling and workflow conventions\n- Automating issue lifecycle (stale, assignment, prioritization)\n\n## Core concepts\n\n- **GraphQL API.**\n  Single endpoint, typed schema, efficient nested queries. Use the playground\u002Fdocs to explore; generate typed clients where it pays off.\n- **API keys.**\n  Personal API keys per automation (service account where possible). Scoped by the key owner's permissions — least privilege.\n- **Issues core.**\n  Create, update, comment, label, assign, set priority\u002Fstatus, link (blocks\u002Frelated\u002Fduplicate). Most automation lives here.\n- **Cycles and projects.**\n  Query active cycles, move issues between cycles, track project progress programmatically.\n- **Webhooks.**\n  Real-time events (issue created\u002Fupdated) to your endpoint. For reactive automation; API polling for periodic jobs.\n- **Rate limits.**\n  Linear enforces rate limits; batch operations and back off on errors. Bulk work: pace requests, don't hammer.\n- **Teams and workflows.**\n  Team IDs, workflow states per team — states differ by team, so resolve state IDs dynamically, don't hardcode.\n- **Idempotency.**\n  Check-before-create for synced issues; dedupe keys in descriptions or external IDs. Re-runs must be safe.\n\n## Practical workflow\n\n1. **Define the automation.**\n   What Linear objects, what operations, what trigger? Write the equivalent manual flow first.\n2. **Set up auth.**\n   API key for a service account with minimal team access. Secrets manager; never in code.\n3. **Explore the schema.**\n   Use the GraphQL playground to shape queries\u002Fmutations. Resolve team IDs, state IDs, label IDs dynamically.\n4. **Prototype small.**\n   Test mutations on a test team\u002Fproject with 2-3 issues. Verify states, labels, notifications.\n5. **Build idempotent scripts.**\n   Check-before-create, upsert patterns, external ID tracking for synced items.\n6. **Wire triggers.**\n   Webhooks for real-time; scheduled scripts for periodic (triage, stale, reports). Log every run.\n7. **Respect limits.**\n   Pace bulk operations; exponential backoff on errors; cache team\u002Fstate metadata.\n8. **Document.**\n   README: purpose, scope, auth, schedule, what it changes, how to disable. Future maintainers need the map.\n\n## Common pitfalls\n\n- **Hardcoded state IDs.**\n  Workflow states differ per team and change. Resolve dynamically by name; never hardcode IDs.\n- **No idempotency.**\n  Sync scripts creating duplicate issues on re-run. Check-before-create with external IDs.\n- **Rate limit hammering.**\n  Bulk updates in tight loops hitting limits and failing halfway. Pace + backoff.\n- **Overprivileged keys.**\n  Personal key with admin everywhere for a triage script. Service account, minimal teams.\n- **Notification storms.**\n  Bulk operations pinging everyone. Use quiet options where available; batch during off-hours for big jobs.\n- **Polling when webhooks fit.**\n  Cron every minute for events webhooks push instantly. Match mechanism to need.\n- **Ignoring team differences.**\n  One script assuming all teams share workflow states. Linear teams customize — handle per-team.\n- **No disable path.**\n  Automation misbehaving, nobody knows how to stop it. Document the off switch; keep key access handy.\n","# Linear API Automation\n\n## Overview\n\nLinear's GraphQL API exposes issues, projects, cycles, teams, users, and comments — everything the UI does, scriptable.\n\nUse cases: bulk issue management, custom triage, syncing with GitHub\u002FSentry\u002FCRMs, reporting beyond Linear's views, and enforcing conventions.\n\nThis skill uses Linear's native GraphQL API directly — scripts you control, no middleware required.\n\n## When to use\n\n- Bulk creating, updating, or triaging Linear issues\n- Custom reports and exports from Linear data\n- Syncing Linear with GitHub, Sentry, or other tools\n- Enforcing labeling and workflow conventions\n- Automating issue lifecycle (stale, assignment, prioritization)\n\n## Core concepts\n\n- **GraphQL API.**\n  Single endpoint, typed schema, efficient nested queries. Use the playground\u002Fdocs to explore; generate typed clients where it pays off.\n- **API keys.**\n  Personal API keys per automation (service account where possible). Scoped by the key owner's permissions — least privilege.\n- **Issues core.**\n  Create, update, comment, label, assign, set priority\u002Fstatus, link (blocks\u002Frelated\u002Fduplicate). Most automation lives here.\n- **Cycles and projects.**\n  Query active cycles, move issues between cycles, track project progress programmatically.\n- **Webhooks.**\n  Real-time events (issue created\u002Fupdated) to your endpoint. For reactive automation; API polling for periodic jobs.\n- **Rate limits.**\n  Linear enforces rate limits; batch operations and back off on errors. Bulk work: pace requests, don't hammer.\n- **Teams and workflows.**\n  Team IDs, workflow states per team — states differ by team, so resolve state IDs dynamically, don't hardcode.\n- **Idempotency.**\n  Check-before-create for synced issues; dedupe keys in descriptions or external IDs. Re-runs must be safe.\n\n## Practical workflow\n\n1. **Define the automation.**\n   What Linear objects, what operations, what trigger? Write the equivalent manual flow first.\n2. **Set up auth.**\n   API key for a service account with minimal team access. Secrets manager; never in code.\n3. **Explore the schema.**\n   Use the GraphQL playground to shape queries\u002Fmutations. Resolve team IDs, state IDs, label IDs dynamically.\n4. **Prototype small.**\n   Test mutations on a test team\u002Fproject with 2-3 issues. Verify states, labels, notifications.\n5. **Build idempotent scripts.**\n   Check-before-create, upsert patterns, external ID tracking for synced items.\n6. **Wire triggers.**\n   Webhooks for real-time; scheduled scripts for periodic (triage, stale, reports). Log every run.\n7. **Respect limits.**\n   Pace bulk operations; exponential backoff on errors; cache team\u002Fstate metadata.\n8. **Document.**\n   README: purpose, scope, auth, schedule, what it changes, how to disable. Future maintainers need the map.\n\n## Common pitfalls\n\n- **Hardcoded state IDs.**\n  Workflow states differ per team and change. Resolve dynamically by name; never hardcode IDs.\n- **No idempotency.**\n  Sync scripts creating duplicate issues on re-run. Check-before-create with external IDs.\n- **Rate limit hammering.**\n  Bulk updates in tight loops hitting limits and failing halfway. Pace + backoff.\n- **Overprivileged keys.**\n  Personal key with admin everywhere for a triage script. Service account, minimal teams.\n- **Notification storms.**\n  Bulk operations pinging everyone. Use quiet options where available; batch during off-hours for big jobs.\n- **Polling when webhooks fit.**\n  Cron every minute for events webhooks push instantly. Match mechanism to need.\n- **Ignoring team differences.**\n  One script assuming all teams share workflow states. Linear teams customize — handle per-team.\n- **No disable path.**\n  Automation misbehaving, nobody knows how to stop it. Document the off switch; keep key access handy.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-linear-api-automation",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-linear-api-automation",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-linear-api-automation",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-linear-api-automation","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-linear-api-automation\u002FSKILL.md",true,[],[46,53,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]