CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

frontend-integration

Implementa interfaces e integra o frontend com APIs e estados. Trigger em: "React", "Next.js", "componente", "página", "Zustand", "React Query", "TanStack Query", "skeleton", "loading", "hook", "frontend", "integração", "mobile responsive", "Tailwind", "formulário", "roteamento", "HTML", "CSS", "JavaScript no navegador", "API do browser".

Quality

82%

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

71%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 highly actionable, code-rich skill body with executable React Query, axios and skeleton implementations plus a valuable forced-error checkpoint for optimistic updates. Its weaknesses are length and inconsistent progressive disclosure: full implementations are inlined even though a docs guide is repeatedly cited as the home for complete examples, and meta sections add tokens without guiding execution.

Suggestions

Pick one home for complete code: either keep the full useApi.ts/api-client.ts/UsersPage listings in SKILL.md and stop citing docs/skill-guides/frontend-integration.md for 'exemplos completos', or move them to that guide and retain only the key excerpts (query-key factory shape, optimistic onMutate/onError rollback) inline — this would fix both conciseness and progressive disclosure.

Trim meta-content that does not guide execution, such as the 'Fontes' gap-measurement justification (e.g. 'grep por localStorage|sessionStorage… não retornava nada') and the 'Gap de baixa prioridade' note in the brownies section; keep only the library facts needed to use them.

Extend the validation pattern beyond optimistic mutations: add brief verify steps for the auth refresh flow (e.g. confirm queue drains and no redirect loop) and for Playwright visual checks (what to capture and what constitutes a pass), mirroring the existing forced-error checkpoint.

DimensionReasoningScore

Conciseness

Prose is mostly dense and directive with no basic-concept padding, but the ~630-line body inlines complete implementations (useApi.ts, api-client.ts, the full UsersPage) while repeatedly saying "Para exemplos completos… consultar `docs/skill-guides/frontend-integration.md`", and carries meta sections ("Fontes" gap-justification, "Integração com Pipeline") that could be trimmed. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the 'several padded sections' of 2, since nearly all code is project-specific rather than concepts Claude already knows.

3 / 5

Actionability

The guidance is fully executable and copy-paste ready: complete query-key factory, usePaginatedQuery/useApiMutation with optimistic-update rollback, an axios client with 401 refresh-queue interceptor, Skeleton/withSkeleton components, a Providers setup, a full users page example, and concrete commands like `npx shadcn@latest add @extend/pdf-viewer`. Specific examples cover the common cases, matching the top anchor.

5 / 5

Workflow Clarity

A clear staged flow exists (Entradas Esperadas → Responsabilidades → implementation patterns → Evidencia de Conclusao → Handoff para QA) with one strong explicit checkpoint ("forçar o backend a retornar erro… e confirmar que a UI reverte pro estado anterior") that even includes error-recovery diagnosis. It is not 5 because validation checkpoints are limited to the optimistic-mutation case; other fragile steps (e.g. auth/refresh, Playwright visual validation) lack equivalent verify loops.

4 / 5

Progressive Disclosure

Section headers are clear and external references are explicitly signaled and one level deep ("consultar `docs/skill-guides/frontend-integration.md`", `policies/*.md`, `docs/skill-guides/ui-component-mcps.md"), but content that the referenced guide should hold — complete store, auth and API-client examples — is also inlined in the body, making the split inconsistent. This matches 'some structure… content that should be separate is inline'; it is not 4 because the inline/external boundary is duplicated rather than cleanly divided.

3 / 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.

A strong description with an explicit what, third-person voice, and an unusually comprehensive bilingual trigger list including synonyms. The main weakness is that the capability statement is thin — two broad actions rather than an enumerated set of concrete capabilities — and a few overly generic trigger terms create mild overlap risk with design-oriented skills.

DimensionReasoningScore

Specificity

The description names the domain and two actions ("Implementa interfaces e integra o frontend com APIs e estados") but does not list several specific concrete actions, matching the anchor for 1-2 concrete actions without comprehensive coverage. It is not 4 because no enumerated set of specific capabilities is given, and not 2 because the actions are concrete rather than minimal or generic.

3 / 5

Completeness

It explicitly answers both what ("Implementa interfaces e integra o frontend com APIs e estados") and when ("Trigger em: 'React', 'Next.js', 'componente', 'página'…") with concrete trigger phrases, matching the anchor for a clear and explicit what AND when. Anchor 4's weakness ('when' could be more explicit) does not apply since the trigger guidance is fully explicit.

5 / 5

Trigger Term Quality

The trigger list covers ~20 natural terms users would say, including synonyms ("React Query" and "TanStack Query"), stack names ("React", "Next.js", "Zustand", "Tailwind"), and UX vocabulary ("skeleton", "loading", "mobile responsive", "formulário", "roteamento"). Coverage is comprehensive with synonyms, so it fits the top anchor rather than the 'a few natural terms missing' anchor at 4.

5 / 5

Distinctiveness Conflict Risk

Core triggers ("React", "Next.js", "Zustand", "React Query") carve a clear implementation niche with mostly minor overlap risk against closely related design/UI skills. It is not 5 because generic terms like "HTML", "CSS", "página", "componente" and "loading" could also fire for a sibling UI/design skill (e.g. the referenced 92-design-director).

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

skill_md_line_count

SKILL.md is long (640 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository

felvieira/claude-skills-fv

Path

skills/04-frontend-integration/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.