CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

frontend-slides

Cria apresentacoes web com slides navegaveis. Trigger em: "criar uma apresentação", "gera os slides", "deck de apresentação", "slides em HTML", "apresentação para pitch", "slide deck", "converte esse PPTX", "apresentação estilo Keynote", "deck single-file", "slides fixos 16:9", "apresentação sem usar PowerPoint", "exportar essa apresentação em PDF".

Quality

80%

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/77-frontend-slides/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-organized, token-efficient skill body with a genuinely useful preset catalog, concrete script invocations, and an explicit preview-then-build workflow with validation gates. Its main gaps are the missing engine/viewport-base.css file that the non-negotiable core rule depends on, no executable example of the stage mechanism, and several referenced governance files (GLOBAL.md, policies/*) that are not present in the bundle.

Suggestions

Ship engine/viewport-base.css in the bundle (or inline its ~essential content in the body) so the instruction "copiado por inteiro, nunca editado" is actually executable — right now the skill's single non-negotiable rule points to a file Claude cannot find.

Add one minimal executable HTML snippet showing the .deck-stage structure, the .active/.visible slide toggling, and the transform: scale(...) fit logic, so the fixed-stage mechanism doesn't have to be reconstructed from prose.

Add a short error-recovery note for the export/deploy steps (e.g., what to check when the Playwright capture or Vercel deploy fails) to close the workflow's missing feedback loop.

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — the "calc(-1 * clamp(...))" CSS gotcha and the fixed-stage letterbox rule are non-obvious, skill-specific knowledge with no padding about basics. Minor trimmable sections (design rationale in "Movimento", the provenance paragraph with a time-sensitive date "2026-06-23" outside a deprecated section) keep it below a 5.

4 / 5

Actionability

Reference scripts are concretely invoked with arguments ("references/extract-pptx.py <input.pptx> <output_dir>", "references/export-pdf.sh <caminho.html> [saida.pdf]" with "--compact"), but the rule designated "não-negociável" — "engine/viewport-base.css (copiado por inteiro, nunca editado)" — points to a file absent from the bundle, and no executable stage HTML/CSS/JS example is given, leaving key details missing for the core mechanism.

3 / 5

Workflow Clarity

The sequence is clear: 3 single-slide previews with an explicit A/B/C slot table, a user-selection checkpoint before the full deck, an anti-AI-slop gate ("antes de entregar, confirmar..."), and a completion checklist in "Evidencia de Conclusao". It lacks an explicit error-recovery loop (e.g., what to do when Playwright export or Vercel deploy fails), so it does not reach 5.

4 / 5

Progressive Disclosure

Good structure with well-signaled, one-level-deep references that all exist in the bundle (style-presets.md at 346 lines correctly split out of the body, plus export-pdf.sh, deploy.sh, extract-pptx.py). However, engine/viewport-base.css, GLOBAL.md, and policies/*.md are referenced in the body but not shipped, leaving broken navigation paths.

4 / 5

Total

15

/

20

Passed

Description

86%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 pairs a concise, concrete capability statement with an unusually rich and natural trigger list that clearly delimits the skill's niche. Its only weakness is that the what-clause undersells the full capability set (PPTX conversion, PDF export, Vercel deploy), which appears only as triggers. Third-person voice is used correctly throughout.

DimensionReasoningScore

Specificity

"Cria apresentacoes web com slides navegaveis" names the domain with one concrete action; PPTX conversion and PDF export appear only inside trigger phrases ("converte esse PPTX", "exportar essa apresentação em PDF") rather than as stated capabilities, so coverage is not comprehensive.

3 / 5

Completeness

A clear third-person "what" ("Cria apresentacoes web com slides navegaveis") is paired with an explicit "Trigger em:" clause listing concrete trigger phrases, answering both what and when explicitly.

5 / 5

Trigger Term Quality

Twelve natural trigger phrases with synonym and extension coverage — "criar uma apresentação", "gera os slides", "slide deck", "deck single-file", "converte esse PPTX", "apresentação sem usar PowerPoint", "exportar essa apresentação em PDF" — are exactly what a user would say when needing this skill.

5 / 5

Distinctiveness Conflict Risk

Distinct HTML slide-deck niche with differentiating triggers ("slides em HTML", "deck single-file", "apresentação sem usar PowerPoint"); only minor overlap risk with native-PPTX skills via "converte esse PPTX" and "apresentação para pitch".

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

16

Passed

Repository

felvieira/claude-skills-fv

Path

skills/77-frontend-slides/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.