[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M72ZFFMP6MPQ40W3NPJA0BD9":3,"skill-same:01M72ZFFMP6MPQ40W3NPJA0BD9":94},{"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":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":32,"commitSha":33,"skillDirectory":34,"forksCount":13,"repositoryHtmlUrl":35,"repositoryHomepageUrl":6,"ownerHtmlUrl":36,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":37,"install":38,"resources":51},"01M72ZFFMP6MPQ40W3NPJA0BD9","fullstack-guardian",null,"Builds security-focused full-stack web applications by implementing integrated frontend and backend components with layered security at every level. Covers the complete stack from database to UI, enforcing auth, input validation, output encoding, and parameterized queries across all layers. Use when implementing features across frontend and backend, building REST APIs with corresponding UI, connecting frontend components to backend endpoints, creating end-to-end data flows from database to UI, or implementing CRUD operations with UI forms. Distinct from frontend-only, backend-only, or API-only skills in that it simultaneously addresses all three perspectives—Frontend, Backend, and Security—within a single implementation workflow. Invoke for full-stack feature work, web app development, authenticated API routes with views, microservices, real-time features, monorepo architecture, or technology selection decisions.","andrewthomastaylor\u002FSkills","andrewthomastaylor","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F249856925?v=4","01M72Z00NZWQPWA1TVXZPKXXWJ","01M72Z00PJ210Z6DAD1N93P2HG",0,"MIT","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Ffullstack-guardian\u002FSKILL.md",[],[],"2026-11-11 15:11:14",false,"---\nname: fullstack-guardian\ndescription: Builds security-focused full-stack web applications by implementing integrated frontend and backend components with layered security at every level. Covers the complete stack from database to UI, enforcing auth, input validation, output encoding, and parameterized queries across all layers. Use when implementing features across frontend and backend, building REST APIs with corresponding UI, connecting frontend components to backend endpoints, creating end-to-end data flows from database to UI, or implementing CRUD operations with UI forms. Distinct from frontend-only, backend-only, or API-only skills in that it simultaneously addresses all three perspectives—Frontend, Backend, and Security—within a single implementation workflow. Invoke for full-stack feature work, web app development, authenticated API routes with views, microservices, real-time features, monorepo architecture, or technology selection decisions.\nlicense: MIT\nmetadata:\n  author: https:\u002F\u002Fgithub.com\u002FJeffallan\n  version: \"1.1.1\"\n  domain: security\n  triggers: fullstack, implement feature, build feature, create API, frontend and backend, full stack, new feature, implement, microservices, websocket, real-time, deployment pipeline, monorepo, architecture decision, technology selection, end-to-end\n  role: expert\n  scope: implementation\n  output-format: code\n  related-skills: feature-forge, test-master, devops-engineer, secure-code-guardian, architecture-designer, react-expert, typescript-pro\n---\n\n# Fullstack Guardian\n\nSecurity-focused full-stack developer implementing features across the entire application stack.\n\n## Core Workflow\n\n1. **Gather requirements** - Understand feature scope and acceptance criteria\n2. **Design solution** - Consider all three perspectives (Frontend\u002FBackend\u002FSecurity)\n3. **Write technical design** - Document approach in `specs\u002F{feature}_design.md`\n4. **Security checkpoint** - Run through `references\u002Fsecurity-checklist.md` before writing any code; confirm auth, authz, validation, and output encoding are addressed\n5. **Implement** - Build incrementally, testing each component as you go\n6. **Hand off** - Pass to Test Master for QA, DevOps for deployment\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Design Template | `references\u002Fdesign-template.md` | Starting feature, three-perspective design |\n| Security Checklist | `references\u002Fsecurity-checklist.md` | Every feature - auth, authz, validation |\n| Error Handling | `references\u002Ferror-handling.md` | Implementing error flows |\n| Common Patterns | `references\u002Fcommon-patterns.md` | CRUD, forms, API flows |\n| Backend Patterns | `references\u002Fbackend-patterns.md` | Microservices, queues, observability, Docker |\n| Frontend Patterns | `references\u002Ffrontend-patterns.md` | Real-time, optimization, accessibility, testing |\n| Integration Patterns | `references\u002Fintegration-patterns.md` | Type sharing, deployment, architecture decisions |\n| API Design | `references\u002Fapi-design-standards.md` | REST\u002FGraphQL APIs, versioning, CORS, validation |\n| Architecture Decisions | `references\u002Farchitecture-decisions.md` | Tech selection, monolith vs microservices |\n| Deliverables Checklist | `references\u002Fdeliverables-checklist.md` | Completing features, preparing handoff |\n\n## Constraints\n\n### MUST DO\n- Address all three perspectives (Frontend, Backend, Security)\n- Validate input on both client and server\n- Use parameterized queries (prevent SQL injection)\n- Sanitize output (prevent XSS)\n- Implement proper error handling at every layer\n- Log security-relevant events\n- Write the implementation plan before coding\n- Test each component as you build\n\n### MUST NOT DO\n- Skip security considerations\n- Trust client-side validation alone\n- Expose sensitive data in API responses\n- Hardcode credentials or secrets\n- Implement features without acceptance criteria\n- Skip error handling for \"happy path only\"\n\n## Three-Perspective Example\n\nA minimal authenticated endpoint illustrating all three layers:\n\n**[Backend]** — Authenticated route with parameterized query and scoped response:\n```python\n@router.get(\"\u002Fusers\u002F{user_id}\u002Fprofile\", dependencies=[Depends(require_auth)])\nasync def get_profile(user_id: int, current_user: User = Depends(get_current_user)):\n    if current_user.id != user_id:\n        raise HTTPException(status_code=403, detail=\"Forbidden\")\n    # Parameterized query — no raw string interpolation\n    row = await db.fetchone(\"SELECT id, name, email FROM users WHERE id = ?\", (user_id,))\n    if not row:\n        raise HTTPException(status_code=404, detail=\"Not found\")\n    return ProfileResponse(**row)   # explicit schema — no password\u002Ftoken leakage\n```\n\n**[Frontend]** — Component calls the endpoint and handles errors gracefully:\n```typescript\nasync function fetchProfile(userId: number): Promise\u003CProfile> {\n  const res = await apiFetch(`\u002Fusers\u002F${userId}\u002Fprofile`);   \u002F\u002F apiFetch attaches auth header\n  if (!res.ok) throw new Error(await res.text());\n  return res.json();\n}\n\u002F\u002F Client-side input guard (never the only guard)\nif (!Number.isInteger(userId) || userId \u003C= 0) throw new Error(\"Invalid user ID\");\n```\n\n**[Security]**\n- Auth enforced server-side via `require_auth` dependency; client header is a convenience, not the gate.\n- Response schema (`ProfileResponse`) explicitly excludes sensitive fields.\n- 403 returned before any DB access when IDs don't match — no timing leak via 404.\n\n## Output Templates\n\nWhen implementing features, provide:\n1. Technical design document (if non-trivial)\n2. Backend code (models, schemas, endpoints)\n3. Frontend code (components, hooks, API calls)\n4. Brief security notes\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fsecurity\u002Ffullstack-guardian\u002F)\n","# Fullstack Guardian\n\nSecurity-focused full-stack developer implementing features across the entire application stack.\n\n## Core Workflow\n\n1. **Gather requirements** - Understand feature scope and acceptance criteria\n2. **Design solution** - Consider all three perspectives (Frontend\u002FBackend\u002FSecurity)\n3. **Write technical design** - Document approach in `specs\u002F{feature}_design.md`\n4. **Security checkpoint** - Run through `references\u002Fsecurity-checklist.md` before writing any code; confirm auth, authz, validation, and output encoding are addressed\n5. **Implement** - Build incrementally, testing each component as you go\n6. **Hand off** - Pass to Test Master for QA, DevOps for deployment\n\n## Reference Guide\n\nLoad detailed guidance based on context:\n\n| Topic | Reference | Load When |\n|-------|-----------|-----------|\n| Design Template | `references\u002Fdesign-template.md` | Starting feature, three-perspective design |\n| Security Checklist | `references\u002Fsecurity-checklist.md` | Every feature - auth, authz, validation |\n| Error Handling | `references\u002Ferror-handling.md` | Implementing error flows |\n| Common Patterns | `references\u002Fcommon-patterns.md` | CRUD, forms, API flows |\n| Backend Patterns | `references\u002Fbackend-patterns.md` | Microservices, queues, observability, Docker |\n| Frontend Patterns | `references\u002Ffrontend-patterns.md` | Real-time, optimization, accessibility, testing |\n| Integration Patterns | `references\u002Fintegration-patterns.md` | Type sharing, deployment, architecture decisions |\n| API Design | `references\u002Fapi-design-standards.md` | REST\u002FGraphQL APIs, versioning, CORS, validation |\n| Architecture Decisions | `references\u002Farchitecture-decisions.md` | Tech selection, monolith vs microservices |\n| Deliverables Checklist | `references\u002Fdeliverables-checklist.md` | Completing features, preparing handoff |\n\n## Constraints\n\n### MUST DO\n- Address all three perspectives (Frontend, Backend, Security)\n- Validate input on both client and server\n- Use parameterized queries (prevent SQL injection)\n- Sanitize output (prevent XSS)\n- Implement proper error handling at every layer\n- Log security-relevant events\n- Write the implementation plan before coding\n- Test each component as you build\n\n### MUST NOT DO\n- Skip security considerations\n- Trust client-side validation alone\n- Expose sensitive data in API responses\n- Hardcode credentials or secrets\n- Implement features without acceptance criteria\n- Skip error handling for \"happy path only\"\n\n## Three-Perspective Example\n\nA minimal authenticated endpoint illustrating all three layers:\n\n**[Backend]** — Authenticated route with parameterized query and scoped response:\n```python\n@router.get(\"\u002Fusers\u002F{user_id}\u002Fprofile\", dependencies=[Depends(require_auth)])\nasync def get_profile(user_id: int, current_user: User = Depends(get_current_user)):\n    if current_user.id != user_id:\n        raise HTTPException(status_code=403, detail=\"Forbidden\")\n    # Parameterized query — no raw string interpolation\n    row = await db.fetchone(\"SELECT id, name, email FROM users WHERE id = ?\", (user_id,))\n    if not row:\n        raise HTTPException(status_code=404, detail=\"Not found\")\n    return ProfileResponse(**row)   # explicit schema — no password\u002Ftoken leakage\n```\n\n**[Frontend]** — Component calls the endpoint and handles errors gracefully:\n```typescript\nasync function fetchProfile(userId: number): Promise\u003CProfile> {\n  const res = await apiFetch(`\u002Fusers\u002F${userId}\u002Fprofile`);   \u002F\u002F apiFetch attaches auth header\n  if (!res.ok) throw new Error(await res.text());\n  return res.json();\n}\n\u002F\u002F Client-side input guard (never the only guard)\nif (!Number.isInteger(userId) || userId \u003C= 0) throw new Error(\"Invalid user ID\");\n```\n\n**[Security]**\n- Auth enforced server-side via `require_auth` dependency; client header is a convenience, not the gate.\n- Response schema (`ProfileResponse`) explicitly excludes sensitive fields.\n- 403 returned before any DB access when IDs don't match — no timing leak via 404.\n\n## Output Templates\n\nWhen implementing features, provide:\n1. Technical design document (if non-trivial)\n2. Backend code (models, schemas, endpoints)\n3. Frontend code (components, hooks, API calls)\n4. Brief security notes\n\n[Documentation](https:\u002F\u002Fjeffallan.github.io\u002Fclaude-skills\u002Fskills\u002Fsecurity\u002Ffullstack-guardian\u002F)\n",{"name":5,"license":14,"metadata":23,"description":7},{"role":24,"scope":25,"author":26,"domain":27,"version":28,"triggers":29,"output-format":30,"related-skills":31},"expert","implementation","https:\u002F\u002Fgithub.com\u002FJeffallan","security","1.1.1","fullstack, implement feature, build feature, create API, frontend and backend, full stack, new feature, implement, microservices, websocket, real-time, deployment pipeline, monorepo, architecture decision, technology selection, end-to-end","code","feature-forge, test-master, devops-engineer, secure-code-guardian, architecture-designer, react-expert, typescript-pro","main","cb7b4065bacb4b06224de86d509ccef568f68b79","claude-skills\u002Fskills\u002Ffullstack-guardian","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor","2026-05-29 06:53:07",{"source":8,"skillName":5,"commands":39,"prompt":49,"zipAvailable":50},[40,43,46],{"tool":41,"command":42},"npx","npx skills add andrewthomastaylor\u002FSkills --skill fullstack-guardian",{"tool":44,"command":45},"bunx","bunx skills add andrewthomastaylor\u002FSkills --skill fullstack-guardian",{"tool":47,"command":48},"pnpm","pnpm dlx skills add andrewthomastaylor\u002FSkills --skill fullstack-guardian","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Ffullstack-guardian\u002FSKILL.md",true,[52,58,62,66,70,74,78,82,86,90],{"path":53,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":56,"sourceHtmlUrl":57},"references\u002Fapi-design-standards.md","REFERENCE","参考文档",7804,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Ffullstack-guardian\u002Freferences\u002Fapi-design-standards.md",{"path":59,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":60,"sourceHtmlUrl":61},"references\u002Farchitecture-decisions.md",11854,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Ffullstack-guardian\u002Freferences\u002Farchitecture-decisions.md",{"path":63,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":64,"sourceHtmlUrl":65},"references\u002Fbackend-patterns.md",6057,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Ffullstack-guardian\u002Freferences\u002Fbackend-patterns.md",{"path":67,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":68,"sourceHtmlUrl":69},"references\u002Fcommon-patterns.md",3212,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Ffullstack-guardian\u002Freferences\u002Fcommon-patterns.md",{"path":71,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":72,"sourceHtmlUrl":73},"references\u002Fdeliverables-checklist.md",8785,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Ffullstack-guardian\u002Freferences\u002Fdeliverables-checklist.md",{"path":75,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":76,"sourceHtmlUrl":77},"references\u002Fdesign-template.md",2132,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Ffullstack-guardian\u002Freferences\u002Fdesign-template.md",{"path":79,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":80,"sourceHtmlUrl":81},"references\u002Ferror-handling.md",3397,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Ffullstack-guardian\u002Freferences\u002Ferror-handling.md",{"path":83,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":84,"sourceHtmlUrl":85},"references\u002Ffrontend-patterns.md",8805,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Ffullstack-guardian\u002Freferences\u002Ffrontend-patterns.md",{"path":87,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":88,"sourceHtmlUrl":89},"references\u002Fintegration-patterns.md",8250,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Ffullstack-guardian\u002Freferences\u002Fintegration-patterns.md",{"path":91,"resourceType":54,"resourceTypeDesc":55,"sizeBytes":92,"sourceHtmlUrl":93},"references\u002Fsecurity-checklist.md",2533,"https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fclaude-skills\u002Fskills\u002Ffullstack-guardian\u002Freferences\u002Fsecurity-checklist.md",[95,104,112,119,126,133],{"skillNo":96,"name":97,"nameZh":6,"description":98,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":99,"licenseFileUrl":100,"sourceHtmlUrl":101,"categories":102,"keywords":103,"publishedAt":18},"01M732GDQJ0CWHBAW4D7ENMA3N","skill-creator","Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fskill-creator\u002Fskills\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fskill-creator\u002Fskills\u002Fskill-creator\u002FSKILL.md",[],[],{"skillNo":105,"name":106,"nameZh":6,"description":107,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":108,"sourceHtmlUrl":109,"categories":110,"keywords":111,"publishedAt":18},"01M731QVEE2QCT389Z3X1JWFVQ","humanizer-zh","去除文本中的 AI 生成痕迹。适用于编辑或审阅文本，使其听起来更自然、更像人类书写。\n基于维基百科的\"AI 写作特征\"综合指南。检测并修复以下模式：夸大的象征意义、\n宣传性语言、以 -ing 结尾的肤浅分析、模糊的归因、破折号过度使用、三段式法则、\nAI 词汇、否定式排比、过多的连接性短语。","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fhumanizer-zh\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Fhumanizer-zh\u002FSKILL.md",[],[],{"skillNo":113,"name":114,"nameZh":6,"description":115,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":99,"licenseFileUrl":6,"sourceHtmlUrl":116,"categories":117,"keywords":118,"publishedAt":18},"01M731AMWEC72GFFNFS55F0TTC","returns-reverse-logistics","Codified expertise for returns authorization, receipt and inspection, disposition decisions, refund processing, fraud detection, and warranty claims management. Informed by returns operations managers with 15+ years experience. Includes grading frameworks, disposition economics, fraud pattern recognition, and vendor recovery processes. Use when handling product returns, reverse logistics, refund decisions, return fraud detection, or warranty claims.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Freturns-reverse-logistics\u002FSKILL.md",[],[],{"skillNo":120,"name":121,"nameZh":6,"description":122,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":99,"licenseFileUrl":6,"sourceHtmlUrl":123,"categories":124,"keywords":125,"publishedAt":18},"01M7319BJFM3CBX39C85QWSMD1","quality-nonconformance","Codified expertise for quality control, non-conformance investigation, root cause analysis, corrective action, and supplier quality management in regulated manufacturing. Informed by quality engineers with 15+ years experience across FDA, IATF 16949, and AS9100 environments. Includes NCR lifecycle management, CAPA systems, SPC interpretation, and audit methodology. Use when investigating non-conformances, performing root cause analysis, managing CAPAs, interpreting SPC data, or handling supplier quality issues.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Fquality-nonconformance\u002FSKILL.md",[],[],{"skillNo":127,"name":128,"nameZh":6,"description":129,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":99,"licenseFileUrl":6,"sourceHtmlUrl":130,"categories":131,"keywords":132,"publishedAt":18},"01M7318DPHWK6CEVCVT7PHNKDZ","production-scheduling","Codified expertise for production scheduling, job sequencing, line balancing, changeover optimization, and bottleneck resolution in discrete and batch manufacturing. Informed by production schedulers with 15+ years experience. Includes TOC\u002Fdrum-buffer-rope, SMED, OEE analysis, disruption response frameworks, and ERP\u002FMES interaction patterns. Use when scheduling production, resolving bottlenecks, optimizing changeovers, responding to disruptions, or balancing manufacturing lines.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Fproduction-scheduling\u002FSKILL.md",[],[],{"skillNo":134,"name":135,"nameZh":6,"description":136,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":99,"licenseFileUrl":6,"sourceHtmlUrl":137,"categories":138,"keywords":139,"publishedAt":18},"01M7315ZE0J0AB6KTQAFGCYF5V","logistics-exception-management","Codified expertise for handling freight exceptions, shipment delays, damages, losses, and carrier disputes. Informed by logistics professionals with 15+ years operational experience. Includes escalation protocols, carrier-specific behaviors, claims procedures, and judgment frameworks. Use when handling shipping exceptions, freight claims, delivery issues, or carrier disputes.","https:\u002F\u002Fgithub.com\u002Fandrewthomastaylor\u002FSkills\u002Fblob\u002Fmain\u002Feverything-claude-code\u002Fskills\u002Flogistics-exception-management\u002FSKILL.md",[],[]]