Task: Skill Showcase Article for the Tessl Blog

Background

The Tessl developer relations team wants to publish a showcase article that helps developers discover and evaluate skills available in the Tessl Skills Registry. The team has picked a set of skills focused on code review and static analysis as the subject. The goal is to give developers a realistic picture of what these skills do, how to install them, and what to expect from them in practice — not just a dry feature list.

The developer relations lead provided this note:

"Think of it like a 'what's in the toolbox this week' post, but with real depth. We want engineers to come away knowing which skill to reach for and roughly what it will do for them. Show the install commands, show what the output actually looks like, give them something concrete. And make sure there's a clear path to the Registry at the end."

Skills to Feature

Use the following invented (but realistic) skills for the article. You may expand on the details creatively, but keep them plausible for a code review context:

1. pr-context

• Eval score: 87/100
• Description: Adds pull request diff and linked issue context to the agent's working memory before code review tasks begin.
• Install: tessl i pr-context
• Notable: Works across GitHub and GitLab; respects .tesslignore patterns.

2. lint-annotator

• Eval score: 79/100
• Description: Runs project linters and attaches structured results as inline annotations the agent can reason over.
• Install: tessl i lint-annotator
• Notable: Supports ESLint, Ruff, and Golangci-lint out of the box.

3. test-failure-explainer

• Eval score: 91/100
• Description: Captures failing test output and produces a root-cause hypothesis the agent can act on.
• Install: tessl i test-failure-explainer
• Notable: Highest eval score in the testing category; pairs well with pr-context.

What to Write

Write a publish-ready skill showcase article for the tessl.io blog. The article should:

• Follow the skill showcase format appropriate for this blog
• Show the install commands for each skill
• Include a realistic worked example showing what the agent output looks like before and after one of these skills is active
• Help developers choose which skills suit their workflow
• End with a clear call to action pointing toward the Skills Registry

The article should be appropriate for developers who are already using Tessl agents but may not be familiar with the Skills Registry.

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.