CtrlK
BlogDocsLog inGet started
Tessl Logo

publish-plugin

Use when a composition is built and the user wants to share it, to publish or re-publish it to the Tessl registry. Lints it, confirms private/public visibility, and publishes.

92

1.31x
Quality

77%

Does it follow best practices?

Impact

95%

1.31x

Average score across 9 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugin-creator/skills/publish-plugin/SKILL.md

The canonical home for this skill is tessl/plugin-creator

SKILL.md
Quality
Evals
Security

Quality

Content

75%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured publishing workflow skill that provides concrete CLI commands, appropriate safety guardrails (visibility confirmation, provenance sensitivity, dry-run before publish), and clear sequencing. The content is mostly efficient with only minor verbosity in the introduction. The main improvement opportunity is adding explicit feedback loops for lint failure remediation and clarifying what to verify in dry-run output.

DimensionReasoningScore

Conciseness

Generally efficient and respects Claude's intelligence. Minor verbosity in the provenance section and the introductory paragraph explaining what publishing does, but most content earns its place. The note about the broader distribute workflow is somewhat unnecessary context.

4 / 5

Actionability

Provides concrete CLI commands for linting, dry-run, and publishing. Includes specific flags (--bump patch|minor|major, --dry-run) and auth requirements. Minor gaps: no example output from lint/dry-run, and the 'inspect the live CLI first' instruction is slightly vague about what to look for.

4 / 5

Workflow Clarity

Clear numbered sequence with a logical flow: confirm visibility → check provenance → lint/dry-run → publish. Includes a validation step (lint + dry-run before publish) and an undo section. Minor gap: no explicit feedback loop for fixing lint errors (just 'Fix all issues'), and the dry-run step doesn't specify what to check in the output.

4 / 5

Progressive Disclosure

Well-structured with clear sections for each step, undo procedures, and stopping conditions. References to external tools (tessl/skill-optimizer) are appropriately signaled. For a skill of this size (~40 lines of content), the structure is appropriate without needing separate files. Minor gap: the reference to skill-optimizer could be a clearer link.

4 / 5

Total

16

/

20

Passed

Description

80%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a well-structured description that clearly communicates both the trigger conditions and the specific actions performed. Its main weakness is moderate trigger term coverage — it could benefit from additional natural language synonyms users might use. The domain-specific terminology (Tessl registry, composition) makes it highly distinctive.

Suggestions

Add natural synonyms users might say, such as 'deploy', 'release', 'upload', or 'push' alongside 'publish' and 'share'.

DimensionReasoningScore

Specificity

Lists several specific actions: linting, confirming visibility (private/public), and publishing/re-publishing to a registry. Minor gaps — doesn't elaborate on what 'composition' entails or what linting checks.

4 / 5

Completeness

Clearly answers both 'what' (lints, confirms visibility, publishes to Tessl registry) and 'when' (when a composition is built and the user wants to share/publish it), with explicit trigger guidance at the start.

5 / 5

Trigger Term Quality

Includes relevant terms like 'publish', 'share', 'registry', 'Tessl', and 'composition', but misses natural synonyms users might say such as 'deploy', 'upload', 'release', or 'push to registry'.

3 / 5

Distinctiveness Conflict Risk

Highly distinctive due to the specific domain ('Tessl registry', 'composition') and the narrow workflow (lint → confirm visibility → publish). Very unlikely to conflict with other skills.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository
tesslio/product-plugins
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.