CtrlK
BlogDocsLog inGet started
Tessl Logo

production-scheduling

Codified expertise for production scheduling, job sequencing, line balancing, changeover optimisation, and bottleneck resolution in discrete and batch manufacturing.

64

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/production-scheduling/SKILL.md

The canonical home for this skill is production-scheduling in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

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 well-structured, actionable codification of production-scheduling expertise with excellent progressive disclosure to three reference files. Its main weakness is length: some sections re-explain manufacturing concepts Claude already knows.

Suggestions

Trim definitional explanations of widely-known concepts (e.g. what forward/backward scheduling and finite/infinite capacity are) down to the operational decision rules that follow them.

Condense the OEE calculation block to the formula plus targets, moving the extended loss-type exposition to a reference if needed.

Consider moving the full Communication Patterns and Escalation tables to communication-templates.md, keeping only the tone-calibration summary in SKILL.md.

DimensionReasoningScore

Conciseness

The body is dense and mostly earns its tokens via expert operational detail (buffer zones, escalation timelines, heuristics), but several sections explain broadly-known concepts (forward/backward scheduling, finite/infinite capacity, the OEE formula) that could be trimmed.

3 / 5

Actionability

Highly concrete, actionable guidance — numbered decision trees, specific thresholds (33/67% buffer zones, >85% utilisation), 2-opt improvement steps, and exact KPI targets — with only minor gaps versus strictly executable procedures.

4 / 5

Workflow Clarity

The four Decision Frameworks are clearly sequenced numbered procedures with validation checkpoints ('Validate against due dates', causal bottleneck verification, stability lock), leaving only minor validation gaps.

4 / 5

Progressive Disclosure

A clear overview with three real, well-signaled, one-level-deep references (edge-cases.md, communication-templates.md, decision-frameworks.md); deep material is split out while summaries remain in the body.

5 / 5

Total

16

/

20

Passed

Description

82%Weight 40%Scale 1-5

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, distinctive, and rich in natural trigger terms, but it omits any explicit 'when to use' guidance, which caps completeness. Adding a Use-when clause would lift it to a top-tier description.

Suggestions

Append an explicit trigger clause, e.g. 'Use when planning manufacturing operations, sequencing jobs, balancing lines, resolving bottlenecks, or responding to shop-floor disruptions.'

Add a couple of natural synonyms users might say ('shop floor scheduling', 'APS', 'production planning') to broaden trigger coverage.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'production scheduling, job sequencing, line balancing, changeover optimisation, and bottleneck resolution' scoped to 'discrete and batch manufacturing' — matching the comprehensive-coverage anchor.

5 / 5

Completeness

The 'what' is clear and specific, but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 3.

3 / 5

Trigger Term Quality

Natural trigger phrases a user would actually say ('production scheduling', 'job sequencing', 'line balancing', 'bottleneck') are comprehensively covered; the domain has no file extensions to include.

5 / 5

Distinctiveness Conflict Risk

A clear manufacturing-scheduling niche with distinct, domain-specific triggers and minimal overlap risk with other skills.

5 / 5

Total

18

/

20

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
Reviewed

Table of Contents

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.