[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6C2TY22NSS99G19BMKZJY7A":3,"skill-same:01M6C2TY22NSS99G19BMKZJY7A":92},{"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":16,"sourceHtmlUrl":17,"categories":18,"keywords":29,"publishedAt":50,"linkOnly":51,"markdownContent":52,"markdownBody":53,"frontMatter":54,"refName":61,"commitSha":62,"skillDirectory":63,"forksCount":14,"repositoryHtmlUrl":64,"repositoryHomepageUrl":6,"ownerHtmlUrl":65,"ownerBlogUrl":6,"ownerDescription":66,"updatedAt":67,"install":68,"resources":80},"01M6C2TY22NSS99G19BMKZJY7A","seo-schema",null,"Detect, validate, and generate Schema.org structured data. JSON-LD format preferred. Use when user says \"schema\", \"structured data\", \"rich results\", \"JSON-LD\", or \"markup\".","noirelab\u002Flinux-setup","noirelab","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F142925921?v=4","01M6C29R3FEDGFAXAT0KXY28QX","Kaíque M. Lima","01M6C29R811WX04B0GYHTH1XV6",0,"MIT","https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fopencode\u002Fskills\u002Fseo-schema\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fopencode\u002Fskills\u002Fseo-schema\u002FSKILL.md",[19,24],{"categoryNo":20,"categoryName":21,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000019","营销推广","SCENARIO","使用场景",{"categoryNo":25,"categoryName":26,"taxonomyType":27,"taxonomyTypeDesc":28},"01JBSEEDCAT000000000000035","市场营销","PROFESSION","适用职业",[30,31,32,33,34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49],"seo","schema","seo schema","when","structured data","rich","true","ld","URL","org","detect","json-ld","use","user","results","format","json","data","generate","validate","2026-11-10 10:12:30",false,"---\nname: seo-schema\ndescription: >\n  Detect, validate, and generate Schema.org structured data. JSON-LD format\n  preferred. Use when user says \"schema\", \"structured data\", \"rich results\",\n  \"JSON-LD\", or \"markup\".\nuser-invocable: true\nargument-hint: \"[url]\"\nlicense: MIT\nmetadata:\n  author: AgriciDaniel\n  version: \"2.2.4\"\n  category: seo\n---\n\n# Schema Markup Analysis & Generation\n\n## Detection\n\n1. Scan page source for JSON-LD `\u003Cscript type=\"application\u002Fld+json\">`\n2. Check for Microdata (`itemscope`, `itemprop`)\n3. Check for RDFa (`typeof`, `property`)\n4. Always recommend JSON-LD as primary format (Google's stated preference)\n\n## Validation\n\n- Check required properties per schema type\n- Validate against Google's supported rich result types\n- Test for common errors:\n  - Missing @context\n  - Invalid @type\n  - Wrong data types\n  - Placeholder text\n  - Relative URLs (should be absolute)\n  - Invalid date formats\n- Flag deprecated types (see below)\n\n## Schema Type Status (as of June 2026)\n\nRead `..\u002Fseo\u002Freferences\u002Fschema-types.md` for the full list. Key rules:\n\n### ACTIVE (recommend freely):\nOrganization, LocalBusiness, SoftwareApplication, WebApplication, Product (with Certification markup as of April 2025), ProductGroup, Offer, Service, Article, BlogPosting, NewsArticle, Review, AggregateRating, BreadcrumbList, WebSite, WebPage, Person, ProfilePage, ContactPage, VideoObject, ImageObject, Event, JobPosting, Course, DiscussionForumPosting\n\n### VIDEO & SPECIALIZED (recommend freely):\nBroadcastEvent, Clip, SeekToAction, SoftwareSourceCode\n\nSee `schema\u002Ftemplates.json` for ready-to-use JSON-LD templates for these types.\n\n> **JSON-LD and JavaScript rendering:** Per Google's December 2025 JS SEO guidance, structured data injected via JavaScript may face delayed processing. For time-sensitive markup (especially Product, Offer), include JSON-LD in the initial server-rendered HTML.\n\n### NO RICH RESULTS, KEEP IF USEFUL:\n- **FAQPage**: Google retired FAQ rich results for ALL sites on May 7, 2026 (supersedes the Aug 2023 gov\u002Fhealth restriction). No Google SERP rich-result benefit; flag existing FAQPage at Info (not Critical) rather than removal. For genuine user Q&A pages, use **QAPage**.\n\n### DEPRECATED (never recommend):\n- **HowTo**: Rich results removed September 2023\n- **SpecialAnnouncement**: Deprecated July 31, 2025\n- **CourseInfo, EstimatedSalary, LearningVideo**: Retired June 2025\n- **ClaimReview**: Retired from rich results June 2025\n- **VehicleListing**: Retired from rich results June 2025\n- **Practice Problem**: Deprecation notice 2025-11-05; Search Console \u002F Rich Results Test support removed 2026-01-06\n- **Book Actions**: Deprecated\u002Fremoved from Google rich results; do not recommend it for SERP features.\n- Search Console \u002F Rich Results Test \u002F appearance-filter support for CourseInfo, EstimatedSalary, LearningVideo, SpecialAnnouncement, VehicleListing was removed 2025-09-09; Practice Problem support was removed 2026-01-06.\n\n### Supported for Dataset Search only:\n- **Dataset**: Not discontinued; consumed by Google Dataset Search, with no Google Search rich-result surface. Don't advise removal as if it were killed.\n\n### Still supported (do not flag):\n- QAPage (expanded comment-thread properties 2026-03-24), DiscussionForumPosting, Education Q&A (Quiz \u002F `eduQuestionType=Flashcard`). For e-commerce, **hasAdultConsideration** (added 2026-05-22; value `https:\u002F\u002Fschema.org\u002FSexualContentConsideration`) is required for adult products.\n\n## Generation\n\nWhen generating schema for a page:\n1. Identify page type from content analysis\n2. Select appropriate schema type(s)\n3. Generate valid JSON-LD with all required + recommended properties\n4. Include only truthful, verifiable data. Use placeholders clearly marked for user to fill\n5. Validate output before presenting\n\n## Common Schema Templates\n\n### Organization\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"Organization\",\n  \"name\": \"[Company Name]\",\n  \"url\": \"[Website URL]\",\n  \"logo\": \"[Logo URL]\",\n  \"contactPoint\": {\n    \"@type\": \"ContactPoint\",\n    \"telephone\": \"[Phone]\",\n    \"contactType\": \"customer service\"\n  },\n  \"sameAs\": [\n    \"[Facebook URL]\",\n    \"[LinkedIn URL]\",\n    \"[Twitter URL]\"\n  ]\n}\n```\n\n### LocalBusiness\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"LocalBusiness\",\n  \"name\": \"[Business Name]\",\n  \"address\": {\n    \"@type\": \"PostalAddress\",\n    \"streetAddress\": \"[Street]\",\n    \"addressLocality\": \"[City]\",\n    \"addressRegion\": \"[State]\",\n    \"postalCode\": \"[ZIP]\",\n    \"addressCountry\": \"US\"\n  },\n  \"telephone\": \"[Phone]\",\n  \"openingHours\": \"Mo-Fr 09:00-17:00\",\n  \"geo\": {\n    \"@type\": \"GeoCoordinates\",\n    \"latitude\": \"[Lat]\",\n    \"longitude\": \"[Long]\"\n  }\n}\n```\n\n### Article\u002FBlogPosting\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"Article\",\n  \"headline\": \"[Title]\",\n  \"author\": {\n    \"@type\": \"Person\",\n    \"name\": \"[Author Name]\"\n  },\n  \"datePublished\": \"[YYYY-MM-DD]\",\n  \"dateModified\": \"[YYYY-MM-DD]\",\n  \"image\": \"[Image URL]\",\n  \"publisher\": {\n    \"@type\": \"Organization\",\n    \"name\": \"[Publisher]\",\n    \"logo\": {\n      \"@type\": \"ImageObject\",\n      \"url\": \"[Logo URL]\"\n    }\n  }\n}\n```\n\n## Output\n\n- `SCHEMA-REPORT.md`: detection and validation results\n- `generated-schema.json`: ready-to-use JSON-LD snippets\n\n### Validation Results\n| Schema | Type | Status | Issues |\n|--------|------|--------|--------|\n| ... | ... | ✅\u002F⚠️\u002F❌ | ... |\n\n### Recommendations\n- Missing schema opportunities\n- Validation fixes needed\n- Generated code for implementation\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| URL unreachable | Report connection error with status code. Suggest verifying URL and checking if the page requires authentication. |\n| No schema markup found | Report that no JSON-LD, Microdata, or RDFa was detected. Recommend appropriate schema types based on page content analysis. |\n| Invalid JSON-LD syntax | Parse and report specific syntax errors (missing brackets, trailing commas, unquoted keys). Provide corrected JSON-LD output. |\n| Deprecated schema type detected | Flag the deprecated type with its retirement date. Recommend the current replacement type or advise removal if no replacement exists. |\n","# Schema Markup Analysis & Generation\n\n## Detection\n\n1. Scan page source for JSON-LD `\u003Cscript type=\"application\u002Fld+json\">`\n2. Check for Microdata (`itemscope`, `itemprop`)\n3. Check for RDFa (`typeof`, `property`)\n4. Always recommend JSON-LD as primary format (Google's stated preference)\n\n## Validation\n\n- Check required properties per schema type\n- Validate against Google's supported rich result types\n- Test for common errors:\n  - Missing @context\n  - Invalid @type\n  - Wrong data types\n  - Placeholder text\n  - Relative URLs (should be absolute)\n  - Invalid date formats\n- Flag deprecated types (see below)\n\n## Schema Type Status (as of June 2026)\n\nRead `..\u002Fseo\u002Freferences\u002Fschema-types.md` for the full list. Key rules:\n\n### ACTIVE (recommend freely):\nOrganization, LocalBusiness, SoftwareApplication, WebApplication, Product (with Certification markup as of April 2025), ProductGroup, Offer, Service, Article, BlogPosting, NewsArticle, Review, AggregateRating, BreadcrumbList, WebSite, WebPage, Person, ProfilePage, ContactPage, VideoObject, ImageObject, Event, JobPosting, Course, DiscussionForumPosting\n\n### VIDEO & SPECIALIZED (recommend freely):\nBroadcastEvent, Clip, SeekToAction, SoftwareSourceCode\n\nSee `schema\u002Ftemplates.json` for ready-to-use JSON-LD templates for these types.\n\n> **JSON-LD and JavaScript rendering:** Per Google's December 2025 JS SEO guidance, structured data injected via JavaScript may face delayed processing. For time-sensitive markup (especially Product, Offer), include JSON-LD in the initial server-rendered HTML.\n\n### NO RICH RESULTS, KEEP IF USEFUL:\n- **FAQPage**: Google retired FAQ rich results for ALL sites on May 7, 2026 (supersedes the Aug 2023 gov\u002Fhealth restriction). No Google SERP rich-result benefit; flag existing FAQPage at Info (not Critical) rather than removal. For genuine user Q&A pages, use **QAPage**.\n\n### DEPRECATED (never recommend):\n- **HowTo**: Rich results removed September 2023\n- **SpecialAnnouncement**: Deprecated July 31, 2025\n- **CourseInfo, EstimatedSalary, LearningVideo**: Retired June 2025\n- **ClaimReview**: Retired from rich results June 2025\n- **VehicleListing**: Retired from rich results June 2025\n- **Practice Problem**: Deprecation notice 2025-11-05; Search Console \u002F Rich Results Test support removed 2026-01-06\n- **Book Actions**: Deprecated\u002Fremoved from Google rich results; do not recommend it for SERP features.\n- Search Console \u002F Rich Results Test \u002F appearance-filter support for CourseInfo, EstimatedSalary, LearningVideo, SpecialAnnouncement, VehicleListing was removed 2025-09-09; Practice Problem support was removed 2026-01-06.\n\n### Supported for Dataset Search only:\n- **Dataset**: Not discontinued; consumed by Google Dataset Search, with no Google Search rich-result surface. Don't advise removal as if it were killed.\n\n### Still supported (do not flag):\n- QAPage (expanded comment-thread properties 2026-03-24), DiscussionForumPosting, Education Q&A (Quiz \u002F `eduQuestionType=Flashcard`). For e-commerce, **hasAdultConsideration** (added 2026-05-22; value `https:\u002F\u002Fschema.org\u002FSexualContentConsideration`) is required for adult products.\n\n## Generation\n\nWhen generating schema for a page:\n1. Identify page type from content analysis\n2. Select appropriate schema type(s)\n3. Generate valid JSON-LD with all required + recommended properties\n4. Include only truthful, verifiable data. Use placeholders clearly marked for user to fill\n5. Validate output before presenting\n\n## Common Schema Templates\n\n### Organization\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"Organization\",\n  \"name\": \"[Company Name]\",\n  \"url\": \"[Website URL]\",\n  \"logo\": \"[Logo URL]\",\n  \"contactPoint\": {\n    \"@type\": \"ContactPoint\",\n    \"telephone\": \"[Phone]\",\n    \"contactType\": \"customer service\"\n  },\n  \"sameAs\": [\n    \"[Facebook URL]\",\n    \"[LinkedIn URL]\",\n    \"[Twitter URL]\"\n  ]\n}\n```\n\n### LocalBusiness\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"LocalBusiness\",\n  \"name\": \"[Business Name]\",\n  \"address\": {\n    \"@type\": \"PostalAddress\",\n    \"streetAddress\": \"[Street]\",\n    \"addressLocality\": \"[City]\",\n    \"addressRegion\": \"[State]\",\n    \"postalCode\": \"[ZIP]\",\n    \"addressCountry\": \"US\"\n  },\n  \"telephone\": \"[Phone]\",\n  \"openingHours\": \"Mo-Fr 09:00-17:00\",\n  \"geo\": {\n    \"@type\": \"GeoCoordinates\",\n    \"latitude\": \"[Lat]\",\n    \"longitude\": \"[Long]\"\n  }\n}\n```\n\n### Article\u002FBlogPosting\n```json\n{\n  \"@context\": \"https:\u002F\u002Fschema.org\",\n  \"@type\": \"Article\",\n  \"headline\": \"[Title]\",\n  \"author\": {\n    \"@type\": \"Person\",\n    \"name\": \"[Author Name]\"\n  },\n  \"datePublished\": \"[YYYY-MM-DD]\",\n  \"dateModified\": \"[YYYY-MM-DD]\",\n  \"image\": \"[Image URL]\",\n  \"publisher\": {\n    \"@type\": \"Organization\",\n    \"name\": \"[Publisher]\",\n    \"logo\": {\n      \"@type\": \"ImageObject\",\n      \"url\": \"[Logo URL]\"\n    }\n  }\n}\n```\n\n## Output\n\n- `SCHEMA-REPORT.md`: detection and validation results\n- `generated-schema.json`: ready-to-use JSON-LD snippets\n\n### Validation Results\n| Schema | Type | Status | Issues |\n|--------|------|--------|--------|\n| ... | ... | ✅\u002F⚠️\u002F❌ | ... |\n\n### Recommendations\n- Missing schema opportunities\n- Validation fixes needed\n- Generated code for implementation\n\n## Error Handling\n\n| Scenario | Action |\n|----------|--------|\n| URL unreachable | Report connection error with status code. Suggest verifying URL and checking if the page requires authentication. |\n| No schema markup found | Report that no JSON-LD, Microdata, or RDFa was detected. Recommend appropriate schema types based on page content analysis. |\n| Invalid JSON-LD syntax | Parse and report specific syntax errors (missing brackets, trailing commas, unquoted keys). Provide corrected JSON-LD output. |\n| Deprecated schema type detected | Flag the deprecated type with its retirement date. Recommend the current replacement type or advise removal if no replacement exists. |\n",{"name":5,"license":15,"metadata":55,"description":58,"argument-hint":59,"user-invocable":60},{"author":56,"version":57,"category":30},"AgriciDaniel","2.2.4","Detect, validate, and generate Schema.org structured data. JSON-LD format preferred. Use when user says \"schema\", \"structured data\", \"rich results\", \"JSON-LD\", or \"markup\".\n","[url]",true,"main","d8378e461d60315bd1ca8a6e71716df39b6abe4a","configs\u002Fcommon\u002Fopencode\u002Fskills\u002Fseo-schema","https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup","https:\u002F\u002Fgithub.com\u002Fnoirelab","Artificial Intelligence Researcher |\r\nComputer Science majoring at UTFPR","2026-11-11 09:12:51",{"source":8,"skillName":5,"commands":69,"prompt":79,"zipAvailable":60},[70,73,76],{"tool":71,"command":72},"npx","npx skills add noirelab\u002Flinux-setup --skill seo-schema",{"tool":74,"command":75},"bunx","bunx skills add noirelab\u002Flinux-setup --skill seo-schema",{"tool":77,"command":78},"pnpm","pnpm dlx skills add noirelab\u002Flinux-setup --skill seo-schema","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fopencode\u002Fskills\u002Fseo-schema\u002FSKILL.md",[81,86],{"path":82,"resourceType":83,"resourceTypeDesc":84,"sizeBytes":85,"sourceHtmlUrl":16},"LICENSE.txt","LICENSE","许可证",143,{"path":87,"resourceType":88,"resourceTypeDesc":89,"sizeBytes":90,"sourceHtmlUrl":91},"references\u002Fdeprecated-types-2024-2026.md","REFERENCE","参考文档",5061,"https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fopencode\u002Fskills\u002Fseo-schema\u002Freferences\u002Fdeprecated-types-2024-2026.md",[93,124,159,184,204,220],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":98,"sourceHtmlUrl":99,"categories":100,"keywords":104,"publishedAt":50},"01M6C2Q1S6HCS7Y9TBQ2PJ2NAM","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\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fclaude\u002Fskills\u002Fsynced\u002Ffcfa9261-0073-49cb-8312-19eea68f0c58_391f3767-a35d-4280-81a1-363cd861a8e6\u002Fskill-creator\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fclaude\u002Fskills\u002Fsynced\u002Ffcfa9261-0073-49cb-8312-19eea68f0c58_391f3767-a35d-4280-81a1-363cd861a8e6\u002Fskill-creator\u002FSKILL.md",[101],{"categoryNo":102,"categoryName":103,"taxonomyType":22,"taxonomyTypeDesc":23},"01JBSEEDCAT000000000000023","Skill与智能体开发",[105,106,107,108,109,110,111,112,113,114,115,116,42,117,118,119,120,121,122,33,123],"skill creator","creator","performance","run evals","test","variance analysis","create","run","benchmark","analysis","improve","edit","evals","optimize","existing skill","for","accuracy","scratch","new",{"skillNo":125,"name":126,"nameZh":6,"description":127,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":128,"categories":129,"keywords":130,"publishedAt":50},"01M6C2ZRGJ9HN4N9BP24DPNCR4","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\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fopencode_home\u002Fskills\u002Freturns-reverse-logistics\u002FSKILL.md",[],[131,132,133,134,135,136,137,138,139,140,141,142,143,144,145,146,42,147,148,149,150,151,152,153,154,155,120,156,157,33,158],"returns","returns reverse logistics","reverse logistics","reverse","github","code","product","https","authorization","detection","fraud","recovery","decisions","management","operations","vendor","claims management","frameworks","fraud detection","pattern","grading","processing","economics","managers","claims","expertise","refund","inspection",{"skillNo":160,"name":161,"nameZh":6,"description":162,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":163,"categories":164,"keywords":165,"publishedAt":50},"01M6C2ZGWSNZGZZQ5VCFWHD2QT","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\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fopencode_home\u002Fskills\u002Fquality-nonconformance\u002FSKILL.md",[],[166,167,135,168,169,136,170,138,171,47,172,173,114,174,144,42,175,176,177,178,179,180,181,182,120,156,183,33],"quality","quality nonconformance","root cause analysis","interpretation","issues","audit","methodology","lifecycle","investigation","fda","across","manufacturing","environments","corrective action","supplier quality management","action","conformance","root cause",{"skillNo":185,"name":186,"nameZh":6,"description":187,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":188,"categories":189,"keywords":190,"publishedAt":50},"01M6C2Z8VQ9AYZYKPZW1KD9DX5","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\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fopencode_home\u002Fskills\u002Fproduction-scheduling\u002FSKILL.md",[],[191,192,193,135,136,194,138,195,114,196,197,42,198,199,148,200,201,202,177,203,120,156,33],"Production","production scheduling","scheduling","batch","Optimization","erp","bottleneck","toc","patterns","line","interaction","sequencing","buffer",{"skillNo":205,"name":206,"nameZh":6,"description":207,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":208,"categories":209,"keywords":210,"publishedAt":50},"01M6C2YR01NNN2Z1G18RN7F9MP","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\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fopencode_home\u002Fskills\u002Flogistics-exception-management\u002FSKILL.md",[],[144,211,135,136,212,170,213,138,214,42,148,215,216,217,218,155,120,156,219,33],"logistics exception management","shipping","protocols","escalation","delivery","claude-code","judgment","with","freight",{"skillNo":221,"name":222,"nameZh":6,"description":223,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":97,"licenseFileUrl":6,"sourceHtmlUrl":224,"categories":225,"keywords":226,"publishedAt":50},"01M6C2YC5PXTEJYBJJQZVXPQS0","inventory-demand-planning","Codified expertise for demand forecasting, safety stock optimization, replenishment planning, and promotional lift estimation at multi-location retailers. Informed by demand planners with 15+ years experience managing hundreds of SKUs. Includes forecasting method selection, ABC\u002FXYZ analysis, seasonal transition management, and vendor negotiation frameworks. Use when forecasting demand, setting safety stock, planning replenishment, managing promotions, or optimizing inventory levels.","https:\u002F\u002Fgithub.com\u002Fnoirelab\u002Flinux-setup\u002Fblob\u002Fmain\u002Fconfigs\u002Fcommon\u002Fopencode_home\u002Fskills\u002Finventory-demand-planning\u002FSKILL.md",[],[227,228,229,230,135,136,138,231,195,232,114,144,146,233,42,234,148,235,236,237,238,239,120,156,240,33],"planning","inventory","inventory demand planning","demand planning","negotiation","Safety","forecasting","selection","estimation","stock","seasonal","lift","at","transition"]