If a skill's YAML front matter was invalid — most often an unquoted : inside a description — the skill was skipped while the portal started up perfectly. Nothing was logged, nothing turned red, and the only symptom was that the slash command had quietly disappeared from the menu.

Skipping is still the right behaviour: one bad file must never stop the portal from starting. But the skip is no longer silent. The file is now named in the log, together with the reason and the usual cause, so a broken skill takes seconds to find instead of being invisible.

The same guarantee already applied to agents; skills now match it.

Reconnecting…
The server was updated. Reloading the page to pick up the latest version.