CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

deployment

Processos gerais de deploy, validação, backup e boas práticas para deploy em produção

Quality

68%

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 ./skills/infrastructure/deployment/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

73%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.

The body is a solid operational runbook: real commands, clearly sequenced deploy/rollback workflows, explicit validation checkpoints, and phase-based checklists that satisfy the destructive-operation validation requirement. Its weaknesses are redundancy (duplicated date line, checklist restating principles, a descriptive rather than instructive CI/CD section) and inlined platform-specific content that would be better split into reference files.

Suggestions

Remove the duplicated "Última Atualização" line and the verbatim restatement of the description under the title; consolidate the Deploy Checklist with Princípios Core to eliminate overlap.

Split the per-platform guides (Hostinger, Render, Vercel) into separate reference files and keep a brief overview with clearly signaled links, matching the existing Referências pattern.

Turn the CI/CD section from a description of the pipeline into actionable steps (e.g., what to verify after an automatic deploy, what to do when it fails).

DimensionReasoningScore

Conciseness

The body is mostly operational (commands, checklists, sequences) but includes padding: the frontmatter description repeated verbatim under the title, the "Última Atualização: 2026-01-23" date duplicated at top and bottom (time-sensitive info penalized per guidelines), the Deploy Checklist substantially restating the Princípios Core, and a CI/CD section that merely describes what happens rather than instructs. Anchor 3 (mostly efficient but could be tightened) fits; not 4 given this avoidable redundancy.

3 / 5

Actionability

Concrete, real commands throughout — pg_dump backup, `make up-prod`, `docker compose -f docker-compose.prod.yml up -d --build`, `ssh root@<server-ip>`, `curl http://<server>/health`, rollback git/psql commands — with minor gaps: parameterized placeholders (<db-container>, <user>, <server-ip>) are not copy-paste ready and the flexibility is not explicitly justified, so anchor 4 rather than 5.

4 / 5

Workflow Clarity

The skill provides explicit pre-deploy validation (6 numbered checks), mandatory backups before destructive changes (migrations, dependency upgrades), post-deploy verification (health checks, logs, service status), a rollback workflow ending in re-validation, troubleshooting sections for error recovery, and three phase-based checklists — matching anchor 5 (clear sequences, explicit validation, feedback loops, checklists).

5 / 5

Progressive Disclosure

No bundle files exist, so scoring rests on body structure: sections are well-organized and the Referências section clearly signals one-level-deep pointers to sibling skills (docker-execution, makefile, docker-compose, commit-workflow). Anchor 4 (good structure, references mostly clear, minor gaps) rather than 5 because per-platform guides (Hostinger/Render/Vercel) are inlined where separate reference files would keep the overview leaner.

4 / 5

Total

16

/

20

Passed

Description

50%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 communicates the skill's domain and a few of its actions but stays at a generic level: no explicit "when to use" guidance, no natural trigger variations, and broad scope that risks overlapping with more specialized deployment skills. Adding a "Use when..." clause with concrete triggers (deploy em produção, CI/CD, rollback, Hostinger/Render/Vercel) would raise it substantially.

Suggestions

Append an explicit trigger clause, e.g. "Use quando fizer deploy em produção, configurar CI/CD, ou antes de migrations/mudanças críticas em servidores (Hostinger, Render, Vercel)".

Replace generic qualifiers ("processos gerais", "boas práticas") with the concrete capabilities the body already covers: health checks pós-deploy, rollback, backup via pg_dump, configuração de Nginx/SSL.

Include natural keyword variations users would say (CI/CD, staging, rollback, servidor, Docker) to improve trigger matching and distinctiveness.

DimensionReasoningScore

Specificity

The description names the domain and a couple of actions ("deploy, validação, backup") but wraps them in generic qualifiers like "Processos gerais" and "boas práticas" — matching anchor 3 (domain + 1-2 concrete actions, not comprehensive) rather than anchor 4, which requires several specific actions.

3 / 5

Completeness

The "what" is reasonably clear (deploy processes, validation, backup for production), but there is no "Use when..." clause or equivalent explicit trigger guidance in the description — the judging guidelines explicitly cap completeness at 3 in that case.

3 / 5

Trigger Term Quality

It includes natural terms users would say ("deploy", "backup", "validação", "produção") but misses common variations and synonyms the body itself uses (CI/CD, staging, rollback, servidor, Docker). Anchor 3 (some relevant keywords, missing variations) fits better than anchor 4.

3 / 5

Distinctiveness Conflict Risk

"Processos gerais de deploy" is a distinct domain but its breadth (covering Docker, CI/CD, SSH, Hostinger, Render, Vercel per the body) creates overlap risk with platform- and tool-specific skills — anchor 3 (somewhat specific but could still overlap).

3 / 5

Total

12

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

fernandezbaptiste/cursor-multiagent-system

Path

skills/infrastructure/deployment/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.