product-plugins

Use during build when a skill or a problem is too big for one skill - a sprawling SKILL.md doing several jobs, or a large problem the user wants a single skill for. Splits it into focused, independently-verifiable skills, with a plugin as the superstructure that holds them together.

Use when someone wants to turn a problem, a messy or sprawling skill, or some existing work into well-shaped reusable context for their agent. Triggers include "help me make a skill for X", "my skill is a mess, sort it out", "I want to get more out of Tessl with this skill", or "package this so my team can use it". Runs the arc - understand the problem, gather the artifacts, plan the right composition, build it - then points to eval as a separate next step.

Use when reviewing a pull request, to check for logic bugs, style consistency, and security concerns and summarise the findings for the author.

Database administration tasks including schema changes, backups, monitoring, and user access management.

Evaluate a SKILL.md for quality. An agent that dynamically discovers the rubric files and scores the skill against each, producing one result per rubric. Use when running a skill review workflow or testing skill quality against configurable rubrics.

Find and call Tessl API endpoints. Use this WHENEVER you need a Tessl REST API endpoint — to discover which endpoint does something, to learn an endpoint's path, parameters, request body shape, or response shape, or to actually call the Tessl API. Reach for this skill INSTEAD OF reading the raw `openapi.json` spec.

Add an endpoint to the backend.

Use once there is a confirmed composition plan, to create it. Scaffolds the plugin, authors or restructures the skills, and adds the rules, hooks, MCP servers, or commands the plan called for. Uses the CLI to scaffold the plugin, then authors the planned composition.