CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

saas-conversion-playbook

Audita e melhora a conversao do funil SaaS. Trigger em: "auditoria de conversão", "auditar meu SaaS", "onde colocar o paywall", "desenhar onboarding", "trial to paid", "freemium ou trial", "reverse trial", "hard paywall", "evento de ativação", "aha moment", "gatilho de upgrade", "funil de assinatura", "R por mil usuários", "modelo de monetização SaaS", "quiz de onboarding", "paywall genérico", "downsell", "cancel-save", "paywall que converte", "paywall multi-página", "fluxo de paywall", "timeline do trial", "win-back", "fricção positiva", "quando mostrar o paywall", "teste de paywall".

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exceptionally well-governed instruction skill: the mandatory flow embeds a validate-and-correct checkpoint, rules are stated as testable prohibitions with concrete counter-examples, and detail is correctly deferred to five real, one-level-deep reference files. The two weaknesses are the dangling governance references (GLOBAL.md and three policies/*.md files absent from the bundle) and mild token cost from provenance dates and four partially overlapping boundary-routing sections.

Suggestions

Ship the four governance files referenced in Governança Global (GLOBAL.md, policies/source-driven.md, policies/handoffs.md, policies/evals.md) into the bundle, or inline their operative rules — as written, the skill's first section points to files the executor cannot open.

Compress the ~15-line Fontes section to 2–3 lines (drop access dates and the note about the duplicate saas-conversion-audit skill) and merge Integração com Pipeline into Handoff, since both restate the same 01→73→63→21 routing.

DimensionReasoningScore

Conciseness

The body is information-dense with no filler — every section (Fluxo Obrigatório, Regras de Diagnóstico, Anti-Padrões, Evidência de Conclusão) carries operational rules, and behavioral models are referenced with only parenthetical anchors rather than explained. It sits at anchor 4 ('efficient; minor instances that could be trimmed') rather than 5 because the ~15-line Fontes section carries provenance dates ('consultada em 2026-10-19', '2026-09-27') with no operational value, and boundary routing is repeated across four sections (Fronteira, Quando Não Usar, Handoff, Integração com Pipeline).

4 / 5

Actionability

For an instruction-only skill the guidance is fully actionable: a 9-step flow with hard parameters (max 5 intake questions, 14 paywall blocks, híbrido = '2 empréstimos, nunca metade'), concrete formatting rules ('Downsell … é estender o trial (ex: 7→14 dias), não "50% OFF eterno"'), a named decision rule ('o aha é um plano revelado (A) ou um artefato criado (B)?'), and the R/1K formula components. This matches anchor 5's 'specific examples cover the common cases' via report-schema.md and copy-bank.md; per the rubric's instruction-skill note, absence of code is not penalized when guidance is this concrete.

5 / 5

Workflow Clarity

The 9-step Fluxo Obrigatório is explicitly sequenced with a built-in validation checkpoint and feedback loop — step 8: 'todo número fora dessas faixas ou sem rótulo HIPOTESE volta pra correção antes do relatório sair' — plus error-recovery fallbacks (step 2: 'nunca bloquear o relatório: assumir e marcar HIPOTESE') and a completion checklist (Evidência de Conclusão). This matches anchor 5 ('explicit validation steps; feedback loops for error recovery; checklists').

5 / 5

Progressive Disclosure

Structure is good: an overview-length body with a Recursos section annotating each of the five bundle files, references exactly one level deep (verified: the reference files point only to siblings, not to further-nested content), and all five referenced bundle files exist. It falls below anchor 5 because Governança Global cites four files — 'GLOBAL.md', 'policies/source-driven.md', 'policies/handoffs.md', 'policies/evals.md' — that are not present in the bundle, leaving broken navigation in the very first section; this is more than a trivial gap but the overall split and signaling remain strong, matching anchor 4 ('minor organization gaps').

4 / 5

Total

18

/

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.

A strong description: the niche is unmistakable and the explicit 26-phrase trigger list is exactly what enables reliable routing, with the when-clause fully explicit. The main weakness is the thin what-clause — two generic verbs (audits, improves) — which undersells the concrete deliverables (playbook classification, paywall design, lifecycle sequences, 4-week backlog) documented in the body.

Suggestions

Expand the opening what-clause from two verbs to the concrete deliverables, e.g. 'Audita e melhora a conversao do funil SaaS: classifica o playbook (A/B/híbrido), desenha onboarding e paywall, define evento de ativação e lifecycle de e-mail, e entrega backlog de 4 semanas.'

Disambiguate the paywall triggers from neighboring checkout-UI skills by adding a scope qualifier such as 'estratégia de paywall (momento, copy, estrutura) — não a implementação de checkout', so 'fluxo de paywall' style triggers don't route to a UI-implementation skill.

DimensionReasoningScore

Specificity

The what-clause is a single sentence — "Audita e melhora a conversao do funil SaaS" — naming a specific domain with exactly two concrete actions (audit, improve); the remaining 26 phrases are trigger terms, not capabilities, so coverage of what the skill does is not comprehensive. This matches the anchor 'Names domain and 1-2 concrete actions, but not comprehensive' and falls below anchor 4 ('lists several specific actions') because no further actions are explicitly stated.

3 / 5

Completeness

It explicitly answers both questions: what ("Audita e melhora a conversao do funil SaaS") and when ("Trigger em: 'auditoria de conversão', 'auditar meu SaaS', 'onde colocar o paywall'…") with concrete trigger phrases, directly matching the anchor-5 example pattern. It is above anchor 4 because the when-clause is not merely present but enumerates 26 explicit trigger phrases.

5 / 5

Trigger Term Quality

The trigger list is comprehensive and natural — "onde colocar o paywall", "trial to paid", "freemium ou trial", "quando mostrar o paywall", "teste de paywall" — covering synonyms and phrasings a user would actually say, including both PT-BR and English terms. It clearly matches anchor 5's 'comprehensive coverage of natural terms including synonyms'.

5 / 5

Distinctiveness Conflict Risk

The niche is clear (SaaS subscription funnel conversion) and most triggers are distinctive, matching 'mostly distinct; minor overlap risk'. It is not anchor 5 because several triggers — "hard paywall", "paywall multi-página", "fluxo de paywall", "teste de paywall" — overlap with closely related paywall/checkout skills in the same kit (the body itself acknowledges 63-mobile-paywall-checkout as a neighbor), so minor conflict risk remains.

4 / 5

Total

17

/

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

allowed_tools_field

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

Warning

Total

15

/

16

Passed

Repository

felvieira/claude-skills-fv

Path

skills/73-saas-conversion-playbook/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.