AD fjsp-baseline-repair-with-downtime-and-policy
This skill should be considered when you need to repair an infeasible or non-optimal flexible job scheduling planning schedule into a downtime-feasible, precedence-feasible one while keep no worse policy budget.
As a process D 40/100 · Unfinished process — weak spots: steps, result and completion, when it triggers
How to improve
For the model run — optional
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 2. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 40/100
- 0Steps. Prose only: no discrete steps
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 40Consistency. Frontmatter name (fjsp-baseline-repair-with-downtime-and-policy) differs from the folder (manufacturing-fjsp-optimization-fjsp-baseline-repair-with-downtime-and-policy)
- 60Failures and branches. 2 branches
- 100Tools and files. No external tools needed
- 100Execution cost. Instruction body is 1133 tokens
- 100Running it twice. No mutating operations
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +4Structure: 0 headings, hard to scan
- +3No numbered steps or checklist
- +3Output format is not stated: the model decides each time
- +1No license
- +2Single-language instructions
- +3Description length 211: enough signal without eating the budget
- +4Has examples (7 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 77.
External checks
ClawHub: clean
This is an instruction-only scheduling helper with no executable code, credential use, persistence, or external data access.
LLM: benign (high) · VirusTotal: · 29 May 2026