CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

app-reference-architecture

Define arquitetura de referencia para aplicacoes completas. Trigger em: "novo app", "app do zero", "greenfield mobile", "Next.js + Tauri", "APK do zero", "arquitetura de referencia", "auth dual web e app", "gerar APK a partir do Next.js", "template de SaaS", "monetizar app mobile", "Google Play IAP", "assinatura Stripe e Play Store", "mesma estrutura dos outros apps", "boilerplate de app", "starter kit mobile+web".

Quality

83%

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, decision-dense architecture skill with an exemplary workflow: sequenced responsibilities, a real validation checkpoint with error-recovery guidance for its riskiest operation, and a completion checklist. The main gaps are the repetition of its framing principle and its total dependence on an external guide file that is not bundled with the skill.

Suggestions

Bundle the detailed guide (or at least its highest-value sections: the build-tauri swap/restore script and the payment schema) as a references/ file inside the skill so the 'Ver secao X' pointers resolve without depending on the repo's docs/skill-guides/ layout.

State the 'decide a arquitetura, nao implementa' rule once in the intro and cut its repetition in Responsabilidade 7 and the Handoff section.

Inline one minimal copy-paste snippet for the riskiest piece (e.g. the Subscription status enum or the rename/finally restore skeleton) so the most failure-prone pattern is executable from SKILL.md alone.

DimensionReasoningScore

Conciseness

The body is decision-dense and assumes Claude's competence — Stripe, BullMQ, Tauri, RTDN are named with no concept explanations — but the 'esta skill decide a ARQUITETURA GERAL, as skills de dominio implementam' framing is repeated three times (Governanca Global, Responsabilidade 7, Handoff) and the ceremonial Governanca/Integracao com Pipeline sections could be tightened. Efficient with minor trimming opportunities — anchor 4, not the every-token-earns-its-place 5.

4 / 5

Actionability

Names exact artifacts ('next.config.tauri.mjs', 'Dockerfile.android', '.github/workflows/android-release.yml'), a concrete action ('r0adkll/upload-google-play@v1'), exact Subscription status enums, and a full decision table with defaults — highly actionable for an instruction-only skill. Not 5 because all copy-paste code is deferred to the external guide ('Ver secao... para o codigo de referencia'), so nothing in the SKILL.md itself is executable.

4 / 5

Workflow Clarity

Responsabilidades 1-7 form a clear sequence (classify app type → decide each piece → register decision and hand off), with an explicit checkpoint ('rodar o build Tauri de verdade... antes de considerar a feature pronta'), error-recovery feedback ('Se o build falhar, checar primeiro se o finally rodou na ultima execucao (arquivos ainda renomeados)'), and a completion checklist (Evidencia de Conclusao). This matches the anchor with explicit validation, feedback loops, and checklists.

5 / 5

Progressive Disclosure

References are well-signaled and one level deep with section-level pointers ('Ver secao 1. Auth em docs/skill-guides/app-reference-architecture.md', 'consultar... apenas quando necessario — este SKILL.md cobre o suficiente para decisoes e setup inicial'), and the decision table keeps the overview lean. Not 5 because the referenced guide and policy files (docs/skill-guides/, GLOBAL.md, policies/*) are not part of the skill bundle — no references/ directory exists — so the disclosure chain cannot be followed from the skill alone.

4 / 5

Total

17

/

20

Passed

Description

82%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 with exceptional trigger coverage and an explicit 'Trigger em:' clause for routing. Its main weaknesses are an abstract, under-scoped what-statement and a few overly broad triggers that would over-fire for web-only apps the skill itself excludes.

Suggestions

Expand the what-statement to enumerate the concrete scope, e.g. 'Define a arquitetura de referencia (auth dual web+APK, pagamento Stripe+Google Play IAP, push Web Push+FCM, build Tauri, Docker/CI-CD) para apps novos web+APK', so the description alone conveys what the skill covers.

Narrow broad triggers like 'novo app' and 'boilerplate de app' to web+APK-specific phrasings (e.g. 'app novo web + APK') to avoid firing for web-only apps the body explicitly excludes.

Add trigger terms for the capabilities named in the body but missing from the description (push notification, Dockerfile, CI/CD de APK) so those requests also route here.

DimensionReasoningScore

Specificity

The what-clause 'Define arquitetura de referencia para aplicacoes completas' is a single abstract action, but the trigger list names several concrete capabilities ('auth dual web e app', 'gerar APK a partir do Next.js', 'Google Play IAP', 'assinatura Stripe e Play Store'). Not 5 because push dual, Docker and CI/CD — major responsibilities in the body — are absent from the description; not 3 because well more than 1-2 concrete specifics are stated.

4 / 5

Completeness

'Trigger em: ...' explicitly answers when with concrete phrases, and 'Define arquitetura de referencia' answers what — but the what is one abstract sentence that under-describes the skill's actual scope (auth dual, pagamento dual, push dual, build Tauri, Docker, CI/CD per the body). The when fully matches the 5 anchor while the what sits at the 3-4 level, landing between anchors 4 and 5.

4 / 5

Trigger Term Quality

Fifteen trigger phrases with rich synonym coverage ('novo app', 'app do zero', 'greenfield mobile', 'boilerplate de app', 'starter kit mobile+web') plus natural feature requests ('monetizar app mobile', 'template de SaaS') in both Portuguese and English. This matches the comprehensive synonym-coverage anchor; no common variation of the request is obviously missing.

5 / 5

Distinctiveness Conflict Risk

Stack-specific triggers ('Next.js + Tauri', 'APK do zero', 'Google Play IAP') establish a clear niche, but broad triggers like 'novo app' and 'boilerplate de app' would also fire for web-only apps that the body explicitly excludes ('app que é só web... nao precisa'), and overlap with sibling skills (15-mobile-tauri, 03-backend-api). Mostly distinct with minor overlap risk — anchor 4, not the minimal-conflict 5.

4 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 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

referenced_paths_exist

Referenced path issues: 1 missing

Warning

Total

13

/

16

Passed

Repository

felvieira/claude-skills-fv

Path

skills/60-app-reference-architecture/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.