CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

baume-deploy

Deploy the Baume MCP server to Fly.io with correct build context

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/baume-deploy/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

72%Weight 40%Scale 1-5

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

This is a highly actionable, token-efficient operational runbook: every command is copy-paste ready and the deploy checklist includes real verification steps. The main gaps are the missing validation/confirmation around destructive operations (destroy, scale-to-zero), which caps workflow clarity, and the monolithic single-file structure with no progressive disclosure for reference material.

Suggestions

Add a validation/confirmation step before destructive commands, e.g. 'Before fly apps destroy or scale count 0, run fly status -a baume-mcp and confirm the app name with the user' — this would lift the workflow-clarity cap.

Move the env-variable table, debugging recipes, and resource-management commands into one-level-deep reference files (e.g. references/env-vars.md, references/debugging.md) linked from short summary sections in SKILL.md.

Deduplicate the deploy command and health-check curl (each appears 3 times across sections) to tighten token efficiency.

DimensionReasoningScore

Conciseness

The body is dominated by lean, commented command blocks with no padding or explanations of concepts Claude already knows. Minor redundancy keeps it from 5: the deploy command is repeated across the 'Correct Command', 'Deploy', and 'Deployment Checklist' sections, and the health-check curl appears three times.

4 / 5

Actionability

Every section provides fully executable, copy-paste-ready commands with the app flag, real URLs, and concrete values (deploy, status, logs, secrets, SSH, machine inspection, local Docker build, postgres, storage, scaling). Matches the 'fully executable, covers common cases' anchor.

5 / 5

Workflow Clarity

The Deployment Checklist provides a clear sequence with explicit validation (verify secrets, check logs, curl health and MCP endpoints) and a build-failure feedback loop, which alone would merit 5. However, the skill includes destructive operations ('fly apps destroy baume-mcp' marked only '(DANGEROUS)', 'fly scale count 0') with no validation or confirmation steps, and the rubric explicitly caps workflow clarity at 3 for destructive operations without validation.

3 / 5

Progressive Disclosure

The body is a well-sectioned single-file runbook with no bundle files or external references. Section headers make it navigable, but ~255 lines of inline content (env-var table, debugging recipes, resource management) that could be split into one-level-deep reference files keeps it at 'some structure, content that could be separate is inline'. Not 2 because structure is genuinely good; not 4 because nothing is offloaded and the file is well over the ~50-line simple-skill threshold.

3 / 5

Total

15

/

20

Passed

Description

57%Weight 40%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.

The description is precise and unambiguous about its niche but undersized relative to what the skill does. It states a single action (deploy) with no 'Use when...' trigger clause, so it both under-informs triggering and under-advertises the operational coverage (status, secrets, scaling, debugging) the body actually provides.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user wants to deploy or update the Baume MCP server on Fly.io, check deployment status, or fix build/deployment issues.'

Mention the additional operations the skill covers (secrets, scaling, postgres/storage management, runtime debugging) so the description matches the body's scope and captures those trigger terms.

Include natural user phrasings such as 'fly deploy', 'deployment fails', or 'Fly.io logs' to improve trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('Baume MCP server', 'Fly.io') and one concrete action ('Deploy') with the qualifier 'with correct build context', but does not list several specific actions, matching the '1-2 concrete actions, not comprehensive' anchor. Not 4 because operations the skill actually covers (update, status, secrets, scaling, debugging) are absent from the description.

3 / 5

Completeness

The 'what' is clear (deploy the Baume MCP server to Fly.io with correct build context), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which the rubric explicitly caps at 3. Not 4 because the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

'Deploy', 'Fly.io', and 'MCP server' are natural terms a user would say, but coverage is narrow: common variations users would naturally utter ('update the deployment', 'check status', 'fly logs', 'troubleshoot') are missing. Fits the 'some relevant keywords but missing common variations' anchor.

3 / 5

Distinctiveness Conflict Risk

The combination of a named application ('Baume MCP server') and a named platform ('Fly.io') creates a clear niche with distinct triggers and minimal conflict risk with other skills. It matches the anchor-5 example's level of specificity.

5 / 5

Total

14

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

getlarge/claude-api-care-plugins

Path

.claude/skills/baume-deploy/SKILL.md

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.