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/drum-buffer-rope, SMED, OEE analysis, disruption response frameworks, and ERP/MES interaction patterns. Use when scheduling production, resolving bottlenecks, optimizing changeovers, responding to disruptions, or balancing manufacturing lines.

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a dense, actionable codification of scheduling expertise with clear sequenced workflows and concrete thresholds, but it is verbose (re-explaining concepts Claude knows) and monolithic with no progressive disclosure structure.

Suggestions

Trim re-explanations of widely-known concepts (e.g., the OEE formula, SMED phase definitions, basic DBR/TOC) down to the plant-specific thresholds and decision rules Claude would not already know.

Split the 'Key Edge Cases', 'Communication Patterns' templates, and 'Performance Indicators' tables into referenced files (e.g., EDGE_CASES.md, TEMPLATES.md) and link them one level deep from SKILL.md to enable progressive disclosure.

Move the ERP/MES interaction patterns and OEE fundamentals into a reference file, keeping SKILL.md as a concise overview pointing to the detailed material.

Dimension	Reasoning	Score
Conciseness	The ~240-line body restates well-known concepts Claude already knows (DBR/TOC definitions, the OEE = Availability × Performance × Quality formula, SMED phases, EDD/SPT) and could be tightened, though it is information-dense with concrete thresholds rather than generic filler.	2 / 3
Actionability	Provides highly concrete, executable guidance for an instruction-only skill: numbered decision trees, specific dispatching rules, numerical targets (e.g., '>85% utilization is your drum', 'buffer consumed <33%'), and copy-ready escalation tables with timelines.	3 / 3
Workflow Clarity	Multi-step processes are explicitly sequenced with validation checkpoints — 'How It Works' (6 steps), disruption re-sequencing with 'Validate against due dates', 'Communicate within 30 minutes', and a 4-hour 'stability lock' feedback loop.	3 / 3
Progressive Disclosure	A monolithic single file with no bundle files or one-level-deep references; the 'Key Edge Cases' section gestures at expanding into separate playbooks but nothing is split out, so well-organized content that could be separated remains inline.	2 / 3
	Total	10 / 12 Passed

Description

100%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific, trigger-rich, and complete with an explicit 'Use when' clause and a well-defined manufacturing niche. It avoids vague fluff and uses third person throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'production scheduling, job sequencing, line balancing, changeover optimization, and bottleneck resolution' plus 'TOC/drum-buffer-rope, SMED, OEE analysis, disruption response frameworks, and ERP/MES interaction patterns' — and uses third person throughout.	3 / 3
Completeness	Clearly answers both 'what' (codified expertise and the listed frameworks) and 'when' via an explicit 'Use when...' trigger clause, meeting the top anchor.	3 / 3
Trigger Term Quality	Natural user-facing terms appear in the explicit 'Use when scheduling production, resolving bottlenecks, optimizing changeovers, responding to disruptions, or balancing manufacturing lines' clause, matching phrases a user would actually say.	3 / 3
Distinctiveness Conflict Risk	Scoped to 'discrete and batch manufacturing' production scheduling with distinct triggers, making it unlikely to fire for unrelated skills.	3 / 3
	Total	12 / 12 Passed

Validation

81%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 13 / 16 Passed

Validation for skill structure

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	13 / 16 Passed

Repository: affaan-m/ECC
Commit: 754b8dd

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.