CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

mobile-paywall-checkout

Skill de UI/UX de paywall e checkout de pagamento em apps mobile — seleção de plano, periodicidade, cupão, Google Play Billing, Google Pay e PSPs externos (Stripe, Mercado Pago). Cobre a decisão de arquitetura de cobrança (quando é obrigatório Play Billing vs. PSP externo), o fluxo periodicidade→ plano→cupão→pagamento→autenticação→confirmação, hierarquia de plano-alvo sem manipulação, estados de pagamento (processing/3DS/pending/succeeded/failed) e posição do campo de cupão. Complementa a skill 60 (backend/dados multi-provider) com o lado de interface e decisão de produto. Trigger em: "paywall", "tela de assinatura", "checkout de assinatura", "seleção de plano", "plan card", "checkout de pagamento mobile", "google play billing", "in-app purchase", "iap", "purchase sheet", "campo de cupão", "3ds", "3d secure", "payment sheet", "google pay no checkout", "mercado pago mobile", "preço anual vs mensal", "billing period selector", "plano recomendado", "fluxo de assinatura android", "tela de preços do app".

72

Quality

91%

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

SKILL.md
Quality
Evals
Security

Quality

Content

81%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-structured instruction-only skill: specific, opinionated guidance with explicit validation checkpoints and a clean overview-plus-detail-docs layout. Main weaknesses are modest redundancy across the four boundary/handoff sections and reliance on external docs for the concrete artifacts.

Suggestions

Consolidate 'Governanca Global', 'Handoff', and 'Integração com Pipeline' into a single boundary/handoff section — the same neighbor skills (02, 60, 06) are described three times with overlapping content.

Include minimal inline versions of the highest-value deferred artifacts (e.g., the payment-state machine with one-line microcopy per state, or the funnel event names) so the skill is actionable without opening external docs.

Ship the seven detail docs inside the skill's own bundle (e.g., references/01-billing-decision.md …) and point the section links there, making the progressive-disclosure structure self-contained and verifiable.

DimensionReasoningScore

Conciseness

The body is dense and domain-specific ('Touch target mínimo 48×48dp', exact price-format strings, the state machine) with no generic padding, but neighbor-skill boundaries are restated across 'Governanca Global', 'Quando Não Usar', 'Handoff', and 'Integração com Pipeline', which could be consolidated. Efficient with minor trimmable redundancy — anchor 4, not the lean anchor 5.

4 / 5

Actionability

Concrete, specific guidance throughout — the four-entity table, the billing-decision matrix naming SDKs and the Checkout Bricks WebView caveat, exact microcopy formats, and precise rules like 'campo de cupão recolhido atrás de um link'. Falls short of anchor 5 only because key artifacts (wireframes, QA matrix, event dictionary) are pointed to rather than given even minimally inline.

4 / 5

Workflow Clarity

Clear sequence (billing decision → periodicidade→plano→cupão→pagamento→autenticação→confirmação → states → QA) with an explicit 'Checkpoint:' handling timeout via Reconciling-with-backoff, error recovery that preserves validated work, a payment-state taxonomy, and an 'Evidência de Conclusão' checklist — matching the anchor with explicit validation, feedback loops, and checklists.

5 / 5

Progressive Disclosure

Each section ends with a well-signaled, numbered, one-level-deep pointer to its detail file (01-billing-decision.md … 07-qa-and-timeline.md) and the body stays an overview — textbook structure. However, those detail files live outside the skill's own bundle (no references/ directory ships with the skill), so the split cannot be verified from the package itself — anchor 4.

4 / 5

Total

17

/

20

Passed

Description

100%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 model description: concrete capabilities, explicit third-person trigger guidance with natural terms and synonyms in two languages, and a clearly delimited niche that distinguishes it from the backend (skill 60) and marketing price page (skill 02) neighbors. No vague fluff or over-claims.

DimensionReasoningScore

Specificity

Names multiple concrete capabilities — 'seleção de plano, periodicidade, cupão, Google Play Billing, Google Play e PSPs externos (Stripe, Mercado Pago)', the billing-architecture decision, payment states '(processing/3DS/pending/succeeded/failed)', and coupon field positioning — with no meaningful coverage gaps, matching the comprehensive-anchor example.

5 / 5

Completeness

Explicitly answers both 'what' (full capability list for mobile paywall/checkout UI) and 'when' (dedicated 'Trigger em:' clause with concrete trigger phrases), written in third person; this matches the top anchor exactly.

5 / 5

Trigger Term Quality

The 'Trigger em:' list covers natural user phrasing comprehensively, including abbreviations and synonyms in both English and Portuguese: 'paywall', 'in-app purchase', 'iap', 'purchase sheet', 'payment sheet', '3ds', '3d secure', 'campo de cupão', 'billing period selector', 'mercado pago mobile'.

5 / 5

Distinctiveness Conflict Risk

Clear niche — in-app mobile paywall with real transactions — and it explicitly delimits neighbors ('Complementa a skill 60 (backend/dados multi-provider) com o lado de interface e decisão de produto'); trigger terms are domain-specific with minimal overlap risk.

5 / 5

Total

20

/

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

metadata_version

'metadata.version' is missing

Warning

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

14

/

16

Passed

Repository

felvieira/claude-skills-fv

Path

skills/63-mobile-paywall-checkout/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.