Task: Article on Skill Filename Conventions

Background

The Tessl content team is producing a short series of focused pieces for the engineering blog. Each piece is meant to argue a single sharp idea that an engineer could read on a coffee break and walk away with a small, actionable opinion change. The content lead has asked for the first piece in the series.

The content lead's brief:

"I want a piece that argues skill filenames need to be self-explanatory without reading the contents — that 'commands.md' is a code smell and 'script_parameters.md' is the standard. Make it a tight, opinionated read. This is for the tessl.io engineering blog and should be publish-ready with full metadata. The series is going to be a regular fixture so we want it to feel substantial, not throwaway."

The audience is engineers who write or maintain skills.

What to Write

Write a publish-ready article for the tessl.io blog that argues the case for self-explanatory skill filenames. Include all metadata needed to publish directly. Pick whichever article type best fits the topic and its natural depth, and structure accordingly.

Output Specification

Save the completed article as article.md in the current working directory. The file must include a metadata block at the top (title, type, primary keyword, meta description, URL slug, internal links, estimated read time) followed by the full article body in markdown.